ICU Coach ICUCOACH Intelligent Coaching Utility
Back to Home

Privacy Policy

Last Updated: November 20, 2026

Türkçe

1. Introduction

ICU Coach ("we", "our", "the app") is an AI-powered training coach application for endurance athletes. This Privacy Policy explains how we collect, use, store, and protect your information in compliance with the General Data Protection Regulation (GDPR), the California Consumer Privacy Act (CCPA), and applicable data protection laws.

Data Controller

The data controller responsible for your personal data is:

  • Name: Murat Aydın (Individual Developer)
  • Email: support@icucoach.app
  • Country: Türkiye

2. Legal Basis for Processing (GDPR)

We process your personal data based on the following legal grounds:

  • Consent (Art. 6(1)(a) GDPR): Health data access (HealthKit / Health Connect), data from Garmin Connect, push notifications, optional AI analysis, and coach data sharing (athletes explicitly consent via the invite acceptance flow).
  • Contract Performance (Art. 6(1)(b) GDPR): Providing the core app functionality (training analysis, recovery calculation, coaching services) as part of our service.
  • Legitimate Interest (Art. 6(1)(f) GDPR): Crash reporting and error monitoring to maintain app stability and security.
  • Legitimate Interest (Art. 6(1)(f) GDPR): Keeping a short record that a Garmin connection was removed, so that we can apply the removal again if we ever restore a backup. The record holds no health data and is deleted after 100 days.

3. Data We Collect

3.1 Data You Provide Directly

  • Intervals.icu account connection authorization (OAuth consent), display name, and selected sport preferences
  • AI provider API keys (OpenAI, Gemini) — stored securely on your device only
  • Training preferences (sport type, target race, thresholds, experience level)
  • App settings (language, theme, notification preferences)
  • Profile information (age, gender, weight)

3.2 Data Accessed from Intervals.icu (with your permission)

  • Wellness data (HRV, resting heart rate, sleep hours, weight, SpO2)
  • Training activities (distance, duration, power, heart rate, TSS, pace)
  • Planned workouts and events
  • Athlete profile (FTP, max HR, training zones, VO2max)
  • Weather data associated with your location

Stored history for athletes whose activities come from Garmin. If your activities on Intervals.icu come from Garmin, the app can ask our server to keep a copy of up to 180 days of your activity summaries and wellness fields from Intervals.icu. Beside these summaries we keep values that we compute from your recordings: training load, the time you spent at each heart rate, power and pace (pace also by gradient), your best efforts over set durations, your average heart rate, power and speed in each half of the activity, and how complete each recording is. From these values we also keep a small personal model for each group of sports and each source of recordings: two numbers that describe how your heart rate relates to training load, and figures that show how well they fit. They are computed only from your own recordings and are used only to compute your training load. They are deleted together with this copy. To compute them, our server reads the recording from Intervals.icu once and does not keep it. We do not store free text (such as notes or descriptions), second-by-second recordings, or GPS positions. If a later response from Intervals.icu leaves out a field, we keep the value already stored. This copy is deleted when you delete your account or disconnect Intervals.icu.

3.3 Health Data (with your explicit permission)

Health data is only accessed when you explicitly grant permission through your device's health settings. You can revoke this permission at any time.

Data TypeiOS (HealthKit)Android (Health Connect)
Sleep Duration & Quality✅✅
Heart Rate Variability (HRV)✅✅
Resting Heart Rate✅✅
Heart Rate✅✅
Weight✅✅
Blood Oxygen (SpO2)✅✅
VO2 Max✅✅
Steps✅✅
Body Fat Percentage✅✅
Active & Total Calories✅✅
Distance✅✅
Basal Metabolic Rate✅✅

If you enable Health Sync in the app, the device health metrics listed in the table above (including sleep, HRV, resting heart rate, heart rate, weight, SpO2, VO2 Max, steps, body fat percentage, calories, distance, and basal metabolic rate where available) may be synced to your Intervals.icu wellness account using your OAuth-authorized connection. This sync is used for core app functionality such as wellness continuity, dashboard readiness, and coaching insights. You can disable Health Sync at any time from Settings.

3.4 Coaching Data (with your explicit consent)

When you accept a coach's invitation to join their team, you explicitly consent to sharing your Intervals.icu training data with that coach. This connection is established through the standard Intervals.icu OAuth flow — you authorize access on the Intervals.icu consent screen before any data is shared.

When you join a coaching team, the following data is collected and stored:

  • Coach-athlete relationship: Your Intervals.icu athlete ID, display name, the coach you are connected to, and the date you accepted the invitation
  • Invite metadata: The invitation token used to join, invite status, and acceptance timestamp
  • OAuth access token: Your Intervals.icu OAuth access token is stored in encrypted form (AES-256-GCM) on our server so your coach can access the data you authorized. The encryption key is stored separately from the database and is never exposed. This token grants access only to the scopes you approved on the Intervals.icu consent screen.

The following Intervals.icu data becomes accessible to your coach through their authorized connection:

  • Training activities (workouts, rides, runs, swims)
  • Wellness data (weight, sleep, HRV, resting heart rate)
  • Calendar (planned workouts and events)
  • Athlete settings (profile and preferences)

Your coach accesses this data using your individually authorized OAuth token — no additional data access is granted beyond what you approved on the Intervals.icu consent screen. When you revoke the coach connection, the stored encrypted token is permanently deleted.

3.5 Automatically Collected Data

The following data is collected automatically to maintain app stability and improve the service:

  • Crash and error reports: Device model, operating system version, app version, crash stack traces, and error context (via Sentry)
  • IP address: Collected incidentally by Sentry and cloud services during network requests. Not used for tracking or profiling.
  • AI usage metrics: Daily count of AI feature usage, stored locally on your device for rate-limiting purposes only
  • Subscription status: Anonymous purchase and entitlement data processed by RevenueCat for subscription management
  • Coach push notification tokens: When a coach enables push notifications, an Expo push token is stored server-side (Supabase, EU). Used solely to deliver team activity notifications (athlete joined/disconnected). Removed when the coach disables notifications or uninstalls the app.

3.6 AI Service Data Sharing (with your explicit consent)

Before any data is sent to an AI service, the app asks for your explicit consent. You must review and accept which data is shared, who it is shared with, and how it will be used. You can decline at any time, in which case no data is sent and AI features will not be available until you provide consent.

When you use AI-powered features (Auto Coach, reports, nutrition advice, race predictions), the following data may be sent to your selected AI provider:

  • Training data: Recent activities (type, duration, load, pace, power zones), planned workouts, and weekly volume
  • Health metrics: HRV, resting heart rate, sleep duration, VO2max, stress and Body Battery, whatever their source
  • Profile information: Age, weight, height, gender, active sports, fitness level (CTL/ATL/TSB scores)
  • Wellness data: Recovery state, fatigue scores, form rating

Data is sent to one of the following AI providers, depending on your configuration:

  • Google Gemini — when you use your own Gemini API key (data sent directly from your device to Google's servers)
  • OpenAI (GPT-4o) — when you use your own OpenAI API key (data sent directly from your device to OpenAI's servers)
  • ICU Coach Cloud AI — when you use the Cloud AI subscription (data sent to our Vercel backend and processed via OpenAI; the resulting AI report is cached for up to 42 days, see section 6)

Data that we receive directly from Garmin is sent to an AI service only through ICU Coach Cloud AI. It is never sent with your own API key.

All AI providers are subject to their own privacy policies. Data sent for AI analysis is:

  • Used solely to generate the requested coaching response
  • Not stored by ICU Coach after the response is generated, except the Cloud AI report cache described in section 6
  • Not used for advertising, profiling, or model training by ICU Coach
  • Subject to the AI provider's data handling policy (see Google's and OpenAI's privacy policies for details)

3.7 Data from Garmin Connect (with your permission)

If you choose to connect your Garmin account, ICU Coach receives the data types below that you allow in Garmin Connect. You connect through Garmin's own sign-in page; we never see or store your Garmin password.

Data from GarminWhat we use it for
Daily summaries (including resting heart rate)Daily recovery status and training readiness; long-term tracking
SleepRecovery status and training readiness; long-term tracking
Heart rate variability (HRV)Recovery status and training readiness; long-term tracking
StressRecovery status; long-term tracking
RespirationRecovery status; long-term tracking
Pulse oximetryRecovery status; long-term tracking
User metrics (such as VO2max)Your fitness level and how it changes over time
Body composition (such as weight and body fat)How your body composition changes alongside your training; long-term tracking
Activities (summaries and details)Your activity list, training analysis, training load and fitness tracking; long-term tracking

Why we keep it. We keep this data so that you can follow how these values change over months and years. It stays on our server for as long as your Garmin connection and your account exist. ICU Coach gives training guidance; it is not a medical service and does not diagnose any condition.

What we keep from activities.

  • For each activity we keep its summary: sport, start time, duration, distance, heart rate, speed, power, cadence, elevation, laps, pool lengths for swims and device model, the identifier Garmin gives the activity, whether it was entered by hand, and which parts of a multisport activity belong together.
  • We also keep values we compute when the activity arrives: training load, the time you spent at each heart rate, power and pace (pace also by gradient), your best efforts over set durations, your average heart rate, power and speed in each half of the activity, and how complete each recording is.
  • Garmin also sends the second-by-second recording. Our server uses it once to compute these values and does not keep it.
  • We do not keep GPS positions, or an activity's name or notes.
  • Activities are kept like the other Garmin data above: for as long as your Garmin connection and your account exist.

The personal model described in section 3.2 is also fitted on these activities; the part built from them is deleted when your Garmin connection ends.

Garmin sends this data to our server from the moment you connect. Earlier history is not transferred. The access tokens Garmin issues are stored encrypted on our server and are renewed only there, on a schedule before they expire, never on your device.

You can disconnect at any time in the app's settings or in Garmin Connect. If you disconnect in the app, we delete the Garmin data we hold for you immediately. If you revoke access in Garmin Connect instead, we delete it as soon as Garmin notifies us. Deleted data can remain in encrypted backups for up to 90 days (see section 6).

Unused connections. If you do not open ICU Coach for 60 days, we end your Garmin connection at Garmin and delete the data we received directly from Garmin, as when you disconnect. You can connect again at any time. Garmin does not resend data from before the new connection.

Removal record. When a Garmin connection is removed (by you in the app, by you at Garmin, by replacing it with a different Garmin account, by deleting your ICU Coach account, or by us after 60 days without use), we keep a small record that the removal happened: an internal connection identifier, your Intervals.icu athlete id, the reason and the date. It holds no health data and no Garmin account identifier. We keep this record for 100 days and then delete it. We keep it so that, if we ever restore a backup, we can apply your removal again.

3.8 AI Transparency Statement

What AI does in ICU Coach. AI features (Auto Coach, reports, nutrition advice, race predictions) read your training and recovery data to produce coaching advice for you.

Your consent comes first. No data is sent to an AI service until you have given explicit consent in the app. You can withdraw that consent at any time in Settings. After you withdraw, no further data is sent to AI services. A request that was already sent cannot be called back; if it finishes, its result is kept for at most 42 days and then deleted. The AI reports we cached for you are deleted.

Which AI service. Data from Garmin is processed only by ICU Coach Cloud AI, which uses OpenAI's API. It is never sent to an AI provider through your own API key.

No AI training. We do not use your data, or anything derived from it, to train, evaluate or improve AI models. Under OpenAI's API terms, data sent to the API is not used to train or improve OpenAI's models. OpenAI may keep it for up to 30 days for abuse monitoring.

AI results. AI results produced from your data are treated with the same protections as the data itself.

4. How We Use Your Data

  • Generate personalized AI training recommendations
  • Calculate recovery status and training readiness
  • Show long-term trends in your health and training data
  • Provide nutrition advice based on your activity
  • Predict race performance
  • Display weather conditions for your training location
  • Send scheduled training notifications (with your permission)
  • Monitor and fix app crashes and errors
  • Manage your subscription and in-app purchases
  • Facilitate coach-athlete connections so coaches can view athlete training data and provide personalized coaching guidance

We do NOT use your data for advertising, profiling, or automated decision-making that produces legal effects.

5. Data Storage and Security

  • Intervals.icu OAuth access tokens are stored locally on your device using encrypted secure storage (Expo SecureStore).
  • Training preferences and app settings are stored locally on your device (AsyncStorage).
  • Coach-athlete relationship data (athlete ID, display name, coach ID, invite token, connection status) and encrypted OAuth tokens are stored in a secure PostgreSQL database hosted on Supabase (EU — Frankfurt, Germany). OAuth tokens are encrypted at the application layer using AES-256-GCM before storage; the encryption key is held only on the application server (Vercel) and never stored in the database.
  • When using the Cloud AI option, your training context is sent to our secure backend (hosted on Vercel, US region) for AI processing. This data is processed in memory and not persisted — it is discarded immediately after the AI response is generated.
  • When using your own AI keys (OpenAI/Gemini), data is sent directly from your device to the AI provider's servers.
  • OAuth client secrets are never stored in the mobile app. Authorization code exchange is handled on a secure backend endpoint.
  • Data from Garmin and the stored Intervals.icu history (sections 3.2 and 3.7) are kept in the same Supabase database (EU — Frankfurt, Germany). Data deleted from this database can remain in encrypted backups for up to 90 days and is then removed.
  • API request rate limiting metadata (request counts per identifier) is processed by Upstash Redis (serverless, EU region) to prevent abuse. No personal data beyond an anonymized request identifier and timestamp is stored. Rate limiting data expires automatically within the configured time window (typically 60 seconds).

6. Data Retention

Data TypeRetention PeriodLocation
Intervals.icu OAuth tokens & AI provider API keysUntil you delete them or uninstall the appYour device (SecureStore)
App settings & preferencesUntil you delete them or uninstall the appYour device (AsyncStorage)
Cached training dataAutomatically refreshed; stale data expires within 24 hoursYour device (AsyncStorage)
AI usage countersReset daily; cleared on uninstallYour device (AsyncStorage)
Crash reports (Sentry)90 days (Sentry default retention)Sentry servers (EU — Frankfurt, DE)
Subscription data (RevenueCat)As per RevenueCat's retention policyRevenueCat servers (US)
Cloud AI reportsCached up to 42 days so a report opens again without a new AI call; deleted at once when you disconnect or delete your account, or when you withdraw AI consentSupabase (EU — Frankfurt, DE)
Garmin connection (encrypted tokens and the Garmin user ID mapped to your profile)Until you disconnect or delete your account. Deleted immediately when you disconnect in the app, or as soon as Garmin notifies us that you revoked access in Garmin Connect.Supabase (EU — Frankfurt, DE)
Garmin health data (all types listed in section 3.7)Until you disconnect or delete your account. Deleted immediately when you disconnect in the app, or as soon as Garmin notifies us that you revoked access in Garmin Connect.Supabase (EU — Frankfurt, DE)
Garmin removal record (internal connection identifier, Intervals.icu athlete id, reason and date; no health data and no Garmin account identifier)100 days after the connection is removed, then deletedSupabase (EU — Frankfurt, DE)
Stored Intervals.icu history (up to 180 days of activity summaries and wellness fields; only if your activities come from Garmin)Until you delete your account or disconnect Intervals.icuSupabase (EU — Frankfurt, DE)
Encrypted backups of our databaseData deleted from the database can remain in encrypted backups for up to 90 daysSupabase (EU — Frankfurt, DE)
Coach-athlete relationship dataUntil the athlete or coach revokes the connection, or upon deletion requestSupabase (EU — Frankfurt, DE)
Encrypted OAuth tokens (coaching)Until the connection is revoked — deleted immediately upon revocationSupabase (EU — Frankfurt, DE), encrypted with AES-256-GCM
Coach push notification tokenUntil coach disables notifications or uninstalls the appSupabase (EU — Frankfurt, DE)
Rate limiting metadataAutomatically expires within 60 secondsUpstash Redis (serverless, EU)

7. Third-Party Services

The app integrates with the following third-party services. Each has its own privacy policy governing their data handling:

ServicePurposeData SharedServer Location
Garmin (Garmin Connect) Data source you choose to connect Garmin provides the health data you allow (see section 3.7); see Garmin's privacy policy Per Garmin
Intervals.icu Training data platform OAuth-based authorized access token; planned workouts created by the app; selected wellness metrics synced from device health when Health Sync is enabled EU
Google Gemini AI analysis (optional) Anonymized training context for AI processing US
OpenAI AI analysis (optional) Anonymized training context for AI processing US
Sentry Crash reporting & error monitoring Device info, OS version, crash data, IP address EU (Frankfurt)
RevenueCat Subscription & purchase management Anonymous user ID, purchase receipts, entitlements US
Open-Meteo Weather data Geographic coordinates only (no personal data) EU
Apple HealthKit Health data (iOS) Read-only access with your permission Your device
Google Health Connect Health data (Android) Read-only access with your permission Your device
Supabase Coach-athlete relationship database Athlete ID, display name, coach ID, invite token, connection status EU (Frankfurt)
Expo Push Service Remote push notifications for coaches Expo push token, notification title and body text US
Upstash Redis API rate limiting & abuse prevention Anonymized request identifier, request count (no personal data) EU

Processors of data from Garmin: Vercel (backend, US), Supabase (database, EU — Frankfurt, DE) and OpenAI (AI processing, US).

We encourage you to review each service's privacy policy.

8. International Data Transfers

Some third-party services process data in the United States. When your data is transferred outside the European Economic Area (EEA), we rely on:

  • Standard Contractual Clauses (SCCs) adopted by the European Commission
  • The service provider's compliance with applicable data protection frameworks

Crash reporting data (Sentry) and coach-athlete relationship data (Supabase) are processed within the EU (Frankfurt, Germany).

Data from Garmin about users in the EEA, the UK and Switzerland is transferred under the EU Standard Contractual Clauses that are part of our agreement with Garmin.

9. Push Notifications

9.1 Local Notifications (Athletes)

With your permission, the app can send local push notifications to remind you of your daily training readiness. These notifications are:

  • Scheduled locally on your device — no data is sent to any server
  • Fully configurable (time, enable/disable) in app settings
  • Can be disabled at any time through app settings or your device's notification settings

9.2 Remote Notifications (Coaches)

Coaches may receive remote push notifications when team-related events occur, such as:

  • An athlete accepts an invitation and joins the team
  • An athlete disconnects from the team

These notifications are delivered via the Expo Push Notification Service. Coach push tokens are stored in our database (Supabase, EU — Frankfurt) and are used solely for delivering team activity notifications. Coaches can disable push notifications at any time from the app, which removes the stored token from the server.

10. Data Sharing

We do NOT sell, rent, or share your personal data with any third parties for marketing or advertising purposes.

We do not sell data from Garmin and do not share it with anyone other than the processors listed in section 7 and a coach you have linked yourself.

Your data is only shared with third-party services in the following circumstances:

  • When Health Sync is enabled, selected Apple Health / Health Connect metrics are synced to your Intervals.icu wellness account via your OAuth-authorized connection
  • When you explicitly request an AI analysis (training context sent to AI provider)
  • When a crash occurs (anonymous error data sent to Sentry)
  • When you make a purchase (transaction data processed by RevenueCat and the platform store)
  • When you accept a coaching invitation, your Intervals.icu training data becomes accessible to that coach through the OAuth token you authorized. The coach can view your activities, wellness, calendar, and settings for coaching purposes only.

11. Your Rights

For All Users

  • You can delete your account in the app settings. This deletes the data on your device and most of the data on our servers; what is deleted and what is kept, and why, is listed on our Delete Your Data page. Uninstalling the app deletes only the data on your device.
  • You can revoke health data permissions at any time through your device settings.
  • You can revoke Intervals.icu access — the OAuth connection is automatically revoked when you delete your profile from the app. You can also manually revoke it via Intervals.icu → Settings → Apps.
  • You can disconnect from a coaching team at any time. When you revoke a coach connection, the coach immediately loses access to your training data and the relationship record is marked as revoked in our database.
  • You can disable push notifications at any time.
  • You can use the app without providing AI keys (demo mode available).
  • You can access, correct, export or delete your data, including data from Garmin, and withdraw any consent. To export your data, email support@icucoach.app. You can delete your account in the app's settings.

Additional Rights Under GDPR (EU/EEA Users)

  • Right of Access (Art. 15): You can request a copy of all personal data we hold about you.
  • Right to Rectification (Art. 16): You can correct inaccurate personal data via app settings.
  • Right to Erasure (Art. 17): You can request deletion of your personal data by uninstalling the app or contacting us.
  • Right to Data Portability (Art. 20): Since your data is stored locally on your device, you already have full access and control over it.
  • Right to Restrict Processing (Art. 18): You can disable specific features (AI, health data, notifications) independently.
  • Right to Object (Art. 21): You can object to processing based on legitimate interest by contacting us.
  • Right to Withdraw Consent: You can withdraw consent at any time without affecting the lawfulness of prior processing.
  • Right to Lodge a Complaint: You have the right to lodge a complaint with a supervisory authority in your country of residence. For Türkiye: KVKK (kvkk.gov.tr).

Additional Rights Under CCPA (California Users)

  • You have the right to know what personal information is collected and how it is used.
  • You have the right to request deletion of your personal information.
  • We do not sell your personal information.
  • You will not be discriminated against for exercising your rights.

12. Children's Privacy

ICU Coach is not intended for use by children under 16. We do not knowingly collect data from children. If you believe a child under 16 has provided us with personal data, please contact us so we can take appropriate action.

13. Changes to This Policy

We may update this Privacy Policy from time to time. When we make significant changes, we will notify you through an in-app notice or by email. The latest version will always be available within the app. We recommend reviewing this policy periodically.

14. Contact

For questions, data requests, or concerns about this Privacy Policy, contact us at:

  • Email: support@icucoach.app

We will respond to your request within 30 days.

© 2026 ICU Coach. All rights reserved.