CoachCian Privacy Policy
Last updated 11 November 2026
CoachCian is a personal running coach for iPhone, Apple Watch, Android, Wear OS, and Garmin. This policy explains
what data the app uses, how partner integrations (including Garmin Connect, Strava, Apple Health, and Health Connect) work, which third-party
services process data, our AI Transparency commitments, and how you can access, correct, export, or delete your data and withdraw consent at any time.
The short version: your data stays on your device by default, there is no mandatory account or login, we never sell your data, we never use
Garmin or Strava data to train or evaluate AI models, we never use data for advertising, and we do not track you across apps or websites.
At a glance
- No mandatory account, no sign-in. Everything works on first launch.
- On-device first. Your plans, runs, routes, and history are stored locally on your device.
- Permissions & integrations are explicit opt-in — requested only when you connect or use the feature that needs them.
- No sale of data, no advertising, no cross-app tracking.
- Zero AI training on user or partner data. Garmin and Strava data (and anything derived from them) are never used to train, evaluate, or improve AI models.
Who we are
CoachCian ("the app", "we", "us") is developed and operated by Cian Murphy (CoachCian).
For any privacy, data-subject, or partner-compliance inquiry or request, contact
coachciansupport@gmail.com.
Data stored on your device
By default CoachCian keeps your data locally on your device (encrypted OS storage and local app database on iOS and Android).
This includes your training plan, recorded runs, GPS routes, run history, gear mileage, fuelling logs, achievements, and settings.
This data is not sent to us or to any server unless you explicitly turn on one of the optional features described below.
Garmin Connect API & Garmin Watch Integration (Optional, Explicit User Consent)
If you choose to link your Garmin Connect account or pair a Garmin watch in Settings → Garmin Watch, CoachCian handles Garmin user data strictly as follows:
- How Garmin user data is used by CoachCian:
- OAuth 2.0 Authorization & Account Link: When you tap "Connect Garmin Connect" and grant consent on Garmin's official authorization screen, CoachCian receives an OAuth 2.0 access/refresh token pair, reads your Garmin Connect user ID (
/wellness-api/rest/user/id) and granted permissions (/wellness-api/rest/user/permissions), and stores your OAuth tokens exclusively in your device's encrypted Keychain / Keystore.
- Structured Workout & Calendar Sync (Training API): With your
WORKOUT_IMPORT permission, CoachCian sends your upcoming 14-day planned structured running workouts (step durations, repeat counts, and target speed bands) to the official Garmin Connect Training API (POST /training-api/workout/v2 and POST /training-api/schedule) so they appear automatically on your Garmin Connect calendar and Garmin watch. When your training plan changes or you disconnect, CoachCian updates or deletes those scheduled entries (DELETE /training-api/schedule and DELETE /training-api/workout/v2).
- Activity / Workout Files (when authorized or imported): If you import a Garmin workout file (
.FIT, .TCX, or .GPX) or authorize Garmin Activity/Wellness sync, your activity summary and workout telemetry (start time, duration, distance, pace, splits, heart rate, cadence, elevation, and GPS route) are stored locally on your device solely to display your run log, mark planned sessions complete, and calibrate your training paces.
- Optional Companion Watch Pairing Code: If you use the optional CoachCian Garmin Connect IQ companion app with an 8-character pairing code instead of OAuth, the watch sends only that random pairing code and today's date to fetch today's workout targets; completed runs are saved locally by the watch into Garmin Connect without sending your GPS track or heart-rate stream to our servers.
- Third parties that receive or process Garmin user data:
- Garmin Ltd. / Garmin International, Inc.: Receives the structured workouts CoachCian pushes to your Garmin Connect calendar and authenticates your OAuth 2.0 session directly on
connect2.garmin.com, diauth.garmin.com, and apis.garmin.com.
- Supabase Inc. (hosted on Amazon Web Services / AWS): Our backend hosting provider operates a stateless HTTPS OAuth 2.0 PKCE token-exchange proxy (
garmin-token Edge Function) solely so our Garmin API client secret is never embedded in mobile binaries, and relays short-lived workout step targets if you use the optional 8-character pairing code. Supabase does not store, log, or retain Garmin user activity data, wellness metrics, or Garmin OAuth tokens in any database.
- Apple Inc. / Google LLC (On-Device OS Services, Optional Health & Backup): Your Garmin OAuth tokens are stored encrypted in Apple iOS Keychain or Android Keystore on your device. Only if you explicitly enable Apple HealthKit, Android Health Connect, or private iCloud Drive backup on your device will locally stored workout summaries sync to your own personal Apple or Google account under your control.
- Cloudflare Inc.: Hosts CoachCian's static website and privacy policy (
coachcian.pages.dev). Cloudflare does not receive or process any Garmin API traffic or Garmin user data.
- AI Providers, Analytics & Ad Networks — None for Garmin Data: Zero Garmin API data or Garmin device-sourced data is shared with analytics providers, advertising networks, Strava, or cloud AI/LLM providers.
- Whether Garmin user data is sold or shared with third parties:
No. CoachCian never sells, rents, licenses, trades, or shares Garmin user data (or data derived from it) with any third party for commercial, advertising, marketing, analytics, data-brokerage, or independent third-party purposes. Data is transmitted strictly to the infrastructure sub-processors itemized above solely to execute the Garmin sync or personal device backup you explicitly initiated.
- Strict prohibition on AI model training, evaluation, or improvement:
Garmin user data — and anything derived from Garmin user data or Garmin APIs — is never used to train, evaluate, fine-tune, benchmark, or improve any artificial intelligence (AI), large language model (LLM), or machine-learning model (internal or third-party). Garmin API keys issued to CoachCian are used exclusively by CoachCian and are never shared with or transferred to any third party.
- How to withdraw Garmin consent & disconnect:
You can withdraw consent at any time in Settings → Garmin Watch → Disconnect Garmin Connect (which immediately erases your Garmin OAuth tokens and scheduled-workout ledger from your device and calls Garmin's
DELETE /wellness-api/rest/user/registration endpoint to revoke CoachCian's registration with Garmin), or at any time inside your Garmin Connect Account Settings → Account Information → Connected Apps.
AI Transparency Statement (Explicit Consent, Easy Withdrawal & Zero Model Training)
- Deterministic Coaching by Default (No AI Required): CoachCian builds your training plan, calculates target paces, schedules Garmin and Apple Watch workouts, and generates your post-run debriefs on your device using deterministic sports-science rules, with no AI and no network calls required.
- No Garmin or Strava Data in AI Systems & Zero AI Model Training: Data sourced from Garmin APIs/devices or the Strava API (and anything derived from them) is never used to train, evaluate, fine-tune, or improve any AI or machine-learning model, and CoachCian does not send Garmin API or Strava API payloads to third-party AI providers.
- Explicit Opt-In Consent for Optional Cloud AI Features: Optional AI features — (1) conversational Coach chat and "Life Happens" schedule adjustments, (2) optional cloud AI wording polish on locally recorded run debriefs, and (3) optional "Snap a Meal" photo calorie/macro estimation — are off by default. Before any data leaves your device for cloud AI inference, CoachCian presents an explicit in-app Cloud AI Consent prompt disclosing what local context is sent (for example: your prompt, training plan summary, locally recorded run/readiness summary, or meal photo — never your name, email, or GPS track) and will not proceed unless you tap to consent.
- AI Providers Used (Only After Explicit Consent): Depending on your choice, inference is handled either on-device by Apple Intelligence (never leaves your phone), via CoachCian's stateless cloud AI proxy on Supabase forwarding to Groq Inc. (stateless API inference with zero training retention), or directly via your own optional user-supplied API key for Anthropic (Claude), OpenAI, or Google Gemini.
- Easy 1-Tap Consent Withdrawal: You can withdraw AI consent at any time with a single switch in Settings → Coach → Cloud AI (toggle off) or by clearing any user-supplied API key in Settings. Withdrawing consent stops all cloud AI requests immediately without affecting your training plan, run tracking, or Garmin/Watch sync.
Apple Health (HealthKit) & Android Health Connect
- Reads (with your permission): your past running workouts (exercise sessions, distance, and exercise routes), to recalibrate your
training paces; the heart rate and step counts recorded with those workouts (for heart-rate charts,
debriefs, and cadence); resting heart rate, heart-rate variability, sleep, and VO2max (for readiness and
coaching); and your most recent body mass, to compute workout energy.
- Pregnancy and breastfeeding (only if you turn it on): if you switch on "Use my
Apple Health pregnancy log", the app also reads the pregnancy and lactation entries you have logged
in Apple Health, so it can offer to adjust your training (for example, turn on pregnancy
mode or the breastfeeding fuel add-on). It never changes anything until you choose, and this data
stays on your device.
- Writes (with your permission): the runs you record in CoachCian are saved to
Apple Health or Android Health Connect as workouts (including exercise sessions, routes, distance, heart rate, steps, and active calories burned) so they appear in your fitness ecosystem.
- In the background: when another app or device saves a run to Apple Health or Health Connect, the
app checks for it so your debrief is ready. You can turn this off in Settings.
- Limited Use Compliance (Apple HealthKit & Google Health Connect Permissions Policy): The use of information received from Apple HealthKit and Android Health Connect adheres strictly to the Apple HealthKit guidelines and the Google Play Health Connect Permissions Policy, including the Limited Use requirements. Health data is used only to provide or improve user-facing running, coaching, and readiness features directly inside the app. It is never
transferred or shared with third parties (except when you explicitly opt in to cloud AI coaching for a local workout summary, as described in the AI Transparency Statement above), never used for advertising, marketing, or use-based data mining, never used for creditworthiness or lending determinations, and never sold.
Location
- Precise location is used to record your run route, distance, and pace, and for a once-a-day
background check of the weather for your next planned run.
- The app may request "Always" location so it can keep recording your run when
your phone is locked or you switch to another app — standard for a run tracker.
- Location is used only for these features. It is never sold or shared for advertising.
Other optional features that send data off your device
Each of the following is off by default and only sends data when you choose to use it.
iCloud backup (default off)
If you enable it, your runs, routes, and plans are backed up to your own private iCloud
Drive so they survive a new phone. Heart-rate and power data are stripped before
backup — only fitness/location/plan data is stored. It also includes the answers you give
in the app's check-ins (such as soreness or sleep) and, if you use pregnancy mode, which runs were
recorded during pregnancy and at what week, so restored runs keep being treated correctly. Nothing
read from Apple Health about pregnancy or breastfeeding is backed up. This uses your Apple iCloud
account; we have no access to it.
Friends (default off)
The optional Friends feature lets you add friends by handle or QR code to compare exploration territory, weekly distance, and send cheers using Apple CloudKit and our cross-platform social relay on Supabase. Shares carry aggregate running stats and explored map grid cells only — never raw heart-rate, medical, or Garmin OAuth data. You can remove any friend at any time with a swipe.
Route share links & live safety sharing (default off)
When you choose to share a route or send a temporary live-tracking safety link to your chosen safety contact, the app publishes an unguessable expiring link via Supabase. Live safety links expire automatically (default 6 hours) and never include heart rate — location, pace, and distance only.
Strava API Integration (default off, you connect it)
If you choose to connect your Strava account via OAuth 2.0 in Settings → Connected Devices, CoachCian uses the Strava API in strict compliance with the Strava API Agreement:
- What we access and why: CoachCian uploads your own completed runs (GPS route, heart rate, cadence, splits, and workout summary) to your own Strava profile (
activity:write), and reads your own saved Strava running routes (read_all) when you open the route picker for turn-by-turn navigation.
- Visible only to you: Data retrieved from the Strava API is displayed exclusively to you on your own device. We never display, share, sell, or aggregate your Strava data with other CoachCian users or any third party.
- Never used for AI, LLMs, or machine learning: Data obtained from the Strava API is never sent to, processed by, or used to train, fine-tune, evaluate, or prompt any artificial intelligence (AI), large language model (LLM), or machine learning system.
- Disconnect & immediate deletion: You can disconnect Strava at any time in Settings → Connected Devices → Disconnect Strava or via your Strava Connected Apps settings, which immediately deletes your Strava OAuth tokens and cached Strava data from your device.
Weather, Voice Journal, Contacts & Notifications
- Weather: Sends coarse run coordinates (no personal identifiers) to Open-Meteo for run weather forecasts.
- Voice journal (optional): Transcribed on-device via Apple Speech Recognition; audio and transcript stay on your device.
- Contacts & Notifications (optional): Contacts is used only to pick an on-device safety contact; workout and weather reminders are scheduled locally on your device.
All third-party services, hosting providers, integration partners & AI vendors
Depending on which optional features you explicitly enable, data may be processed by the following third-party providers, each bound by its privacy policy and security commitments. We never sell user or Garmin data to any third party, and we use zero third-party advertising or behavioral-analytics SDKs.
| Third Party & Role | What Data Is Processed & Purpose | Receives Garmin Data? | Privacy Policy |
Garmin Connect (Garmin Ltd.) Integration Partner |
OAuth 2.0 user authentication and pushing your 14-day structured running workouts to your Garmin Connect calendar (when you connect Garmin). |
Yes (your own Garmin account, with your consent) |
garmin.com/privacy/connect |
Supabase Inc. (hosted on AWS) Backend Hosting & Token Proxy |
Stateless OAuth 2.0 PKCE token-exchange proxy (garmin-token & strava-token Edge Functions); expiring route/live-safety share links; companion watch pairing relay; stateless AI proxy when Cloud AI is enabled. |
Stateless OAuth token exchange & planned workout targets only (not stored in DB) |
supabase.com/privacy |
Cloudflare Inc. Web & DNS Hosting |
Static hosting and TLS delivery for coachcian.pages.dev web pages. |
No |
cloudflare.com/privacypolicy |
Apple Inc. OS Platform, HealthKit, Keychain, iCloud |
Encrypted on-device Keychain token storage; optional Apple Health workout sync; optional private iCloud Drive backup & CloudKit Friends; on-device Speech & Apple Intelligence. |
Encrypted Keychain storage on your device (and optional user-enabled Apple Health / iCloud backup) |
apple.com/legal/privacy |
Google LLC Android Platform & Health Connect |
Encrypted Android Keystore storage and optional on-device Health Connect workout sync on Android. |
Encrypted Keystore storage on your Android device |
policies.google.com/privacy |
Cloud AI Providers (Groq Inc., Anthropic PBC, OpenAI, Google Gemini) Optional AI Inference Vendors |
Stateless coaching chat, local debrief wording polish, or meal-photo macro estimation — only when you grant explicit opt-in Cloud AI consent (or supply your own API key). Never used to train models. |
No — Garmin data & derivatives are never sent to AI systems or used for AI model training/evaluation |
groq.com/privacy-policy |
Strava Inc. Integration Partner |
Uploading CoachCian-recorded runs and reading saved Strava routes (only when you connect Strava). |
No |
strava.com/legal/privacy |
Open-Meteo Weather Data Vendor |
Coarse latitude/longitude weather forecasts for pre-run pacing adjustments (no user identifiers). |
No |
open-meteo.com/en/terms |
Data retention
On-device data remains on your device until you delete individual items, run Delete Everything in Settings, or uninstall the app.
Garmin and Strava OAuth tokens remain in your encrypted device Keychain only while connected and are deleted immediately upon disconnecting.
Optional iCloud backups stay in your personal iCloud Drive until overwritten or deleted by you. Route and live-safety share links expire automatically.
How to access, correct, export, or delete your data & withdraw consent
You have full control over your data directly inside CoachCian at any time — without waiting on a support ticket:
- Access your data: View all of your workouts, routes, plans, and profile settings in the History, Plan, and Settings tabs, and inspect a live itemized summary of all stored data, backups, and connected accounts in Settings → Privacy & Data.
- Correct your data: Edit, recalibrate, or repair any recorded workout (distance, duration, splits, effort, notes, or assigned shoe) in History → Select Run → Edit / Repair, and update any profile metric, goal, or scheduled workout directly in Plan or Settings.
- Export your data (Data Portability): Export a complete, machine-readable archive of your runs, GPS routes, workouts, and training data at any time in standard open formats (JSON, CSV, TCX, GPX, and FIT) via Settings → Privacy & Data → Export Data.
- Delete your data: Delete any individual run in History, or permanently erase all CoachCian data (all runs, plans, profile records, Keychain OAuth tokens, preferences, iCloud Drive backups, and active partner connections) via Settings → Privacy & Data → Delete Everything. Uninstalling CoachCian also removes its local database.
- Withdraw consent at any time:
- Garmin Connect: Tap Settings → Garmin Watch → Disconnect Garmin Connect (immediately deletes local tokens and revokes registration via Garmin's API) or revoke CoachCian in your Garmin Connect Account Settings.
- Cloud AI: Switch off Settings → Coach → Cloud AI at any time to immediately withdraw AI processing consent.
- Strava: Tap Settings → Strava → Disconnect or revoke in Strava Settings.
- Apple Health / Health Connect, Location, Contacts, Microphone & Notifications: Revoke any permission at any time in your iOS or Android system Settings.
- Privacy inquiries & assistance: You can also email coachciansupport@gmail.com at any time to exercise any privacy right or request assistance with access, correction, export, deletion, or consent withdrawal.
Children
CoachCian is not directed to children under 13 (or the minimum digital-consent age in your jurisdiction), and we do not knowingly collect personal data from children.
Security
All network connections use encrypted HTTPS/TLS 1.2+. Partner OAuth client secrets and backend service-role keys are held exclusively in server-side Edge Function secrets — never embedded in shipped mobile binaries — and OAuth user tokens are stored encrypted in the iOS Keychain / Android Keystore.
Changes to this policy
If this policy changes materially, we will update the "Last updated" date at the top of this page and, where appropriate, note it in the app.