Privacy Policy
This policy explains how the Biteshot iPhone app ("Biteshot", "the app") handles your information. Biteshot is made by Aniruddha Daptardar, an individual developer ("I", "me"). If you have any questions, email biteshotapp@gmail.com.
1. Meal photos you scan and meals you describe
When you scan a meal, the app shrinks the photo and sends it to Biteshot's server, a Google Cloud Function. If you type a note under "Something look wrong?", that text is sent along with the photo. When you use Log food โ Describe a meal, the words you type or dictate (for example "2 eggs and toast") are sent the same way, without a photo. If you dictate, your iPhone turns speech into text using Apple's keyboard dictation; Biteshot only receives the text. The server forwards the photo or description, and any note, to a third-party AI service, which returns an estimate of the foods, portions and nutrients. Biteshot uses these AI services:
- Google Gemini (Google LLC)
- Groq (Groq, Inc.)
Biteshot's server handles your photo or description only long enough to get the estimate and send it back to your phone. It does not save photos or descriptions. The AI providers process photos under their own terms and privacy policies, which are described below.
Daily scan limits
To keep the free service available for everyone, the app sends a random install ID with each scan (a described meal counts as a scan). The ID is created on your device, isn't tied to your name or Apple Account, and survives reinstalls. Biteshot's server counts scans per install ID and per IP address each day, and the same way counts pantry requests and plans per install ID and IP address, and week plans per subscription. These counters hold only the ID, address or transaction ID, the date and a count, and are deleted automatically after about two days. The one exception is a record that this install has used its free preview week (and that day's plan, see section 1a), which is kept so the preview isn't offered again; email me to have it deleted.
All scans, free and Pro
Scans use Google's Gemini AI service, and Groq may be used as a backup. Under Google's terms for this service, Google may use the photos, descriptions and notes you submit to improve Google's products, including training its AI models, and human reviewers at Google may see them. This applies to Biteshot Pro subscribers too: Pro gives you unlimited scans, not a different AI service. Please don't scan photos that show people's faces, documents or anything else you wouldn't want shared this way.
Typed text and your first name. The same free Gemini service also receives what you type for the AI: a meal description or a "Something look wrong?" note, and plan, recipe and companion requests. Those requests carry your first name (if you gave one), your diet, allergies, dislikes and condition settings, and anything you write, including health details such as a medicine or a condition if you type them. They never carry your install ID, Dig In profile id, username or Apple ID, and Biteshot's server does not keep them, but Google's terms for the free service (above) apply to them too. Please don't type anything you wouldn't want shared that way.
Weekly insights (Pro)
If you subscribe to Biteshot Pro, Insights (in your Diary) can show "Your week", a short AI summary of your past week. To make it, the app sends Biteshot's server a summary that contains only aggregate nutrition numbers and meal times: each day's total calories, protein, carbs, fat and fiber, how many meals you logged and at what times, and your daily goals and goal (lose, maintain or gain). It does not include photos, meal names or descriptions, your weight or body profile, Apple Health data, or your install ID. The server checks your proof of purchase (section 5), passes the summary to the same AI services as scans, returns the summary bullets to your phone and doesn't keep them. It counts how many summaries each subscription asks for per day, in the same short-lived counters as the daily scan limits.
Your consent
Before the first photo or description is sent, the app shows a consent screen explaining this. Nothing is sent until you agree. If you don't want photos or descriptions sent, don't use the scan or describe features; barcode scanning and food search don't use the AI.
Network data
Like any internet service, Biteshot's server receives your device's IP address with each request. It is used only to deliver the response and to limit abuse (for example, too many requests per minute), and Biteshot does not store it in a profile. Google Cloud may keep standard technical logs for a limited time.
Community weekly goal (from 1.2): if usage analytics are on (section 7a), the app tells Biteshot's server once a day that you logged something, with the random install ID, so everyone's logged days can count toward one shared weekly goal. Nothing about what you logged is sent. The server keeps a daily marker per install for about two days (so a day counts once) and only the week's total after that.
1a. Meal plans and recipes
Today's plan, the week plan, swapping a meal and Cook from my fridge use the same server and AI services as scans. Before the first plan or recipe request, the app asks for your permission on a separate screen; nothing is sent until you agree.
Nutrition per ingredient. When you tap Show nutrition per ingredient on a recipe, the recipe's name, number of servings and its ingredient names and amounts (never your name, diet, allergies, health details, install ID or Dig In profile) go through Biteshot's server to the same free Gemini service to estimate each line's calories and protein; USDA food data is used where it applies. Nothing is sent until you tap, and the first time the app asks for your permission on a separate screen. The server keeps the answer for that recipe's ingredients (the ingredient names, amounts and servings with the numbers worked out for them, not linked to you or your phone) for up to 180 days, so the same recipe isn't estimated twice for anyone, and the app keeps it on your iPhone or Android phone. It is the same service and limits as reading a recipe you paste (section 1a).
- What's sent with a plan or swap: your food preferences (cuisines, diet such as vegetarian, halal or kosher, allergies and the foods you dislike), your goal (lose, maintain or gain) and daily calorie and macro targets, the date, and a short summary of your history: the names of up to 10 favorite meals (meals you logged on 3 or more days in the last 60 days, and saved meals), up to 15 meal names from the last 7 days, up to 10 plan meals you swapped away, and the share of plan meals you logged. On Biteshot Ultimate, also how many people you cook for (2 to 6), if you chose more than one. From 1.2, also your eating style and food rules (such as keto, Mediterranean, Jain or no beef), and short codes, never the details, that change how meals are planned: GLP-1 mode (and whether today or yesterday was an injection day) if you take a GLP-1 medicine; patterns from your after-meal check-ins (for example "dairy tends to bloat"); and, if you entered health history, codes such as "lower sodium", "diabetes-friendly", "heart-healthy", "kidney care", "pregnancy-safe" or "gentle, no numbers". Your medicines, doses, check-ins, gut log, conditions and lab results themselves stay on your iPhone. If you subscribe, requests also send the proof of purchase described in section 5, and every request sends the install ID described in section 1 (shown in You โ Privacy & about, so you can quote it if you ask me to delete your preview record).
- What's sent with Cook from my fridge: up to 2 photos (5 with Biteshot Pro) of your pantry, fridge or shelf (or the ingredient list you edited), the calories and protein you have left today, your goal and your food preferences. Kitchen photos can show people, documents or labels; please frame just the food.
- What's sent with Order in (Biteshot Ultimate): the calories and protein you have left today (none in gentle mode), your goal, which meal it's for (such as dinner), your food preferences and the codes described above, and your taste memory as short codes: up to 5 cuisines and 5 kinds of dishes you like (for example "thai", "curry") and up to 5 of each you said aren't for you. Never the restaurants you order from, the dishes you logged, or your location.
- What's sent with Help me pick (Biteshot Pro and Ultimate): one or two photos of a restaurant menu you choose, plus the same details as Order in (the taste memory codes only on Ultimate). The photos go through Biteshot's server to the AI service to read the menu for that one request; Biteshot doesn't store or log them. Menu photos can show people or your table; please frame just the menu.
- Delivery apps and Apple Maps: Biteshot doesn't order food, connect to any delivery service or see what you order. When you tap Find it, the app checks on your iPhone which delivery apps are installed (Uber Eats, DoorDash, Grubhub, Zomato, Swiggy, Deliveroo) and opens the one you pick, its website, or Apple Maps, searching for the dish's name. That service then gets the dish name you searched for under its own privacy policy; Apple Maps uses your location on its own, and Biteshot never receives it.
- What's never sent: your weight, body profile, meal times, meal photos (other than the pantry and menu photos you choose), workouts or anything from Apple Health.
- A diet such as halal or kosher, or an allergy, can say something about your religion or health. You don't have to give them; you can skip the questions or change them any time in Plan โ My food preferences.
- The server uses this only to make the plan or recipes and doesn't keep it, with one exception: if you don't subscribe, the first day of your free preview week is kept with your install ID so you can open it again. The same Google and Groq terms as in section 1 apply, including that Google may use what's sent to improve its products and that people may review it.
1b. Ratings and feedback
You can rate an AI estimate, a plan meal or a recipe with ๐ or ๐. For a scan you can pick what was off (wrong food, wrong portion, missed something) and add an optional note; for a meal or recipe, why it didn't work (not my taste, too much effort, missing ingredients, not filling). Ratings are also remembered on your iPhone, and the names of meals you liked or disliked (plus which of those reasons keep coming up) are sent with your plan and recipe requests so suggestions fit you better. Biteshot's server then stores the rating, the reason, your note, the dish, meal or recipe name and its item or ingredient names, the total calories, where it came from (photo, description, plan or recipe), the app version and the app's random install ID. It never includes the photo. It's used only to find where estimates go wrong, is deleted automatically after 180 days, and I'll delete it sooner if you email me your install ID (You โ Privacy & about).
1c. Talking with your companion (Mira and others)
If you talk to your Biteshot companion, Apple's speech recognition turns your voice into text on your iPhone; the recording never leaves it (if your iPhone can't recognise speech in your language on the device, voice is off and you can type, unless you turn on Use Apple's speech service in You โ Language: then your voice goes to Apple to become text, under Apple's privacy policy, and never to Biteshot). Biteshot then sends the conversation as text (the last 12 lines of the conversation, yours and the companion's, or the last 40 on Biteshot Ultimate, and how long you spoke), the first name you gave, which companion you chose, the screen you're on, your goal, calories and protein left today, how many meals you've logged today and which of breakfast, lunch, snack and dinner they were (never what you ate), your streak, whether today's plan exists, which helpful settings are still off (Apple Health, reminders, Daily bite, food preferences), your diet and allergies if you've set them (so suggestions fit you), your local time, the app's random install ID and, if you subscribe, Apple's proof of purchase. The text goes through Biteshot's server to Google Gemini to write a reply (or, as a backup when Google is busy, to Groq; see section 1), and, for Pro subscribers, the reply goes to Google to make the companion's natural voice (free users hear the iPhone's built-in voice, made on the iPhone). Biteshot doesn't keep the conversation; the server only counts seconds and turns (per install and per IP address) for the daily limits, and those counters are deleted after about two days. On their free plans, Google may use this content to improve its products and people may review it, so please don't share anything you want to keep private, including health details you'd rather not share. Your companion remembers your first name, on your iPhone. On Biteshot Ultimate it also keeps the last 40 lines of your conversation with that companion, on your iPhone only, so it can pick up where you left off; those lines are sent again with your next messages as described above. Clear it in You โ Companion โ Forget what โฆ knows or with Erase all; it's also erased when you change companion or leave Ultimate. The companion is an AI, not a person, and not a medical professional. Saying a meal with the mic on Describe a meal works the same way: your voice becomes text on your iPhone (or with Apple's speech service, only if you turned it on), and only the text is sent to Biteshot, like a typed description (section 1).
Answers in the chat. Your companion answers some things on your iPhone without sending anything: what's in today's plan, recipes from your last fridge photo, a Library article or video, a quiz. When it shows you something from your plan or log, only a short note that it did (for example "showed their breakfast from today's plan") goes along with your next messages, never the dish or what you ate. If your health history includes an eating disorder, only a "gentle" flag goes with the conversation, so replies leave out numbers, and calories, protein and your streak aren't sent. Saying what you ate ("I had oatmeal") logs it: a meal you logged before is copied on your iPhone; anything else is estimated like Describe a meal (section 1). Common questions answered in the last few hours may be answered again from your iPhone. For Pro's natural voice, each sentence of a reply is sent to Google separately so it can start speaking sooner. Videos play in a viewer inside the app, from YouTube, under Google's privacy policy.
Live Bitey (Pro and Ultimate). In a live voice chat the microphone stays on while the chat is open, so you can talk over your companion. Your voice is turned into text on your iPhone the same way as above (or by Apple's speech service, only if you turned it on); no audio is recorded, stored or sent to Biteshot. Each thing you say is sent as text, exactly like a chat message above, and the replies are spoken the same way (Pro's natural voice per sentence, from Google). The live transcript is the chat itself and stays on your iPhone (kept only as described above for Ultimate's memory). Live never runs in the background: it ends when you leave the app or after 10 minutes. Biteshot's server only counts live sessions and turns, per install, for the daily limits, and those counters are deleted after about two days.
What Bitey knows about your day (1.2.4). To answer "what should I have for dinner?" in a way that fits you, each message you send to Bitey also carries a short summary of today: how many calories you have eaten (one number; never sent in gentle mode or with Hide numbers) and how many are left, how much protein is left (not with kidney care), your goal, how you eat, and your allergies, plus a yes/no flag saying whether Bitey may save a new note. If you let Bitey remember things (Settings → Bitey → Bitey remembers), up to 20 short notes you saved (at most 120 characters each), such as "I don't eat after 8", are included too. These notes are written in your words and live only on your phone, in a file that is left out of backups; you can see, change or delete any of them, or all of them, at any time, and Erase all deletes them. Biteshot does not store this summary: it goes with your message to the AI services that write Bitey's answer, as described above. Bitey's daily check-in (off until you turn it on) is built on your phone from today's meals and shown as a notification; nothing is sent to make it.
Typed food Search (1.2.4). When you type a food in Search, the words you typed and an anonymous install ID (a random number, not linked to your Dig In profile) go to Biteshot's server. Only the words go on to the US Department of Agriculture's FoodData Central database; no ID of any kind is sent to it. The install ID and your network address are used only for an hourly request counter that is deleted within about a day, and the answer is cached by the words alone, with no person attached, for up to 30 days.
1d. Changing the app's language
When you switch Biteshot to another language, the text the AI wrote for you earlier can be translated so it matches: your meal plan, recipes and grocery list (only if you agreed to meal plans), and, only if you agreed to send meals to AI, the names, portions and notes of meals you logged in the last 60 days and your weekly insights. That text, with no photos, Apple Health data or account details, goes from Biteshot's server to Google Gemini's free tier, which may use it to improve Google's products under the Gemini API Additional Terms. Grocery items you typed yourself are never sent. Biteshot's server doesn't keep the text; it keeps only a daily count per install and per network (about two days) to limit use. Translations are stored on your iPhone so switching back doesn't send anything again.
1e. Health Academy (the Library)
Each day Health Academy asks Biteshot's server for that day's new article and quiz questions and for the day's videos, podcasts and people to follow. The request carries only the date, the app's language and, for Pro and Ultimate, the App Store's proof of your subscription so the full article and Ultimate's archive can be sent. Nothing about you, your meals or your health is sent. The articles are written once a day for everyone with AI (Google Gemini's free tier) and are the same for every reader. What you read and your quiz answers stay on your iPhone. Videos and podcasts are free YouTube videos from public health bodies, universities, hospitals and credentialed experts; their thumbnails load from YouTube, and tapping one plays it in the app's player (see Videos played in the app), where YouTube's privacy policy applies. Links to people to follow open their own sites.
1f. Dig In
Dig In is a food-sharing feed. It mixes posts from people with posts from a few AI food personas: accounts written by AI, never presented as real people. Dig In says so the first time you open it and in Settings โ Dig In โ About Dig In; each persona's profile says "โฆ AI persona", and their comments and replies carry a small โฆ. AI personas may react to or comment on your posts (for example a welcome on your first post), from pre-written lines in your post's language; nothing about you is sent to an AI for this. You can turn this off in Settings โ Dig In โ "Let AI personas comment on my posts"; Biteshot's server keeps that choice with your Dig In profile. Their reactions aren't counted in any public totals. Their posts are written ahead of time and published on a schedule; their photos are free-licence photos (Pixabay, Unsplash or Wikimedia Commons), credited on each photo, and never claimed as their own. Photos from Unsplash load from Unsplash's servers (Unsplash then sees your iPhone's IP address, like any website); the others load from Biteshot's own storage. Browsing Dig In sends Biteshot's server only the app's language, whether you asked for other languages, and, if you have a Dig In profile, its id. Your diet, allergies, eating style and health history are never sent: the feed and search are filtered on your iPhone. What you type in Dig In search goes to Biteshot's server to find matching posts and isn't kept or logged.
Not seeing the same dish twice. To keep the feed from repeating, the app remembers on your iPhone which posts it showed you in the last week, as a small scrambled table (a Bloom filter) per day, and sends that table with each page request. It holds no post ids or names, and nothing about it is stored on our servers. Your photos and meals are not involved, and health data never decides what you see or any ad.
Your Dig In profile (optional). The first time you follow, react, comment or post, you choose a username (not your real name). Biteshot's server then keeps: that username, which of your Bitey characters is your picture, who you follow and block, your reactions, likes on comments, when you accepted Dig In's rules (13 or older), and a random secret that proves the profile is yours (stored as a one-way hash; the secret itself stays in your iPhone's Keychain). Unless you choose to add them (see Your name and Finding friends from contacts below), it doesn't keep your name, email, phone number, install ID or location. Usernames are checked against a list of words that aren't allowed. Dig In is for people 13 and older.
Your Bitey's look. From 1.2.4, a person's Bitey look (character, colour, eyes and extras) is public on Dig In, like their avatar.
Save your profile with Apple (optional). You can link your Dig In profile to your Apple ID with Sign in with Apple, only so you can get the profile back on a new phone. Biteshot asks Apple for no email and no name. It keeps a one-way keyed hash of the private ID Apple gives the app (not the ID itself), next to your profile, and nothing else. Deleting your account in Settings > Dig In removes the link and revokes Biteshot's access to your Apple ID. If you delete the account, the keyed hash is deleted with it. Your profile's secret is kept in your iPhone's Keychain, which can move with an encrypted backup to a new phone.
Your top dishes (optional sharing). Ranking your own plates ("Which did you like more?") happens on your iPhone and your ranking stays there. Only if you choose Count my picks, the names of the dishes you compared are sent to Biteshot's server (never their photos or your account; your install ID is sent only to count you once and is never kept) to build that week's list of most-loved dishes in your language; distinct people are counted with a one-way code that changes every week, and these counts are deleted after 21 days. A dish name shows only once several people ranked it and it passes our checks. You can turn it off anytime in Your top dishes, and Erase all removes your ranking.
Your posts and comments. What you post is public to everyone on Dig In: your photo, the dish's name, your caption and hashtags, your recipe if you add one, the diet tags you choose, and calories only if you turn on "Show calories". Before a photo leaves your iPhone it is resized and re-encoded, which removes its location and other details (EXIF). Posts are checked automatically; we may remove posts that break the rules. Before a post shows, your iPhone checks that the photo looks like food, and Biteshot's server checks the photo with Google Cloud Vision SafeSearch and your words against a list of words that aren't allowed; if SafeSearch can't run, the post waits for a person at Biteshot to review it. Right after it's up, the server also checks the photo and your words with Google Gemini's free tier, under the Gemini API Additional Terms (Google may use free-tier content to improve its products; your post is public anyway), and takes it down if they break the rules (you'll see why, and a person at Biteshot reviews it). Comments are checked the same way. Photos are stored in Biteshot's Firebase Storage (Google Cloud) and reachable only through the links in the app; comments, likes and posts are stored in Firestore. Delete a post or a comment any time from its โฏ menu.
Following people and tags. You can follow other people, not just AI accounts. Your profile shows your username, your Bitey, your published dishes and how many posts, followers and people followed you have; Biteshot's server keeps who you follow and counts your followers. When you post you can tag up to 5 co-chefs ("Cooked with") and 5 guests, only among people who follow you; their usernames and Bitey show on your post, and anyone tagged can remove their tag from the post's โฏ menu. If you block someone, they can't follow, see or tag you. Deleting your Dig In profile also removes who you follow, who follows you and your tags on other people's posts. My kitchen (your cooking journal on the Bitey tab) is built on your iPhone from your logged meals and your own posts; nothing about it is sent.
Reports and blocks. If you report a post, comment, person or AI account, Biteshot keeps the report (what was reported, the reason, the time and your Dig In profile id if you have one, never your install ID) for 180 days to review it; three reports from different established members (signed in for a few days) hide it until it's reviewed. Blocking someone is kept with your profile; they aren't told.
Translations. When you tap Translate on an AI account's post in another language, the post's own text (not anything about you) goes from Biteshot's server to Google Gemini's free tier, under the Gemini API Additional Terms. The translation is kept on the server so the same post isn't translated twice; a daily count per install limits use (about two days).
Mentions in comments (build 95). Typing @ in a comment offers the people you follow and the people who follow you. Mentioning someone sends their account ID along with the comment so Biteshot can notify them (a push naming only you, never the comment; they can turn it off in Settings → Dig In). The engine checks each mention is one of your connections, never someone who blocked you, and keeps at most 5 per comment. The mention is stored with the comment and is no longer shown once the comment is deleted. The comment text is checked like any other comment.
Notifications. Biteshot asks once, after you choose a username, whether it may send notifications. If you allow it, Biteshot's server sends a push, through Apple's notification service, when someone comments on or replies to your post, reacts to or likes something of yours, tags you, follows you or becomes your friend, or posts something new (people you follow only). Each kind has its own switch in Settings → Notifications & reminders, and all are on by default. For this, your iPhone's notification token is kept with your Dig In profile until you turn the notifications off, sign out or delete the profile; a token belongs to one profile at a time. Pushes are grouped, capped at 8 a day and not sent between 10 pm and 8 am where you are; they name only the other person, never what they wrote. Nothing is sent to yourself, to people you blocked or from AI accounts. Notifications for AI accounts you follow, and the reminders you set (meals, streaks, the daily bite and so on), are scheduled by your iPhone itself and send nothing to a server.
Your name (Dig In)
You can add a first name and, if you like, a last name to your Dig In profile. It is optional to browse Dig In, but a first name is needed to follow people, post, comment or message, so people know who they are talking to. You choose who sees your name: everyone on Dig In (the default), only people you follow and who follow you, or nobody. Your @username is always visible as before. We check names with the same rules and the same free text check we use for captions. We use your name only to show it where you allow and to let people find you by name within that choice. You can change or remove it any time in Settings. It is not used for ads and is never put in our usage statistics.
Nicknames
A nickname is a private label you give someone ("Aai"). It stays on your phone, is never sent to Biteshot and nobody else can see it. It is deleted when you erase your data in Settings or remove the app.
Finding friends from contacts (optional, off until you turn it on)
- Let friends find me. If you choose this, you either continue with Google or Apple (we read only the verified email address from that sign-in, if there is one; an Apple "hide my email" address cannot be matched) or you type your own phone number or email. We do not keep the address or number itself. We keep a one-way scrambled code made with a secret key that only our server holds. Friends who have your address or number in their contacts can then find you, and you appear with a checkmark if you used Google or Apple. A number or email you only typed is never verified: it can only show you to a friend as a suggestion, and only when you each have the other's number or email in your contacts and each have used Find friends.
- Find friends from contacts. Nothing is read until you tap the button and allow access. Your phone scrambles each contact's email addresses and phone numbers on the phone and sends only those codes. Contact names, and the addresses and numbers themselves, never leave your phone. We tell you which people are already on Biteshot (their @username, and their name only if they allow you to see it); we never tell you who is not. To make the two-way rule work we keep your scrambled contact codes until you use Find friends again (they are then replaced), choose "Forget my contacts", use Erase all or delete your profile. Codes older than 90 days are never used for matching, but they stay stored until one of those happens.
- Tell me when friends join. If this is on, we also remember the scrambled codes of contacts who are not on Biteshot yet, so that when one of them joins and chooses to be found you get one notification a day at most ("3 friends joined"), never at night. We never tell the person who joined that you were watching.
- Who sees what. Someone who has blocked you, or whom you blocked, never matches. Someone who chose "nobody" for their name is never matched at all. People under 18 are treated like everyone else: nothing is shown that the person has not chosen, and contact matching is optional.
- Deleting. Turning "Let friends find me" off removes your scrambled address and number codes. "Erase all" and deleting your profile remove your name, your codes, your stored contact codes, the contacts we were watching and any waiting notification. Backups of our database roll off within the normal backup period.
Who we share with. Google and Apple see that you signed in (as they already do for sign-in). Nothing in this feature is sold, shared for advertising or used to track you across other companies' apps and websites.
Direct messages
On Dig In you can send a private message, with an optional photo of food, to another Dig In member. If you follow each other or either of you follows the other, the chat goes to their inbox; otherwise it arrives in the same Messages list, marked as from someone unknown, and they can reply, delete it or block the sender. Messages and photos are stored on our servers, linked to both profiles, so they can be delivered and shown in both people's apps; they are not end-to-end encrypted. We remove location and camera details from photos and run automatic safety checks on messages and photos (the text goes to Google's free Gemini service, with no account id or username, and photos go to Google Cloud Vision SafeSearch and the same AI check as Dig In posts), which can hold a message back until a person at Biteshot has looked at it. Only if someone reports a message do we keep that message and the few before it for up to 180 days so we can review it; our team does not read other conversations. Messages are deleted a year after they were sent, when both people have deleted them, and when you delete your Dig In profile or use Erase all in the app, which also removes your side of every chat. Notifications about messages show only who wrote, never what was written, and you can switch them off in Settings. You can block anyone, and a blocked person cannot message you.
Deleting it. Settings โ Dig In โ Delete account and data, or Erase all, deletes your username (and any you used before: a changed username stays reserved for you, so nobody can pose as you on your old posts), posts and their photos, comments, likes, follows, blocks and reactions from Biteshot's server (if you're offline, the next time the app can reach it). A post's draft stays only on your iPhone until you send or discard it.
Polls, compliments and share cards. Dig In shows one quick food poll a day. When you vote, Biteshot's server keeps which option you picked for that poll, under your Dig In profile if you have one or otherwise under a one-way hash of the app's install ID (never the install ID itself), and adds it to the poll's anonymous totals; you can't change a vote. Which options you see is decided on your iPhone from your diet, allergies and health history, which aren't sent. Compliments to the chef ("Chef's kiss", "Nailed it"โฆ) are fixed words, kept with your Dig In profile and the post until you take one back or delete your profile; the post's author may see that your username sent one. A share card is a picture drawn on your iPhone (the dish's photo, its name, the username or AI account, the photo's credit and a link); nothing is sent to Biteshot when you make or share one, and where it goes is up to you and the app you share it with. Its link (biteshot.web.app/d/โฆ; cards made before this release use snapcal-engine.web.app/d/โฆ) opens a page that only offers to open the post in Biteshot or get the app; that page loads nothing about the post. "Save recipe" copies a post's recipe into Saved recipes on your iPhone. Deleting your Dig In profile also deletes your compliments and the votes kept under it (the anonymous totals stay).
Friends, persona follow-backs and search. The Friends tab in the feed shows posts from everyone you follow, whether or not they follow you back; your public Friends list is made of people who follow each other. Anyone who can see a person's Dig In profile can see their Friends list (usernames and Bitey pictures only); people blocked either way never appear in it. When you follow an AI food persona, it follows you back within about a minute, so it shows up in your own Friends list with a small โฆ; Biteshot's server keeps only that the persona follows you back (on your Dig In profile), it is visible only to you, never counted in the follower or friends numbers anyone else sees, and it ends when you unfollow. Dig In's search now sends your Dig In profile id (to keep posts from people you follow and your own in the results) and whether "Other languages" is on (Settings โ Dig In); search results follow the same language setting as the feed. Search by meal type uses a "course" (main, dessert or drink) worked out from a post's words and, for a photo you post, the same AI photo check that already reads your dish (no new data leaves your iPhone). Yesterday's poll results show totals only, never who voted. "Hide this dish" and the People to follow strip's choices stay on your iPhone.
1f-2. Potluck parties and groups
Potluck parties are real-life potlucks you plan in the app, and groups are your friends & family. They're private: only the people invited see them, and nothing in them appears on Dig In unless you share your own photo there yourself. They use your Dig In profile (your username and your Bitey as your picture).
What Biteshot's server keeps. For a group: its name, who's in it (by profile id, with their usernames and Bitey) and who made it. For a potluck: its title, date and time, the place and note if the host adds them, who's coming, the dish sign-up list (each dish's name and who's bringing it, and what the dish's name suggests about common allergens and diets), the album's photos, and reports made inside it. Invite links are long random codes; the server keeps only a one-way hash of each, and a link stops working when the host makes a new one or the potluck is over. The invite page on this website holds nothing but the code and only hands it to the app.
Allergies and diets you choose to share. When you join a potluck (or later), you can choose to share your allergies and diet labels (for example "peanuts" or "vegetarian") with that potluck only. It's off unless you turn it on. Others see counts ("2 guests avoid peanuts"), and your username next to them only if you allow it. Health conditions and pregnancy are never shared. What you share is deleted a week after the potluck, when you turn it off, or when you leave.
Dish names and photos are checked the same way as Dig In posts: a dish name goes to Google Gemini's free tier, and a photo is resized and re-encoded on your iPhone (removing its location and other details), then checked by Google Cloud Vision SafeSearch and Gemini before others see it; anything unclear waits for review. Photos are kept in Biteshot's Firebase Storage and shown only to the potluck's people.
Reminders for a potluck (the evening before and two hours before) are scheduled by your iPhone itself; you can turn them off for each potluck.
How long. A potluck, its list and its album are deleted 90 days after it (or as soon as the host deletes it). Leaving a potluck or group removes your dish, photos and what you shared there. Deleting your Dig In profile (or Erase all) deletes your groups and the potlucks you host, and takes you out of the others.
1f-3. Bites from Dig In and invites
Social Bites. When you share a plate, compliment or comment, follow people, or someone reacts to your plate on Dig In, Biteshot's server records that it paid Bites to your pseudonymous Dig In profile: the kind of action, the amount, when, and a one-way code of what it was for (never who followed whom or what you posted). It also counts your actions per day and month (for example "2 plates shared today") for quests and challenges. Day counts are deleted after 40 days, month counts after 13 months; the rest is deleted with your Dig In profile.
Invites. Your invite code is stored with your Dig In profile. When a friend uses it, the server stores who invited whom, when, and the invite's status, plus a one-way code of each phone's app install id (so the same phone can't invite itself; the install id itself is never stored). No contacts are uploaded and the app never reads your clipboard: the code travels in the link or is typed. When an invited friend buys Pro or Ultimate, their purchase carries an anonymous account token (derived one-way from their Dig In profile) so Apple's purchase notifications and the app can tell the server that the friend's first paid period started or was refunded; the server keeps the App Store transaction id of that subscription to count it once. Invite records are kept while the profiles exist and at most 13 months after their last change, and are deleted with your Dig In profile. Biteshot receives the App Store's signed purchase notifications for this; they contain purchase details (product, dates, transaction ids, the token), never your name or payment details.
1g. Food photos you took (formerly "Find meals I forgot")
If you tap Find meals I forgot (the + sheet), Biteshot asks iOS for access to your photos (you can allow only the photos you choose). It then looks at today's and yesterday's photos on your iPhone, using Apple's on-device image recognition, to find ones that look like food you haven't logged. This happens only while that screen is open after you tap the button, never in the background. No photo, and nothing about your photos, leaves your iPhone at this step. When you choose Log this on a photo, that one photo is scanned like any meal photo you pick (section 1), and the meal is logged at the time the photo was taken. Biteshot remembers on your iPhone, for 7 days, which photos you logged or marked "Not a meal" (by the photo's identifier only), so they aren't offered again; Erase all clears this. You can turn photo access off any time in iOS Settings.
Sharing found photos, the card and the reminder. The screen is now called Food photos you took, and each photo it finds can also be shared to Dig In: that opens the usual "Share your plate" screen with the photo, and nothing is sent until you tap Post (then it's a Dig In post like any other, section on Dig In). Photos you share are remembered on your iPhone like logged ones (by identifier only, 7 days). Only if you have already given Biteshot access to your photos (all or some), the app also checks today's photos on your iPhone when you open it, at most every few hours and only while it's open (never in the background), and may show a card such as "You took 3 food photos today: share or log them?" with small pictures. It never asks for photo access itself; without access there's no card. No photo, and nothing about your photos, leaves your iPhone for this; Biteshot remembers on your iPhone which photos were on a card and when you put it away, so it shows at most once a day and never again for the same photos. An optional reminder ("Took any food photos today?", 8 pm, off unless you turn it on in Settings โ Reminders) is a notification scheduled on your iPhone; it doesn't look at your photos. Usage analytics count only that a scan found something (how many), that the card was shown, opened or put away, that a found photo was shared and whether the reminder is on โ never the photos, what's in them or when they were taken.
1h. Importing and exporting recipes
From a link. When you import a recipe from a link, the link goes to Biteshot's server, which opens that web page and reads the recipe information the page publishes (schema.org Recipe data). No AI is used, and neither the link nor the page is kept. A daily count per install and per network address limits use.
From a TikTok, Instagram or YouTube link. When the link is a TikTok video, an Instagram post or reel, or a YouTube video, Biteshot's server reads that post's public caption or the video's description and the creator's public name and handle from the platform (TikTok's and YouTube's public embed information, or the public page Instagram serves). The caption is then read by Google Gemini (AI) to find the recipe, so the app asks for your consent first, the same consent as pasted text. The caption and link aren't kept on the server; the recipe you save keeps the link and credits the creator (their name, handle and a link to their page) on your iPhone. The same daily counts as links and pasted text apply.
From text or a photo of a recipe. Text you paste goes to Biteshot's server, which uses Google Gemini's free tier (under the Gemini API Additional Terms; Google may use it to improve its products, and it may be reviewed by people) to sort it into ingredients and steps; the text isn't kept. For a photo of a recipe card or cookbook page, the words are read on your iPhone (Apple's on-device text recognition); you can check and edit them, and only that text is sent, never the photo. You're asked for consent before the first time.
From a file. Files from other recipe apps (such as a Paprika export) and saved recipe pages are read on your iPhone; nothing is sent.
Imported recipes are saved on your iPhone (Plan โ Saved recipes). Export creates a text or PDF copy on your iPhone and opens the iOS share sheet; Biteshot doesn't receive it. Your recipes are always yours to export.
1i. Pregnancy and breastfeeding mode, more health conditions, and Bitey
On your iPhone only. If you add a due date or your baby's birthday, feeding or pumping logs (side, minutes, amount), whether Crohn's or colitis is in a flare, or new conditions (such as breastfeeding, a severe food allergy, heart failure, dialysis, gout, anemia, a blood thinner, weight-loss surgery, Crohn's or colitis, or osteoporosis), they stay in your health history on your iPhone, protected while it's locked and left out of iCloud backups. "Delete health history" removes them all. Feeding and pumping reminders are local notifications you turn on yourself; the lock screen only says "Time for a feed?" or "Time to pump?". None of this is sent to analytics.
Plans, fridge recipes and eating out get only short codes, as in section 1a (for example "breastfeeding-safe", "lower purine", "steady vitamin K", "dialysis", "low-residue during a flare" or "bone health"), never the condition list, dates, notes or lab results.
"Let Bitey follow these too" (off unless you turn it on). In Health history you can let your companion follow your conditions. Only then, each chat or voice message also sends short codes from a fixed list (for example "gout", "dialysis" or "second trimester of pregnancy"), so Bitey's suggestions fit. Never your dates, notes, lab results, medicines or an eating-disorder history (that only ever sends the "gentle" flag described in section 1c). Biteshot's server drops anything not on the list and doesn't keep or log the codes. Turn it off any time and nothing more is sent.
Lab results. If a lab result you entered is in a range often linked with a condition (for example a high uric acid and gout), Health history may show a neutral note that you can add the condition if your clinician has talked to you about it. This is worked out on your iPhone; Biteshot never diagnoses, and once you add or dismiss a note it isn't shown again.
Meal names in English. When you use Biteshot in another language, a meal scan also returns the dish's name and items in English, used only on your iPhone to show food-safety tips.
1j. Blog comments
You can leave a comment on the Biteshot Blog without an account. We store the name you type, your comment, and when you posted it. Comments are public once they are approved, so please don't include personal details, and don't share personal health information. To limit spam and abuse we also keep a salted, one-way hash of your IP address for 30 days; we cannot turn it back into your address, and we use it only to limit how often one visitor can post. Comments are checked automatically (and sometimes by hand) for spam and safety before they appear; comments that are not approved are deleted after 7 days. We do not collect your email address and we do not set advertising cookies for comments. Your browser keeps a private deletion key for each comment you post, so you can delete it from the same browser at any time. If you cannot delete a comment yourself, email us from the Support page and tell us where it appears, and we will remove it.
Reactions on blog posts and comments (such as "Chef's kiss") are anonymous counts. To stop repeat taps we keep the same salted, one-way hash of your IP address for 30 days; the counts themselves are kept without it.
1k. Connected AI apps (ChatGPT, Claude and others)
This is optional and off until you turn it on. In Settings → Connected AI apps you can let an AI app such as ChatGPT or Claude add meals you tell it about to your Biteshot diary. You approve each app yourself, in the Biteshot app, by entering the short code the app's connect page shows. Nothing is connected until you tap Allow, and you can tap Disconnect at any time.
- What the AI app can do: add a meal you describe (the dish, the foods and portions, and the calories, protein, carbs and fat the AI app estimated, and when you ate it), undo a meal it added before your phone picked it up, and look up Biteshot's public recipes. It cannot read your diary, your photos, your goals or any health data. Biteshot never sends your diary to an AI app.
- What Biteshot keeps, and for how long: a meal an AI app added waits on Biteshot's server (Google Cloud) only until your phone picks it up, which happens the next time you open Biteshot. The server deletes it as soon as your phone has confirmed it, and deletes it anyway after 7 days. It is not used for analytics, ads or AI, and it is not shared. Once your phone has it, it is an ordinary meal in your diary that stays on your phone, marked "Added from" the app's name.
- The connection itself: to know that the app is allowed, Biteshot keeps, until you disconnect, erase or delete your data: the app's name, the address it returns to (for example chatgpt.com), the dates it was connected and last used, and access tokens stored only as one-way hashes. This is linked to your Biteshot profile ID, the private ID Dig In uses. If you have no Dig In profile, connecting creates a private one with no username, no posts and nothing public.
- What the AI app's company sees: what you say to ChatGPT or Claude is handled by that company under its own privacy policy, not Biteshot's. Biteshot receives only the meal details the AI app sends when you ask it to log a meal.
- Deleting it: Disconnect in Settings stops an app at once. Erase all and Delete account and data remove every connection and any meal still waiting. Anything left expires on its own.
- Estimates: calories and nutrients from an AI app are estimates and can be wrong. Change a portion or delete the meal like any other.
1l. Workouts from connected devices
This is optional and off until you connect it in Settings → Connected devices. You sign in on Garmin's own page and choose what to share there. Workouts from your phone's health app (Apple Health or Health Connect) go to the same place once you have connected it.
- What Biteshot reads: your completed workouts (type, time, duration, distance, active calories and which device or app recorded them) from Garmin Connect, and from Apple Health or Health Connect if you connected it. Never a route, location or heart-rate stream.
- How it's used: only to show you your own workouts in your Diary, adjust your own daily targets for activity, and suggest a recovery meal from your own saved recipes that fits your diet and allergies. These suggestions use simple rules, not AI.
- Never: shown to other people, used for ads, sold or shared, or sent to any AI system or used to train one. Bitey, meal plans and connected AI apps never see Garmin data.
- Where it's kept: on Biteshot's server (Google Cloud, Firebase). Sign-in tokens are encrypted. Workout summaries from connected devices are kept until you delete them or your account.
- Your control: delete any workout from your Diary (press and hold it) and it is deleted from our server too, and stays deleted. Disconnect in Settings (or removing Biteshot in Garmin Connect) deletes your tokens, and you can choose Disconnect and delete workouts to delete that service's workouts as well. Erase all and Delete account and data delete everything. You can ask us for a copy, a correction or deletion at any time at biteshotapp@gmail.com.
2. Barcodes and food search (Open Food Facts)
When you use Log food โ Scan a barcode or Search foods, the app looks the food up in Open Food Facts, a free, open database of food products run by the non-profit Open Food Facts association. These requests go directly from your phone to Open Food Facts, not through Biteshot's server, and no AI is involved.
- What is sent: the barcode number you scan or type, or the words you search for. Each request names the app ("Biteshot/1.0") as Open Food Facts asks apps to do. Product pictures are loaded from Open Food Facts' image server.
- What isn't sent: your photos, meals, goals, body profile or install ID.
- The barcode scanner reads the camera image on your iPhone. Camera images are not sent anywhere; only the barcode number is.
Like any website, Open Food Facts receives your IP address with each request. Its handling is covered by the Open Food Facts privacy policy.
3. Data that stays on your iPhone
The following is stored only on your device and is never sent to Biteshot:
- Your logged meals, including their photos, foods, portions and nutrition totals
- Foods you star as favorites (your recent foods are read from your logged meals)
- Your daily calorie and macro goals
- Your body profile: sex, age, height, weight, activity level and goal (lose, maintain or gain). The app uses these only to calculate your suggested daily goals.
- App preferences such as units
- Your food preferences (sent only inside plan and recipe requests, section 1a, and, as your diet and allergies, with companion chats, section 1c), your plans, the grocery list and recipes you saved to cook later
- On Biteshot Ultimate, your taste memory ("What you like to order"): the cuisines and kinds of dishes learned from the delivery and restaurant meals you log and your ๐ or ๐ on Order in ideas and plan meals, and the ones you chose yourself. You can see, change or clear it in Settings โ About you โ Food preferences โ What you like to order, and Erase all deletes it. Only its codes are sent (section 1a).
- Workouts you logged by hand before version 1.2.5, including strength exercises, sets, reps and weights (manual workout logging has ended; the ones you logged stay)
Saving your photos to Photos. Photos you take with Biteshot's camera are also added to your iPhone's Photos library, as you took them, so you keep a copy. Biteshot only adds photos (iOS asks "add photos only" the first time) and does not read your library for this; the copy lives in your own Photos app, never on Biteshot's servers. Turn it off in Settings > Privacy & about > Save photos to Photos.
Biteshot has no app account (only the optional Dig In profile in section 1f) and does not sync this data to any server. If your iPhone backs up to iCloud or a computer, this data may be included in that backup, which Apple's terms and your own settings govern.
4. Apple Health
Biteshot can connect to Apple Health on your iPhone. It's off until you turn it on in You โ Apple Health, and iOS asks your permission first.
- Reading: if you tap Connect Apple Health (Today's tracker row or Insights) or turn on "Add exercise calories to my budget", Biteshot reads your steps, active energy, workouts, weight and sleep, including what Apple Watch, Oura, Garmin, Whoop, Strava, smart scales and other apps save to Apple Health. It uses them only to show your steps and workouts, add weigh-ins to your weight history, show your sleep and a sleep score, show trends and insights, pick your Daily bite on your iPhone (for example after a short night), and (if you turn it on) add the calories you burned to that day's budget.
- Sleep is read-only: Biteshot never writes or changes sleep data in Apple Health. Your nights and sleep score are worked out on your iPhone and stay there; they're never sent to Biteshot's server, an AI service or analytics.
- Writing: only if you turn on "Save meals to Apple Health", Biteshot saves each meal you log (calories, protein, carbs, fat, fiber, sugar and sodium, at the meal's time) to Apple Health. Editing or deleting the meal in Biteshot updates or deletes what it saved.
- Workouts you logged by hand in Biteshot are added to the same budget and never leave your iPhone. Meal plans are sized from your daily goal only, never from Health data.
- Health data stays on your iPhone, with one exception: workout summaries. For your Diary, the summary of each workout (type, start, duration, distance, calories and which app recorded it, never a route or heart rate) goes to Biteshot's server and is kept until you delete it or your account (section 1l). Nothing else from Apple Health is sent to Biteshot's server, and none of it is ever sent to any AI service, never used for advertising or marketing, and never sold or shared with anyone. You can turn access off at any time in iOS Settings โ Privacy & Security โ Health โ Biteshot.
5. Purchases
Biteshot Pro and Biteshot Ultimate are subscriptions bought and handled through Apple's App Store. Biteshot never sees your name, payment card or billing details. To confirm that you have an active subscription, the app sends Biteshot's server a proof of purchase signed by Apple. It contains purchase details such as the product, dates and a transaction ID, but no payment information. The server checks it to unlock subscriber features.
Trial reminder. If your subscription starts with a free trial or an introductory price that will renew, the app schedules one notification on your iPhone 2 days before it renews (only if notifications are allowed), using the renewal date from the App Store. Nothing is sent to a server for this. No sales calls, ever; you can manage or cancel in one tap from the plans screen or Settings โ Plan & subscription, which opens Apple's own subscriptions page.
6. Sponsored picks and ads
If you don't subscribe to Biteshot Pro, the Home screen shows one "Sponsored ยท Picks for you" card: a link to an Amazon search for something that may help with your goals, such as water bottles when you're behind on water.
- Matching happens on your iPhone. The app picks the link from what you've logged in Biteshot (today's totals against your goals, water, your goal, when you last weighed in, recent meals) and the time of day. None of this is sent to Biteshot, Amazon or anyone else. Apple Health data is never used.
- The list of picks is a public file the app downloads from Biteshot's website about once a day. That request carries nothing about you beyond what any web request does (your IP address).
- After you tap, you're on Amazon, and Amazon's privacy notice applies. The link includes Biteshot's Amazon Associates tag, so Amazon can tell the visit came from Biteshot.
- Biteshot earns a commission. As an Amazon Associate, Biteshot earns from qualifying purchases made through these links, at no extra cost to you.
- You can hide the card for the day with โ. Biteshot Pro removes it.
Ads (Google AdMob). If you don't subscribe to Biteshot Pro, Home also shows a small banner ad and, when no pick fits your day, an ad in the sponsored card. They come from Google AdMob.
- What Google collects. Google's ads software in the app collects your device's advertising identifier (only if you allow tracking), your approximate location from your IP address, how you interact with the ads, and diagnostic data such as crashes and performance, to show, measure and protect ads. See how Google uses information from apps that use its services.
- What Biteshot never shares. Your meals, photos, goals, weight and Apple Health data are never given to Google or any advertiser. Every ad request carries the same general topics (such as nutrition and recipes) for everyone.
- Your choices. iPhone asks whether Biteshot may track you; you can change it any time in Settings โ Privacy & Security โ Tracking. Where the law requires it (for example in the EU and UK), Google asks for your consent first, and Biteshot's You โ Privacy & about โ Ad privacy choices lets you change it. Biteshot Pro removes all ads.
- Ads are limited to content suitable for general audiences.
Videos played in the app. YouTube, TikTok and Instagram videos in the Library, on Dig In posts, in recipes and in the companion's chat now play in a player inside Biteshot, using each platform's official embed (YouTube's privacy-enhanced youtube-nocookie.com player, TikTok's embed and Instagram's embed). Biteshot sends nothing about you to these platforms: no account, meals, photos or health data, only the request for the video itself, which your iPhone makes directly to the platform. Biteshot uses YouTube API Services (the YouTube embedded player) to play YouTube videos. When the player opens and while you watch, the platform may set cookies and collect information under its own policy (Google/YouTube, TikTok, Instagram), and YouTube's own ads may play as part of its player. The player keeps nothing between videos (its cookies and storage are cleared when you close it). If a video can't be played inside an app, it opens in Safari's in-app viewer; only "Open in YouTube" (or TikTok, Instagram) in the player's menu leaves Biteshot. In Low Data Mode, video thumbnails aren't preloaded and a video loads only when you tap "Play video". Usage analytics (section 7a) count that a video was played (from the Library, a post, a recipe or the chat, and which platform) or couldn't play embedded (and why), never which video.
7. What Biteshot doesn't do
- No sign-in: the only profile is the optional, pseudonymous Dig In profile (section 1f)
- No advertising SDK other than Google AdMob, for free users (section 6). Usage analytics are described in section 7a
- No tracking across other companies' apps or websites unless you allow it when iPhone asks
- No selling or renting of your data. Your meals, goals and health data are never shared for advertising
7a. App usage and crash reports
Biteshot's own anonymous usage log (Help improve Biteshot). When the "Help improve Biteshot" switch in Settings is on (the same switch as above), the app also sends a small anonymous log to Biteshot's own server: which screen or button was used, for how long, a build number, the operating system version, your language and country code, and error codes. It is tied to a random ID made on your phone that is not connected to your Dig In profile, your Apple ID, your purchases or your other IDs, and that is replaced when you use Erase all, delete your Dig In profile or switch the setting off and on. It never contains meals, photos, dish names, anything you type, health data, your IP address or your location. Detailed records are deleted after about 14 days; only daily totals are kept. Turning the switch off stops it and deletes what was sent from that phone.
To see which features help and where the app gets in the way, Biteshot uses Google Firebase Analytics and Crashlytics. They receive events such as which screen was opened, that a scan finished or failed (with an error code), that a meal was logged and from which source, that a recipe was imported or exported (how, and how many) or a forgotten meal was found or logged (counts only), onboarding steps completed, whether a purchase went through and whether you're on the free, Pro or Ultimate plan, how quickly you're exploring the app (one word: slow, steady or fast, worked out on your iPhone from how often you open it and log, post or follow; the details stay on your iPhone), plus crash reports and basic device information (model, iOS version, app version, country). Companion use is counted (a turn happened, whether it was spoken, and which suggestion was tapped), never what was said. To see whether people keep coming back, events also carry the week you installed the app (for example "2026-W41") and how many weeks ago that was; that a Dig In post was shared or a dish was recreated is counted the same way, never the post, dish, caption or photo. They never receive your meals, food names, photos, notes, calories, goals, weight, workouts or Apple Health data, and they don't use your advertising identifier. In the EU, EEA, UK and Switzerland this is off unless you turn it on; elsewhere it's on and you can turn it off any time in You โ Privacy & about โ Share usage data. Google processes this data under its Firebase privacy terms.
Biteshot's own anonymous event log. The same switch, Settings → Privacy → Help improve Biteshot (called "Share usage data" before), also controls a small log on Biteshot's own server: which screens and buttons are used and for how long, how long a visit lasts, and error codes (crash reports go through the existing crash reporting above). It is identified only by a random number made on your iPhone, which is not linked to your Dig In profile, your Apple ID or any other ID, is replaced when you erase everything, delete your Dig In profile, or switch the setting off and on, and is replaced after about a year. The log never contains your meals, photos, dish names, anything you typed, health data, your IP address or precise location, and error messages are never sent, only numeric or short codes. Raw events are deleted after about 14 days; daily totals are kept. Switching the setting off stops everything, deletes the number and the unsent events from your iPhone and asks the server to remove what it holds for that number. It is on by default except in the EU/EEA, UK and Switzerland, where it starts off until you turn it on.
Getting started. The first-run questions are light and all but the language are optional: a first name (stored on your iPhone so Bitey can greet you; it goes with companion chats as described in section 1c), the app's language, cuisines you like, how you eat and any allergies or dislikes (stored on your iPhone, used to filter Dig In on your iPhone, and sent only with plan, recipe and companion requests as described in sections 1 and 1c), who you cook for (the same household setting meal plans use; it goes with a week plan request only on Biteshot Ultimate) and how often you cook (kept on your iPhone; it only changes which accounts are suggested to follow). Biteshot no longer asks for your age, sex, height, weight, activity or a goal when you start; calorie goals are optional and set later in Settings โ Profile & goals (they're stored on your iPhone and used as described in sections 1 and 1c). People you pick to follow at this step are kept on your iPhone until you choose a Dig In username, then followed like any follow (section 1f). Analytics record which step was reached or skipped, the language chosen and how many accounts were followed, never your name, diet, allergies or other answers.
8. Deleting your data
To delete everything Biteshot stores on your phone, go to Settings โ Your data โ Erase all meals and start over (on Android: Settings โ Privacy & about โ Erase all), or delete the app. Erasing also deletes the meals Biteshot saved to Apple Health. Biteshot's server doesn't keep photos, descriptions or preferences; the only things it keeps beyond about two days are your Dig In profile, follows and reactions until you delete them in the app, your groups and potluck parties (each potluck up to 90 days after it, and allergies or diets shared with one a week after it), Dig In reports (180 days), direct messages (a year after they were sent, or sooner as described in section 1f), scrambled contact codes for Find friends (until you replace or forget them, use Erase all or delete your profile; never used for matching after 90 days), the shared recipe-ingredient cache (ingredient names, amounts and the numbers worked out for them, not linked to a person, up to 180 days), the typed food Search cache (the words typed and the foods found, not linked to a person, up to 30 days), cached translations of AI cooks' posts (no personal data), for subscribers a monthly estimate of their AI use, kept with the App Store's anonymous subscription number for about 70 days so heavy use stays fair (fair use, see the Terms), the companion's natural voice for the app's own fixed lines (no personal data), the free-preview record and preview day described in sections 1 and 1a, scan feedback (section 1b, 180 days), and the companion's daily time counters (section 1c, about two days), which I'll delete if you email me. For anything already processed by Google, Groq or Open Food Facts, see their policies: Google Privacy Policy, Gemini API Additional Terms, Groq Privacy Policy, Open Food Facts privacy policy. To delete your Dig In profile, see how to delete your Dig In profile.
9. Children
Biteshot is not directed to children under 13, and I don't knowingly collect personal information from them. A Dig In profile is for people 13 and older; Biteshot doesn't ask for your age when you set up the app; before your first Dig In post, comment or follow it asks you to confirm that you are 13 or older and accept the terms. If you think a child under 13 has used the app to send information, contact me and I'll help.
10. Your rights
Depending on where you live, you may have rights to access, correct or delete personal information. Since Biteshot keeps your data on your own device, you can view, edit and delete it in the app. For any other request, email me.
11. Changes to this policy
If how Biteshot handles data changes, I'll update this page and its effective date. Significant changes will also be shown in the app.
11a. Biteshot for Android
Biteshot for Android works the same way as on iPhone, and everything above applies to it, with these differences:
- "Your iPhone" means your Android phone. Meals, photos, goals, preferences, allergies and health history stay in the app's private storage on your phone. Android can back up your plates (meals, photos, water and saved recipes) to your own Google account and copy them to a new phone; you can turn this off in Android's backup settings. Nothing else is backed up: not your health history, weigh-ins, Dig In account or settings. The cloud copy needs a screen lock, which makes it end-to-end encrypted. The secret that proves your Dig In profile is yours is kept in that same private storage instead of the iPhone's Keychain.
- Health Connect instead of Apple Health. Biteshot for Android can connect to Health Connect. It's off until you turn it on in Settings, and Android asks your permission first. If you connect it, Biteshot reads your steps, sleep, exercise sessions and active calories, and uses them only on your phone: to show your steps, workouts and sleep, and, if you choose, to add exercise calories to your budget. It's read-only: Biteshot never writes or changes anything in Health Connect. What it reads stays on your phone, except workout summaries (type, start, duration, calories and which app recorded them), which go to Biteshot's server for your Diary and are kept until you delete them or your account (section 1l). None of it is used for ads, sent to an AI or shared. You can turn it off in Biteshot's Settings, or remove the permissions any time in Health Connect or in Android Settings.
- Your install ID is a random number made by the app when it's first opened, kept in the app's storage. Clearing the app's data or reinstalling makes a new one.
- Purchases go through Google Play. When you subscribe, Google Play handles the payment; Biteshot never sees your card or Google account. To give you your plan, the app sends Biteshot's server the purchase token Google Play gives it, plus the product (for example Pro yearly). The server asks Google Play whether it's active and in which country it was bought, remembers the answer for a few minutes, and keeps only a monthly estimate of AI use under a one-way hash of the purchase token for about 70 days (fair use, as in section 8), the same way it does with the App Store's anonymous subscription number. Manage or cancel any time in Google Play โ Payments & subscriptions, or from the app's Settings in one tap. See the Google Privacy Policy.
- Ads (Google AdMob). If you're on the free plan, Google's ads software collects what section 6 describes. On Android it may use your phone's advertising ID, which you can reset or delete in Android Settings โ Privacy โ Ads. Where the law requires it, Google's consent form asks you first. Biteshot's own analytics (section 7a) never use the advertising ID.
- Talking: typing works everywhere; for voice, Android's keyboard microphone is used and that is between you and your keyboard app.
- Deleting your data: Settings โ Privacy & about โ Erase all deletes what's on your phone; Settings โ Dig In โ Delete account and data deletes your profile, follows and reactions from Biteshot's server. You can also ask by email: see how to delete your Dig In profile.
12. Contact
Aniruddha Daptardar, developer of Biteshot
biteshotapp@gmail.com