← Back to Tayro

Tayro Privacy Policy

Effective: October 1, 2026 · Questions: support@tayro.run

Tayro is an AI training coach for runners. This policy says what we collect, why, who can see what, and the rules we hold ourselves to, in plain language, because that's how we build.

What we collect

How we use it

Who sees what: the visibility contract

This is the core of Tayro, and the server enforces these rules on every read:

Kids and teens

The AI

Your training questions and relevant training context (like your mileage, paces, and goals) are sent to our AI providers to generate coaching responses. Today those are Google (Gemini) and Groq. To find relevant coaching knowledge for an answer, your message is also sent to OpenAI to be turned into a numerical representation, which we then match against our coaching library. Your PAR-Q health-screening answers are never included in coach-chat prompts. Their safety function is enforced in the plan engine itself, in code. If you connected Apple Health, a short summary of your recent recovery signals travels with your own coaching prompts (how you have been sleeping, whether your resting heart rate is up) so the coach can ease a hard session when your body says to. It is a summary of your own data, in your own conversation; it never reaches a human coach. Body metrics (weight and height, if you provided them) are used only by your fueling and recovery coach, to set your fueling and hydration targets, and never by any other AI coach. Allergy and dietary notes are used by your fueling and recovery coach and by your race-day coach, for example in race-day fueling advice, and never by any other AI coach. Sleep hours you share are used by your fueling and recovery coach and by your training coaches, to plan your training load, and never by any other AI coach. The rest of your profile, such as your goals, paces, races, shoes and injuries, is shared across the coaching team. The coaches also remember other facts from your chats, and we sort each one by the topic it is saved under: training topics, such as a workout, a race, your gear or an injury, are shared across the coaching team; sleep goes to your fueling and recovery coach and your training coaches; any other topic goes only to your fueling and recovery coach.

Each provider processes this under its paid API terms, and those terms are why we chose them: for Google (Gemini) and Groq (the two that see your coaching conversation), your content is not used to train their models, and is retained only for a short abuse-monitoring window before deletion, not stored as your data on their side. OpenAI sees only the message being turned into a numerical representation, under the same class of paid API terms, and that content is not used to train its models either.

Where your data lives

Hosting and database: Supabase and Vercel (US regions). Sign-in: Google or Apple. Payments: Apple (App Store) and Stripe. Safety report email: Resend.

A few features talk to other services. Weather and city lookups go through our own server, never straight from your phone: when weather is shown it comes from Apple Weather, and looking up a city name (or turning a location into a city name) goes to Apple Maps. In both cases Apple receives the coordinates or the place name being asked about, never who is asking. Course and race maps are different: they are drawn in your device's browser by Apple Maps (MapKit JS), so your device requests the map imagery from Apple directly. Apple sees the map area you are looking at and your device's IP address, never your name, your account, or anyone's position.

Your training location is kept to the nearest kilometre. When you set your training city, we round the coordinates to roughly 1.1 km before storing them or sending them anywhere. Weather and the vitamin D estimate are the only things that use them and neither needs to know your street. The GPS route of a run is different, and precise by necessity (a map of your run is the point of recording it), and it is covered by the visibility rules above.

If you turn notifications on: in the iOS app they are delivered by Apple's push service (APNs), which means Apple holds a device token for your phone and passes along the notification's title and text. On the web they go through your browser's push service instead (Google, Apple, or Mozilla, depending on the browser). Either way the notification carries only what you can see on the banner itself: a short title, a line of text, and a link back into the app.

Your controls

Changes

If this policy changes materially, we will update this page and its effective date before the change takes effect.

Tayro · California, USA