Data safety summary
What we collect, in one table.
Last updated: 4 October 2026
Summary
In plain words
We collect what the app needs to work. We do not show ads and we do not sell or share data for advertising.
This page matches the Data safety section on our Google Play listing. For the full detail, read the Privacy Policy.
- No ads. No selling or sharing of data for advertising.
- Data is encrypted in transit (HTTPS/TLS).
- Health-related data is used only to provide the app’s features.
- Purchases go through Google Play Billing. The app never sees card details.
- You can ask us to delete your account and cloud data: see Delete your account and data.
Data types
| Data type | Collected or shared | Purpose | Optional or required | Encrypted in transit | Can be deleted |
|---|---|---|---|---|---|
| Personal info Name, email address, user IDs. | Collected. Not shared. | App functionality (sign-in, account), analytics. | Optional (only if you create an account). | Yes | Yes, on request. |
| Health & fitness Weight, nutrition (calories, protein, carbs, fat). Profile answers such as age, sex and height. | Collected on device. Uploaded only for signed-in users: daily summaries (30 days) and the Pro backup. Not shared. | App functionality, personalisation. | Optional. | Yes | Yes, on request. On-device data is cleared by Reset all data or uninstalling. |
| Photos Meal photos sent for AI analysis. | A downscaled copy is processed by Google’s Gemini model through Firebase AI Logic. We do not store it on any server. Photos are never backed up. | App functionality (food recognition). | Optional (only when you use an AI scan). | Yes | Not stored by us. Photos on your device are deleted with the app. |
| App activity App usage events: sign up, onboarding, meal logged (meal type), weight logged, photo scan, paywall viewed, purchase, export. No calorie or weight values. | Collected. Not shared for advertising. | Analytics. | Required for analytics events. | Yes | Tied to your user ID when signed in. Anonymised data is kept by Google for up to 14 months for analytics data and 90 days for crash reports. |
| App info & performance Crash logs, diagnostics, performance timings, app version. | Collected. Not shared for advertising. | Analytics, app stability and performance. | Required. | Yes | Anonymised data is kept by Google for up to 14 months for analytics data and 90 days for crash reports. |
| Device or other IDs Identifiers created by Firebase for analytics and crash reporting. | Collected. Not shared for advertising. | Analytics, app stability, fraud prevention (App Check). | Required. | Yes | Kept by Google for up to 14 months for analytics data and 90 days for crash reports. |
Notes
- Meals, foods, weigh-ins, profile answers and settings are stored on your device. For signed-in users, summaries and a Pro backup are stored with Firebase (Google).
- “Shared” in Play’s sense means given to a third party for its own use. Google acts as our service provider for Firebase and Gemini, so these are declared as collected, not shared.