Delete your Daily Bite account

Effective date: October 11, 2026 (last updated November 2, 2026: copies of Ask Nib conversations; November 1, 2026: Ask Nib's working steps and web finds; October 30, 2026: Ask Nib; October 27, 2026: the shared import cache keeps entries for about one year; October 19, 2026: public profiles, plates, reviews, and comments, and recreating a dish from a photo; October 15, 2026: recipe share links, Android app version 1.0.6, and Superwall paywalls on Android; October 14, 2026: session recordings; October 13, 2026: shared import cache)

You can delete your Daily Bite account and everything in it at any time. There is no support request to file and nobody to email first. Deletion is permanent and cannot be undone.

Delete it yourself, in the app

This is the fastest way and it takes effect immediately.

1. Open Daily Bite
2. Go to your profile and open Settings
3. Tap Delete account at the bottom
4. Tap Delete to confirm

Your account and its data are removed straight away. You do not need to contact us and we do not review or delay the request.

Delete it by request

If you cannot get into the app, or you have already uninstalled it, email us from the address you signed up with:

dailybiteapp12@gmail.com

Put “Delete my account” in the subject line. We will confirm the request and delete the account within 30 days. We only ask that you write from the email address on the account, so that nobody can delete someone else’s data.

What gets deleted

Deleting your account permanently removes:

• Your account and login details
• Your name and email address
• The preferences you set during setup, including your dietary and goal choices
• Every recipe you imported or created
• Your cookbooks
• Your meal plan
• Your shopping list
• Your cooking activity, such as the recipes you marked as cooked
• The setup log entries tied to your account (a record of the setup screens you reached and some of the answers you picked)
• The cover images we copied from links you imported, including converted copies made for the team’s admin page (separate copies in our shared import cache are explained below)
• The recipe cover photos you chose
• The recipe share links you made (trydailybite.com/r/...), with their pages and the images we copied for them. Anyone you sent a link to will see that the recipe is no longer available.
• Your paywall history and the free tries of Pro features you used (iPhone and Android version 1.0.6 and later; free tries on iPhone only, except the one free dish recreate, which is recorded on iPhone and Android)
• Your Recreate it with AI request records, each with a short fingerprint of the photo (never the photo itself), and the note of your last offer to recreate a dish from a photo (version 1.0.7 and later)
• Your Ask Nib chats and the copies of them we keep to improve Nib, Nib's working steps, the photos copied for recipe pages Nib picked online, and Nib ask counts (version 1.0.8 and later)
• From iPhone version 1.0.7: your public profile (username, display name, bio, and profile photo), your birth year and age group, your plates and their photos, your shared saves and their photo copies, your reviews, the comments you wrote anywhere, your likes, the people you blocked and the records of who blocked you, and your Activity
• Your reports about imported recipes, your phones’ push tokens, and your background import records (iPhone and Android version 1.0.6 and later; push tokens on iPhone only)

We also ask RevenueCat, the service that manages Daily Bite Pro, 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 that part can take up to 30 days. If you signed in with Apple, we ask Apple to revoke Daily Bite’s access to your Apple ID.

Photos you import with the camera or from your photo library are never uploaded to your account. They are kept in the app’s temporary storage on your phone as the recipe’s picture, do not sync to other devices, and may be cleared by your phone. Uninstalling Daily Bite removes them. A screen recording of about 1 in 10 iPhone sessions can show one while it is on screen (see “Session replays” below). From iPhone and Android version 1.0.6, the app also keeps a copy of your paywall history (the Daily Bite Pro screens you have seen and closed, and whether you have had a free trial or a paid plan before; on Android, only whether you have had a free trial or a paid plan before) on your phone until you uninstall it.

What we keep, and why

A small amount of data survives account deletion: some because we are legally required to keep it, some because another company has already received it, some because it is tied only to a random ID rather than to your name or email address, some because it expires on its own within 30 days (session replays), some because it was never linked to your app account, and some only until the team’s working copy is next rebuilt. That working copy includes your name, email address, and saved recipes until then.

• Purchase and transaction records. Subscription purchases are handled by Apple and Google, not by us. We keep the minimum billing records needed for tax and accounting law. Deleting your Daily Bite account does not cancel a subscription. See below.
• Crash reports and logs. Sentry crash reports and server error logs may include your account ID, but not your name or email address. Crash reports are kept for up to 90 days and server error logs for a limited period, so we can fix bugs. Firebase also keeps short-lived sign-in logs, such as login IP addresses, for a few weeks.
• App usage analytics. PostHog events about how the app was used (such as screens viewed and imports started) are linked to a random account ID, not your name or email address. They are not removed automatically when you delete your account and are kept for up to one year. This includes any feedback you sent in the app. 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 dailybiteapp12@gmail.com and we will delete your feedback, any session replays that show it, and these facts.
• Session replays. From iPhone version 1.0.6, PostHog records about 1 in 10 app sessions as a screen recording that shows the app as you saw it, including your first name, your recipes, what you type, your own photos once they are in the app, and pages you open in the in-app browser. We do not record sessions on an iPhone set to a UK, EU, EEA or Swiss region, or to a European time zone. Only your password and your email address are hidden, on the app’s own screens, and they are hidden on your phone before anything is sent. What you type into a website in the in-app browser can appear in a recording. Replays are linked to the same account ID, are not removed automatically, and expire after 30 days. Email dailybiteapp12@gmail.com and we will delete your replays sooner.
• Paywall data under a random ID. 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 and Android version 1.0.6, paywall data Superwall’s software sends before you sign in, may not be removed.
• RevenueCat records under a random ID. 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) are not removed. They can hold the device identifiers and purchases described in Section 3 of the Privacy Policy.
• Your old username, for 90 days. From iPhone version 1.0.7, a record that your username was released, with your account ID, keeps the name reserved for 90 days so nobody can pose as you right away.
• Reports you made. From iPhone version 1.0.7, reports you made about other people’s content stay so we can keep acting on them, with your account ID removed. Coded records that stop the same person reporting an item twice also stay; they do not store your account ID.
• The Nib question log and reported Nib answers. The Nib question log and reported Nib answers hold no account ID, so they cannot be linked back to you and are deleted on their own after 90 and 180 days.
• Setup log entries never linked to an account. If you closed the app during setup before signing in, the entries from that visit carry no account ID, so they are not tied to you and are not removed.
• The shared import cache. When you import a public post or page, our import service may keep what it read from it (the recipe, the creator’s public credit, copies of the cover image and the creator’s profile photo, and the link without tracking tags) for about one year, so the next person who imports the same link gets it faster. These entries are not linked to your account and hold nothing that identifies you, so deleting your account does not remove them. They are deleted automatically after about one year, and their photos a few days later. See “Shared import cache” in Section 6 of the Privacy Policy.
• The team’s working copy, until its next rebuild. The Daily Bite team may keep a working copy of account data on its own computer, including your name, email address, and saved recipes. It is rebuilt from current data, so your account drops out of it the next time it is rebuilt.
• Website waitlist and Android tester sign-ups. If you joined the waitlist or the Android tester list on trydailybite.com, that sign-up is not linked to your app account, so deleting the account does not remove it. You can unsubscribe from our emails at any time, or email us to have your address removed. See the Privacy Policy for details.
• Link previews of recipes you shared. A messaging app that showed a preview of one of your share links (the recipe’s title and photo) may keep that preview. The page itself stops working within a few minutes of the deletion.
• Ads measurement data. On iPhone, Meta may already have received records of the app being installed and opened and of purchases made in the app, and, if you allowed tracking, your advertising identifier, your Daily Bite account ID (or RevenueCat's random ID), and your subscription events, which we use to measure our own Facebook and Instagram ads. Deleting your Daily Bite account does not delete data held by Meta. You can manage it in your Facebook or Instagram settings, and you can turn tracking off for Daily Bite in iPhone Settings > Privacy & Security > Tracking. The Android app does not send anything to Meta.

The recipes in our own library are our original work and were never yours to begin with, so nothing there is affected.

⚠️ Cancel your subscription separately

Deleting your account does not cancel an active subscription, because subscriptions are billed by the App Store or Google Play rather than by us. Cancel it first, or you will keep being charged.

• iPhone or iPad: Settings › your name › Subscriptions › Daily Bite › Cancel Subscription
• Android: Google Play app › profile icon › Payments and subscriptions › Subscriptions › Daily Bite › Cancel subscription

Questions

Email dailybiteapp12@gmail.com. You can also read our Privacy Policy for the full picture of what we collect and how long we keep it.