CalorieVault Privacy Policy
Last updated: 11 October 2026.
CalorieVault has no account, no server and no analytics. This page goes through every permission and says exactly what the app does and doesn't do with your data. Nothing's left out.
This isn't written to tick a legal box in the hope nobody reads it. What you eat and weigh is about as personal as data gets, and turning it into an analytics feed would only ever benefit us, so we don't build it that way. Here are the specifics.
Where your data lives
Every weigh-in, diary entry, custom food, recipe, body measurement and setting is stored in a local database on your device only. None of it is ever sent to Meltware. It only leaves your device when you tell it to. Backups and exports go only to a place you choose and control (see "Backing up your data" below). Anything sent to a third party is sent one item at a time, only when you ask, after you've been shown exactly what will go. Every such case is listed under "Everything that uses the internet" below. There's no account to create and no server that could be breached, because Meltware doesn't run one for this app.
Permissions, and exactly what each one is for
| Permission | What it's for | Leaves the device? |
|---|---|---|
| Camera | Barcode scanning and nutrition-label scanning, both done on the device with an offline recognition model. Also progress photos: your phone's own camera app takes the photo, and CalorieVault keeps it in its own storage on the device. | Never. No photo or camera frame is uploaded, stored anywhere else, or sent anywhere. |
| Notifications | An optional daily reminder to log your day, and an optional "fast complete" alert from the fasting timer, each only if you turn it on. | Never leaves the device. |
| Internet | The uses listed in full below, and nothing else. | Only for those uses. See below. |
| Health Connect (steps, active calories, weight, body fat %, hydration, exercise and the calories it burned, nutrition; opt-in, off by default) | Shows today's steps and active calories, for information only. Syncs weight, body fat %, hydration and exercise entries (with the calories each exercise burned) both ways with Health Connect, Android's on-device data broker. Sends your food diary entries to Health Connect as you log them, so other apps can see them. That direction is one-way: nothing another app writes to Health Connect's nutrition data is ever read back in or added to your calorie totals here. | Never. Health Connect is itself on the device, so none of this touches the network, and it's off until you turn it on in Settings. |
Everything that uses the internet
Check the app's manifest yourself: this is the whole list, and there's nothing else. Every item on it has to meet the standard in "Where your data lives" above. Nothing goes on this list as an exception to it. The first two send none of your data. The third sends one food you've added yourself, only when you ask, after showing you exactly what will go.
- Processing your one-off purchase. Google Play's billing service handles the payment. CalorieVault asks it whether you're entitled to the full app, including when you tap "Restore purchase" after a reinstall. Payment details are handled entirely by Google Play and the app never sees them.
- Importing a recipe from a link, only when you ask. Food → Recipes → Import from URL fetches the one page you paste a link to, the same way a browser would, and reads the recipe from it. It never fetches anything on its own, and matching the ingredients against your food catalogue afterwards happens entirely on the device.
- Adding a food to Open Food Facts, only when you ask. Open Food Facts is a free, public food database run by a non-profit, and CalorieVault's bundled catalogue is partly built from it. From your list of custom foods you can choose to add one food you entered yourself, if it has a barcode. There are two steps, and each only happens when you tap for it. First, Check sends just the barcode, to see whether Open Food Facts already has the product. If it doesn't, you can add the food. If it does but has no nutrition information, you can add just the nutrition figures and leave everything else about the product alone. If it already has nutrition information, nothing more is sent. Before anything else goes, the app shows you every field it will send (the barcode, and the name, serving size and nutrition figures as applicable) and asks you to check them against the pack. Only then does it send them, along with CalorieVault's name and version and a random contributor ID created for your phone the first time you contribute. Open Food Facts' moderators use that ID to block misuse without blocking every CalorieVault user. It isn't linked to you, to an account (there isn't one), or to anything else in the app. As with any website, Open Food Facts sees your internet address. No photo is sent, and nothing from your diary, weight log or any other food ever is. What you send becomes public under the Open Database License and can't be withdrawn through CalorieVault. It's one food at a time: no setting sends foods automatically, and nothing is sent in the background.
What's never collected
- No analytics, telemetry or usage tracking of any kind.
- No advertising identifiers or ad SDKs.
- No crash reports sent automatically. Errors are logged to a file in the app's own private storage only. The only way that file leaves your device is if you choose Settings → Diagnostics → Share diagnostics log, which opens your phone's normal share sheet, under your control.
- No location data.
- No data sold or shared with third parties. There's no data collected to share in the first place.
Backing up your data
Settings → Backup & switch devices exports your entries as a single JSON file, saved wherever you choose. You create and keep that file; CalorieVault doesn't upload it anywhere. Progress photos aren't included in it. They stay as files on the device only, so moving to a new phone means adding them again by hand. The same screen can also export your food diary or weight log as a spreadsheet (CSV) file, saved wherever you choose. If your free trial ends and you don't buy, the screen you see then has the same backup and spreadsheet exports, so you can always take your data with you.
Automatic backup (off by default) saves the same file once a day to a folder you pick with Android's own folder picker. If that folder belongs to a cloud storage app, Google Drive for example, then that app uploads the file, under that service's own terms. CalorieVault only ever hands the file to Android. By default each automatic backup is encrypted on your phone (AES-256) with a passphrase you choose before it's saved, so the copy in the folder can't be read without it. The passphrase is kept on your phone, locked with a key in Android's secure keystore, so the daily backup can run without asking you. It's never sent anywhere, and Meltware can't recover it if it's lost.
Third-party reference data
The bundled UK food database draws on the government's CoFID dataset (Crown copyright, Open Government Licence v3.0) and on Open Food Facts (Open Database License). Both are reference data shipped with the app, not services it calls while running. The attribution notices are in the app under Settings → About & help → Data sources & licences. The Open Food Facts extract the app ships is published under the same licence on the CalorieVault open data page. It contains no user data.
Children's privacy
CalorieVault isn't aimed at children and doesn't knowingly collect data from anyone. It doesn't collect data from anyone at all, of any age, beyond what's described above.
Changes to this policy
If this policy changes, the date at the top of this page changes with it. There's no account and no email address on file, so this page is the only place updates are posted.