KetoTrue Privacy Policy
- Your profile, weight, food, ketone and other health logs stay on your phone. We have no server and no access to them.
- There is no account, no sign-in and no analytics.
- The free version shows ads from Google AdMob. Google receives device and advertising identifiers, but never your health or food data.
- Online food search sends only the words you search for to Open Food Facts. Label photos are read on your phone and never uploaded.
Who we are
KetoTrue ("we", "us") is the developer of the KetoTrue app for Android and iOS. This policy explains what happens to your information when you use the app.
Contact: sabuj.cse.diu@gmail.com
Information stored on your phone
To calculate your targets and your measured maintenance calories (TDEE), the app stores what you enter in a database on your phone:
- Profile: sex, age, height, weight, body fat (if you enter it), activity level, goal, keto status, units and nutrition-label region.
- Daily logs: weight, foods and their nutrients, ketone and glucose readings, sodium, potassium and magnesium, and notes.
- Your own foods and app settings, such as language.
This information is never uploaded by the app. We cannot see it, and we cannot recover it if you lose your phone.
Your phone's own system backup (for example, Android backup to your Google account) may include app data, depending on your phone's settings. That backup is handled by your phone's maker, not by us.
Backups and exports you make
In Settings you can export a backup (JSON) or your daily totals (CSV). The file goes wherever you choose in your phone's share sheet, such as email, a cloud drive or another app. After that, the file is handled by the service you picked, under its own privacy policy. Restoring a backup reads a file you select and does not send it anywhere.
Advertising (free version)
The free version shows banner and full-screen ads from Google AdMob, provided by Google LLC (Google Ireland Limited for users in the EEA, UK and Switzerland). To show and measure ads and to prevent fraud, the Google Mobile Ads SDK in the app collects and shares with Google:
| Data | Examples |
|---|---|
| Device and advertising identifiers | Android advertising ID, or on iPhone the IDFA if you allow tracking |
| Approximate location | Derived from your IP address |
| App interactions | Ad views and taps, app launches |
| Diagnostics | Ad loading performance and crash information from the ads SDK |
Nothing from your logs is sent to Google: no weight, food, ketone, health or profile data.
Ads are limited to content suitable for general audiences (rated PG).
Your ad choices
- EEA, UK and Switzerland: before any ads load, the app shows Google's consent form. You can choose personalised ads, non-personalised ads, or refuse. You can change your choice at any time in Settings → Ad privacy choices in the app.
- Android: you can reset or delete your advertising ID in your phone's settings (Settings → Privacy → Ads, or Settings → Google → Ads, depending on your phone). Without it, ads are not personalised.
- iPhone: the app asks for permission to track. If you choose "Ask App Not to Track", the IDFA is not shared and ads are not personalised. You can change this in Settings → Privacy & Security → Tracking.
Learn how Google uses this data: How Google uses information from apps that use its services and the Google Privacy Policy.
Online food search
When a food isn't on your phone, the app can look it up in Open Food Facts, a free, non-profit food database run by the Open Food Facts association in France. It searches automatically only when nothing on your phone matches; otherwise you tap Search online.
- Sent: the words you type in the search box, the app's language and your phone's country (so products sold where you shop come first). Like any web request, Open Food Facts also receives your IP address.
- Not sent: your logs, profile, weight, health data or any identifier for you.
- When you add a food from the results, it is saved on your phone so it works offline next time. Nothing is sent back to Open Food Facts.
Open Food Facts handles these requests under its own privacy policy. Food data from Open Food Facts is available under the Open Database License (ODbL).
Label scanner (camera and photos)
You can fill in a food from a photo of its nutrition label, taken with the camera or chosen from your photos. Text recognition runs entirely on your phone (Google ML Kit on Android, Apple Vision on iPhone). The photo is never uploaded or stored by the app, and only the numbers you choose to save are kept.
Removing ads (in-app purchase)
You can buy a one-time upgrade that removes ads. Payment is handled entirely by Google Play or the Apple App Store; we never see your card or payment details. The app only receives confirmation that the purchase was made, and stores a note on your phone that ads are removed. To check for a refund, the app asks the store on launch whether you still own the upgrade.
Permissions
- Internet: to load ads and Google's consent form, for online food search, and for in-app purchases.
- Camera: only when you tap Scan label, to take the photo. You can refuse and choose a photo instead.
- Photos: the app uses your phone's photo picker, so it can only see the one photo you select. It does not ask for access to your photo library.
The app does not ask for your location, contacts or microphone.
Sale and sharing of personal information
We do not sell your information. Sharing advertising identifiers with Google for ads may count as "sharing" for cross-context behavioural advertising under some laws, such as California's. You can opt out with the ad choices above.
Keeping and deleting your data
- Your logs stay on your phone until you delete them.
- To erase everything, use Settings → Delete all data in the app, or uninstall the app.
- Backup and CSV files you exported are not deleted by the app. Remove them from wherever you saved them.
- Data that Google collects for ads is kept and deleted under Google's policies.
- Search requests received by Open Food Facts are handled under its privacy policy. The app keeps no record of your searches.
Security
Your data is stored in the app's private storage, which other apps cannot read, and is protected by your phone's own encryption. A screen lock on your phone helps keep it safe. Exported files are not encrypted, so store them somewhere you trust.
Your rights
Depending on where you live (for example, under the GDPR or UK GDPR), you may have rights to access, correct, delete or object to the processing of your personal data. Because your logs exist only on your phone, you can view, change, export and delete them yourself in the app. We hold no copy. For data collected for ads, use the ad choices above or contact Google. You may also complain to your local data protection authority.
Where the GDPR applies, the legal basis for personalised ads is your consent, which you can withdraw at any time. Storing your logs on your phone is needed to provide the app's features.
Children
KetoTrue is a diet and health tool intended for adults. It is not directed to children under 18, and we do not knowingly collect information from children.
Not medical advice
KetoTrue gives estimates, not medical advice. Don't use it for medical keto (such as epilepsy treatment), type 1 diabetes, pregnancy or eating disorders without your doctor.
Changes to this policy
If we change how the app handles data, we will update this page and its effective date. Significant changes will also be noted in the app's release notes.
Contact
Questions or requests about privacy: sabuj.cse.diu@gmail.com