Consumer Health Privacy Policy
Last Updated: October 6, 2026
This Consumer Health Privacy Policy describes how mevitals ("Company," "we," "us," or "our") collects, uses, stores, and protects your personal and health-related data.
Important Legal Notice: mevitals is a direct-to-consumer software service. We are not a "covered entity" or "business associate" under the Health Insurance Portability and Accountability Act (HIPAA). Instead, our handling of your health data is regulated by consumer protection laws, including the Federal Trade Commission (FTC) Act, the FTC Health Breach Notification Rule, and state consumer health privacy statutes (such as Washington’s My Health My Data Act).
1. Categories of Health Data We Collect
When you authorize and connect your third-party accounts, we collect and aggregate the following metrics:
- Dexcom Continuous Glucose Monitor (CGM) Data: Estimated glucose values (EGV), timestamps, and trend arrows.
- Garmin Wearable Data: Heart rate, resting heart rate, sleep duration and stages, blood pressure readings (manual or synced via Garmin Index BPM), step counts, and active calories.
- Oura Ring Data: Readiness, sleep duration and stages, resting heart rate, heart-rate variability, respiratory rate, body-temperature deviation, stress and recovery, daily activity, and workouts.
- Google Health Data (Fitbit, Pixel Watch & Android): Steps, distance, active/total calories, active minutes, resting and daytime heart rate, heart-rate variability, sleep duration and stages, blood oxygen (SpO₂), respiratory rate, skin/core temperature deviation, body weight and body-fat, VO₂max, and workouts.
- Food & Meal Data: Meal photos you capture or upload, written notes, identified food items, and estimated nutrition.
- Account Credentials & Telemetry: Account email address, encrypted authentication tokens/session identifiers, IP address, and device type.
2. How We Collect and Source Health Data
We collect health data through the following mechanisms:
- Direct Account Linking: When you provide or authorize authentication credentials to import metrics from Dexcom, Garmin, Oura, and Google Health.
- Direct Input: When you manually log food, medicine, or notes directly within the app.
3. Purpose of Processing and Use of Health Data
We process your health metrics exclusively for the following purposes:
- Aggregating, displaying, and visualizing your combined glucose, biometric, and activity metrics in a single interface.
- Generating personal health trends and history charts for your own review.
- Analyzing meal photos you submit to identify foods and estimate nutrition (see Section 4).
- Maintaining, troubleshooting, and securing your account.
WE DO NOT SELL YOUR HEALTH DATA. We do not rent, license, or monetize your health metrics or personal details to third-party ad networks, data brokers, or marketing firms.
4. How We Share Consumer Health Data
We only share your data in limited circumstances:
- Service Providers / Cloud Infrastructure: With cloud hosting and database vendors (e.g., AWS, Supabase, or Google Cloud) that process data under strict confidentiality obligations to keep our app running.
- Authentication: If you sign in with Google, Google processes your sign-in; we receive your email address and basic profile only.
- Data Sources: When you connect them, the Dexcom, Garmin, Oura, and Google Health APIs provide the health metrics you import. Their handling of your data is governed by their own policies.
- Notifications: Email/SMS operational alerts (for example, a failed backup) are delivered through our messaging provider and never include health content.
- Meal-photo analysis (Google Gemini): When you ask us to identify a meal, the photo you submit is sent to Google's Gemini API solely to return a food identification and estimated nutrition. Google processes it under its API terms as our service provider; it is not used to target advertising or sold. If you prefer not to use this feature, simply don't submit meal photos — everything else works without it.
- Barcode product lookup (Open Food Facts): When you scan a packaged food's barcode, we send only that public barcode number to the Open Food Facts API (a non-profit, open food database) to retrieve the product's name, brand, and nutrition. No health data, photo, or account identifier is sent. Product images we display are publicly licensed and cached on our servers; Open Food Facts' own terms govern its handling of the request. If you prefer not to use this feature, log the item with a photo or manual entry instead.
- In-app feedback (Jira Service Management): When you use Report an issue or Suggest an improvement, the text you enter, the page you were viewing, the app version, and the contact email you provide are sent to our support team's issue tracker hosted by Atlassian (Jira Service Management) so we can investigate and reply. Using these forms also creates a support account for your email address with Atlassian and sets you as the reporter, so we can send you updates about your request; you will receive an invitation email from Atlassian, and you can reply to those emails to continue the conversation. Do not include medical or health information in feedback — this channel is not designed for it and the form reminds you. Atlassian processes this content as our service provider under its own terms; it is not used to target advertising or sold. If you prefer, you can also use the contact form.
- Legal Obligations: When required by valid law, subpoena, or government order.
- Business Transfers: In connection with a merger, acquisition, or sale of company assets, subject to the buyer agreeing to maintain the privacy protections set forth in this policy.
5. Security Practices and Encryption
We implement technical, administrative, and physical safeguards designed to protect your sensitive metrics:
- Encryption in Transit: All communications between our app, backend servers, and third-party APIs use TLS 1.3 protocol.
- Encryption at Rest: Sensitive health metrics and authorization tokens stored in our database are encrypted using AES-256 standard.
- Access Control: Server access is restricted to authorized operations personnel using multi-factor authentication.
6. Your Privacy Rights and Data Control
Regardless of where you reside, we provide you with direct control over your health metrics:
- Right to Access / Portability: You may request a copy of all aggregated health records stored in our database.
- Right to Delete (Permanent Purge): You may request the permanent deletion of your account and all associated Dexcom, Garmin, Oura, and Google Health records at any time directly in app settings or by contacting us.
- Right to Revoke Consent: You may disconnect your Dexcom, Garmin, Oura, or Google Health accounts at any time, immediately halting future data fetching.
To exercise these rights, use the Privacy Center in your account settings — deletion and consent withdrawal are self-service, and you can request a copy of your data there. If you can't sign in, use the contact form. We will process your request within 30 days.
7. Notice Under the FTC Health Breach Notification Rule
In the event of an unauthorized security breach or unapproved disclosure involving your identifiable health information, we will notify affected users without unreasonable delay and comply with mandatory reporting to the Federal Trade Commission in accordance with 16 CFR Part 318.
8. Changes to This Privacy Policy
We may update this Consumer Health Privacy Policy from time to time. If we make material changes to how we process or share health data, we will notify you via in-app banner or email before those changes take effect.
9. Contact Us & Appeals Process
If you have questions about this policy, or if you wish to appeal a decision regarding a data deletion or access request, please contact our Privacy Team:
- Privacy requests: the Privacy Center in your account settings, or the contact form if you can't sign in
- Appeals: open an appeal from the Privacy Center in your account settings