Privacy Policy
This policy explains what Long Run Hybrid Coach processes, why it is needed, where it goes, and how to revoke access or delete product-held data.
1. Data processed and purpose
| Data | Purpose |
|---|---|
| Completed activities | Reconcile planned training against what you actually completed and maintain the current direction. |
| Available wellness summaries | Inform coaching judgment when the evidence is present and current. Missing or stale fields remain unknown. |
| Planned calendar workouts | Read the current calendar, prevent duplicate ownership conflicts, and publish only workouts you approved. |
| Goals, constraints, and preferences | Make the plan usable for your schedule and stated direction. |
| Training and body records you report | Keep what no device records: strength sets you report, sessions you describe, body weight or body fat you state, and training-history files you upload. Each is stored as athlete-reported evidence, never silently upgraded into a provider actual. Supported records can be corrected or retracted through the coach. |
| How you say you feel, and recovery numbers you state | Inform coaching judgment in your own words — including heart-rate, HRV, or sleep values you read off your device. Subjective statements are stored as statements rather than translated into a score. Request-scoped recovery readings are used for that coaching turn and are not kept as a raw provider upload. |
| OAuth authorization | Access your Intervals.icu account within the scopes you grant. Your Intervals.icu password is never collected. |
2. Storage and authorization
When a hosted gateway is used, it stores owner-scoped product state including PlanState versions, decisions and receipts, athlete-reported evidence, and delivery bookkeeping needed to maintain one current plan. Provider identity and a keyed token fingerprint are stored separately so requests can resolve to the same owner.
Request logs record the operation and its outcome, and identify the account by the same opaque reference your data export shows you; they last only as long as the hosting platform keeps them. The raw Intervals.icu OAuth access token is used for authorized requests but is not written to the owner state store or application logs. The OAuth client secret stays server-side and is not exposed to the active AI interface.
3. AI processing
Long Run Hybrid Coach may be used through ChatGPT, Claude, or another supported AI interface. The active interface processes the training context needed for the coaching task under that AI provider's applicable terms and privacy policy. Which interface is used depends on the entry you choose. This service receives only the coach tool calls that interface sends it, never a copy of your conversation.
The gateway does not use training data to train a proprietary model. The current repository does not call a separate large-language-model API or require you to provide an AI API key. If you do not want training or wellness information processed by the AI provider behind the interface you chose, do not use that interface.
4. Connected platform
Long Run Hybrid Coach reads from and writes to Intervals.icu under the authorization scopes you grant. Intervals.icu handles that data under its own terms and privacy policy. The product does not sell training data, use it for advertising, or write completed activities or wellness records.
5. Retention, correction, and deletion
Owner-scoped training state is retained until you delete it, so that current decisions can be reconciled and audited. There is no expiry and no inactivity sweep.
In the conversation: ask the coach for a copy of your data through the connection you already use. Deleting all of it is not done there and no tool performs it — ask the coach and it answers with the support page below.
By email: write to tingcctwai@gmail.com. This is the only route for deleting your data, and an export can be asked for the same way. It does not depend on your AI client letting a request through: some AI clients refuse a tool call at their own approval step before it reaches this service, and the conversation can then neither finish your request nor explain why — which is why the operation that cannot be undone is not offered there. You give your Intervals.icu athlete id and, where you can reach the page, a screenshot of your Intervals.icu Settings page showing it; the export or the deletion is then run for you. A copy goes only to the address that made the request, and a deletion runs against the exact scope you confirm. You will never be asked for a password, an API key, or an authorization token. The steps are on the support page.
Athlete-reported records that use a latest-wins key can be corrected by reporting the replacement value; supported athlete-reported records can also be retracted when removal is the right outcome. This does not rewrite the append-only PlanState/decision history: plan revisions remain auditable rather than being edited in place.
Deletion removes plan state, its version history, athlete-reported evidence, snapshots stored beside it, and the identity mappings that resolve your account. It does not remove workouts already written to your Intervals.icu calendar, and it does not withdraw your Intervals.icu authorization. This product creates no routine backups; any deployment that enables host-level volume snapshots must document its own retention behavior.
No backup-retention period is promised, because none has been measured — matching what the support page already states.
To stop future access immediately, revoke Long Run Hybrid Coach in Intervals.icu. Revocation prevents future authorized reads and writes, but does not by itself delete product-held state or identity mappings; ask for deletion separately if that is what you want, in either order — the email route needs no working connection. Product-created workouts already on your Intervals.icu calendar are managed there.
6. Security
Authorization uses OAuth. Raw access tokens are not persisted or logged; account lookup uses a keyed HMAC-SHA256 fingerprint. Owner state is separated by owner identifier, credentials are not committed to source control, and private training records do not belong in this public website repository.
7. Your choices and rights
You may access, export, correct or retract supported athlete-reported records in the conversation, and may ask by email to delete the hosted data associated with your owner account (section 5). You may also revoke Intervals.icu access at any time through Intervals.icu. PlanState history itself is not edited in place; deletion removes it as part of deleting the owner data.
8. Children
Long Run Hybrid Coach is not intended for anyone under 16 and is not directed at children.
9. Not medical advice
Long Run Hybrid Coach is a training-planning tool. It does not diagnose, treat, or monitor medical conditions and is not a substitute for qualified medical care or a human coach.
10. Contact
Corrections and retractions need no contact — report the right value through your authenticated connection. An export works the same way, and can also be requested by email; deleting your data is always an emailed request (section 5). For anything else, the support page is the way in: write to tingcctwai@gmail.com, which is private and is the right channel for anything involving your health data or your account. The public repository issue tracker stays open for bugs and feature requests; do not include health data, credentials, OAuth tokens, or other private information in a public issue. The opaque account reference printed in your data export is safe to quote publicly and is enough for an operator to find your account.
11. Changes
If this policy changes materially, the updated date above will change and the new version will be published at this URL.
Long Run Hybrid Coach is an independent project and is not affiliated with, endorsed by, or sponsored by Garmin, Intervals.icu, Apple, or any other device or platform provider. Garmin and Intervals.icu are trademarks of their respective owners.