openpacemaker

Privacy

Your data.
Your control.

Last updated: October 2026

What we collect

Depending on which sign-in method you use, we may store:

  • Email address - only if you sign up via Google. Used for sign-in, and for a receipt if you choose to make an optional contribution. Not stored if you sign in with Strava (Strava does not share email with third-party apps).
  • Google account ID - only if you sign in with Google.
  • Strava athlete ID and OAuth tokens - if you connect Strava.
  • Activity data (distance, pace, heart rate, splits, etc.) fetched via the Strava API, including the title, description and private note you write on an activity - the coach reads your private notes so it can take your own account of a session into its read of it. They are stored with the activity, shown to you (and to your human coach, if you link one - see below), and deleted with your account. GPS route polylines are not stored.
  • Coaching notes, conversation history, wellness, and training plan data from your Telegram sessions.
  • Payment metadata - Stripe customer / subscription identifiers, only if you make an optional contribution or hold a legacy subscription from before OpenPacemaker became free for everyone. Card details are never visible to us; they live with Stripe.

How we use it

Your data is used exclusively to provide you with personalised coaching analysis and responses. We do not sell your data, and we never share it for any other party's own purposes. To run the service we do rely on the sub-processors listed below. We do not post to Strava on your behalf.

To generate coaching responses, your messages and training data are sent, per request, to third-party AI model providers. We route these requests through OpenRouter and restrict them to vetted inference providers, explicitly excluding China-based providers. Those providers are configured not to retain your data after the request and not to use it to train their models. The underlying AI model may change as the technology improves - it is always operated under these same no-retention, no-training terms.

Human coaches (optional)

You can link a human coach who works alongside the AI. Nothing is shared with a coach until you tap Link in Telegram, and the card you tap lists what they will see. Once linked, your coach can see your training data (activities, including private notes on them), your training plan, your chats with the AI coach, your flags, debriefs and weekly summaries. They can message you, give the AI standing instructions, keep notes about you, review your next week's plan before it is sent, and suggest plan changes (which only apply when you accept, unless you have chosen to let them change your plan without asking). If you agree, they can write your weekly plan themselves instead of the AI.

If you ask a coach to coach you from the directory, they see your name and your message, plus a short training summary (goal, main sport, recent weekly distance) only if you tick the box to share it.

Leave at any time with /coach in Telegram: your coach stops seeing your data immediately, and the AI drops their instructions and notes about you. Coaches are independent people, not OpenPacemaker staff; they are approved by us before they can coach on the platform.

Coaches: the profile you write for the directory (name, bio, sports, and any Strava, Instagram or website link you add) is public at openpacemaker.com/coaches. Your account works like any other user's: the rights below apply to you too.

Data storage & retention

Data is stored in a PostgreSQL database hosted on Google Cloud (europe-west2). Access is restricted to the application service account.

During the beta, the OpenPacemaker team can view your training data, plan, wellness entries and the profile the AI keeps about you, to check the coaching is right, and can leave notes that guide how the AI coaches you (it will tell you the team reviewed your coaching if you ask where a change came from). If you train without a plan, the team may also send you a suggested week in Telegram; it only applies if you tap to add it. The team can also ask your AI coach to send you a message, which the coach writes itself; ask it and it will tell you. We cannot see your conversations with the AI coach; only a human coach you link can. Once you link a human coach, the team's notes stop applying.

Two different retention windows, so the “remembers you” promise is honest:

  • Chat transcripts - raw messages between you and the bot - auto-purge after 180 days as data minimisation.
  • Durable coaching memory - preferences, injuries, patterns, race results, the structured profile the coach uses to answer you - is retained for the lifetime of your account so the bot can still recall a 4-month-old niggle.
  • Activities and training plans - retained for the lifetime of your account.

You can wipe all three at any time with /delete confirm or by revoking Strava access.

Your rights

Data export (Article 20) - send /mydata to the bot and tap Export to receive a complete JSON download of everything stored for your account.

Deletion (Article 17) - you can request full deletion of your data at any time by:

  • Sending /delete confirm to the Telegram bot - permanent and immediate
  • Revoking access in Strava → Settings → My Apps (triggers automatic deletion)

Third-party services

  • Strava - activity data source and an authentication option (Strava Privacy Policy)
  • Google - an authentication option (Google Privacy Policy)
  • OpenRouter - AI gateway that routes coaching requests to third-party model providers; we restrict it to vetted, non-China inference providers configured for no data retention and no training (OpenRouter Privacy Policy)
  • AI model providers (currently DeepSeek and Anthropic, via the gateway above) - generate the coaching responses; data sent per request, not retained, not used for model training
  • Stripe - payment processing for optional contributions / legacy subscriptions (Stripe Privacy Policy)
  • Telegram - messaging interface
  • Google Cloud - hosting infrastructure

Contact

Questions? Message the bot, or email hello@openpacemaker.com.

← Back to openpacemaker.com