Privacy policy
This policy covers the Snap n Bite app and https://snapnbite.com. The separate Consumer health data privacy policy explains our health data practices, including choices for US users.
Who is responsible
Entegrix Ltd is the controller of information we process for this service. Company number: 16338087. Registered address: 167-169 Great Portland Street, London, England, W1W 5PF. Contact: support@entegrix.com.
Your choices come first
Bite AI, the AI in Snap n Bite, is powered by Anthropic's Claude models. Search, manual logging and your saved diary remain available if you decline Bite AI. Its photo, label and description features require a separate disclosure and affirmative choice before a request is sent. Old Bite AI choices do not automatically authorise a new purpose.
Your allergies and free-text foods to avoid stay on your phone unless you separately allow our server to use them for meal ideas. Sending those choices to Anthropic requires another affirmative choice. A checked local recipe library uses the server-processing choice when you submit health preferences, without sending them to Anthropic.
In Profile, open Health data choices to withdraw either health permission, or Photos and descriptions for Bite AI to withdraw Bite AI permission. Withdrawal stops future requests and cancels app requests in progress where possible. It cannot unsend a request already delivered. You can keep or remove local preferences separately. US users are also offered an optional local health-data choice before body and target setup; declining permits the manual diary without a body profile.
What stays on your phone
The optional household meal planner stores household names or nicknames, ages, food and health choices, pantry stock, prices, receipts, plans and ratings locally. Its calculations run on your phone. JSON imports require a preview and explicit local replacement choice; imports cannot grant Bite AI permissions or purchase access. You can export a readable JSON backup or explicitly share an offline plan through another app. A shared backup can reveal household health information, and we cannot recall copies you send. There are no family accounts or live shared-list synchronisation in this build.
Your diary, meal thumbnails, saved recipes, weight history, body profile, goals, pregnancy or breastfeeding choices, eating-disorder response, hidden-numbers preference and consent records are stored locally. We do not send your body measurements, weight history or eating-disorder response to Bite AI or Anthropic. If you are pregnant or breastfeeding and allow it in Health data choices, that setting goes with meal-idea requests, so the recipes follow NHS food advice for pregnancy: the server-processing choice covers our checked recipe library, and the separate sending choice is needed before it goes to Anthropic with a Bite AI request. It is not stored by us. The app uses a birth date locally to enforce an adult age gate; the manual diary saves only the completed adult check, not a body profile. If the check shows someone is under 18, the app closes and keeps on the phone only the date it may open again, which is not sent to us and is removed by Delete my data.
The optional local wellness features also keep water entries, exercise, fasting windows and manually selected prayer-time location, custom macro goals, body measurements and progress photos. Insights and habit summaries are calculated locally. Progress photos are kept in the app's private storage and are not sent to Bite AI. Reminders need your separate notification choice. They use generic text rather than displaying diary or body details.
You can deliberately export a CSV, PDF or full app backup to a file or app you choose. These copies can reveal food, body, household and imported health information; a full backup can include selected meal and progress photos. Exported files are readable copies, not an encrypted cloud vault. Review the export choice and protect the destination. Restore needs a preview and explicit replacement choice; a backup cannot grant Bite AI, health, operating-system or payment permissions. There is no automatic app cloud backup or live household account.
Delete my data removes local records, app-owned meal thumbnails and progress photos, widget snapshots and temporary app export files. Temporary upload images are cleared after preparation and during deletion. Original gallery photos and files you explicitly exported elsewhere are not deleted. The Android app disables automatic OS cloud backup and excludes its private files, databases and settings from device transfer. Copies already made by another app, a previous version, or a recipient remain under that service's and your device's control.
Optional Android Health Connect
In Profile, you can separately allow reading steps, workouts and associated active energy, weight, body-fat percentage or height from Health Connect. The app reads the recent 30-day window while it is open, keeps source-attributed copies locally, and does not send these imported records to our server or to Anthropic, which powers Bite AI. Readings do not silently replace your body profile. Exercise energy changes a food target only when you separately choose exercise add-back.
You may separately allow writing your logged meal nutrition, water and manually entered weight to Health Connect. Unknown nutrients are omitted rather than reported as zero. Health Connect and other apps you authorise may then use those records under their own settings and policies. We request no heart-rate, sleep, medical-record, background-health or extended-history permission.
Permissions are checked before each sync. You can disconnect in the app or change individual permissions in Android Health Connect. Disconnect clears imported copies and stops future sync. Delete my data also attempts to remove only records Snap n Bite wrote, using its local ownership record, and to revoke permission. If permission or the service is unavailable, the app explains the remaining manual cleanup. Android may require the app to close and restart before revocation completes. Records from other apps, and copies those apps have already made, are not deleted by us.
Voice, home-screen widget and shortcuts
Voice is optional text input. Microphone access is requested only after you tap it. The app first checks for an installed on-device recogniser in your chosen language. If that is unavailable, you can type or separately choose an online phone recogniser after a disclosure that audio may reach its provider. There is no automatic switch to online recognition. Snap n Bite does not store audio files or receive your audio on its server. Recognised text remains editable; only a later explicit food-analysis action sends that text to Bite AI as an ordinary description. The chosen online recogniser's processing and retention are governed by its provider.
A home-screen widget can display today's meal count, water and optional remaining energy and macro progress. Hide numbers removes calorie and macro values from the widget too. Widget data stays in the app's private storage. We declare home-screen placement and use Android 16's lock-screen opt-out, but older or vendor launchers may behave differently. Check where your launcher places it: anyone who can see that screen may see the widget. App-icon shortcuts open review screens and do not log a meal, start recording or upload data automatically.
What a request sends
Barcode lookup checks your confirmed phone cache and our packaged-food tables first. If these do not have the barcode, the app asks Open Food Facts directly from your phone. That service receives the barcode, your network IP address and our app name/version. This request does not include our installation ID, your diary, allergies or body profile. Open Food Facts is a community database credited under ODbL 1.0; check your packet before confirming a result. Up to 100 complete labels you explicitly check, including your corrections, can be cached on your phone and are removed by Delete my data. A failed lookup offers label photo or manual entry.
If a request gets no answer from our server, the app makes one plain request to Google's connectivity check at connectivitycheck.gstatic.com, the address Android itself uses on every network, so it can tell you whether the problem is your connection or our server. Google receives your network IP address and nothing from the app: no installation ID, food or health details.
Food search sends the words you type, your selected country, the app language and your favourite cuisines to our server, so it can rank familiar foods. Packaged-food search sends the product words you type and selected country to our server to search the installed USDA and Open Food Facts tables. Ordinary technical request metadata reaches our hosting provider. These requests do not include your diary, allergies or body profile, and our application does not save the search text in its database or logs. When a search, a typed list, a menu dish or a packaged search finds nothing, you can tap Estimate it: the words you typed, your country, the app language and your food preferences then go through our server to Anthropic for a Bite AI estimate, under the same Bite AI choice as a scan, and it uses some of your monthly Bite AI scans. Our server keeps no copy of your words; if Bite AI names a food that none of our food tables holds, the server counts that food's name, as described under the small records our server keeps. Words you keep for later while offline stay on your phone until Today estimates them with a connection, and are removed by Delete my data.
The frequent unknown-food review list stays on your phone until you choose Share this review list. Sharing opens your phone's share sheet with a week-ending date, food names, counts and public food references. It does not include diary entries, profile fields or health preferences. A food name you enter can itself reveal personal information, so review the list before choosing a recipient. Nothing is sent automatically. You can clear the local list; copies already shared are handled by the recipient and the app you choose.
- For a Bite AI request: the selected image or food description, confirmed ingredients where applicable, and the food preferences needed for that feature. Images can accidentally contain personal information, so keep people, documents and screens out of the shot.
- For meal ideas: vegetarian or vegan choices, cuisines, servings and time, plus allergies or foods to avoid only after the health choices above. Halal is an optional preference with its own choice before transmission. These preferences may reveal sensitive information.
- Country, language/locale and calendar month provide regional context; household oil preference can adjust estimates. If you saved a plate size, its diameter and whether you measured it go with a plate photo as a rough guide. Selected country and Cloudflare's coarse request country determine whether Bite AI is available, and are kept, as a country code only, with the anonymous counts described below. We never request precise or background location; Eating out asks for approximate location only when you tap it, as described below. In the meal planner, Use my nearest city asks our server to name the city in the official price report nearest the approximate location Cloudflare reads from your connection; that location is used for that one answer and is not stored.
- A random installation ID, app version and ordinary technical request metadata support request handling and fair-use limits. A barcode lookup sends its code and country to our server; a manual label entry need not upload a photo.
Photos, descriptions, reviewed recipe text, health preferences and model answers are processed for the requested response and are not written to our application database or request logs. The one exception is the anonymous count of the name of a food our tables could not find, described below, which keeps nothing else from the request. The app does not automatically upload your diary. Deliberate exports and Ask Bite AI questions, described above, have their own choices. A request that has already reached a provider is subject to that provider's retention described below.
The small records our server keeps
| Record | Purpose and retention |
|---|---|
| Installation and network counters | Fair-use and abuse prevention. A salted, one-way network hash is separate from the installation ID. Normal scan, menu, ingredient photo, recipe page, recipe, Ask Bite AI question and report counters are pruned by a daily cleanup. The monthly Bite AI allowance counters (scans, with their menu, ingredient photo and recipe page limits, recipe requests and questions, per calendar month) are kept for the current and previous month only, so October’s are deleted on 1 December. Daily report and network counters are deleted after yesterday, normally within three days. |
| Bite AI attempt and cost records | Provider attempt counts and estimated/reserved cost enforce a service budget. They contain no request images, descriptions or health preferences and are pruned after yesterday. |
| Problem reports | Only if you choose Report a problem: answer reference, result kind, selected reason and optional note, up to 500 characters. No photo, installation ID or IP address is stored with a report. Reports expire after 365 days. Avoid putting personal or health information in the note. |
| Names of foods we could not find, and other anonymous counts | When Bite AI names a food in a photo, a menu, a takeaway order or words you typed or said, and none of our food tables has a record for it, our server adds one to a count for that food's name, with the country you chose in the app and the date. If the app reports that foods were corrected or estimates used, the server adds them to a daily total of those events with the date and the country Cloudflare reads from your connection. Nothing that identifies you or your device is kept with these counts: no installation ID, network address, request reference, time of day, photo, note, amount or other words of the request. Long names, and names with numbers, @ signs, web addresses or words that make a sentence, are not kept at all. We use the counts only to find the foods people eat that our tables lack or get wrong, so we can add or correct them, and we will not try to link them to anyone. They are deleted after 180 days by the daily cleanup. Because nothing in them points to you, Delete my data cannot find them. Ordinary network metadata still reaches our hosting provider. |
| Google Play purchases, only when plans are enabled | We process a purchase token to verify with Google, then store its one-way hash, installation ID, product, expiry, verification time, active state, the time you last restored it to a new installation and the billing country Google reports for it, which sets the plan's monthly Bite AI allowance. Raw purchase tokens and payment card details are not stored in our database. Expired entitlement records are removed after 30 days by the daily cleanup, or earlier through Delete my data. Separate purchase-check abuse counters expire after three days, with the daily cleanup margin. |
| Technical logs | Request reference, timings, error category, AI model/capacity and safety-filter counts support reliability. Our application does not log request photos, bodies or raw purchase tokens. Hosting-provider log and backup retention depends on the deployed configuration and provider terms. |
| Messages you send us | Your contact details and message are used to reply and handle requests. Early-access contacts are kept until launch notification or withdrawal; other correspondence is kept for up to two years after the last message unless a legal obligation requires longer. |
Who processes information
Eating out and nearby places. Food places near you are looked up only when you tap Use my approximate area. Android then asks whether Snap n Bite may use your approximate location; the app never asks for precise or background location. Your phone rounds the point to an area of about 4 km at once, and only that rounded area goes to our server, which rounds it again and answers from its own copy of Overture Maps Places, an open list of businesses. No diary, household choices, allergy list, photo or installation ID goes with this search, and our application does not store the area or write it to its logs; ordinary network metadata still reaches Cloudflare, as for any request. The list of places is kept in app memory for up to 24 hours. Places you choose or type are kept on your phone as recent places, with any meals out you plan, until you remove them or delete app data. You can type a place instead and share no location at all. Dishes and calories at a place come from the app's own food tables and the chains' published menus, so most are estimates. Opening a place or directions in Google Maps is an explicit action: Google receives the place you open under its own terms.
Cloudflare hosts our website, API and database. It processes requests, including network addresses and coarse country metadata, to deliver and protect the service. Its network logs and database recovery copies are governed by the configured service and Cloudflare data processing terms.
Anthropic powers Bite AI: Bite AI runs on Anthropic's Claude models, and Anthropic processes the requests you choose to send to it. Those are the plate, ingredient, label and menu photos, order screenshots and bill photos, meal descriptions and notes, typed food names, recipe page text and Ask Bite AI questions described above, with the food preferences, country and language each request needs. Its commercial API retention policy normally deletes inputs and outputs within 30 days; contractual settings, covered models, safety investigation and legal requirements can change that period. Some flagged content may be retained longer. We do not promise zero retention or a universal 30-day maximum. See Anthropic's commercial retention policy and API data-retention details. We do not submit requests for training; provider commercial use is governed by its applicable agreement.
Google distributes the Android app and handles any enabled Google Play subscription, billing, refunds and account records under its own terms and privacy policy. Our server verifies eligible purchases with Google. We never receive your payment card details.
The Android barcode camera includes Google ML Kit. Its bundled SDK can send device and app information, a per-installation identifier, performance and API configuration information, and feature/error events to Google for diagnostics and usage analytics. This SDK processing is separate from our own anonymous counts described above. Barcode recognition runs on the phone; this disclosure does not mean your camera images are uploaded to Google. See Google's ML Kit data disclosure for the SDK categories. You can type a barcode instead of using the barcode camera.
We do not sell or rent personal or consumer health data, use advertising trackers, share health data with data brokers, or create advertising audiences. Service providers receive only the information needed for their function. Disclosure may also be required by law or necessary to protect legal rights. A corporate transfer must preserve applicable privacy obligations and rights.
UK and EEA processing and transfers
Where UK GDPR or EU GDPR applies, we use the requested service and contract basis for ordinary feature requests, explicit consent for optional health data processing and transmission, legitimate interests for proportionate security and service reliability and for the anonymous counts that show us which foods to add, and legal obligations where required. Optional Bite AI and health choices may be withdrawn without losing manual logging. We do not make decisions with a legal or similarly significant effect solely by automated means.
Providers may process data outside your country, including in the United States. Applicable data processing agreements and transfer safeguards, such as standard contractual clauses and the UK Addendum where needed, must cover those transfers. Contact us for information about the safeguards applicable to your request. Whether Bite AI is available differs by region.
Access, deletion and other rights
Use Profile to edit local data and Delete my data to remove app records and request removal of installation-linked server counters and purchase entitlements. An unresolved remote deletion is recorded durably for retry; local deletion does not silently erase that pending request. You can also email support@entegrix.com. We may need limited information to verify a request and find the relevant record. We cannot locate anonymous totals or a report by a name we never stored.
Where applicable, you can request access, correction, deletion, restriction or portability, object to processing, and withdraw consent. UK users may complain to the ICO; EEA users may contact their local supervisory authority. US consumer health rights and appeal options are described in our Consumer health data privacy policy. We respond within the period required by applicable law and explain any lawful exception.
Deleting app data does not cancel a Google Play subscription. Manage or cancel it in Google Play. Data already sent to Anthropic for Bite AI cannot be recalled by deleting the local diary; contact us for help with a provider deletion request.
Changes and age
The app is for adults aged 18 and over. Contact us if you believe a child has submitted information. We update this page when practices change and request a fresh choice before using consent-based information for a materially new purpose.