OWLPACEBack to OwlPace
Legal · Privacy

Privacy Policy

OwlPace uses your training data to build an athlete-controlled plan and explain what changed. This policy describes the information we handle and the choices available to you.

Effective July 31, 2026

1. Scope and who we are

This policy applies to OwlPace websites, web and mobile applications, coaching tools, and connected services. “OwlPace,” “we,” and “us” refer to the operator of owlpace.com. Questions or privacy requests can be sent to privacy@owlpace.com.

2. Information we collect

  • Account data, such as your email address, name, role, login timestamps, invitation status, and public username or leaderboard preference.
  • Athlete profile data, including timezone, age or birth year, height, weight, sex, fitness level, goals, race targets, training availability, and heart-rate zones.
  • Plans and activity data, including scheduled and completed workouts, distance, duration, routes, pace, speed, heart rate, power, cadence, elevation, calories, workout structure, edits, matches, and adaptation history.
  • Recovery and wellness data, such as sleep, recovery score, HRV, resting heart rate, recovery protocols, nutrition, hydration, meals, and optional private habit journals.
  • Content you provide, including coach messages, workout or meal text, uploaded images, support requests, and manual corrections.
  • Technical data needed to operate and secure the service, such as browser or device information, session cookies, OAuth state, request logs, error data, and provider sync status.
  • Waitlist data, including your email, optional name, requested plan, optional marketing-consent timestamp, and the page from which you joined.
  • AI usage metadata, including feature, model, token counts, latency, estimated provider cost, errors, and blocked requests. We use this to control abuse and operate fair-use limits.

3. Connected services

Connections are optional. If you connect Strava or WHOOP, you authorize OwlPace to receive the data covered by the permissions shown during that provider’s authorization flow. Structured workouts may be delivered through Intervals.icu to services such as Garmin Connect or Zwift when that delivery path is configured. Each third party handles information under its own terms and privacy policy.

Disconnecting a provider stops new access through that connection, but it does not automatically erase data that was already imported into OwlPace. You can request deletion as described below.

4. How we use information

  • Operate your account, calendar, training plan, activity history, recovery, nutrition, Journey, and leaderboard controls.
  • Match completed work to planned sessions, calculate training load and compliance, generate analysis, and preview or apply athlete-approved plan changes.
  • Personalize workout, recovery, fueling, race, and coaching guidance according to your settings.
  • Generate structured workout files and share cards when you ask us to export them.
  • Maintain security, prevent abuse, diagnose errors, provide support, and improve reliability.
  • Meet legal obligations and enforce our Terms.

5. AI-assisted features

Some coaching, plan generation, meal estimation, workout import, and activity analysis features send relevant prompts or uploaded content to an AI service provider. We limit the context to what is needed for the requested feature. AI output can be incomplete or wrong and should be reviewed before you act on it.

We store provider-reported token counts and operational metadata for metering and cost control. This ledger does not store the text of your prompt; coach messages and uploaded content may be stored separately when the product feature itself requires history or a saved record.

6. How we share information

We do not sell personal information or use athlete data for third-party targeted advertising. We may share data:

  • With infrastructure, database, hosting, analytics, AI, and support providers that process information for OwlPace.
  • With Strava, WHOOP, Intervals.icu, Garmin Connect, Zwift, or another integration when you connect it or request delivery.
  • With an authorized OwlPace administrator for account support, security, and read-only athlete preview features.
  • On public leaderboard or athlete pages only when you enable public participation; those surfaces are limited to the fields described in the app.
  • When required by law, to protect rights and safety, or as part of a business transfer subject to appropriate safeguards.

7. Retention, deletion, and your choices

We retain information while your account is active and as needed to provide the service, resolve disputes, maintain security, and comply with law. Retention can differ by data type and backups may take additional time to expire. You can disconnect integrations, disable optional recovery adaptation, leave the public leaderboard, correct activity facts, and delete supported records from the app.

Public demo profiles are isolated per visitor and scheduled for deletion after two hours. Resetting or exiting the demo deletes that temporary profile immediately. Waitlist records are retained until launch outreach is complete, you unsubscribe, or you ask us to delete them.

To request access, correction, export, or deletion of your account data, email privacy@owlpace.com. We may need to verify your identity before completing a request.

8. Security and international processing

We use technical and organizational safeguards designed to protect account and training data, including scoped authorization, encrypted network transport, access controls, and secret management. No system is perfectly secure. Our providers may process information in countries other than your own, subject to the safeguards available for that processing.

9. Health and sensitive data

Training, recovery, nutrition, route, and habit information can be sensitive. OwlPace is a fitness planning tool, not a medical device or healthcare provider. Only connect accounts and enter information you want OwlPace to process.

10. Children

OwlPace is not directed to children under 16, and we do not knowingly collect their personal information.

11. Changes to this policy

We may update this policy as the product or applicable requirements change. We will post the revised version here, update the effective date, and provide additional notice when a change is material.