Privacy Policy
How TrekReady LLC handles your account, training, and planning information.
Effective 2026-10-25 · version 2026-10-25.v1
Health sharing is off by default. You can export your data, stop optional processing, and request deletion. We do not sell health data or share it with advertisers.
Fitness and recovery information is also covered by our separate Consumer Health Data Privacy Policy. The Terms of Use govern use of TrekReady; accepting them is separate from health-data consent.
Information we collect
- Account and preferences: name, login email, display and notification settings, consent records, and optional profile details. Invitation requests can include your email, prospective objective, and general training region. Magic-link login means we do not store your password.
- Training and recovery: activities, distance, elevation, duration, heart rate, VO2 max, HRV, sleep, resting heart rate, steps, body battery, readiness and stress measurements, and wellness entries.
- Planning and experience: objectives, routes, seasons, gear, trip logs and photos, outcomes, training area and constraints, confirmed course or practice evidence, activity-derived patterns, and earlier home-elevation or altitude notes until changed or deleted.
- Private objective debriefs: reported outcomes and dates, difficulty, energy, pain or discomfort, limiting factors, preparation, outside influences, notes, segments, linked activities or plans, and correction or withdrawal history.
- Coach and connections: conversations, records of Coach actions, recommendations and inferences, connected-service credentials, browser push credentials, sync status, and security/request metadata. Public invitation throttling uses a keyed one-way request-address hash. Recommendation clicks are counted without a member identifier.
How we use it
Information comes from you, services you authorize, and calculations from those records. We use it for login, imports, training displays and preparation estimates, plans, objective teams, Coach, relevant gear or guide suggestions, opted-in notifications, security, troubleshooting, invitation requests, privacy rights, and legal obligations. TrekReady does not infer your home from workout GPS.
Private objective debriefs preserve your account of what happened for later uses you authorize. Existing Team or Coach sharing choices do not authorize this collection or expose the private debrief to teammates or Coach.
Private workout logs, class corrections, routines, starting-point forms, weekly responses, restrictions, and training reviews support personal guidance. A reported routine or response does not mark a workout complete. Coach can explain resulting guidance; teammates receive no calibration rationale. The health-data policy explains training reviews, temporary previews, and retained plan history.
Permit planning: itinerary choices, responsibility confirmations, acquisition status, and document-packing marks stay private. They are your confirmations, not agency verification. We do not collect permit scans, photo IDs, agency credentials, or confirmation numbers. Reminders require explicit opt-in and follow notification preferences; changing responsibility or itinerary invalidates earlier reminder choices. Downloaded calendars are separate copies that do not update automatically.
Product use: with current collection consent, we record trip/objective creation, foreground Training visits, usable-plan opens, and human Coach/Team contributions to understand adoption, return visits, and unavailable plans. Records contain member and relevant record/route identifiers, action type, time, and deduplication identifiers—not content, health readings, browsing URLs, or device fingerprints. Exact usage counts and test-account classification are owner-only; delegated analytics staff receive aggregate creation reports. Neither view reveals private plans, health measurements, gear, or Coach conversations. Invitation and AI-cost records support operations and cost accounting; total spend includes owner and test use.
Connected services
This policy covers Garmin, Strava, Google Health, and intervals.icu. Imported data is associated with your TrekReady account and depends on the available connection, device, source records, and permissions. Connecting does not enable teammate health sharing.
- Garmin: recorded activities and available health/recovery measurements. Members can authorize Garmin Connect to share supported activities and health summaries with TrekReady.
- Strava: activity name, type, date, duration, distance, and ascent.
- Google Health: read-only activity/fitness, sleep, and health metrics you approve. We do not request location/GPS, nutrition, reproductive-health, symptom, or write access.
- intervals.icu: activities and available wellness measurements, including HRV, sleep, resting heart rate, VO2 max, and steps.
Reproductive-health imports and sending workouts or courses to connected services are not currently available. Listing a provider does not authorize these features. Materially 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.
Use and transfer of information from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.
Who can see it
- Private: debriefs, starting-point answers, weekly check-in responses, the assessment and plan history built from them, capacity estimate history, Coach history, training-location context, credentials, notifications, and privacy requests are not teammate-visible. Debriefs and underlying capacity evidence are also excluded from Coach. Existing sharing choices do not authorize a capacity projection.
- Health sharing: off by default and separate from collection consent. You control activity/fitness/capability sharing and recovery sharing independently. Shared health information is limited to teammates on the same objective.
- Trip information: rosters, reactions, gear coverage, and trip logs you mark shared are objective-scoped. A private trip stays private.
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.
Optional member profile: a separate sharing choice starts off. Enabling it shows trip teammates and anyone with your profile link your name, optional photo and broad region, activities, trip style, pace, and up to three accepted course/practice titles and dates. Saving edits updates the shared view. Email, health signals, availability, original documents, private Logbook entries, and Coach conversations are excluded. Turning sharing off revokes the link; enabling it again creates a new one. Viewers may keep their own copies.
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.
Authorized operators and infrastructure providers can access information as needed to operate, secure, support, or delete the service, even when ordinary app screens do not expose it.
Coach and service providers
Anthropic: when you use Coach, we send your prompt and relevant account, objective, training, and recovery context. Presented drafts require confirmation; an explicit command to a supported write tool can update TrekReady data.
AI can also run without a separate Coach request. With current collection and sharing consent and activity sharing enabled, opening Team may send your name, activity identifier, title, date, type, duration, distance, and ascent to Anthropic for an occasional comment. You or a crewmate can trigger this, even if you never open Coach. Recent visible Coach comments provide context to avoid repetition. This does not send private recovery data, Preparation scores, private chats, photos, captions, or member comments. Turning off activity sharing stops new Team Coach processing of your activities, but cannot undo processing already sent.
Choosing “Read the document with Coach” sends an optional experience PDF, image, or text document to Anthropic to propose facts for review. You must confirm any extracted claim; manual entry is available. Records can include your name, provider, dates, explicit expiry, and confirmed skills used in route checklists. TrekReady does not verify issuers or certify your skills. Anthropic states standard commercial API inputs and outputs are ordinarily retained for up to 30 days, subject to its terms, safety enforcement, legal obligations, and any different agreement.
- Supabase and Vercel: Supabase provides authentication, database, and private file storage. Vercel hosts the app and processes feature requests, including needed account, health, training, or Coach data and operational metadata.
- Email: Resend receives your login email address, authentication content including the one-time sign-in link, and delivery metadata. For product and trip invitations, it receives recipient email/name, inviter name, trip name when applicable, message content, and delivery metadata. Replies go to tom@trekready.ai. TrekReady does not send training or health data to Resend through that integration.
- Other services: Cloudflare Turnstile receives ordinary request, browser, and challenge-interaction information on login/invitation requests. Do not put health information in invitation requests. Browser push providers deliver enabled notifications. Open-Meteo receives a weather-location request when a weather card loads. Connected fitness providers receive authentication/API requests; their own policies govern their services and original records. Providers may also process limited information for security, abuse prevention, legal obligations, and service operation.
Recommendations and advertising
We do not sell health data or share it with advertising networks. Gear and guide recommendations are reviewed editorial inventory. A recommendation click records item, surface, time, and relationship type, without member identifier, health value, or objective date. The destination receives ordinary request information such as IP address and browser. Future paid or affiliate relationships will be disclosed without changing eligibility or editorial order. See how we review recommendations.
Cookies and security
Session cookies keep you signed in; local storage remembers interface preferences and installation state. Offline caching covers only the public app shell and static assets, never member pages, API responses, or private data. Connected-service credentials are encrypted before storage. Session checks, restricted database access, rate limits, browser security headers, and short-lived photo links help protect data. Turnstile may use browser storage or similar signals. Encrypted operational backups include database records and private photos. No system can promise absolute security.
How long we keep it
- Account and planning: retained while the account is active and needed for these purposes. Private training reports, corrections, and plan decisions retain history, are exportable, and are removed with the relevant objective or account. Permit plans and minimal reminder receipts remain until cleared, you leave the outing, or the objective/account is deleted. Invitation-interest records remain during evaluation and reasonable security/duplicate handling, and may be deleted on request.
- Profiles: current details, a resized photo with embedded metadata removed, and minimal sharing-choice history remain until account deletion and are included in export and encrypted backups. The original photo is not retained.
- Experience documents: confirmed records and originals remain until removed or account deletion, including after skill claims are withdrawn. Never-confirmed drafts/files are removed after seven days by daily cleanup. You can remove an original while retaining confirmed experience, or delete the record and claims. Removal clears dependent copied evidence where needed; failed file removals stay pending for retry.
- Usage: product-use and creation events expire after 180 days, are exported and deleted with the account, and are excluded from reporting without current consent. Test-account status is exported and stays until changed or account deletion.
- Operations staff: invitation email, role, permissions, acceptance, assignments, and findings support staff access/review. Access and review audit events expire after 365 days; completed or unassigned reviews expire after 365 days without updates. Pending invites expire after seven days and are removed 30 days later; revoked grants are removed after 30 days. Active grants and unfinished reviews remain while needed. Auth account deletion removes grants and unlinks identity from retained reviews/audits.
Capacity estimates retain their history, ranges, confidence, supporting/conflicting evidence references, cutoff, and calculation versions until objective/account deletion. Minimal service-only comparisons check calculation limits without changing current plans. They contain hashes, versions, dimensions, reason codes, range/confidence differences, checks, and timestamps—not 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. 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.
Completed account deletion removes active database records, photos, credentials, conversations, and the authentication identity. Deletion is tracked across systems and retried after provider failures. Limited operational/request records may remain for security, legal requirements, or documenting the request. Provider backups expire on provider schedules; deleted data is not restored to normal use, and deletion is reapplied after disaster recovery. Previously issued photo links may work until their roughly one-hour expiry.
Your controls and rights
Use Settings or the consent screen to export, stop optional processing, or request access, correction, deletion, withdrawal, or appeal. Export and privacy requests remain available without accepting new Terms or health consent. We may verify requests. You can also email privacy@trekready.ai.
- Export: a JSON download includes your records, correction history, connection metadata, short-lived photo links, and authenticated download links for retained documents. Reusable secrets and push credentials are excluded.
- Stop or disconnect: turn health sharing off independently, or use “Stop optional collection and sharing” / “Withdraw collection and stop optional processing” to stop future optional processing, including AI processing and new experience processing. You can disconnect sources, push delivery, and your BYO Coach key. Disconnection stops new imports; it does not erase existing records or stop their other consented uses. Withdrawal likewise does not erase retained history. Request deletion separately. TrekReady deletion does not delete originals at Garmin, Strava, Google Health, or intervals.icu.
- Correct or delete: delete individual photos, trips, and Coach conversations in the app. Correct a debrief by appending a replacement, or withdraw it so it stops contributing evidence immediately. History remains; there is no individual debrief delete control. Objective or completed account deletion removes the full related history.
Operations staff can export their operations data without a current role or accepting new Terms, and request correction/deletion by email. Staff access requires neither health consent nor climbing-team membership. Do not put private member information in review findings.
Changes and contact
A material change receives a new policy version and requires agreement again before optional processing resumes. Contact TrekReady LLC at privacy@trekready.ai.