Last updated: 10 November 2026
Hybrid Athlete: Training Plans ("we", "the app") is a library of coach-written training programs. This policy explains what we collect.
The short version: your training stays on your phone. We collect anonymous usage statistics, and you can turn those off inside the app.
Which version this describes. The sections on Apple Health, location, the camera and the weekly brief below arrive with version 2.0, the marathon release. Version 1.4, the one currently on the App Store, has none of them: it holds no Health or location permission and has no camera feature. As before, this policy is published ahead of the version it describes, not after. Route options and race-morning weather (below) arrive with version 2.1.
What stays on your device — all of it
Everything you enter or produce. Your onboarding answers, which plan you are on, your session logs and your benchmark scores are written to two places, both on your iPhone.
That includes what you tell the app about food. Your diet, your bodyweight and any allergies you select are health information, and they never leave your phone. They are used on the device to pick your recipes and work out a protein target, and for nothing else. We cannot see them, because there is nowhere for them to go.
The two places:
- A single file in the app's Application Support folder, holding your answers, your plan and your session logs.
- Two preference entries: a draft of your onboarding, so a force-quit does not lose it, and a cached copy of whether your subscription is active.
None of that is ever uploaded. We have no server, no account and no way to read your training. If you delete the app it is gone, including from us — because we never had it.
What we do collect: anonymous usage statistics
The app uses Google Analytics for Firebase to answer one question: which screens people use, and where they stop. That is how a two-person studio finds out that, say, everybody abandons on the same question.
What Firebase receives:
- Event names — "onboarding completed", "paywall shown", which step of the coach conversation you reached, whether a session was saved.
- A resettable app instance ID. Firebase generates it, it belongs to this app only, and it is what makes "500 people" different from "500 sessions". It is not your Apple Account, your email or your advertising identifier.
- Standard device facts sent with every event: device model, OS version, language, country.
- Whether you are a subscriber (true/false), so we can tell free and paid usage apart.
What Firebase does not receive: your name, your answers, your plan, your sessions, your scores, or anything you typed. Event names and screen names only.
We do not track you. The app does not ask for the advertising identifier, runs no ads, contains no attribution or session-replay SDK, and does not link anything to data from other companies. Google processes this data for us; see Google's privacy policy and how Google uses data from apps that use its services.
Turning it off
Profile → Privacy → Share usage data. Turning it off stops the collection itself, not just our sending — the app tells the SDK to stop. No feature changes, and nothing about your plan depends on it.
Purchases
Subscriptions are processed entirely by Apple through the App Store (StoreKit). We never see your payment details, your Apple Account, or your name. The app asks Apple's system whether your subscription is currently active and receives yes or no — nothing more. Apple's own handling is covered by Apple's Privacy Policy.
What we do NOT collect
- No account and no login. There is nowhere to sign in.
- We do not collect your name, email or contacts.
- Location is used during a run you start tracking, and once when you ask for route options (both below). Your runs' lines stay on your phone; only if you opt in are anonymous map squares shared (below).
- Apple Health is read and written only as described below, on the device.
- No advertising identifier, no ad network, no session replay.
Apple Health (version 2.0)
If you connect Apple Health, the app reads three things — your workouts, walking + running distance and heart rate — so a run you recorded with a watch or another app can be marked done on your plan with its distance and pace. The matching happens on your phone. Nothing read from Health is uploaded, stored anywhere but on the device, or used for analytics.
The app writes one thing: a run you track inside the app, saved to Health as an outdoor running workout with its distance and duration, so your other apps see it. Nothing else is written. You choose both permissions in the Health sheet and can withdraw them in the Health app at any time.
Location, during a tracked run (version 2.0)
Location is used only when you tap Track run — inside a run session, or on the run screen that Record a run on Today opens. While the run is open the app reads your position — in the background too, so the distance keeps counting with the phone in your pocket — and turns it into a distance, a pace and kilometre splits on the device. The route stays on the phone (from version 2.1 it is kept there for your route options — see "Your runs and where runners run" below — and in 2.0 it is not kept at all). What is saved with the session is the distance, the duration and the splits. Tracking ends with the session, and the system's location indicator shows the whole time.
Route options (version 2.1)
On a planned run day the run screen offers Where to run it: a track for 400s, a steady hill for hill reps, the flattest loops for intervals, a park for an easy run, two loops past your start for a long run. Only when you tap it does the app ask for your position, once, and use it for that search:
- Apple Maps. Your position and the points around it are sent to Apple's map service for walking directions and nearby places (tracks, parks). Apple handles those requests under its own privacy policy; we receive nothing from them but the paths and places.
- Height data. The app downloads elevation tiles for the area around you from the public Terrain Tiles dataset on Amazon Web Services, to measure how hilly each route is. A tile request names a square of about two kilometres and carries no identifier, account or other data.
- This hour's weather. Your position, rounded to about a kilometre, is sent to MET Norway (the Norwegian Meteorological Institute) for the forecast where you stand, so a loop can start into the wind. The request carries the app's name and nothing about you.
We do not store your position or the routes. The route you pick stays in memory, on the run screen, until you close it; a run you then track is saved as described above, without its route.
Your runs and where runners run (version 2.1)
On your phone. A run you track in the app keeps its line on this phone, so the route options can offer it back ("your route, run four times"). It is excluded from iCloud backup, and you can switch it off — which deletes the lines — on the route sheet.
Shared, only if you say yes. After a saved run the app asks, once, whether to share where you run. If you agree, each run sends only the ~150-metre map squares it passed through, with its first and last 400 metres removed on the phone, and nothing else: no name, no account, no time of day, no device identifier. Our server adds them to a running count per square, and the app shows a square as "popular with runners" only once at least five runs have passed through it. To stop abuse, the server keeps a one-day counter keyed by a scrambled (hashed) form of your network address; the address itself is not stored. You can switch sharing off at any time on the route sheet; counts already added cannot be traced back to you and are not removed.
Garmin Connect (version 2.1, when you connect it)
If you connect Garmin Connect in Profile, Garmin sends runs you record on a Garmin watch to our server. Each run — its summary (distance, time, heart rate, climb, the watch's name) and its route with heights — waits there until the app collects it, at most 30 days, and is deleted the moment the app has saved it. Your Garmin access tokens are kept on our server, encrypted, so the app never holds them; the app keeps only its own link key, in the iPhone's Keychain. We never receive your Garmin password.
On the phone, a Garmin run marks the planned day done and its route joins your own routes (above). Garmin runs are not shared in the anonymous street counts, and the numbers from Garmin are not sent to the AI coach.
Disconnect in Profile at any time: we tell Garmin to stop sharing, delete everything our server holds for the link, and delete the Garmin routes on the phone; the days already done stay done, without Garmin's numbers. You can also revoke access from Garmin Connect, with the same result. If the app has not been opened for two months, we disconnect Garmin for you in the same way, and the app asks you to connect again next time.
Race-morning weather (version 2.1)
For a race picked from the app's list, the usual race-morning temperatures come with the app (worked out in advance from NASA's public climate data). In the last nine days before the race the app asks MET Norway for the forecast at the race city — the race's coordinates, never yours.
The camera and the form check (version 2.0)
The form check films fifteen seconds of you running, side-on, with the camera only — the microphone is never used. The clip is measured on your phone: cadence, trunk lean, vertical movement, foot strike and arm carriage are read from your own frames by Apple's Vision framework and drawn back on one of them. That picture is kept on the device, in the app's files, and is deleted with the app.
Separately, and only if you agree on the screen shown before the first clip, the compressed clip is sent once through our Cloudflare proxy to Google's Gemini vision model, which returns short written observations about what was visible — never a diagnosis. The clip is not stored by us or kept by the model service after the request, is never used to identify you and is never used for advertising. Google processes it under Google's terms. If you decline, the form check still measures; it just has no written observations.
The weekly brief (version 2.0)
At the end of each week the app writes a brief on your phone from three printed rules. If you tap Ask the coach, that week's numbers — session titles, distances, durations, heart rates, your morning checks and any form observations — are sent once through our proxy to the same model for a better-written brief. No name, no route, no clip. The request is not stored by us. The plan is never changed by the brief until you tap Apply.
Notifications
Reminders are local notifications the app lays on the phone from your plan: the day's session in the morning, a nudge after lunch and a last call in the evening while it is not logged, one line on rest days, and the week's brief on its last evening. No server is involved and nothing is sent to us.
The morning check and your readiness number (on the device)
Sleep, legs and mood, three taps a morning, are saved with your plan on the phone. The race-readiness percentage, the predicted finish and the brief's rules are computed from your own logs on the device and shown with the rule that produced them. None of it is uploaded.
Links out to other apps
Some sessions offer a music playlist or a short video demonstrating a movement. Those links open Spotify or YouTube, which are not ours. Once you are there, their own terms and privacy policies apply.
Children
The app is rated 4+ and is not in the Kids Category. It has no user-generated content, no messaging and no advertising. It does not knowingly collect personal information from children under 13; the usage statistics above are anonymous and can be turned off in Profile → Privacy.
Your rights
Because your training never leaves your device, there is nothing for us to disclose, export or delete on request — we do not have it. The two requests that do leave the phone (a form-check clip, a week's numbers for the brief) are processed and discarded; we keep no copy and no identifier that would let us find them. It is removed by deleting the app, or through Profile → Reset everything.
For the anonymous usage statistics, your control is the switch in Profile → Privacy. Turning it off stops future collection. Because the data carries no identifier that can be tied back to a person, we cannot isolate one individual's past events to delete them — which is also why they cannot be used to learn anything about you specifically.
If you are in the EU/EEA or the UK, we rely on legitimate interests for these statistics (understanding how the app is used so it can be improved), and you can object at any time using that switch. If you are in California, we do not sell or share personal information as those terms are defined under the CCPA/CPRA.
Your training history is not backed up by us and cannot be recovered by us if you delete the app or lose the phone. Use your iPhone's own backup if you want it kept.
Changes
If a future version starts collecting anything more, this policy will be updated before that version ships, and the App Store privacy label will change to match. The date at the top tells you which version you are reading.
Contact
Samosfi Studio, Dublin — info@kalibrefin.com