Overview
Vitalion follows one rule: your data stays on your device unless you explicitly export it (or your own iPhone backup includes it, see below). There is no account, no server, no analytics, no crash-reporting SDK, no advertising SDK, and no third-party library that performs network requests.
What is stored on your iPhone
- Your food diary, custom foods, saved meals, targets and profile, in a database inside the app's sandbox, protected by iOS Data Protection (encrypted at rest).
- A local cache of the Open Food Facts product records you scanned, so repeat scans work offline.
- A daily snapshot of the Apple Health values you granted access to (steps, sleep, weight, body fat %, energy, resting heart rate, HRV, water). Apple Health remains the system of record; the snapshot can be deleted and recomputed at any time.
- The workouts Apple Health has, if you granted access to them (kind, start and end, duration, active energy, distance, the name of the app or device that recorded them, and whether Apple Watch recorded it as a custom workout), for the Training tab and training days. No route, heart rate or other detail of a workout is read.
- A meal photo you take or choose for "Snap or describe a meal" is not stored: it is used for that one estimate and dropped.
- A photo you take or choose to read a nutrition label is read on the iPhone; it is kept as the food's label photo only when you save the food.
- Automatic backups: about once a week a full export is written, compressed, to a folder inside the app's sandbox (the newest seven are kept, plus up to three made just before an import or restore). They never leave the device unless you share one.
- Before an app update changes the database's structure, a copy of the database is kept next to it, so data can be recovered if the update goes wrong. The next such update replaces it.
- Today's totals for the widgets (calories, macros, steps, sleep, weight, water), in the app's App Group container on the device, readable only by Vitalion and its own widget extension.
- Taps on a widget's or a control's button (a glass of water, a habit ticked) that iOS handled while the app wasn't running, in the same container, until the app next runs and saves them.
- Diagnostics: Apple's own crash and hang reports for Vitalion (MetricKit), kept on the iPhone (the newest 20, at most 5 MB) under Settings → Diagnostics. They are sent nowhere; you can share them yourself, delete them, or switch them off.
What leaves the device
| Destination | When | What is sent |
|---|---|---|
world.openfoodfacts.org |
You scan a barcode that is not already cached, or pick a packaged food from online search | The barcode and a User-Agent header identifying the app |
search.openfoodfacts.org |
You search packaged foods online | The search text and a User-Agent header identifying the app |
images.openfoodfacts.org (only Open Food Facts image hosts, over https) |
A scanned product's card shows its photo | The image address, which names the product's barcode |
api.nal.usda.gov |
You search online, in builds that include a USDA key | The search text and the build's key |
| Apple Health (on the device) | You log food or water, or enter weight | Nutrient, water and weight samples, written only with your permission |
Nothing else. Like any internet request, these lookups reveal your IP address to the service that answers them. Open Food Facts and USDA handle it under their own privacy policies.
"Snap or describe a meal" works on the device: the photo or text is read by the on-device Apple Intelligence model, or, where that isn't available, matched to foods already on the device. Neither is sent anywhere. "Scan nutrition label" recognizes the text of the photo on the device too.
Siri and Shortcuts actions, the widgets and Control Center controls, background refresh, the weekly check-in, hydration and habit reminders (local notifications) and the weekly report image all work on the device. The report image goes only where you share it.
Apple Health
Vitalion reads and writes Apple Health data only with your permission, and only to show it to you and to compute your targets and trends inside the app. Health data is never used for advertising, never sold and never shared with anyone.
Your data, your control
- Export everything as JSON or CSV at any time (Settings → Export & import).
- Erase everything at any time (Settings → Erase all data…): the database, the backups on the iPhone, label photos, diagnostic reports, reminders, widget data and settings, and, if you leave that switch on, the samples Vitalion wrote to Apple Health. What other apps and devices wrote to Health, and files you already exported, are not touched.
- Deleted diary entries, drinks, planned entries, habit checks and saved-meal items are removed from the database for good 90 days after you delete them.
- Your iPhone's own backups (iCloud Backup or a backup to a computer) include the app's data like any other app's. They are encrypted and stored under your Apple Account or on your computer, not on any Vitalion server. Turn Vitalion off in Settings → [your name] → iCloud → iCloud Backup to leave it out of iCloud backups.
- Deleting the app deletes all app data. Samples written to Apple Health remain in Health until you delete them there.
This website
vitalion.app is a static site with no cookies, no analytics scripts and no forms. It is served by Cloudflare, which processes technical request data such as IP addresses to deliver and protect the site. If you email support, your message and address are used only to answer you.
Children
Vitalion collects no personal information from anyone, including children.
Changes
If this policy changes, the new version is published on this page with a new effective date. A feature that would send data anywhere new is off by default and described here before it ships.
Contact
Questions about this policy: support@vitalion.app, or see the support page.