Consumer Health Data Privacy Policy
How TrekReady LLC collects, uses, and shares information linked to your physical health or fitness, and how to exercise your rights.
Effective 2026-10-25 · version 2026-10-25.v1
Health-data collection and teammate sharing are separate choices. Sharing starts off. You can withdraw consent, export your information, or request deletion. TrekReady does not sell consumer health data or share it with advertisers.
This policy applies across TrekReady, including connected fitness services. Account and other data practices are explained in the general Privacy Policy.
Categories collected
- Activities, exercise type, distance, duration, pace, ascent, heart rate, and VO2 max.
- HRV, sleep, resting heart rate, readiness, body battery, stress, steps, and manual wellness entries.
- Objectives, routes, seasons, altitude plans, outcomes, and technical/fitness evidence, including confirmed capability or practice records.
- Private objective debriefs: difficulty, energy or physical response, pain/discomfort, limiting factors, helpful preparation, outside influences, notes, segments, linked activities/plans, and correction or withdrawal history.
- Training context: general area and constraints you confirm, activity-derived workloads and session patterns, and earlier home-elevation or altitude notes until changed or deleted.
- Coach prompts, responses, recommendations, and preparation estimates and confidence.
- Contextual capacity estimate revisions and their evidence references, and minimal service-only comparison records used to verify bounded capacity calculations.
Sources
Data comes from you, fitness services you authorize where available, and calculations from those records. Imports are associated with your TrekReady account and depend on the device, source records, and permissions. We do not buy health data or infer your home from workout GPS.
Members can authorize Garmin Connect to share supported activities and health summaries with TrekReady. Strava supplies activities; intervals.icu supplies activities and available wellness measurements. Google Health supplies approved read-only activity/fitness, sleep, and health metrics. We do not request Google Health location/GPS, nutrition, reproductive-health, symptom, or write access.
Reproductive-health imports and sending workouts or courses to connected services are not currently available. Existing consent does not authorize these features. New categories or uses require updated disclosures, consent, and provider permissions before activation. Reproductive-health collection would require a separate opt-in; gender or a general fitness connection is not consent.
Purposes
We use health data to import and display training, assess preparation evidence and confidence, build and adapt plans, track objective/team preparation, provide AI coaching and occasional shared Team activity comments, suggest relevant gear or guides, synchronize sources, troubleshoot, and honor privacy requests. A materially new category or purpose requires a new policy version and consent before optional processing resumes.
Private reports and plans: debriefs preserve your account of what happened for later uses you authorize. Team and Coach sharing choices do not authorize debrief collection or expose its private contents. Workout logs, class corrections, imported-activity links, routines, and your own objective/Logbook history help explain training and experience. Routines do not create completed activities. These records are not shared with teammates; Coach may receive the concise training background when you discuss training.
Optional Logbook extracts: you can publish a read-only copy of one entry’s place, route name, date and outcome, with selected notes, photographs and captions, outing measurements or a recorded GPS route. GPS starts off. Preview the selection before creating or updating a public link. Anyone with the link can view and copy it. Later private edits and new photos do not automatically publish. Turning off the link closes the page and its photo access; it cannot recall copies already saved. Photo downloads through these links omit camera metadata. Companions’ names, guide details, health signals, private debriefs and Coach conversations are not automatically included. This choice is separate from Team sharing.
Submitted starting-point forms and optional weekly responses record recent activity, comfortable outings, available days, terrain access, effort, discomfort, repeatability, restrictions, and whether your log covers the week. They are self-reports, not diagnoses or demonstrated capacity, and do not mark suggested sessions complete. Starting-point answers, weekly check-in responses, and the assessment and plan history built from them are not shared with teammates. Coach cannot create, prefill, or revise the starting-point assessment; it can explain decisions and link to the Training form.
Personal weekly review may use capacity evidence to propose repeating a supported week or holding an increase for review. It does not raise capacity estimates or confirm a week automatically; you accept or decline. Coach receives the resulting explanation, not private capacity records or debriefs; teammates receive no calibration rationale. Temporary next-week time/access previews are discarded unless confirmed. Confirmation retains the applied constraints and plan history; replacements preserve earlier decisions, and hypothetical dates do not edit your trip.
Product use: with current collection consent, trip/objective creation, foreground Training visits, usable-plan opens, and human Coach/Team contributions help measure adoption, return visits, and unavailable plans. Events contain member and relevant record/route identifiers, action type, time, and deduplication identifiers—not content, health readings, browsing URLs, or fingerprints. Exact usage counts and test-account classification are owner-only; delegated analytics staff receive aggregate creation reports without private plan, health, gear, or Coach details.
Calculation checks: minimal service-only comparisons verify that capacity calculations remain bounded without changing current plans. They contain hashes, versions, dimensions, reason codes, range/confidence differences, checks, and timestamps, never raw health/provider records, debriefs, session payloads, or private narrative. Capacity evidence and comparisons are excluded from Team, Coach, other members, and direct browser data access. Existing sharing choices do not authorize their disclosure or a new collection purpose.
Data shared and recipients
Shared categories can include activities/fitness evidence, recovery measurements and derived signals, objective/training context, and Coach prompts or inferences. Teammate sharing is off by default and separate from collection consent.
- Objective teammates: activity, fitness, and confirmed capability evidence while training sharing is active; recovery information only when recovery sharing is also active. Both require current collection and sharing consent and a shared objective.
- Anthropic: Coach prompts and relevant health, training, and objective context. With current collection and sharing consent and activity sharing enabled, you or a crewmate opening Team can trigger an occasional AI comment, even if you never open Coach. It sends your name, activity identifier, title, date, type, duration, distance, ascent, and recent visible Coach comments for context. It excludes private recovery data, Preparation scores, private chats, photos, captions, and member comments. Turning activity sharing off stops new Team processing, not requests already sent. Explicitly choosing “Read the document with Coach” sends that experience document for proposed facts you must review and confirm; manual entry is available. Anthropic states standard commercial API inputs/outputs are ordinarily retained up to 30 days, subject to its terms and exceptions.
- Supabase: stored health/account data, authentication, and private files.
- Vercel: hosting and processing feature requests containing needed account, health, training, or Coach data, plus limited operational metadata.
- Garmin, Strava, intervals.icu, and Google Health: authentication and API requests for their connections. Google's read-only permissions are described above. Their own policies govern source records and services.
- Browser push providers: notification content if you enable push. TrekReady avoids detailed health measurements in push text.
TrekReady does not sell consumer health data or share it with advertisers. Recommendation-click records contain no member identifier or health measurement. Resend receives login addresses, authentication-message content, and delivery metadata; TrekReady does not send Resend consumer health data through this integration.
Retention and deletion
Optional Team preparation score: a separate choice for each trip starts off. If you enable it, that trip’s crew can see your physical preparation score, assessment date and comparable score changes. You or a crewmate opening Team refreshes your assessment for that trip, even when your training focus is elsewhere. Your answers, health signals, capacity estimates and full assessments remain private. Stop sharing at any time from Team; sharing also stops when you leave the trip, withdraw collection consent or the trip is completed. The choice history is included in your export and encrypted backups and removed with the membership, objective or account. Viewers may keep copies of information already seen.
Private training reports, assessment/week-review corrections and withdrawals, and ordinary/accepted plans retain the earlier history and supporting evidence behind decisions. They are included in export and encrypted backups and removed with the associated objective or account. Workout corrections and withdrawals also retain earlier history and are exported and removed with the account.
Capacity estimate history includes ranges, confidence, supporting/conflicting evidence references, cutoff, and calculation versions until objective/account deletion. Service-only comparisons expire after 180 days from creation; reads/retries do not extend retention and objective/account deletion removes them sooner. No anonymized comparison aggregates remain after expiry. Export includes estimate history, references, and unexpired comparisons. There is no individual estimate-revision or comparison delete control.
Product-use and creation events expire after 180 days, are excluded from reporting without current consent, included in export, and deleted with the account. Test-account status is exported and stays until changed or account deletion.
Completed account deletion removes active database records, photos, credentials, Coach history, and the authentication identity. Work is tracked across systems and retried after provider failures. Provider backups expire on their schedules; deleted data is not restored to normal use, and deletion is reapplied after disaster recovery. Photo links already issued can remain usable until they expire.
Your rights
Subject to applicable law, you may confirm whether we collect/share your health data, access it, withdraw collection or sharing consent, request correction/deletion, and appeal a refusal. Export and stop-processing controls remain available from the consent screen without agreement. Contact privacy@trekready.ai; we may verify requests. If an appeal is denied, you may contact the Washington State Attorney General or another regulator with jurisdiction.
“Stop optional collection and sharing” withdraws future optional processing, including AI processing. Disconnecting a source stops new imports; it does not erase earlier imports or stop their other consented uses. Request deletion to remove retained data. Deleting TrekReady records does not delete originals held by Garmin, Strava, Google Health, or intervals.icu.
Correcting a debrief appends a replacement. Withdrawing one makes the targeted evidence ineffective immediately while keeping its history in your active account. There is no individual debrief delete control; objective or completed account deletion removes the full related history. Withdrawal stops future optional processing without erasing retained records.
TrekReady LLC · privacy@trekready.ai