Privacy Policy
Bite is a calorie and nutrition tracker. You tell it what you ate, it works out the foods and their nutrition, and it keeps that in your diary. This page explains what Bite stores while doing that, who else touches it, and how to get rid of it.
Who this is from
Bite is the mobile app described on this site. Where this policy says “we”, it means the team that builds and runs Bite. If you want to reach a person about anything here, write to support@heybite.app.
What Bite collects
Only what the app needs to work. There is no advertising, no tracking across other apps or sites, and no data broker anywhere in this.
You sign in with Google or Apple. Bite receives your name, email address and the identifier that provider gives us. Bite never sees or stores your Google or Apple password.
If you sign in with Google, Bite asks Google only for your basic profile: your name, email address and Google account identifier. Bite uses them for one thing — creating your Bite account and signing you back in to it. Bite does not request access to your Gmail, contacts, calendar, files or any other Google data.
This information is stored with your account for as long as the account exists and is removed when you delete it — see section 09. It is never sold, never used for advertising, and never shared with anyone except the service providers that run Bite on our behalf. Bite's use and transfer of information received from Google APIs adheres to theGoogle API Services User Data Policy, including the Limited Use requirements.
The details you enter during setup or change later: your age, height and weight, then your goal weight and body fat percentage, and the daily calorie target and macro split you set yourself.
Every food you log: its name, portion, calories, protein, carbs and fat, which meal it belongs to, the date and time, and whether its numbers came from the food database or from an estimate. Your meal history stays until you delete it.
When you record a meal, the audio is sent to Bite's server and on to a third-party AI service that turns it into text. That text is kept with the meal. The recording itself is not kept — see section 03.
If you add a food to Bite's database, the food entry and the name shown on your profile are visible to other people using Bite and on the contributor leaderboard. Nothing else from your account is.
Your timezone, so a day starts and ends when it does for you, and — if you allow notifications — a push token from Apple or Google so reminders can reach your device. Turning notifications off in your system settings stops this.
Whether your subscription is active, when it renews or lapses, and the anonymous purchase identifiers needed to check that. Payment is handled by Apple or Google — Bite never receives your card details.
When something breaks, Bite records what failed, along with the app version, device model and operating system, so it can be fixed. These reports are technical and are not used to build a profile of you.
When you sign up for the waitlist, Bite stores your email address so we can tell you when the app is ready. When you send a contact message through this site, Bite sends your name, email address and message tosupport@heybite.app so someone can reply, and does not store it.
Voice recordings are not stored
Your audio is deleted as soon as the meal has been processed — on your device and on the server. Bite keeps no audio files, no recording archive and no voice profile.
The recording exists only for the length of a single request. It is transcribed, the text is read for foods and quantities, and the audio is discarded as part of finishing that request. What remains is the transcript and the foods it produced, both attached to the meal in your diary. Delete the meal and the transcript goes with it.
Voice logging uses third-party AI
Bite does not run its own speech or language models. When you record a meal, your data is shared with these third-party AI services, each for one step:
None of them receives your name, email address or account details with this data, and none of them is allowed to use it for advertising. Bite itself never saves the audio. Voice logging is optional: if you would rather your meals were not processed this way, search for foods and add them by hand instead. Using voice logging means you agree to this processing.
How Bite uses what it collects
Bite does not sell your data, does not share it for advertising, and does not use your meals to build an advertising profile.
Third parties that process data
Bite uses a small number of services, each for one job, and each receives only what that job needs.
Speech-to-text (third-party AI). Receives your voice recording for the length of the request and returns its text. Bite does not store the recording.
Meal understanding and nutrition estimates (third-party AI). Receives the text of what you said, never the audio. Content sent through the API is not used to train OpenAI's models.
Food matching (third-party AI). Receives food names and search text and turns them into search vectors so they can be matched against Bite's food database.
Database and sign-in. Stores your account, profile, targets and diary on Bite's behalf.
Crash and error reports. Receives technical details of what went wrong, with personal and health details removed first.
Sign-in, in-app purchases and push notification delivery. They handle payment and hold the account you sign in with; their own privacy policies apply to that.
Subscription management. Receives purchase receipts and an anonymous identifier so Bite knows whether Bite Pro is active. It does not receive your meals.
Data may be processed on servers outside your country, including in the United States. We may also disclose information if the law requires it, or to protect Bite and the people using it.
AI-estimated nutrition
Bite matches every food against nutrition data first. Where there is a confident match, the numbers come from that entry. Where there isn't, Bite estimates them from your description and marks the food as estimated in your diary, so you can always tell which figures are looked up and which are approximated. Estimates are approximations, not measurements.
How long things are kept
Security
Data is encrypted in transit and at rest, and access to it is limited to the people who need it to run the service.
Your choices and deleting your data
You can edit or delete any meal, food or profile detail in the app at any time. Deleting your account removes your profile, meals, transcripts and targets from Bite's systems within 30 days, other than anything we are required to keep by law. Delete your account from Profile in the app, or emailsupport@heybite.app and we will do it for you.
Depending on where you live, you may also have the right to a copy of your data, to correct it, or to object to how it is used. Ask at the same address.
Changes to this policy
If this policy changes, the date at the top changes with it. For anything significant, Bite will tell you in the app before it takes effect.
Contact
Questions about privacy, requests about your data, or anything else:support@heybite.app.