Legal
Privacy Policy
The short version. Your food diary stays on your phone. We hold an account for you: your email address and whether you have paid, your name and picture if you sign in with Google, and a record of any payment made on our website. Nothing else. A meal photo you choose to scan is sent for analysis and then discarded. The app has no tracking. Only our website measures visits and ads, as described below.
What stays on your phone
All of the following is written to your device's local storage. It is never uploaded, and we have no copy of it:
- Your profile: name, gender, age, height, weight, goal weight, activity level and dietary preference
- Your calorie and macronutrient targets
- Every meal you log, including any photo you attach to it
- Weight history, water intake, saved foods, favourites and recipes
- App settings such as language, appearance and reminders
We cannot read any of it. Uninstalling the app deletes it. Because the diary is not synced, it does not move to a new phone on its own. Only your subscription does.
What we hold on our servers
BiteIt needs an account so that a subscription you paid for survives a new phone. The account record is deliberately small:
| What | Why | Kept for |
|---|---|---|
| Your email address | It is the account. It identifies you when you sign in and is where a sign-in code is sent. | Until you delete the account |
| An account identifier | A random ID that links you to your subscription record. | Until you delete the account |
| Your name and profile picture Google sign-in only |
Passed to us by Google. Shown on the Account screen so you can see which account you are signed in as. | Until you delete the account |
| Subscription status | Which plan you are on, where it was bought, and when it expires. | Until you delete the account |
| A record of each website purchase biteit.pro purchases only |
The email it was for, the mobile number you gave, the plan, the amount, the payment's reference number and when that premium ends. It lets us check a purchase, and reach you, if something goes wrong. | As a record of the sale, including after the account is deleted |
That is the whole of it. No meals, no photos, no weights, no targets.
If you sign in with Google, Google also passes us the name and profile picture on your Google account, and we store them alongside your email. They are used for one thing: showing your name and picture on the Account screen so you can see which account you are signed in as. They are not used for anything else, and they are deleted with your account.
Nothing else comes across. Not your contacts, not your files, not your Google activity, and nothing else in your Google account. If you sign in with an email code instead, no name or picture is collected at all.
What leaves your phone when you scan a meal
Only when you actively scan or describe a meal:
| What | Where it goes | Kept for |
|---|---|---|
| The meal photo, or the text you typed | Our processing server, then Google's Gemini API, which returns the estimate | Not stored. It is held in memory for the request and discarded. |
| Your IP address and a random install identifier | Our processing server | Counters only, cleared automatically about an hour later |
The IP address and install identifier are used for one thing: counting how many analyses have been requested, so the service cannot be run up as a bill by automated abuse. They are not attached to your meals or your diary.
Google processes the image under its own terms. See Google's Gemini API terms.
Crash reports
When the app crashes, a report is sent to Sentry, an error-tracking service, so the bug can be found and fixed. A report contains the error and where in the code it happened, the app version, your Android version and your device model.
It is configured not to send the contents of your diary. Personal data is switched off at the source, and the trail of recent actions that crash reporters normally attach (which is where a meal name or a weight could otherwise appear) is stripped from every report before it is sent.
Payments
BiteIt never sees your card. A subscription bought on Android is processed by Google Play, under Google's own privacy policy, and we are told only that a purchase happened and when it expires.
Purchases are managed for us by RevenueCat, which receives the purchase token from Google Play and your account identifier so the subscription can be attached to the right account.
A purchase on biteit.pro is paid with bKash, Nagad or Rocket on a payment page that UddoktaPay runs for BiteIt. When you start one, the email address and mobile number you typed are sent to UddoktaPay with the plan and the price, so the payment can be matched to you. With them go your browser type and Meta's cookie ids, if there are any, so that a completed purchase can be reported to Meta (see “On our website” below). You then pay from your own wallet, so UddoktaPay also sees the number you pay from and the transaction ID. It keeps its own record of the payment, including one you start and do not finish, and tells us whether it completed and for which email and plan. We do not store your wallet number or the transaction ID. The mobile number you typed is kept with the purchase record, and used only to contact you about that payment.
Nothing is created on our side for a payment that does not complete: no account and no premium. A completed one creates your BiteIt account for that email address, if there is not one already, so that you can sign in, and an email goes to that address explaining how to sign in to the app. Opening the payment page also records your IP address for a day, only to stop the page being used to flood the payment system. The payment page in your browser keeps the email you typed for that tab only, to show it back to you when you return.
On our website
This part is about biteit.pro only. The app has none of it.
Meta Pixel. Tells Meta how many people came to the site from a Facebook or Instagram ad and how many bought, so the ads reach the right people. For this Meta sets cookies in your browser and learns which pages you opened, whether you started a purchase and whether you finished it. Meta uses this under its own terms.
PostHog. Counts how many people visit, which pages they see and where they get stuck. It may also keep a recording of how you scrolled and tapped on a page, but what you type into a form (email, mobile number) is not in it. You are not identified by name or email.
When a purchase completes, our server also tells Meta: which plan, how much, and your email and mobile number, hashed, meaning turned into a code the address or number cannot be read back from. Meta compares it with what it already holds to see whether the purchase came from one of its ads, and who to show ads to.
If you don't want this, block trackers in your browser or clear its cookies. The site and purchases work the same.
Who else is involved
| Service | What it does for BiteIt |
|---|---|
| Google Gemini | Reads the meal photo and returns the estimate |
| Supabase | Hosts the sign-in system and the subscription records |
| Resend | Delivers the sign-in code, and the sign-in steps after a website purchase, to your email |
| Sentry | Receives crash reports |
| Google Play & RevenueCat | Take the payment and tell us whether it is still valid |
| UddoktaPay | Runs the payment page for purchases made on biteit.pro and tells us when one completes |
| bKash, Nagad, Rocket | Move the money for a website purchase, under their own terms |
| Meta | Measures how many people come to biteit.pro from its ads, and how many buy |
| PostHog | Counts visits to biteit.pro and shows where people get stuck |
Each one receives only what it needs to do that job, and none of them receive your food diary.
Camera and photos
Camera access is used only while a scanning screen is open, to photograph a meal, a barcode or a nutrition label. Photo library access is used only when you pick an existing picture. BiteIt does not browse, scan or upload your photo library, and takes no photo you did not trigger.
Notifications
If you enable reminders, they are scheduled by your phone locally. No notification is sent from a server, and no data leaves the device to produce one.
What we do not do
- No advertising in the app, and no advertising identifiers
- No behavioural or usage analytics in the app. We do not track what you do in the app
- No selling of personal information, and no sharing beyond what this policy describes
- No location collection
- No uploading of your diary, your photos or your weight history
Children
BiteIt is not directed at children under 13, and calorie targets are calculated with formulas intended for adults. We do not knowingly collect data from children.
Your control
Your diary is yours to erase directly. You can delete any individual meal, weight or water entry from inside the app, and uninstalling BiteIt removes everything (diary, photos, weights and profile), because all of it is stored on the device. Neither needs a request to us, because we never had a copy.
Settings → Reset restarts the setup questions and clears your profile and targets. It does not delete your logged meals or weight history.
For the account we do hold, you can ask us to delete it at any time, along with your email address and your subscription record. A website purchase record stays, as described above. The account deletion page explains how, and what happens to a subscription that is still running.
Not medical advice. BiteIt estimates calories and macronutrients for general wellness. Estimates from photographs are approximate and can be wrong. It is not a medical device and does not provide medical advice. Talk to a qualified professional before making significant dietary changes, particularly if you are pregnant, managing a health condition, or have a history of disordered eating.
Changes
If this policy changes materially, the date above will be updated and the new version published here before the change takes effect.
Contact
Questions about this policy: hello@biteit.pro
See also the Terms of Use.