Privacy Policy

TastyForks Mobile privacy policy: recipe content, offline cache, advertising, consent, diagnostics, privacy choices and contact requests.

Effective date: September 29, 2026
Last updated: September 29, 2026

TastyForks is a recipe application operated under the developer or publisher name shown on its App Store or Google Play listing. This policy explains how the TastyForks mobile application handles information. It also covers the TastyForks website when the application opens a recipe, comment form, contact form or other page on that website.

For privacy questions or requests, use the TastyForks contact form and include “Privacy Request” in the subject.

Information handled by the application

The application does not require an account and does not directly ask for a name, email address, postal address, payment information or precise location.

The application retrieves public recipes, categories, images and public comments from the TastyForks WordPress API. Standard network information, including the IP address, request time, user agent and basic device or network information, may be received by the website host, content-delivery services and image hosts when they deliver this content.

Local storage and offline use

TastyForks keeps a limited, size-controlled cache of normalized public recipe data on the device to improve loading time and provide a fallback when the network is temporarily unavailable. Cached entries are automatically discarded after no more than 30 days and may also be removed earlier as the cache fills. The cache does not contain account credentials, comment drafts, names or email addresses.

Users can remove the local cache by clearing the application’s data or uninstalling the application. Recipe images are loaded from remote servers and may not remain available offline.

Comments and contact forms

The current production application displays public comments but does not submit comments directly from the application. When comments are open, it sends the user to the corresponding page on the TastyForks website.

If a user submits a comment or contact form on the website, TastyForks may process the information entered in that form, such as name, email address, subject and message or comment, together with standard anti-spam and security information such as IP address and browser user agent. Email addresses submitted for comments are not displayed publicly. Comments may be moderated before publication.

Advertising, consent and tracking

The native application includes Google Mobile Ads (AdMob) to display advertising. Before requesting an advertisement, it uses Google’s User Messaging Platform (UMP) to determine whether a consent message is required and whether advertisements may be requested. Where required, users can reopen Google’s consent form through Privacy choices on the Home screen.

Depending on the user’s region, consent choices, device settings and Google’s configuration, Google and its advertising partners may process:

  • coarse location inferred from the IP address;
  • device and application identifiers;
  • product and advertisement interactions;
  • advertising data;
  • crash data;
  • performance data; and
  • other diagnostic data.

These data may be used to provide app functionality, select and deliver advertisements, measure advertising, perform analytics, prevent fraud and improve reliability. Google may associate coarse location, device identifiers, product interactions and advertising data with a device or other identifiers. The Apple privacy disclosure identifies the device identifier as data that may be used for tracking by the third-party advertising service. Crash, performance and other diagnostic data are declared as not linked to the user’s identity.

The availability and use of advertising identifiers depend on the operating system, privacy settings, regional requirements and the user’s consent choices. TastyForks does not require an account and does not use advertising data to identify a user by name.

Development, internal preview and TestFlight builds use Google’s test advertisements. Public production builds may use TastyForks production advertising units. More information is available in Google’s privacy policy and Google’s advertising controls.

Notifications

Remote push notifications are not active in the current public release. If recipe alerts are enabled in a future version, the application will request notification permission only after a user action. If permission is granted, the application may send an Expo push token and the device platform to the TastyForks notification service so that alerts can be delivered. Users can disable notifications at any time in their device settings.

Purposes and legal bases

TastyForks processes information only as needed to:

  • deliver recipes and application features;
  • keep the service secure and diagnose failures;
  • remember limited public content on the device for performance and offline fallback;
  • respond to contact or privacy requests; and
  • display and measure advertising where permitted.

Where applicable law requires consent for advertising storage, access or tracking, TastyForks and Google rely on the choices collected through the consent interface. Other limited technical processing is performed to provide the service, protect it and pursue legitimate interests in reliability, security and measurement, subject to applicable law.

Service providers and international processing

The application uses the TastyForks WordPress service, remote image or content hosts, Google Mobile Ads, Google’s User Messaging Platform and the platform services supplied by Apple, Google and Expo. These providers process information under their own terms and privacy policies and may process information in countries other than the user’s country. Where required, they are responsible for using appropriate safeguards for international transfers.

Retention

Public recipe data stored locally is retained for no more than 30 days unless removed earlier. Information submitted through the website, such as comments or contact requests, is kept only as long as reasonably necessary for moderation, response, security, record-keeping and legal obligations. Advertising and diagnostic information is retained by Google and other providers according to their policies and the user’s settings.

Privacy choices and rights

Depending on location, users may have rights to request access, correction, deletion, restriction or portability of personal information, or to object to certain processing. Users may also withdraw consent where processing is based on consent.

To make a request, use the TastyForks contact form with the subject “Privacy Request.” TastyForks may need to verify the request before acting on it. Users can also manage advertising choices through Privacy choices in the application where available, through their device privacy settings and through Google’s advertising controls.

Children

TastyForks is a general-audience recipe application and is not designed or directed specifically to children. The 4+ App Store content rating describes the nature of the content and does not mean that the service is intended for children. A parent or guardian should supervise a child’s use of the application and any interaction with advertising or external websites.

Security

TastyForks uses reasonable technical and organizational measures designed to protect information. No method of transmission or storage is completely secure, and absolute security cannot be guaranteed.

Changes to this policy

This policy may be updated when application features, service providers or legal requirements change. The effective date at the top of this page identifies the current version. Material changes will be reflected on this page before or when they take effect.

Contact

For privacy questions or requests, use the TastyForks contact form and enter “Privacy Request” as the subject.

Website privacy and advertising

When you visit tasty-forks.com, the web server and security tools may process technical information such as your IP address, browser type, requested page, and request time. This information is used to deliver the website, prevent abuse, and diagnose technical problems.

The website may use Google services, including Site Kit, Analytics, and AdSense. Depending on your location and consent choices, Google and its partners may use cookies or similar technologies to measure traffic, prevent fraud, and deliver or measure advertising. You can review how Google uses information from sites that use its services at Google’s partner-sites policy.

Information submitted through the contact form is used to respond to the request and protect the form from spam. For a privacy request, use the contact form and write “Privacy Request” in the subject.