Privacy Policy

VYTL LLC ("we," "our," or "us") is committed to protecting your privacy. This Privacy Policy explains how we collect, use, store, and protect your personal and health information when you use the VYTL fitness application ("App"). Please read this policy carefully before using the App.

1. Information We Collect

We collect information in the following categories to provide you with a personalized fitness experience:

Account Information

• Email address (used for authentication and account management)
• Account creation date
• Referral relationship, if you were referred by another VYTL user or you refer someone else

Health and Body Data

• Body measurements (weight, body fat percentage, waist, chest, arms, thighs)
• Workout history (exercises, sets, reps, weights, duration, volume)
• Food logs (meal entries, nutritional data, portion sizes, calorie counts)
• Meal photos, if you use photo food-logging (not saved — sent for AI processing, then discarded) and voice recordings, if you use voice food-logging (the audio itself stays on your device; only the transcribed text is sent for processing)
• Pantry contents and grocery lists
• Daily readiness scores (sleep quality, muscle soreness, energy level)
• Health data synced from Apple HealthKit (if you grant permission), including steps, heart rate variability (HRV), and sleep data
• Body scan photos, if you use the body scan feature (these stay on your device — see Section 3)
• Training profile details you set during onboarding or in Settings: experience level, the equipment you have access to, and named gym or location profiles (not GPS coordinates)

Location Data

• Precise GPS location during an outdoor cardio session you track in the App, only if you grant location permission for that session — used to record your route, elevation, and splits. This stays on your device; see Section 3.

Device and Technical Information

• Device type and operating system version (for compatibility purposes)
• App version and crash logs (used for debugging)
• Anonymous usage events (e.g., feature interactions); see Section 4 for the coarse, bucketed categories we also send for some workout, nutrition, plan, and readiness events
• Push notification token, if you grant notification permission

2. How We Use Your Information

We use your information solely to provide and improve the VYTL fitness experience:

• Generating personalized workout plans, nutrition targets, and macro recommendations
• Calculating daily calorie and macro goals based on your body stats and activity level
• Tracking progress over time (body metrics, strength gains, consistency over time)
• Providing AI-powered meal suggestions and food logging assistance
• Syncing your data securely across devices via encrypted cloud backup
• Diagnosing technical issues and improving app stability
• Sending account-related communications (password resets, billing receipts)
• Sending notifications — reminders you configure, scheduled on your device, and account-related notifications sent from our servers

We do not use your health or fitness data for advertising or sale to third parties.

On-device analysis. VYTL builds daily summaries and patterns from your training and nutrition data on your device, to power your coaching. These derived summaries never leave your device.

3. How We Store Your Data

On-Device Storage

Your fitness data is stored locally on your device using WatermelonDB, an offline-first database. This means the app is fully functional without an internet connection. Local data is protected by your device's operating system-level encryption and access controls.

Cloud Backup (Supabase)

While you are signed in, your data is synchronized to your account on Supabase, our cloud database provider, so it is backed up and available across your devices. All data in transit is encrypted using TLS 1.2 or higher. Data at rest is encrypted using AES-256. Supabase infrastructure is hosted on AWS and complies with SOC 2 Type II.

Body Scan Photos

If you use the body scan feature, the photos you capture are stored in a private folder on your device. They are not uploaded to our servers, and we never send them to any other company. They are removed when you delete them, when you sign in as a different user, or when you uninstall the App.

Location Data

If you track an outdoor cardio session, your GPS route, elevation profile, and mile/km splits are stored only on your device. They are never uploaded to our servers and never synced to your account. The only way this data leaves your device is if you choose to let VYTL write the workout's route to Apple Health — see Section 5.

4. Third-Party Services and Data Sharing

We use a minimal set of third-party services, each with strict data-handling requirements:

Analytics (PostHog)

We use PostHog for product analytics — which features are used, which screens are viewed — so we can improve the App. We configure PostHog to receive interaction events only: never your raw food logs, exercise names, reps, weights, calorie counts, sleep hours, or exact readiness scores. For a small number of events tied to workouts, meals, plan generation, and daily readiness, we do send coarse, bucketed categories — for example a workout's category and a duration or set-count range, which broad band your readiness score falls in, a meal's type (breakfast, lunch, dinner, snack) and how you logged it, or a general nutrition direction like "cut" or "maintain" — because that tells us the App is working without telling us the specifics of your health. Analytics events are not linked to your name. The one exception on email: when you submit your email to sign in, that single event includes a one-way hash of it — not your email itself, but a scrambled value that always comes out the same for the same address, so we can tell a repeat sign-in attempt from a first one.

Authentication (Supabase Auth)

Supabase provides our database and authentication. It stores your account credentials (email and a hashed password) and the App data that syncs to your account, including the meals, workouts, water, body measurements, cardio, and AI-coach conversation history you generate. Supabase processes this only to provide database and authentication services to us.

Sign In with Google

If you choose to sign in with Google instead of email or Apple, Google authenticates you, and we receive your Google account identifier and the email address associated with it to create your VYTL account through Supabase. We never receive your Google password. This exchange is governed by Google's own privacy policy.

AI Features (Anthropic)

Some VYTL features are powered by AI: recognizing food from a photo you take, cleaning up a voice recording of a meal you describe, chatting with your AI coach, and generating workout or meal plans. When you use one of these features, what you send it — the photo, the transcribed voice text, your message to the coach, or your profile and goals — is sent to Anthropic (the company behind Claude, the AI model VYTL uses) to generate a response.

Cloudflare, our infrastructure provider, routes these requests and briefly caches some AI responses (up to one hour) so an identical repeat request doesn't have to be regenerated. Anthropic processes what you send only to generate the response you asked for, under its standard commercial terms, which state that inputs sent through its API are not used to train its models.

Wearable Connections (Strava, Fitbit, Oura, Whoop)

VYTL has built, but does not currently offer, the ability to connect Strava, Fitbit, Oura, or Whoop. Every connection screen for these four services shows as coming soon today and does not let you start a new connection — we do not currently receive new data from any of them. If your account connected to Strava before this pause, the workouts you imported then — including heart rate data Strava provided — remain in your VYTL data unless you delete them.

Subscriptions (RevenueCat / App Store)

Subscription management is handled by RevenueCat and processed through the Apple App Store. We receive subscription status and entitlement data only. Payment card data is never seen or stored by VYTL.

Push Notifications (Apple / Expo)

If you grant notification permission, the reminders you turn on (workout, meal, water, streak, coach, rest day) are scheduled on your device and delivered by iOS directly — no server is involved. Separately, VYTL stores a push token for your device so we can send notifications from our servers for certain account events, such as an earned referral reward. Sending a server notification uses Apple's Push Notification service and Expo, our push-delivery provider, to reach your device — they receive your push token and the notification's title and body, not your health or fitness data. You can turn off any notification type in Settings, or revoke notification permission entirely in the iOS Settings app.

Error Monitoring (Sentry)

We use Sentry (Functional Software, Inc., United States) for crash reporting and error monitoring. This covers crash reports, error events, stack traces, device model, operating system version, app version, and app performance data. Some of it is sent while you use the App, not only when the App crashes.

We configure Sentry to remove personal and health information from diagnostic data before it is transmitted. Automatic collection of console output, network requests, and request URLs is turned off, and every remaining error event and breadcrumb is run through a redaction filter on your device. Because diagnostic data is generated automatically, we cannot guarantee that it never contains something you typed into the App — for example, a search term appearing inside an error message. We limit that risk with the controls described here rather than promise it cannot happen.

If an error occurs, Sentry may also receive a short recording of the App screens leading up to it. All text, images, and graphics in that recording are masked on your device before it is sent. We do not record your screen at any other time.

We also use Sentry to monitor errors in the backend services that power AI features (meal photo recognition, voice cleanup, and AI coach chat). Like the on-device App, those services run every error report through an equivalent redaction filter before it is sent, and if that filter fails, the report is dropped rather than sent unredacted.

Sentry processes this data only on our instructions and only to provide error-monitoring services to us. Sentry does not use it for its own purposes, does not sell it, and does not use it for advertising.

We do not send body scan photos or medication or injection records to Sentry, whether from the App on your device or from our backend. Nothing in the App has a path that sends them there, and automated tests fail our build if one is ever added.

Meal photographs, voice recordings and transcripts, body-scan measurements, and Apple Health data are not intentionally sent to Sentry, and the on-device filter described above is built to remove them from diagnostic data. As everywhere else in this section, that is a control we apply, not an outcome we can guarantee.

We do not sell, rent, license, or otherwise transfer your personal information or health data to any third party for their commercial use. We do not share data with data brokers, advertisers, or marketing platforms.

We do not share, sell, or transfer your health data to any affiliated company. VYTL is operated by its own company; although its owner operates other, separate businesses, none of them access your VYTL data, and we do not combine your VYTL data with data from any other company.

5. Apple HealthKit

With your explicit permission, VYTL may read data from Apple HealthKit, including:

• Step count and active energy burned
• Heart rate, resting heart rate, and heart rate variability (HRV)
• Sleep duration and sleep stage data
• Respiratory rate and blood oxygen saturation (SpO2)
• VO2 max (cardio fitness)
• Weight, body fat percentage, lean body mass, and body mass index (BMI)
• Height and waist circumference
• Workouts recorded by your other apps and devices
• Your date of birth and your sex, as recorded in Apple Health

With your permission, VYTL also writes data back to Apple Health so your other apps stay current: the workouts you complete and, for outdoor cardio, the route recorded during that workout; your weight; and the calories, protein, carbohydrates, fat, and water you log.

Apple HealthKit data is used to compute your daily readiness score — which can lighten today's workout, for example by dropping a set or adding rest — tailor your calorie and macro targets, and track your body measurements over time. It does not affect per-muscle recovery tracking, which is calculated from your logged workouts and, when you answer it, the soreness check-in you enter yourself on the Readiness screen. That check-in stays on your device for this calculation and is never sourced from Apple Health. It is stored on your device and, like the rest of your App data, syncs to your account on Supabase so it is available when you sign in on another device. We do not send the HealthKit values themselves to analytics providers, advertisers, or data brokers — the one exception is the coarse, bucketed readiness signal described in Section 4 (for example, whether your readiness score falls in a rough band), which is derived from this data but never carries the underlying HealthKit numbers. You may revoke HealthKit access at any time in the iOS Settings app under Privacy & Security → Health.

6. Data Retention

We retain your personal information and health data for as long as your account remains active. When you delete your account from within the App, we delete all of your cloud-stored (Supabase) data — every category you generate in the App, including workouts, food and water logs, wearable and readiness data, body measurements, cardio sessions, AI-coach conversation history, meal plans, and your account profile. That deletion happens right away, not on a delay: our account-deletion routine sweeps every table that stores your data by its ownership record, rather than a fixed list, so a category added to the App in the future is covered without a future update to this policy.

• Anonymized, non-identifiable aggregate data may be retained for product research
• Locally stored data on your device is removed when you uninstall the app

Separately, VYTL also runs automated cleanup at every app launch that removes incomplete workout-session records your device created but never finished — for example, a session left in-progress and abandoned, or a completed session saved with no exercises logged. This is a narrow, ongoing housekeeping process, not the account-level retention described above: it targets unfinished device-side session records, not the food logs, body measurements, or other data categories you've completed and saved.

Diagnostic data sent to Sentry and analytics events sent to PostHog are retained under each provider's own standard retention settings, which we review periodically. The AI response cache described in Section 4 is retained for up to one hour. A short-lived authorization code created when you connect a wearable service is retained for up to 10 minutes and then deleted, whether or not the connection completes.

You may also request deletion of your data at any time without closing your account. See Section 9 for how to submit a deletion request.

7. Data Security

We take the security of your health data seriously and implement multiple layers of protection:

• All data in transit is encrypted via TLS 1.2+
• Data at rest in Supabase is encrypted using AES-256
• Body scan photos never leave your device — no server, no third party
• Authentication tokens use industry-standard JWT with short expiry windows
• Row-level security (RLS) policies in Supabase ensure users can only access their own data
• We configure our analytics and error-monitoring tools to exclude health data, and diagnostic data is redacted on your device before it is sent (see Section 4)

Despite these measures, no internet transmission or storage system is 100% secure. If you believe your account has been compromised, contact us immediately at [email protected].

8. Children's Privacy

VYTL is not intended for use by children under the age of 13. We do not knowingly collect personal information from children under 13. If you are a parent or guardian and believe we have inadvertently collected information from a child under 13, please contact us at [email protected] and we will delete the information promptly.

9. Your Rights and Choices

Regardless of your location, you have the following rights regarding your data:

• Access: Request a copy of all personal data we hold about you
• Correction: Request correction of inaccurate or incomplete data
• Deletion: Request permanent deletion of your account and all associated data
• Portability: Request an export of your data in a machine-readable format
• Opt-out of analytics: Disable non-health analytics collection in Settings
• Revoke health permissions: Revoke HealthKit access at any time in the iOS Settings app under Privacy & Security → Health
• Category-specific consent: medications and injections, workouts and training, food and nutrition, body composition, Apple Health, your AI coach, GPS location, AI features involving your health data, anonymous analytics, and crash reports each have their own consent decision, viewable and revocable at any time in Settings → Consent & Data. If you revoke a category, we stop collecting new data for it; existing data stays visible so you can still review or export it before deciding whether to delete it.

To exercise any of these rights, contact us at [email protected]. We will respond within 30 days.

10. Washington State: My Health My Data Act (MHMDA)

For Washington state residents, we provide the following disclosures under the My Health My Data Act (RCW 19.373):

The consumer health data described in Section 1 comes directly from you; from Apple HealthKit and connected wearable services, where you grant permission; and from information our software derives or infers from that data.

If you use VYTL to track GLP-1 medication or injection information, that category gets its own dedicated Consumer Health Data Privacy Policy, in Settings → Medication → Health data privacy, describing how it is handled — in short, it never syncs to our servers and is stored only on your device.

• We do not sell consumer health data as defined by MHMDA
• We do not share consumer health data with third parties for advertising purposes
• We do not use geofencing near healthcare facilities to collect health data
• You have the right to confirm whether we process your consumer health data, and to access it — including a list of every third party and affiliate we have shared or sold it to and a way to contact them
• You have the right to withdraw consent for data collection at any time
• You have the right to deletion of your consumer health data

Service Providers and Your Consumer Health Data

Some of the service providers we use process consumer health data on our behalf. Supabase stores the meals and workouts you log, Cloudflare routes requests from the App's AI features, temporarily holds a wearable-connection authorization code, and serves the exercise videos shown in your workouts, and Anthropic processes the inputs you submit to those AI features and returns the responses. Diagnostic data sent to Sentry may incidentally contain consumer health data, such as a food search term appearing inside an error message.

We disclose this so that you know it happens. Under the My Health My Data Act, disclosing consumer health data to a processor that acts only on our instructions, for a purpose we have told you about, is not "sharing." We use each of these providers under their standard terms of service, which restrict them to processing data on our behalf and only to provide their service to us. We do not permit any of them to use your data for their own purposes, to sell it, or to use it for advertising.

We do not share your consumer health data with third parties for their own purposes, and we do not sell it. If we ever proposed to do either, we would ask for your separate, specific consent first — and for a sale, a separate signed authorization. Your acceptance of this Privacy Policy is not consent to either.

To exercise your MHMDA rights, contact our designated privacy contact at [email protected] with the subject line "MHMDA Request." We will respond within 45 days; if we need more time, we may extend once by a further 45 days and will tell you why within the first 45. If we refuse a request, you may appeal by replying to our response, and we will answer your appeal in writing within 45 days. If we deny the appeal, you may file a complaint with the Washington State Attorney General at atg.wa.gov/file-complaint-or-report.

11. California Residents: CCPA/CPRA

California residents have the right to know what personal information we collect, correct inaccurate personal information, request deletion of personal information, opt out of the sale of personal information, and limit our use of sensitive personal information — which includes health information and precise geolocation — to what is reasonably necessary to provide the App. We do not sell personal information. To submit a request, email [email protected] with the subject line "CCPA Request."

12. Changes to This Policy

We may update this Privacy Policy from time to time. The current version is always available in the app, and we will change the "Last updated" and "Effective date" at the top when we do. We encourage you to review it periodically. If we want to collect a new category of health data, or use your health data for a new purpose, we will ask for your consent first, separately from this policy. When VYTL introduces or materially changes a data category, it asks in the app. For training and nutrition, undecided consent may continue collection for up to 7 days after first asking. After that, the app requires a decision before continuing.

Summary of changes (2026-07-21): This update clarifies existing practices — push notifications, AI-assisted processing via Anthropic, meal photos, and voice transcripts. No new collection or use was introduced.

Summary of changes (2026-07-26): This update narrows what Section 4 promises about diagnostic data. It previously stated that several kinds of data are not sent to our error-monitoring provider. For two of them that is enforced by the App's own automated tests. For the rest it depends on a filter, so they are now described as filtered rather than promised absent. Nothing about what the App collects or how it is used changed.

Summary of changes (2026-08-18): This update corrects and completes several disclosures for practices that were already part of the App: signing in with Google (Section 4); precise GPS location for outdoor cardio, which stays on your device (Sections 1, 3, and 11); the wearable connections VYTL has built for Strava, Fitbit, Oura, and Whoop, not currently offered (Section 4); the automated cleanup of unfinished workout-session records and retention periods for diagnostic, cached, and token data (Section 6); and a wider description of the bucketed categories sent to our analytics provider (Section 4). It also updates our entity name to VYTL LLC and corrects Section 1's analytics bullet, which previously stated no health data is attached when Section 4 already disclosed otherwise. No new data collection was introduced by this update — every category described here was already part of the App.

13. Contact Us

If you have questions, concerns, or requests related to this Privacy Policy, please contact:

VYTL LLC
Email: [email protected]
Website: vytl.fitness

[email protected] is monitored directly by VYTL. We do not use a third-party support vendor.

For Washington MHMDA requests, include "MHMDA Request" in your subject line.
For CCPA/CPRA requests, include "CCPA Request" in your subject line.