Daily Bite Privacy Policy

Effective date: October 11, 2026

1. Who We Are

Daily Bite ("Daily Bite," "we," "us," or "our") is a recipe app for iPhone (App Store) and Android (Google Play), operated by Successfitness, a sole proprietorship based in Saskatchewan, Canada (brand: Success Recipes / Success Fitness). We are the data controller responsible for your information.

You can reach us about privacy at any time: [email protected]

This policy explains exactly what we collect, why, who processes it on our behalf, how long we keep it, and how you can access or delete it. We do not sell your personal information for money, and Daily Bite shows no ads inside the app. Starting with version 1.0.4 of the iPhone app, we use Meta (the company behind Facebook and Instagram) to measure our own ads for Daily Bite. Your iPhone asks before the app can use your advertising identifier for this, and saying no changes nothing in the app. The Android app does not include this. See "Ads measurement (Meta)" in Section 3, and Section 7. The app uses PostHog to understand which features people use and Sentry to report crashes and errors; see "App analytics" and "Crash reports" in Section 3. Starting with version 1.0.6, the iPhone app also uses Superwall to show and test most Daily Bite Pro screens, and PostHog records a replay of a small share of sessions with all text and your photos and images covered; see "Paywalls (Superwall)" and "Session replays" in Section 3. Our website, trydailybite.com, uses a cookieless website analytics service to count visits and button taps; see "Website analytics" in Section 3.

2. What Daily Bite Does

Daily Bite lets you create an account, browse a curated recipe library, save and organize recipes into cookbooks, plan meals and keep a grocery list, import a recipe from a link (pasted, shared from another app, or found in the in-app browser), a photo, or pasted recipe text, and subscribe to Daily Bite Pro for premium features such as nutrition estimates. We collect only what these features need.

3. Information We Collect

Account information

You can sign in with an email address and password, with Sign in with Apple (on iPhone), or with Google Sign-In (on iPhone and Android).

• Email address: when you sign up with email and password, when you use Google Sign-In, or when you use Sign in with Apple (including an Apple private-relay address ending in @privaterelay.appleid.com, which we treat as your real email and never block or alter).
• Password: only when you choose email and password sign-up. Your password is handled solely by Google Firebase Authentication. It is never written to our database and we cannot see it.
• Apple sign-in identifiers: when you use Sign in with Apple, we receive a stable Apple user identifier and an identity token, which we exchange for a secure login session. We also store an Apple refresh token on our server, only so we can ask Apple to revoke Daily Bite's access to your Apple ID when you delete your account.
• Google sign-in information: when you use Google Sign-In, Google confirms who you are and gives us your Google account's email address, name, and a Google identity token, which we exchange for a secure login session.
• First name: your first name (from Sign in with Apple's first authorization, from your Google account, or as you enter it), used to personalize the app.

Profile and onboarding answers (you provide these during setup; used to personalize recipes): your goals, how many recipes you save per week, how many recipes you actually cook, where you save recipes today, how often you order takeout, who you cook for, dietary preferences, your usual dinner time, allergies you enter, pantry items you list, how you heard about Daily Bite, and when you usually decide what's for dinner (which sets the time of your Daily Bite reminder). Your profile also records the choice you make at sign-up about receiving marketing emails from Daily Bite, and when you accepted the Terms of Service and Privacy Policy (with the versions that were in effect). Your marketing-email choice is stored so we can respect your choice; the app does not send it to our email service provider.

Recipes you pick during setup. Setup can show you recipes from our library to swipe through. The ones you mark "I'd cook this" are saved to your account when you create an account, sign in, or turn a guest account into a full one, so they appear in the app as Your picks. The recipes you pass on are not saved to your account.

Sample recipe. Setup can show you how saving a recipe works, using one of our own sample recipes. When you create an account or sign in, that sample recipe is added to your recipes, so it is there when you start. Which sample you get depends on where you told us you save recipes.

Setup log. While you go through setup, the app also sends a record of the setup screens you reach to an onboarding log in our Firebase database, so we can understand where people drop off in setup. Some entries carry the answer you picked, such as how many recipes you save or actually cook, how often you order takeout, who you cook for, your usual dinner time, how you heard about Daily Bite, where you save recipes, when you usually decide what's for dinner, whether you allowed notifications, the recipes you pick or pass on in setup, which version of setup you were shown, whether your App Store or Google Play account can still get the free trial, your marketing-email choice, and which sign-in method you chose. Each log also carries your platform (iPhone or Android), a random setup-session ID, and, once you sign in, your Daily Bite account ID. Your dietary preferences, allergies, and pantry items are not sent to this log.

We treat dietary preferences and allergies as sensitive lifestyle information. We use them only to filter and personalize recipe suggestions inside the app. Daily Bite does not provide allergy-safety, medical, or nutritional health guarantees, and you should not rely on it for medical decisions.

Recipes and cookbooks you create or import

• A link (URL) you paste, share into the app from another app, or import from the in-app browser to import a recipe. The link goes to our recipe-import service (a Google Cloud Function). For Instagram, TikTok, and Facebook posts, the service reads the post's public caption through ScrapeCreators and, when the recipe is not in the caption, the post's public images or the video's transcript. For other web pages, it fetches the public page through Firecrawl. That content is then sent to Google's Gemini AI to turn it into a recipe. If the post or page has a cover image, we try to copy that image into our Firebase file storage so your saved recipe keeps its picture. If that fails, the recipe keeps a link to the original image, which your phone loads from the source site (so that site receives your IP address, as it would for any image it serves). So your recipe can credit the person who made it, we also save the creator details the post or page already shows publicly: for Instagram, TikTok, and Facebook, the creator's handle, display name, and a copy of their profile photo; for other web pages, the site's name and the author's name when the page lists one. These are stored with your imported recipe. See Section 6 ("AI Recipe Import").
• A photo you take or choose to import. In Add a photo, you can tap Camera to take a picture or tap Image to pick one image with your phone's photo picker. The camera opens only when you tap Camera and allow camera access. The app shrinks that one image on your device and sends it to our recipe-import service and to Google's Gemini AI (vision) to read the recipe from it. The app then keeps that shrunken copy in its temporary storage on your phone as the recipe's picture. The photo is never uploaded to your account and does not sync, so it will not appear if you open the recipe on another device, and your phone may clear it to free up space. See Section 6 ("AI Recipe Import").
• Your own cover photos. If you choose your own cover photo for a recipe, from your photo library or your camera, we upload that photo and store it with the recipe in Google Firebase Storage, so the recipe shows it on every device you sign in to. A photo you pick in the recipe editor is uploaded only when you tap Save; if you leave without saving, it is never uploaded. We never show it to other users and never put it on a shared recipe page. Choosing another photo, or choosing "Use original photo" or "Remove photo", deletes it. If you delete the recipe, the photo is usually deleted a few seconds after the option to undo closes. If the app is offline or closes before then, or the recipe is deleted in an older version of the app, it is deleted when you delete your account. Deleting your account deletes all of them.
• Pages you open in the in-app browser. The import flow includes a browser that opens Google search and websites directly from your phone. Google and the sites you visit receive your searches and visits (including your IP address) under their own privacy policies. Daily Bite does not receive what you search for or browse; we receive a page only when you choose to import it.
• Recipe text you paste. When you paste recipe text to import it, that text is sent to our recipe-import service and to Google's Gemini AI to pull out the recipe.
• Feedback you send us. If you answer "How's Daily Bite going?" or use Send feedback in the app, we receive the reaction you pick and anything you type, with your account ID (or an anonymous ID if you are not signed in), app version and phone type. It is stored with our app analytics (PostHog) and read only by the Daily Bite team to improve the app. Please leave out personal details you don't want us to have. You can ask us to delete it at [email protected].
• The parsed recipe (title, description, ingredients, steps, nutrition, cook time, servings, picture, category, source) and the source URL, which we save to your account so you can return to them.
• Cookbooks you create (their names and timestamps) to organize your saved recipes.
• Your plans and cooking activity: your meal plan, your grocery list, the library recipes you save, the recipes you mark as cooked, the star ratings and private notes you add to recipes, your cooking streak, and recipes you ask us to suggest more or less of, which we use to tailor suggestions. Your ratings and notes are not shown to anyone else.

Subscription and purchase information. Daily Bite Pro is sold through Apple In-App Purchase on iPhone and Google Play Billing on Android, and your subscription status is managed by RevenueCat. We receive your subscription/entitlement status and basic device/transaction information. Starting with version 1.0.4 of the iPhone app, Meta's software in the app also records App Store purchases made in the app, and the app may give RevenueCat device identifiers and your tracking choice so RevenueCat can report subscription events to Meta for ads measurement; when that happens, and what a "no" means, is explained under "Ads measurement (Meta)" below. We never receive or store your credit-card or payment-card details; Apple or Google handles payment.

Information stored only on your device. We keep small convenience caches on your device (using local app storage) so the app loads quickly: a copy of your profile basics, the titles of your imported recipes, your cookbook names, and a snapshot of the curated recipe library. Starting with version 1.0.6, the iPhone app also keeps a copy of your paywall history (see "Paywalls (Superwall)" below) and whether you turned off the reminder for a free trial. Photos you import from your camera or photo library are also kept only in the app's temporary storage on your device, which your phone may clear. These stay on your device and are not separate transfers of your data. The profile cache is cleared when you sign out. The copy of your paywall history stays until you uninstall the app.

Limited technical/log data via our backend. Our backend provider, Google Firebase, processes standard technical information such as your IP address and device/user-agent for security and to deliver the service (for example, Firebase Authentication retains login IP addresses for a short period). Our server functions also write error logs that may include your Daily Bite account ID, but not your name or email address; these are kept for a limited period. We do not use this for advertising.

App updates. Each time the app launches, it checks Expo's servers (EAS Update, run by 650 Industries, Inc.) for an update to the app. That check sends Expo your IP address, your platform (iPhone or Android), the app's runtime version, and a random installation ID used for update delivery. If a previous update failed to start, it also sends a short technical error message. It does not include your name, email address, or Daily Bite account ID.

App analytics. The Daily Bite app uses PostHog, a product analytics service, to see which features people use and where they get stuck, so we can fix and improve the app. The app sends PostHog events about how you use it: the screens you view; when you create an account or sign in, and which sign-in method you used; when a recipe import starts, succeeds, or fails, labeled with the kind of source (Instagram, TikTok, another link, a photo, or pasted text), and, for a success, how long the import took and whether a video transcript filled in part of the recipe, or, for a failure, a short error code; when you save a recipe, and whether it came from our library or an import; when you search, with counts and fixed labels only (such as how many characters you typed, how many results came back, and the sort you chose), never the text you typed; which onboarding steps you finish, but not your answers, and how many recipes you picked during setup (the number only); when a Pro screen is shown or closed, and which Pro screen it was; when you see a special offer or start a trial (with the plan you picked); on iPhone, from version 1.0.6, when a Pro screen is requested, when you cancel a purchase on the App Store screen or switch to a yearly plan, which free tries of Pro features you used, whether Daily Bite Pro already on your App Store account moved to your Daily Bite account when you signed in, whether you turned the trial reminder on or off on a Pro screen, and, if your free trial starts while notifications are off, whether you turned them on when the app offered a reminder; on iPhone, your answer to the tracking question (allowed or not), and whether Meta's software was started at launch or waited for your answer, with the region set on your phone and its time zone; when you mark a recipe as cooked, rate it (the number of stars), or share it, never your note or the recipe itself; when you open the recipe editor and what kind of change you saved, with counts and yes-or-no answers only (such as how many steps you added or whether you changed the cover photo), never the text; which buttons you tap on the Daily Bite home screen, and whether the recipe was from our library or your own, never which recipe; when you open a reminder notification; a few feature taps such as starting Cook Mode; and, only if you choose to send us feedback in the app, the reaction you pick and the text you write (see "Feedback you send us" above). Each event also carries your platform (iPhone or Android), app version, screen size, and which version of setup you were shown (we sometimes test two versions of setup, and the app asks PostHog which one to show you). Starting with version 1.0.6 of the iPhone app, each event also carries which version of the Daily Bite Pro screen at the end of setup you were shown (we test two, chosen the same way). Before you sign in, events are tied to a random anonymous ID. After you sign in, they are linked to your Daily Bite account ID, a random identifier that is not your name or email address. PostHog never receives your recipe titles, links, ingredients, cookbook names, search text, or onboarding answers. The only text you type that reaches PostHog is feedback you choose to send us. PostHog also receives the IP address the events come from and may use it to estimate a rough location, such as your country, city, or approximate postal code. PostHog keeps some facts on its record of your account ID until we delete them. These include whether you have Daily Bite Pro, which version of setup you were shown, your device type, app version, and screen size, and the rough location (country, region, city, approximate postal code, approximate map coordinates, and time zone) it estimated from your IP address the first and last time it saw you. We do not use PostHog analytics for advertising, and PostHog data is not sent to Meta. This data is processed by PostHog in the United States (PostHog Cloud US).

Session replays. Starting with version 1.0.6 of the iPhone app, PostHog also records a replay of a small share of app sessions (about 1 in 10): a series of pictures of the screens you move through and where you tap, so we can see where people get stuck. Before anything leaves your phone, every piece of text, everything you type, and every photo or image of yours is covered with a solid block, so a replay never shows your recipes or their titles, ingredients, or steps, your name, your email address, or your photos. Replays do not include the app's logs or its network activity. Recording pauses while a Daily Bite Pro screen is open. Replays are linked to the same anonymous ID or account ID as the events above, are processed by PostHog in the United States, and are kept for 30 days. The Android app does not record replays.

Paywalls (Superwall). Starting with version 1.0.6 of the iPhone app, most Daily Bite Pro screens and offers in the app are shown by Superwall, our paywall tool. Each time you open or leave the app, and when it shows one of these screens, Superwall's software sends Superwall your Daily Bite account ID once you sign in (a random ID before that, which Superwall links to your account ID when you sign in), an identifier for the app on your device and Apple's ID for your App Store download of the app (which is the same on any device that uses your Apple Account), which screens you were shown and what you tapped on them, whether you subscribe, and Apple's records of the Daily Bite purchases made with your Apple Account (product, purchase and expiry dates, price, currency, App Store country, and transaction IDs). It also sends your device model, operating system, app version, language, region and currency settings, time zone, when you installed the app, and other technical details, such as text size, network type and display settings. To pick the right screen, the app also tells Superwall: whether you have Daily Bite Pro, whether you have had a free trial or a paid plan before, which plan you are on and roughly how many months you have paid for it, whether you can still get a free trial, whether notifications are on for the app, which of your free tries of Pro features (Cook Mode, unit conversion, and one import from a photo or screenshot) you have used, whether you are signed in, whether this is your first time using the app, and which Pro screens you have seen or closed before, how often, and when. Superwall estimates a rough location (country, region, and city) from your IP address. Superwall also uses the details it receives to estimate how likely you are to subscribe, and that estimate can be used to choose which screen or offer you see. We use this to choose which screen or offer to show you, to compare two versions of a screen, and to see which work best. Your purchase is still made through Apple and managed by RevenueCat, which also sends Superwall your subscription events, with your account ID, or with RevenueCat's random ID for you, for example if you bought before signing in. We also keep a record of the Pro screens you have seen and closed, and whether you have had a free trial or a paid plan before (your paywall history), with your account, or only on your phone until you sign in, and a record on our server of the free tries you have used, so offers are not shown too often and each free try works once. Other than whether notifications are on, Superwall never receives your answers from setup, and it never receives your name, email address, or recipes. We do not use Superwall data for advertising or send it to Meta. The Android app does not show Superwall screens; RevenueCat still sends Superwall the subscription events from Google Play purchases.

Trial reminder. Starting with version 1.0.6 of the iPhone app, some Daily Bite Pro screens let you choose whether to be reminded before your free trial ends. The reminder is a notification scheduled on your phone, not sent from our servers. If your trial starts while notifications are off, the app may ask whether you want to turn them on. What you choose is recorded in our app analytics, as described in "App analytics" above.

Crash reports. The app uses Sentry to report crashes and errors in the versions we publish on the App Store and Google Play (it is turned off in our development builds). A report includes what went wrong and where in the app it happened, technical details about the app's state at the time, and your device model, operating system, and app version. We filter out one kind of harmless network error that happens while the app is in the background, so real problems stand out. Crash reports may include your Daily Bite account ID, but not your name or email address. This data is processed by Sentry in the United States.

Ads measurement (Meta). We run ads for Daily Bite on Facebook and Instagram. Starting with version 1.0.4 of the iPhone app, the app includes software from Meta (the Facebook SDK) so we can see which of those ads lead to installs, free trials, and subscriptions, and so Meta can show our ads to people more likely to want the app. Daily Bite shows no ads inside the app. This applies to the iPhone app only: the Android app does not start Meta's software and does not collect the Android advertising ID.

The tracking question. After setup is finished, your iPhone asks once whether to allow Daily Bite to track you across other companies' apps and websites. The question reads: "Daily Bite uses this to see which of our Instagram and Facebook ads bring people to the app. Your recipes are never shared." Only if you tap Allow does the app receive your iPhone's advertising identifier (IDFA) and give it to Meta and RevenueCat. Nothing in Daily Bite changes either way. Every feature works the same.

What is sent at launch, on every iPhone. When the app launches, Meta's software contacts Meta's servers to fetch its own settings. That request carries our Meta app ID and, like any internet request, your IP address. It carries no identifier about you and no events. What happens after that depends on where your iPhone is set.

If your iPhone is set to a UK, EU, EEA or Swiss region, or to a European time zone. The app sends Meta no events and no identifiers unless you tap Allow. If you tap Allow, Meta's software starts and sends Meta a record that the app was installed and of each time it is opened, with an anonymous ID it creates for this install, your advertising identifier (IDFA), your IP address, and technical details about your device (such as model, operating system and app version, screen size, language, time zone, and mobile carrier), plus a record of each App Store purchase it detects in the app, such as a free trial starting or a subscription purchase, with the product, price, and currency. The app also gives RevenueCat that anonymous ID, your iPhone's identifier for our apps (IDFV), your advertising identifier, your IP address, and your tracking choice, and RevenueCat reports your subscription events to Meta from its servers: a free trial starting, a purchase, or a renewal, with the price, currency, those identifiers, and the ID RevenueCat holds for you (your Daily Bite account ID, or RevenueCat's random ID if you are not signed in), sent as is (or in a coded, hashed form if we later move RevenueCat to Meta's Conversions API). If you tap Ask App Not to Track, nothing about you is sent to Meta, including your subscription events.

Everywhere else, including the United States, Canada, and Australia. From the first time you open the app, Meta's software sends Meta a record that the app was installed, of each time it is opened, and of each App Store purchase it detects in the app, such as a free trial starting or a subscription purchase, with the product, price, and currency. These records carry an anonymous ID it creates for this install, your IP address, and the technical details about your device listed above, but not your advertising identifier, unless you tap Allow. The app also gives RevenueCat that anonymous ID, your iPhone's identifier for our apps (IDFV), your IP address, and your tracking choice. If you tap Allow, your advertising identifier (IDFA) is added to what Meta's software sends and to what the app gives RevenueCat, and RevenueCat reports your subscription events to Meta from its servers: a free trial starting, a purchase, or a renewal, with the price, currency, those identifiers, and the ID RevenueCat holds for you (your Daily Bite account ID, or RevenueCat's random ID if you are not signed in), sent as is (or in a coded, hashed form if we later move RevenueCat to Meta's Conversions API). Meta matches this with what it knows about ads you saw or tapped on Facebook or Instagram. RevenueCat forwards a subscription event to Meta only if you tapped Allow before that event happened. If you tap Ask App Not to Track, or have not yet been asked, iOS does not give the app your advertising identifier and RevenueCat sends Meta none of your subscription events. Meta still receives the install, app-open, and in-app purchase records above from Meta's software, which carry no advertising identifier. Apple may also send Meta a delayed install report that does not identify you or your device.

What is never sent to Meta: your name, email address, recipes, saved links, cookbooks, meal plans, grocery lists, onboarding answers, dietary preferences, or allergies.

Who receives it. Meta Platforms, Inc. receives this data and uses it for its own purposes, under its own terms and privacy policy, to provide measurement and to target, deliver, and improve ads. RevenueCat handles the identifiers and forwards subscription events as our service provider.

Your choices. You choose when your iPhone asks, and you can change your answer at any time in iPhone Settings > Privacy & Security > Tracking. To stop every app from asking, turn off Allow Apps to Request to Track on the same screen. Declining changes nothing in the app. You can also review the activity other apps send to Meta in your Facebook or Instagram settings.

Website waitlist and Android tester sign-up. If you join the waitlist or the Android tester list on trydailybite.com, we collect the email address you enter, the time you signed up, and which form on the site you used. We use your email to tell you when the app launches or when your tester install link is ready, and to send occasional recipes and updates, and you can unsubscribe at any time. The list is stored with Cloudflare (our website host). When you join the Android tester list, your tester invite email is sent automatically through Resend, and we add your email address to our Google Play tester list so you can install the test app. Launch news, recipes, and updates are sent through Flodesk, our email service provider. We do not sell the list. These sign-ups are not linked to a Daily Bite app account.

Website analytics. On trydailybite.com we use PostHog, a product analytics service, to see which pages are visited and which buttons are used, so we can improve the site. PostHog receives the page you view, when you leave a page, the site that referred you, your device type, browser and operating system, whether you opened the site inside another app's browser (for example Instagram or TikTok), and taps on the download buttons and FAQ questions. We run it in cookieless mode: it stores nothing in your browser (no cookies, no local storage), and it counts visitors with a one-way hash of your IP address, your browser and our site name that changes every day and cannot be turned back into any of those values. The IP address itself is discarded before anything is stored, so no location data is kept. Session recording is turned off, and PostHog never receives your email address or anything you type into a form. This data is processed by PostHog in the United States (PostHog Cloud US) and kept for one year on our current plan; we can delete it earlier at any time. The site shows no cookie banner because nothing is stored in your browser.

What we do NOT collect

We want to be explicit. The Daily Bite app does not collect or access:

• Your device's location. The app never asks for location permission and never reads GPS. (PostHog and, from iPhone app version 1.0.6, Superwall may estimate a rough location from an IP address, as described in "App analytics" and "Paywalls (Superwall)" above.)
• Health or HealthKit data (the "allergies" field is a self-typed onboarding answer, not health-app data).
• Your contacts.
• Your photo library or camera, beyond the one photo you choose. Daily Bite does not browse or scan your photo library, and it uploads only a photo you choose as a recipe's cover photo. The photo picker gives the app only the single image you pick, and the camera opens only when you tap Camera in Add a photo or Take photo for a cover photo. A photo you import is used only to read the recipe and as the recipe's picture on your device; a cover photo you choose is stored with that recipe (see Section 3, "Recipes and cookbooks you create or import").
• Ads inside the app. Daily Bite shows no ads, and your recipes, saved links, onboarding answers, dietary preferences, and allergies are never used for advertising or sent to Meta. On Android, the app does not collect the advertising ID at all. On iPhone, it receives your advertising identifier only if you tap Allow on the tracking question (see "Ads measurement (Meta)" above).
• Your recipe content in analytics. Recipe titles, links, ingredients, cookbook names, and search text are never sent to PostHog, and session replays (iPhone app version 1.0.6 and later) cover every piece of text and every photo or image of yours.

Starting with version 1.0.4 of the iPhone app, Daily Bite does one kind of tracking, as Apple defines that word: measuring our own Facebook and Instagram ads with Meta (see "Ads measurement (Meta)" above). Your iPhone asks for your permission first, and what Meta receives before and without that permission depends on where your iPhone is set, as that section explains. The Android app does no such tracking. App analytics and crash reports cover only how the Daily Bite app itself works and are not sent to Meta. Website analytics is limited to our own site and is not connected to your app account.

4. How We Use Your Information

We use your information only to: create and secure your account and log you in; personalize recipe recommendations and filtering using your onboarding answers and cooking activity; save, display, and organize the recipes, cookbooks, meal plans, and grocery lists you create or import; import a recipe from a link, photo, or pasted text (via our import providers and Google's Gemini AI); estimate a recipe's nutrition when a Daily Bite Pro user asks for it (via Google's Gemini AI); provide and manage Daily Bite Pro subscriptions, including restoring purchases; choose which Daily Bite Pro screens and offers to show you, compare two versions of a screen, keep offers from showing too often, and, from iPhone app version 1.0.6, make each free try of a Pro feature work once; remind you before a free trial ends; understand where people drop off in setup; tell you when the app launches and send occasional recipes and updates if you joined the website waitlist or tester list; understand how the app and our website are used (which screens and features are used in the app, and which pages are viewed and which buttons are tapped on the site) so we can improve them; read the feedback you choose to send us in the app; measure and improve our own ads for Daily Bite on Facebook and Instagram (see "Ads measurement (Meta)" in Section 3); find and fix crashes and errors; and maintain security, prevent abuse, and operate the service. We do not use your recipes, profile, or onboarding answers for advertising, we do not build profiles of you for other companies, and we do not sell your information for money.

What the Daily Bite team can see. The Daily Bite team (the people who build and run the app) can view account and app data, including your name, your email address, and the recipes you save or import, including cover photos you choose for your recipes. We look at this data to run and support the app, fix problems, prevent abuse, and understand what people save so we can improve our recipes and features. The team may also keep a working copy of this data on its own computer to review what people save. That copy is rebuilt from current data, so a deleted account drops out of it the next time it is rebuilt. The team's private admin page, which shows the same kind of data, is protected by sign-in and relayed through Cloudflare. So that some cover images display in a web browser, the admin page may save a converted copy of a cover image (for example, a HEIC image turned into a JPEG) in our Firebase file storage; these converted copies are removed when you delete your account. We never sell this data for money, and we never show your information or your recipes to other users.

5. Legal Bases for Processing (GDPR/UK GDPR)

For users in the EU/UK, we rely on: performance of a contract (creating your account, syncing and saving your recipes/cookbooks, importing a recipe you asked to import, and providing subscriptions); legitimate interests (keeping the service secure, preventing abuse, finding and fixing crashes, measuring how our app and website are used, and choosing and testing which Daily Bite Pro screens and offers to show); and consent for ads measurement with Meta (on an iPhone set to a UK, EU, EEA or Swiss region, or to a European time zone, the app sends Meta no events and no identifiers unless you tap Allow on the tracking question) and anywhere else consent is legally required. You can withdraw it at any time (Section 10).

6. Third-Party Services (Sub-Processors) and AI Recipe Import

We use a small number of trusted service providers to run Daily Bite. Each processes your data only to provide its service to us, under its own privacy policy and data-processing terms. There is one exception: Meta receives ads measurement data and also uses it for its own purposes, as its row below explains. We require that any third party with whom we share user data provides the same or equal protection of that data as stated in this policy and as required by Apple's App Store guidelines and Google Play's policies.

AI Recipe Import: details. When you import a recipe from a link, our recipe-import service first gets the public content: Instagram, TikTok, and Facebook posts are read through ScrapeCreators (the caption and, when needed, the post's images or the video's transcript), and other web pages are fetched through Firecrawl. That content is sent to Google's Gemini AI to convert it into a structured recipe. We use the paid Gemini API tier, under which Google does not use your prompts or the responses to train or improve its models, and retains data only for a limited period for abuse and policy enforcement. The fetched content is not stored by Daily Bite; we save only the resulting recipe, the source link, and the cover image: a copy in our Firebase file storage when the copy succeeds, or otherwise a link to the original image on the source site. ScrapeCreators and Firecrawl may cache the public content they fetch under their own policies; ScrapeCreators may cache and reuse a video's transcript for up to 30 days. When you import from a photo instead, the single image you took or chose is sent to Gemini in the same way; we do not send any of your other photos, and the photo itself stays in the app's temporary storage on your phone as your new recipe's picture. Pasted recipe text is sent to Gemini in the same way. When a Daily Bite Pro user taps Calculate nutrition on a recipe, that recipe's ingredient list and number of servings are sent to Gemini to estimate its nutrition.Please do not import links, photos, or text that contain sensitive personal information, since their content is sent to our providers for processing.

7. Data Sharing

We do not sell your personal information for money, and no one pays us for your data. We disclose your information to the service providers listed in Section 6 so they can operate the app for us, to Meta for ads measurement as described in Section 3, and where required by law. Some privacy laws, including California's, define these words broadly: sending device identifiers, Meta's anonymous ID for this install, your account ID or RevenueCat's random ID, and subscription and in-app purchase events to Meta so it can measure and improve our ads can count as "sharing" personal information for cross-context behavioral advertising, and under some readings as a "sale", even though no money changes hands. We began doing this with version 1.0.4 of the iPhone app, released on September 24, 2026. Before that release we did not, and the Android app does not. To opt out, see "Your choices" under "Ads measurement (Meta)" in Section 3.

8. International Data Transfers

Daily Bite's providers (Google Firebase, Google Gemini API, Google Sign-In and Google Play, Apple, RevenueCat, Superwall, Meta, PostHog, Sentry, Expo, ScrapeCreators, Firecrawl, Cloudflare, Flodesk, and Resend) process and store data on infrastructure in the United States and other countries. Where data is transferred out of the EU/UK/Canada, our providers rely on recognized transfer mechanisms such as the EU-U.S. / Swiss-U.S. Data Privacy Frameworks and/or Standard Contractual Clauses. By using Daily Bite you understand your information may be processed in these locations.

9. Data Retention and Deletion

• Account and profile data (including your marketing-email choice and Terms acceptance), saved recipes, cookbooks, meal plans, and grocery lists: kept until you delete them or delete your account.
• Setup log entries: entries tied to your account are kept until you delete your account, which removes them. Entries that were never linked to an account (for example, if you closed the app before signing in) carry no account ID and are not removed.
• Cover images copied from links you import, and converted copies of them made for the team's admin page: kept in our Firebase file storage while your account exists, and removed when you delete your account. If a cover image could not be copied, the recipe keeps a link to the original image instead, and that image stays on the source site.
• Recipe cover photos you choose: kept in our Firebase file storage until you replace or remove the photo, delete the recipe, or delete your account, as described in Section 3 ("Your own cover photos").
• Photos you import from your camera or photo library: kept only in the app's temporary storage on your phone, never uploaded to your account, not synced, and may be cleared by your phone.
• The content sent for AI import or nutrition estimates (captions, transcripts, page content, photos, pasted text, and ingredient lists): not stored by us; processed transiently and retained only briefly by Google for safety/abuse purposes. Our link import providers may cache the public content they fetch under their own policies; ScrapeCreators may cache video transcripts for up to 30 days.
• Technical/auth log data (e.g., IP): retained by Firebase for a short period (typically a few weeks).
• Server error logs: may include your account ID, but not your name or email address, and are kept for a limited period.
• Purchase records: retained by Apple and Google per their policies, and as we are required to keep for tax and accounting obligations. When you delete your account, we also ask RevenueCat to delete your subscriber record, and Superwall to delete the subscription events and paywall data it holds for your account (see "Paywall data" below).
• Paywall data (Superwall): Superwall, our paywall tool, receives your subscription events from RevenueCat (product, price, currency, country, dates, and transaction IDs, tied to your Daily Bite account ID, or to RevenueCat's random ID for you, for example if you bought before signing in), with the device and technical details on your RevenueCat subscriber record, which can include the identifiers listed in RevenueCat's row in Section 6, and, from iPhone app version 1.0.6, the data the app sends it (see "Paywalls (Superwall)" in Section 3). Superwall keeps this data while we use Superwall. When you delete your account, we ask Superwall to delete the data it holds for your account, whether or not you ever subscribed. Superwall handles these requests by email, so this can take up to 30 days. Subscription events RevenueCat sent Superwall under a random ID rather than your account ID (for example, for a purchase made before you signed in), and, from iPhone app version 1.0.6, paywall data Superwall's software sends before you sign in, may not be removed.
• Paywall history and free tries (iPhone app version 1.0.6 and later): your paywall history (the Pro screens you have seen and closed, and whether you have had a free trial or a paid plan before) and the record of free tries you have used are kept with your account and deleted when you delete your account. The copy of your paywall history on your phone stays until you uninstall the app.
• Session replays (iPhone app version 1.0.6 and later): kept by PostHog for 30 days. Replays linked to your account ID are not removed automatically when you delete your account; they expire after 30 days.
• On-device caches: cleared when you sign out (profile cache) or uninstall the app.
• App and website analytics events: kept by PostHog for one year on our current plan, and deletable by us at any time. Website events are not linked to your app account. App events linked to your account ID are not removed automatically when you delete your account. This includes feedback you send in the app; email [email protected] and we will delete yours sooner. PostHog also keeps some facts on its record of your account ID until we delete them. These include whether you have Daily Bite Pro, which version of setup you were shown, your device type, app version, and screen size, and the rough location (country, region, city, approximate postal code, approximate map coordinates, and time zone) it estimated from your IP address the first and last time it saw you. Email [email protected] to have them removed.
• Crash reports: kept by Sentry for up to 90 days so we can fix bugs. They may include your account ID, but not your name or email address.
• Ads measurement data: the identifiers the app gives RevenueCat while you are signed in sit on your RevenueCat subscriber record, which we ask RevenueCat to delete when you delete your account. RevenueCat also passes them to Superwall with your subscription events, and we ask Superwall to delete those too. If you allowed tracking, Meta also receives your subscription events with your Daily Bite account ID (or RevenueCat's random ID for you), sent as is (or in a coded, hashed form if we later move RevenueCat to Meta's Conversions API). Data Meta has already received is kept by Meta under its own policy. We cannot delete it for you, but you can manage it in your Facebook or Instagram settings.
• Website waitlist and Android tester sign-ups: your email address, the time you signed up, and the form you used are kept in our Cloudflare D1 database (for a tester sign-up, also when your invite email was sent). Your email address may be added to Flodesk so we can send launch news, recipes, and updates, and, if you joined the Android tester list, it is sent through Resend for your tester invite and added to our Google Play tester list. We keep sign-ups until you ask us to remove them, and you can unsubscribe from our emails at any time. Deleting your app account does not remove a website sign-up, because the two are not linked; email [email protected] to have it removed.

Deleting your account. You can delete your account and its associated personal data directly in the app: open Settings from your profile, then tap Delete account at the bottom and confirm. This permanently deletes your Daily Bite account, your profile and onboarding answers, your saved recipes and cookbooks, your meal plan and grocery list, your cooking activity, the setup log entries tied to your account, the cover images copied from links you imported, including converted copies made for the team's admin page, and recipe cover photos you chose, and your paywall history and free tries (iPhone app version 1.0.6 and later). We also ask RevenueCat to delete your subscriber record and Superwall, our paywall tool, to delete the subscription events and paywall data it holds for your account, whether or not you ever subscribed (Superwall handles these requests by email, so this part can take up to 30 days), and if you signed in with Apple, we ask Apple to revoke Daily Bite's access to your Apple ID. Deletion does not remove: PostHog analytics events (tied to a random account ID and kept for up to one year); the facts PostHog keeps on its record of your account ID until we delete them; session replays from iPhone app version 1.0.6 (which show no text and none of your photos or images, kept for 30 days); subscription events RevenueCat sent Superwall under a random ID rather than your account ID (for example, for a purchase made before you signed in), and, from iPhone app version 1.0.6, paywall data Superwall's software sent before you signed in (these may not be removed); RevenueCat records under a random ID that were never linked to your account (for example, from a phone where you used the app before logging in to an existing account), which can hold the device identifiers and purchases described in Section 3; Sentry crash reports (which may include your account ID, kept for up to 90 days); ads measurement data Meta has already received; short-lived server error logs and Firebase sign-in logs; setup log entries never linked to an account; the copy of your paywall history on your phone (iPhone app version 1.0.6 and later), until you uninstall the app; the Daily Bite team's working copy until its next rebuild, which contains names, email addresses, and saved recipes; purchase records kept by Apple and Google and those we must keep for tax and accounting; and website waitlist and Android tester sign-ups, which are not linked to your app account. Those PostHog facts include whether you have Daily Bite Pro, which version of setup you were shown, your device type, app version, and screen size, and the rough location (country, region, city, approximate postal code, approximate map coordinates, and time zone) PostHog estimated from your IP address the first and last time it saw you. Deletion is processed immediately; residual copies in routine backups are purged on our normal backup cycle. This option is available to all users regardless of location, with no phone call or support request required. If you have trouble, email [email protected].

10. Your Rights and Choices

Depending on where you live, you have some or all of these rights:

GDPR/UK GDPR (EU/UK): access, rectification, erasure, restriction, portability, objection, and the right to withdraw consent.

CCPA/CPRA (California): the right to know/access, delete, and correct your personal information; to opt out of the sale or sharing of your personal information (we do not sell it for money); to limit the use of sensitive personal information; and to non-discrimination for exercising your rights. To opt out of the sharing with Meta described in Section 7, tap Ask App Not to Track when your iPhone asks, or turn tracking off for Daily Bite in iPhone Settings > Privacy & Security > Tracking. This stops your advertising identifier, your account ID, and RevenueCat's subscription events from reaching Meta. Meta's software still sends the install, app-open, and in-app purchase records described in Section 3, with its anonymous ID for this install and no advertising identifier. You can also email us with any of these requests.

PIPEDA (Canada): the right to meaningful consent, to withdraw your consent at any time, including for ads measurement, to access and correct your information, and to direct a complaint to us as the responsible business.

To exercise any right, use the in-app Delete account option or email [email protected]. We will respond within the timeframe required by your local law. You also have the right to complain to your local data-protection authority (in Canada, the Office of the Privacy Commissioner of Canada).

11. Security

We protect your information with industry-standard safeguards. Data is encrypted in transit and at rest on Google's infrastructure. Our database security rules make sure that, inside the app, only you can read or write your personal records. Beyond that, access is limited to our server-side functions and to the Daily Bite team through our administrator access, used only for the purposes described in Section 4. Your password is handled only by Firebase Authentication and is never stored by us.

12. Children's Privacy

Daily Bite is intended for users 13 and older (16 in parts of the EU) and is not directed to children. We do not knowingly collect personal information from children under that age. If we learn we have collected such information, we will delete it. A parent or guardian who believes their child has provided us information can contact [email protected] to request deletion.

13. Changes to This Policy

We may update this policy as the app evolves or the law changes. We will post the updated version with a new effective date, and for significant changes we will provide notice in the app. Your continued use after an update means you accept the revised policy.

14. Contact Us

Questions, requests, or complaints about your privacy:

Successfitness
Saskatchewan, Canada
[email protected]