← Back to home

Privacy Policy

Effective date:

Users of beta versions accept that this is a draft policy under legal review.

Resumo em linguagem simples

Recolhemos os dados de treino e recuperação que escolhes ligar, usamo-los apenas para te treinar, nunca os vendemos, nunca anunciamos com eles e apagamo-los quando pedes. Essa é toda a política — as secções abaixo são os detalhes.

1. Who We Are

Zorv Technologies LLC (“Zorv,” “we,” “our,” or “us”) respects the privacy of your information. This Privacy Policy explains how we collect, use, store, and protect information when you use the Zorv platform, including our websites, mobile applications, and any related services (collectively, the “Services”).

From time to time, we may update this Privacy Policy. If we make material changes, we will notify you by posting a revised version with a new effective date on our website or by sending you a notification through the Services. We encourage you to review this policy periodically.

2. What Data We Collect

Account data

  • Name and email address
  • Profile information you choose to provide (e.g., age, weight, height, sport preferences)
  • Authentication credentials (passwords are stored in hashed form)
  • Mobile phone number, if you choose to sign in by text message. We use it only to send you sign-in codes and to secure your account. It is never shown to your coach or team and never used for marketing. Codes are delivered by our SMS provider (Twilio).

Athletic and health data

When you connect supported devices, applications, or services through our platform, we may receive athletic and health-related data, including but not limited to:

  • Heart rate and heart rate variability (HRV) and other cardiovascular metrics
  • Sleep data (duration, stages, quality scores)
  • Recovery and readiness scores
  • GPS routes and activity location data
  • Power, cadence, pace and other workout performance metrics
  • Biometric data from continuous monitoring devices (e.g., glucose levels), where you choose to connect them

The specific data we receive depends on which third-party services and devices you choose to connect and the permissions you grant. A current list of supported integrations is maintained at zorv.ai/integrations.

Device identifiers

We receive device identifiers from connected wearables and applications as necessary to associate data with your account and to support synchronization.

App usage data

We collect anonymized usage data to improve our Services. We use Sentry for error reporting. We do not use advertising SDKs and do not track you for advertising purposes.

Waitlist and marketing site

When you join the waitlist, we store your signup details and optional confirmation-page engagement (survey answers you submit, first-party link clicks, and share actions) to operate the waitlist and prioritize cohorts. We do not use advertising trackers or browser fingerprinting for this.

Map and location services

We use the open-source MapLibre GL JS library to display activity routes and maps within the app, with map tiles, route planning, elevation and place search provided by Stadia Maps. Map tiles and requests are used for visualization and course planning only; we do not use Stadia Maps for persistent location tracking. See Stadia Maps' Privacy Policy for their practices.

Payment data

Payments are processed by Stripe. We do not store your full card number or card verification details. We retain only billing-related identifiers (e.g., Stripe customer ID) as needed to provide the Services.

3. How We Collect It

  • Directly from you — When you create an account, update your profile, or input information.
  • Via authorized connections to third-party services — When you authorize a connection (e.g., via OAuth) to a third-party device, application, or platform, we receive data in accordance with that provider's API terms and the permissions you grant.
  • Via background sync — When you enable background sync, our applications may periodically retrieve data from linked services to provide up-to-date coaching and metrics.
  • Automatically via tracking technologies — Through cookies and server-side analytics as described in Section 8.

4. How We Use Your Data

We use your data to:

  • Provide personalized coaching recommendations based on your activity, recovery, and goals.
  • Calculate training load metrics and display performance insights in your dashboard.
  • Generate your daily briefings, trend analyses, and other in-app insights.
  • Improve, develop, and personalize the Services.
  • Communicate with you about your account, the Services, and support requests.
  • Comply with applicable legal obligations and protect our legal rights.

We do not sell your personal or health data to third parties. We do not share your health or fitness data with advertising networks or for advertising purposes.

We may use anonymized, aggregated data (e.g., population trends and benchmarks) for product improvement, research, and service development. Such data cannot be used to identify you.

Race data from your recordings and results. If you record a race that is in our race catalog, your race file and your result may be combined with those of other athletes who raced the same event, in two ways. Course profiles: the GPS track of your race file may help build an anonymous course line (route and elevation profile); a line is only built from at least 3 athletes’ files and stores only the combined median line and counts — never your individual route, start time, or identity. Finish-time ranges: your finish time (and swim, bike, run and transition splits, where recorded), with your sex and age group, may be added to anonymous finish-time percentiles for that race; a group is only published when it has at least 30 athletes, and only the group size and percentiles are shown — never your individual time or identity. Files we receive through the Strava or Garmin APIs are never used for either, and athletes under 18 are never included. This is on by default; you can turn it off at any time under Settings → Privacy → “Use my race recordings and results to improve race data”. Once you turn it off, your recordings and results are left out of every future build; your stored result is deleted at once, finish-time percentiles are recalculated without you at the next scheduled update (usually within an hour), and course lines that used your files are rebuilt without them (or withdrawn if fewer than 3 athletes remain).

5. How We Share Your Data

We may share your data in the following circumstances:

  • Service Providers — We share data with third-party service providers who perform services on our behalf, such as cloud hosting, payment processing, error monitoring, analytics, and map display. These providers are contractually obligated to use your data only for the purposes we specify.
  • Third-Party Integration Partners — When you connect a third-party device, application, or platform, data may be exchanged between Zorv and that partner in accordance with the permissions you grant and that partner's terms of service. We do not share data with integration partners unless you have actively connected that service.
  • Your Coach or Team — If you are connected to a coach or team within Zorv, your athletic data may be visible to authorized coaches and team administrators as part of the coaching relationship. Your sign-in phone number is never shared with them.
  • Legal Obligations — We may disclose data when required by law, regulation, legal process, or enforceable governmental request, or to protect the rights, property, or safety of Zorv, our users, or the public.
  • Corporate Transactions — In connection with a merger, acquisition, financing, or sale of assets, your data may be transferred as part of that transaction.

6. Third-Party Integration Partners

Zorv is designed to integrate with a variety of third-party devices, applications, and platforms. When you connect a third-party service to your Zorv account:

  • Data obtained from that service is used only to provide and improve the Zorv coaching experience for you.
  • We practice data minimization — we collect only the data necessary for the features you use.
  • We do not sell, license, or share integration partner data with unrelated third parties for their own marketing or commercial purposes.
  • We comply with the applicable API terms, developer agreements, and data protection requirements of each integration partner.
  • You may disconnect any integration and revoke Zorv's access at any time via your account settings or through the partner's own authorization management.
  • Upon disconnection or account deletion, we delete data received from that integration in accordance with our data retention schedule (see Section 9).

Where specific integration partners impose additional privacy requirements (e.g., restrictions on using health data for advertising or profiling), we comply with those requirements. For a current list of supported integrations and any partner-specific data handling notes, visit zorv.ai/integrations.

Garmin Connect

If you connect your Garmin account to Zorv, Garmin sends us the data you choose to share in Garmin Connect. Depending on your Garmin sharing settings, this can include:

  • Activities — type, start time, duration, distance, pace and speed, heart rate, power, cadence, elevation, temperature, laps, GPS track, the activity file, and the name of the Garmin device that recorded it.
  • Health and wellness summaries — for example steps, heart rate and resting heart rate, stress and Body Battery, respiration, pulse oximetry, heart rate variability (HRV), sleep (duration, stages and sleep score), body composition, blood pressure, skin temperature, and fitness metrics such as VO2 max and fitness age.
  • Account identifiers — a Garmin user ID and the permissions you granted. We never ask for, receive or store your Garmin password.

Purpose. We use Garmin data only to provide the Services to you: to show your training, sleep and recovery in Zorv and to calculate your Zorv metrics (for example Session Load, Training Form and recovery). Zorv's AI coach uses Garmin data only if you give separate consent (see “Garmin data and AI” in Section 7).

Independent controllers. Garmin and Zorv each act as independent controllers of your data. Garmin's collection and use of your data is governed by the Garmin Connect Privacy Policy; Zorv's is governed by this Privacy Policy. We do not sell Garmin data.

Retention and deletion. We keep Garmin data while your Garmin account is connected and your Zorv account is active; temporary copies of the raw data Garmin sends us are deleted after about 90 days (see Section 9). When you disconnect Garmin — in Zorv (Settings → Integrations → Garmin) or in Garmin Connect — or delete your Zorv account, we end the connection with Garmin and delete the data we received from Garmin: the raw data, the sleep and recovery records sourced from Garmin, the activity files Garmin sent us, and the activities created only from those files (unless you have since added your own entries to an activity). Your consent to AI use of Garmin data ends at the same time. Activities you uploaded yourself, including files you exported from Garmin Connect, are not affected. Copies in backups are removed as described in Section 9.

7. AI and Automated Processing

Zorv uses artificial intelligence and machine learning to provide personalized coaching, training recommendations, and performance insights. Specifically:

  • AI models analyze your athletic and health data to generate coaching recommendations, training load calculations, and recovery guidance.
  • No legally or similarly significant decisions are made solely by automated processing without human oversight.
  • You may request information about the logic involved in automated processing by contacting privacy@zorv.ai.
  • AI-generated recommendations are informational and are not a substitute for professional medical or coaching advice.

Garmin data and AI

  • We process data from Garmin Connect with AI only after you give explicit consent, separately from connecting Garmin. We ask when you connect Garmin, and you can give or withdraw consent at any time in Settings → Integrations → Garmin. Withdrawing consent takes effect immediately.
  • Without your consent, your Garmin data is shown to you in Zorv but is never sent to an AI model.
  • With your consent, Garmin data is used only as input when Zorv's AI coach answers your questions or writes your insights, briefings and summaries.
  • We never use Garmin data to train, test, benchmark or improve AI models, and we do not add it to AI knowledge bases.

AI food recognition

In the fueling log you can log food from a photo of your meal (Photo), a photo of a nutrition label (Label), or by saying what you ate (Dictate). These features use AI services from other companies and are off until you turn them on.

  • Opt-in and revocable. We ask for your consent the first time you use Photo, Label or Dictate. You can give or withdraw consent at any time in Settings → Privacy → AI food recognition; withdrawing takes effect immediately for new requests. Without your consent nothing is sent to an AI service, and search, barcode scanning and repeating earlier entries keep working. We keep a record of when you gave or withdrew consent and which version of this notice you were shown.
  • What is sent. Photo: your meal photo (resized), together with the names of foods you have logged recently and your preferred units, to help recognise foods and portions. Label: the photo of the nutrition label. Dictate: your voice recording, which is converted to text, and the resulting transcript, which is analysed to identify foods and amounts. We do not send your name or email address with these requests.
  • Who processes it. We use two AI providers as subprocessors, acting on our instructions: Anthropic (recognising foods in meal and label photos and in dictation transcripts) and OpenAI (converting voice recordings to text). They process this data to return the result to us. Per their API terms, data sent through their APIs is not used to train their models. Their retention of API data is governed by those terms.
  • What we keep. Meal photos are stored with your fueling log so you can see them with your entries; they are kept while your account is active and deleted with your account (see Section 9). We do not store label photos, voice recordings or transcripts: they are processed to return the result and then discarded. The foods you confirm are saved to your fueling log like any other entry. We also keep a daily count of your AI food recognition requests to apply the daily limit.
  • Daily limit. AI food recognition is limited to 20 requests per person per day; each photo, label or dictation counts as one request. The limit resets each day in your local time zone.
  • Results are estimates. Review them before you save an entry.
  • We do not use your meal photos, label photos, voice recordings or transcripts to train AI models.

8. Cookies and Tracking Technologies

  • Session cookies — We use a session cookie required for authentication. This is essential for the Services to function.
  • Server-side analytics — We use Axiom for server-side operational analytics. We do not use browser-side analytics SDKs.
  • We do not use Facebook Pixel, Google Analytics, or other advertising or tracking cookies.

Opt-out preference signals

We recognize the Global Privacy Control (GPC) signal. If your browser sends a GPC signal, we will treat it as a valid opt-out request under applicable privacy laws. We do not currently respond to Do Not Track browser signals as there is no uniform industry standard for this.

9. Data Retention

  • Active account — We retain your data while your account is active and as needed to provide the Services.
  • Deleted account — After you request account deletion, we apply a 30-day grace period during which you may recover your account. After that, we permanently delete your data within 60 days of the deletion request.
  • Backups — Backups that may contain your data are removed within 90 days of account deletion.

Recovery and wearable data (ZORV Recovery)

  • Core recovery data — Normalized sleep records, recovery scores (ZRI), and recovery journal entries are retained while your account is active unless you ask us to delete them or delete your account.
  • Raw wearable payloads — Temporary copies of provider API responses used for debugging and normalization are automatically deleted after approximately 90 days; normalized sleep and scores remain the long-term source of truth.
  • Metric baselines — Rolling statistical baselines are trimmed to a recent window (on the order of 90 days of history).
  • AI recovery insights — Generated insights and summaries are automatically deleted after approximately one year.
  • Garmin data — Deleted when you disconnect Garmin (in Zorv or in Garmin Connect) or delete your account, as described in Section 6 (“Garmin Connect”).
  • AI food recognition — Meal photos are kept with your fueling log while your account is active. Label photos, voice recordings and transcripts are not stored. Daily request counts are kept while your account is active. See Section 7 (“AI food recognition”).
  • Pipeline and notification logs — Completed or failed background jobs are removed after about 7 days. Notification delivery audit rows are removed after about 30 days.

10. Data Storage & Security

  • Cloud infrastructure — We use Amazon Web Services (AWS) for our infrastructure, hosted in the United States (us-east-2).
  • Encryption in transit — All traffic is encrypted using TLS 1.3.
  • Encryption at rest — Data stored in our databases is encrypted at rest using AES-256.
  • OAuth tokens — Stored encrypted in AWS Secrets Manager; we do not log OAuth tokens.
  • Access controls — We implement role-based access controls and the principle of least privilege for internal access to user data.

We take commercially reasonable measures to protect your data. However, no method of transmission or storage is 100% secure, and we cannot guarantee absolute security.

11. International Data Transfers

Our Services operate from infrastructure located in the United States. If you access the Services from outside the United States, your data will be transferred to and processed in the United States, which may have data protection laws different from those of your jurisdiction.

For transfers of personal data from the European Economic Area (EEA), Switzerland, or the United Kingdom, we use appropriate safeguards, including, where applicable, Standard Contractual Clauses approved by the European Commission. To request a copy of these safeguards, contact us at privacy@zorv.ai.

12. Your Rights

Depending on your jurisdiction, you may have the following rights:

  • Right to access — Request a copy of the personal data we hold about you. Contact us at privacy@zorv.ai or use the in-app account settings to request a data export.
  • Right to erasure — Request deletion of your account and associated personal data. Account deletion can be initiated via settings or by contacting privacy@zorv.ai.
  • Right to data portability — Receive your data in a portable format (e.g., JSON export). Contact us at privacy@zorv.ai to request an export.
  • Right to rectification — Update or correct your personal data in your account settings.
  • Right to restrict processing — Request that we restrict how we process your data in certain circumstances.
  • Right to object — Object to our processing of your data, including for marketing purposes.
  • Right to withdraw consent — Where processing is based on consent, you may withdraw it at any time.

To exercise any of these rights, contact us at privacy@zorv.ai or use the relevant options in your account settings.

Legal basis for processing (EEA/UK)

Where applicable under the GDPR, our legal bases for processing your personal data include:

  • Performance of a contract — to provide the Services to you.
  • Legitimate interests — to improve and secure the Services, provided these do not override your rights.
  • Consent — where you explicitly opt in, e.g., connecting a third-party integration.
  • Legal obligation — where required by applicable law.

California residents (CCPA)

If you are a California resident, you have the right to know what personal information we collect, request its deletion, and opt out of any “sale” or “sharing” of your personal information as defined under the CCPA. We do not sell your personal information. To exercise your rights, visit our Do Not Sell My Data page or contact us at privacy@zorv.ai.

Other US state privacy rights

Residents of states with applicable privacy laws (including Colorado, Connecticut, Virginia, and others) may have similar rights to access, correct, delete, and opt out of certain processing of their personal data. To exercise these rights, contact us at privacy@zorv.ai.

13. Children's Privacy

The Services are not directed at individuals under the age of 16. We do not knowingly collect personal data from children under 16 without parental or guardian consent. If we become aware that we have collected personal data from a child under 16 without appropriate consent, we will take steps to delete that information promptly. If you believe we have collected data from a child, please contact us at privacy@zorv.ai.

15. Third-Party Services

We use the following third-party services to operate Zorv. Each processes data as described below:

  • Sentry — Error reporting and performance monitoring. We send anonymized error logs and stack traces to help us fix bugs. Sentry Privacy Policy
  • Stripe — Payment processing. Stripe handles card transactions; we do not store full card numbers. Stripe Privacy Policy
  • Axiom — Server-side analytics. We use Axiom for operational metrics and logs; no browser-side tracking. Axiom Privacy Policy
  • Stadia Maps — Map tiles, route planning, elevation and place search for activity routes and course visualization. Map tiles and requests; no persistent location tracking. Stadia Maps Privacy Policy
  • Supabase — Authentication and database infrastructure. User accounts and app data are stored in Supabase, hosted on AWS in East US (Ohio), us-east-2. Supabase Privacy Policy
  • Anthropic — AI processing, including recognising foods in meal photos, nutrition label photos and dictation transcripts when you turn on AI food recognition (Section 7). Anthropic Privacy Policy
  • OpenAI — Speech-to-text for dictation when you turn on AI food recognition (Section 7). OpenAI Privacy Policy

16. Contact & Privacy Inquiries

  • Data Controller — Zorv Technologies LLC
  • Privacy contact — privacy@zorv.ai
  • EU/UK Representative (if applicable): To be designated

For any request related to your personal data or this policy, please contact us at privacy@zorv.ai.