Effective date: September 6, 2026 · Last updated: October 4, 2026
This Privacy Policy explains how MEGHANBYTES (“we,” “us,” “our”) handles information in connection with Vital (the “App”).
Vital works entirely offline. Your health data — blood sugar, weight, blood pressure, food, and medication information, including readings imported from Bluetooth devices you pair — is stored only on your device. We do not operate a backend server, we do not have accounts, and we never receive, see, or store a copy of your health data. Backups and summaries are created on your device and go only where you choose to send them. The App shows non-intrusive, non-personalized ads (including native-style ad cards on Home and History) to stay free, and those ads are never targeted using your health information.
We do not collect your health data. Blood sugar readings (including tags and notes), weight, blood pressure and pulse, food entries (meals, food names, servings, calories, and carbs), medication names/doses/schedules, and adherence records are stored exclusively in local storage on your device. They are never transmitted to us, because we have no server for them to be transmitted to.
If you choose to pair a Bluetooth blood pressure monitor or glucose meter, the App asks for Bluetooth permission so it can find and connect to that device. Readings travel directly from the device to the App on your phone and are stored there like any other entry. The details of devices you pair are also kept on your phone. We never receive your readings or information about your devices. You can remove a device at any time in Settings → Devices → Forget device, and you can revoke Bluetooth permission in your phone’s settings.
On Android 11 and earlier, the operating system requires location permission for an app to scan for Bluetooth devices, so Vital asks for it there. It is used only to find nearby devices you choose to pair — Vital never uses it to determine, record, or share your location. On Android 12 and later, Vital uses Bluetooth permissions only and does not request location access.
If you turn on notifications, medication reminders are scheduled and shown by your phone. No reminder or medication information is sent to us.
When you export a backup, the App creates an encrypted file protected by a passphrase you choose. The passphrase is saved on your device so you can view it later. Summaries you create from the History screen (for example, to show your doctor) are also generated on your device. In both cases, the file goes only where you choose to save or share it — such as a cloud drive, email, or your computer — and that service’s own privacy policy then applies. We never receive your backups, passphrases, or summaries.
We (or our service providers, as described below) collect only:
To serve ads, our ad partner, Google AdMob, may collect limited technical information such as your device’s advertising identifier (if you have not limited it), general device type, operating system version, approximate location derived from IP address, and which ads were shown or clicked. This is standard ad-delivery information and does not include anything you’ve entered into the App — the ad SDK operates independently of, and has no access to, your logging data.
We use Sentry, a crash-reporting service, to receive technical crash reports (e.g., which screen crashed, device model, OS version) to help us fix bugs. Reports never include screenshots, your IP address, or other personal information, are not linked to your health data, and do not include the content of your entries. You can review Sentry’s privacy policy at https://sentry.io/privacy/.
We do not use any information we or our partners collect to build a profile of your health status, and we do not sell personal information of any kind.
| Data | Where it’s stored |
|---|---|
| Health entries (blood sugar, weight, BP, food, medications, adherence), including readings imported from paired Bluetooth devices | On your device only — never transmitted to us |
| Paired Bluetooth device details | On your device only |
| Automatic recovery snapshots | On your device only, used to restore your data if the App’s database has a problem |
| Backup passphrase | On your device only |
| Exported backups and shared summaries | Wherever you choose to save or share them — never sent to us |
| Ad delivery identifiers | Held by Google AdMob, per their own retention practices |
| Crash reports | Held by Sentry, our crash-reporting provider — technical data only |
We do not have a database of user health information, because we don’t operate a backend to put one in.
If you are in the EU/UK/EEA: because we don’t collect or process your health data at all, most GDPR data-subject rights (access, erasure, portability) are naturally already satisfied — that data has only ever been on your device. For the limited ad-related and crash-diagnostic data described above, you can exercise applicable rights by contacting us or your device’s ad settings.
If you are a California resident: we do not sell personal information. Ad-delivery data handled by our ad partner is governed by their own CCPA/CPRA disclosures, linked above.
The App is not directed at children under 13 (or the relevant age of digital consent where you live). Our advertising is configured to avoid child-directed treatment; if you believe a child has used the App and information was collected inappropriately by our ad partner, contact us at [email protected].
We may update this Privacy Policy from time to time, for example if we change advertising partners or introduce new features. When we do, we’ll update the “Last updated” date above.
Questions about this Privacy Policy: [email protected]
MEGHANBYTES
If you’re in the EU/UK, you also have the right to lodge a complaint with your local data protection authority.