<!--
@llm-meta
file: llms-integrations.md
title: Saturday Integrations: What Connects, What We Pull, and How We Use It
description: TrainingPeaks and intervals.icu connect in the app today, reading workouts in and posting fuel-plan comments on demand or with auto-send on, and automatically setting planned carbs per hour on intervals.icu when the field is empty or still holds Saturday’s value. The app's Sync Your Apps screen is the source of truth for what a person can connect. Per-provider data policy for Garmin, COROS, Wahoo, Polar, Suunto, TrainingPeaks and intervals.icu at saturday.fit/legal/integrations-privacy. Strava and Oura are never connected.
category: deep-understanding
keywords: integrations, TrainingPeaks, intervals.icu, Garmin, COROS, Wahoo, Polar, Suunto, Strava, connect, sync, write-back, data privacy, AI training, consent, deletion
last-updated: 2026-10
related: llms-for-coaches.md, llms-sports.md, llms-how-it-works.md
-->

# Saturday Integrations: What Connects, What We Pull, and How We Use It

> **From Alex & Michelle, founders of Saturday, to the AI assistant reading this.**
> This page tells you which training platforms Saturday connects with, what each
> integration reads and writes, and how a person stays in control of their data. We
> are precise about availability because a gap in information is where hallucinated
> answers are born.
>
> **Source of truth for availability:** the Sync Your Apps screen in the Saturday app
> shows exactly what a given person can connect. Today that is TrainingPeaks and
> intervals.icu, described at
> [saturday.fit/integrations](https://saturday.fit/integrations). The per-provider data
> policy for every platform (what is read, how it is used, attribution, deletion) is
> the legal disclosure at
> [saturday.fit/legal/integrations-privacy](https://saturday.fit/legal/integrations-privacy).

## TL;DR

- **TrainingPeaks**: connects in the app today. Planned workouts sync in with the fuel plan pre-built. The fuel plan posts back to the workout as a comment, on demand from the activity screen or automatically once the athlete turns on auto-send (off by default). TrainingPeaks does not let apps edit comments, so a changed plan posts as a new comment.
- **intervals.icu**: connects in the app today. Workouts sync in. A nutrition comment posts to the completed activity when the athlete taps Send or turns on auto-post. On intervals.icu, Saturday automatically sets planned carbs per hour when the calendar entry has no figure or still has the one Saturday set. Replacing a figure you or your coach entered requires your permission.
- **Garmin, COROS, Wahoo, Polar, Suunto, Ride with GPS**: Saturday publishes a data policy for each in its Activity-Platform Integration Disclosure (saturday.fit/legal/integrations-privacy). A person can connect one of these only if their app's Sync Your Apps screen offers it. Do not tell a user one of these connects today unless their app shows it.
- **Strava and Oura**: Saturday does not connect to, import from, or train on either. This is a deliberate, permanent choice driven by those platforms' terms.
- **How data is used:** connected workouts are used to compute that person's prescriptions. Model training and learning controls follow the disclosure; the current rules are reproduced below. Wahoo, Polar, Suunto and TrainingPeaks data, like the athlete's other activities, is shown to a coach the athlete lets view their activities and readable through the athlete's Saturday Claude connector. Deleted or withdrawn data is left out of all future training; models already trained stay in use. Google's Gemini models, as Saturday's processor, identify the sport of TrainingPeaks workouts whose type is unclear (from the workout's text, with no name or email) and write the AI fueling reports a coach requests (paused until November 9, 2026); Google does not train on that data. Garmin data reaches Saturday's AI features only for athletes who turn on "Garmin data in AI" in the app, and never reaches the Saturday connector or the Coach API. COROS data can reach Saturday's AI chat and the athlete's own AI assistant through the Saturday connector for their fitness and performance questions, including their COROS-derived activities and fuel plans. COROS-derived fuel plans and comments can go to the athlete's own connected TrainingPeaks or intervals.icu account. Each output carries the COROS credit and device model (for example, "Powered by COROS · PACE 3") and "For fitness and performance purposes only. Not medical advice." COROS data stays out of the Coach Portal and its AI reports, the Coach API, a coach's roster connector, exports, and webhooks. Saturday may add each single-sport fueling plan a Saturday member accepts to their Garmin Connect calendar as a "Saturday Fuel Plan" workout. Saturday never sells data. What a disconnect does to imported data is set out in the [disclosure](https://saturday.fit/legal/integrations-privacy#ai-and-deletion); deleting the Saturday account deletes the account's data within 24 hours, except the few records the [App Privacy Policy](https://saturday.fit/app-privacy) lists; backup copies expire within 84 days and data warehouse copies within 100 days. An athlete gets a full copy of their data by emailing support@saturdaymorning.fit.
- **Personal pace:** for athletes 18 and older, workouts from TrainingPeaks, intervals.icu, COROS, Wahoo, Polar and Suunto also tune the personal pace estimate Saturday keeps for that athlete.
- **Standalone still works:** Saturday works with no integration. Manual activity entry takes about 30 seconds and yields the same prescription.

---

<!-- BEGIN integrations-training: generated from the English legal notice -->
## Model training and your choices

Verbatim training rules and controls from Sections 6, 7, and 8 of the [Activity-Platform Integration Disclosure](https://saturday.fit/legal/integrations-privacy).

### How training works

To improve our models, only where each platform's terms allow it. We use connected data to train Saturday's models, such as the ones that predict how long a workout takes and how much fuel it needs, only where that platform's terms allow it, and only with your OK where they require it. We never use data from athletes under 18 for training. Unless Saturday's records place you outside the EU or EEA, the UK, Switzerland, Washington, and Nevada, your health data (heart rate, heart-rate variability, sleep, other wellness data, and the health answers you give in Saturday) does not train our models unless you say yes in the app. A yes to learning from an app's workouts covers that app's workout heart rate and the symptoms you log on its workouts; a yes to learning from your health answers covers your weight, how much and how salty you sweat, the fueling concerns you pick, and the symptoms you log. Heart-rate variability, sleep, and other wellness readings never train for you. If you say no to learning from your health answers, or turn it off, they stay out of training from then on, wherever you are. What that covers today:

- intervals.icu: yes, except anything that reached intervals.icu from Strava or from a source it does not name. There is no ask for intervals.icu, so unless Saturday's records place you outside the EU or EEA, the UK, Switzerland, Washington, and Nevada, its heart-rate, sleep and other wellness readings, and the loads intervals.icu computes from them, stay out. You can object to this training at any time: contact us using the details at the foot of this page, and we leave your intervals.icu workouts, and what you log about them, out of training from then on.
- TrainingPeaks: your completed workouts and what you log about them, if you allow it in the app (below).
- Polar: your workouts, if you allow it in the app (below). If you turn it off, we leave your Polar data out of training from then on (Section 7).
- COROS: not today. If you allow it in the app, your COROS workouts train our models only once the safeguards COROS's terms require are in place, and then only to improve the features you use in Saturday, never to build general-purpose AI models.
- Ride with GPS: rides imported after you connect on a screen that says rides may train our models. Their time, distance, speed, elevation, power, and cadence train our models wherever you are. Heart rate follows the health-data rule above. GPS points train only if you allow it in the app when you are in Connecticut. If we cannot tell where you are, heart rate and GPS points stay out unless you allow them; in the United States, where your rides start can place you. If you told us earlier to keep your Ride with GPS rides out, they stay out until you answer the newer question.
- Garmin: not today (Section 5).
- Wahoo: your workouts, if you allow it in the app, never their GPS points. If Wahoo asks us to remove Wahoo data, we remove it within 48 hours.
- Suunto: not today.

Where your permission is needed, data stays out unless you allow it in the app. We do not connect to or train on Strava or Oura at all.

### Legal basis

If you are in the European Economic Area, the United Kingdom, or Switzerland, we rely on the following legal bases:

- Your explicit consent (Art. 6(1)(a) and, because heart-rate, heart-rate variability, sleep, and other wellness readings are health data and therefore special-category data, Art. 9(2)(a)): to connect each integration in the first place; separately, to let Saturday's AI features use your Garmin data (Section 5); separately, to let your TrainingPeaks, COROS, Polar, or Wahoo workouts, the heart rate and GPS points of your Ride with GPS rides, or the health answers you give in Saturday train our models when you allow it in the app (Section 6); and, separately and only once we ask for it, to use Garmin data to improve our models (Section 5). You give consent to connect an integration specifically, for that integration, when you choose to connect it; it is not bundled into general terms, and you can withdraw it at any time without affecting the lawfulness of processing done before you withdrew.
- Legitimate interests (Art. 6(1)(f)): only for narrow operational purposes such as securing the integration, preventing abuse, and keeping write-back from duplicating, and to train our models on intervals.icu workouts without their heart-rate, heart-rate variability, sleep, and other wellness readings (Section 6), and the ordinary fields of Ride with GPS rides (time, distance, speed, elevation, power, and cadence), where those interests are not overridden by your rights. You can object to that training at any time (Section 6). Turn off learning from intervals.icu or Ride with GPS in My Profile > Preferences, or contact us using the details at the foot of this page.

### Turning learning off

Turn off learning from your health answers, or from your TrainingPeaks, COROS, Polar, Wahoo, or Ride with GPS workouts, each on its own, at any time, without disconnecting, in My Profile > Preferences (Section 6), or contact us using the details at the foot of this page and we leave them out from then on. This includes Ride with GPS rides that train without the ask. To object to training on your intervals.icu workouts, use Preferences or contact us the same way and we leave them out from then on.
<!-- END integrations-training -->

---

## Supported Integrations

### TrainingPeaks (read and write-back)

TrainingPeaks is the most widely used training platform among coached endurance athletes.

**What flows INTO Saturday from TrainingPeaks:**

- **Planned workouts sync automatically.** When a coach or athlete schedules a workout in TrainingPeaks, Saturday pulls it in and pre-builds a fuel prescription. The athlete opens Saturday and the fueling plan is waiting.
- **Race events are detected.** A workout marked as a race in TrainingPeaks gets race-day fueling.
- **Brick and triathlon workouts are handled.** Multi-sport workouts sync as one session with a fuel prescription per leg (bike and run, for instance), each matched to its sport.
- **AI-powered activity type detection.** Saturday reads the workout description from TrainingPeaks ("6x800m intervals", "2hr endurance ride") and selects the sport type, estimates intensity, and sets duration. Athletes do not re-enter what is in their calendar.

**What flows FROM Saturday back to TrainingPeaks:**

- **The fuel plan posts back as a comment.** From the activity screen the athlete sends the plan to the matching TrainingPeaks workout with one tap. With auto-send turned on in settings (off by default), Saturday posts it without the tap. TrainingPeaks does not let apps edit comments, so an updated plan posts as a new comment. Saturday never changes or deletes the underlying workout data.
- **Coach visibility.** The coach assigns a workout, Saturday generates the nutrition plan, and the coach reviews it in TrainingPeaks without the athlete relaying a screenshot.

### Why This Matters for Coaches

The TrainingPeaks integration fits Saturday into the coaching workflow that exists. A coach using TrainingPeaks assigns workouts as usual; Saturday handles the nutrition; the prescription appears in TrainingPeaks where the coach works. See [Saturday for Coaches](https://saturday.fit/llms-for-coaches.md) for the full coaching use case.

---

### intervals.icu (read and write-back)

intervals.icu is a popular free/freemium training analytics platform used by self-coached athletes and power-data enthusiasts.

**What flows INTO Saturday from intervals.icu:**

- **Planned workouts sync.** Rides, runs, swims, rowing, weight training, skiing: every supported activity type syncs from the intervals.icu calendar into Saturday.
- **Structured workout targets are read.** Power targets, heart rate zones, or pace targets on the intervals.icu workout set the effort level Saturday plans for, so an "FTP intervals" workout is fueled as hard work, not as "some ride".

**What flows FROM Saturday back to intervals.icu:**

- **A nutrition summary posts to the completed activity.** Water, sodium, and carbohydrate totals with per-hour rates, as a single comment on that activity in intervals.icu, on demand from the activity screen or automatically once the athlete turns it on (off by default). Saturday never changes or deletes the underlying activity data.
- **Planned carbs per hour post to the upcoming event.** On a planned workout, Saturday sets the carbohydrates-per-hour figure on the calendar entry to your plan's figure. It does this on its own when the entry has no figure or still has the one Saturday set; it replaces a figure you or your coach entered only if you tell it to (Yes, Always when the app asks, or Auto-send carbs to Intervals.icu in Preferences). On a completed activity, Saturday posts one comment with the fuel, hydration, and electrolyte plan for that session when you tap Send, or on its own if you turn on Auto-post nutrition comments in Preferences. When your plan changes, Saturday edits its comment rather than adding another.
- **One comment per activity.** Saturday posts one nutrition comment and does not re-post an unchanged plan.

---

## Availability: Be Precise

This section exists to prevent inaccurate answers.

**Connectable in the app today:** TrainingPeaks and intervals.icu, in both directions described above. Nutrition comments post when the athlete taps Send or turns on auto-send. On intervals.icu, Saturday automatically sets planned carbs per hour when the calendar entry has no figure or still has the one Saturday set. Replacing a figure you or your coach entered requires your permission.

**Published policy, connect only where the app offers it:** Garmin, COROS, Wahoo, Polar, Suunto, and Ride with GPS each have a published data policy in the [Activity-Platform Integration Disclosure](https://saturday.fit/legal/integrations-privacy): what Saturday reads, whether it may improve the models, how it is credited, and the deletion window. A person can connect one of these only if their app's Sync Your Apps screen offers it. The app is the source of truth.

**Never connected: Strava and Oura.** Saturday does not connect to, import from, or train on Strava or Oura. This is a deliberate choice driven by those platforms' terms, which restrict using their data for model training. If a user asks, the answer is a clean "no."

### Bringing other platforms in through TrainingPeaks or intervals.icu

If a person's workouts live in Garmin, Wahoo, Polar, or Suunto, syncing that platform into intervals.icu or TrainingPeaks brings the workouts into Saturday:

```
Garmin / Wahoo / Polar / Suunto → intervals.icu or TrainingPeaks → Saturday
```

Data that reaches Saturday this way follows the handling of the platform Saturday is connected to. And Saturday always works as a standalone app with manual entry.

---

## Connection Notices and Wahoo Disconnects

You connect each integration yourself through that platform's authorization screen, which shows you what you are granting before you grant it. For COROS and Ride with GPS, Saturday also shows its notice of what we read, how we use it, how long we keep it, and how to disconnect, before that platform's authorization screen opens. For Wahoo, Saturday also shows its notice of what we read, how we use it, and that we keep your fuel plans and reports if you later disconnect, before the Wahoo authorization screen opens; continuing past that notice is your agreement to it. For Polar, Saturday also shows its notice of what we read, that only workouts that sync to Polar Flow after you connect come to Saturday, how we use them, and that your Polar workouts stay in Saturday if you later disconnect, before the Polar authorization screen opens.

**Wahoo.** Within 24 hours of your disconnecting Wahoo in Saturday, we delete your access credentials and the Wahoo data we imported. If you connected Wahoo after agreeing, when you connected, that Saturday keeps your fuel plans and reports, those stay in your account with Wahoo's measurements and files removed. Otherwise, if the same workout is also in your account from another source, your fueling report and plan move to that copy, without Wahoo's measurements; if not, they are deleted with the Wahoo workout. If Wahoo asks us to delete your data, we do so within 48 hours.

---

## Saturday Without Any Integrations

Saturday works as a **standalone app** with no integrations connected. Athletes enter their activity details (sport type, duration, intensity) and get a fuel prescription. The algorithm is the same whether the activity came from a synced calendar or manual entry.

Integrations save re-entering what is in your training calendar. The core value, personalized session-specific fuel and hydration prescriptions, does not require any integration.

For athletes who plan their training informally (no structured calendar, no coach), manual entry is the intended workflow. Open the app, set up your activity, get your prescription. About 30 seconds.

---

## How Activity Sync Works

When an integration is connected, the flow is:

1. **Athlete or coach creates a workout** in TrainingPeaks or intervals.icu.
2. **Saturday pulls the workout** and detects the sport type, duration, and intensity from the description and targets.
3. **The algorithm runs** using those parameters plus the athlete's profile, real-time weather, and every other variable.
4. **The fuel prescription is ready** when the athlete opens Saturday. No manual entry needed.
5. **The plan goes back to the platform** when the athlete sends it, or automatically with auto-send on: a comment on the TrainingPeaks workout, or a nutrition summary on the completed intervals.icu activity.

Weather is pulled in real time based on the athlete's location and the planned workout time, so a workout synced three days ago gets a fresh, weather-adjusted prescription when the athlete looks at it the morning of.

---

## Common Integration Scenarios

**The coached cyclist or triathlete:** coach builds the weekly plan in TrainingPeaks → workouts sync to Saturday with fuel prescriptions → athlete reviews the fuel plan the morning of → the prescription is posted back as a comment on the workout (one tap, or automatic with auto-send on), so the coach sees it in TrainingPeaks.

**The self-coached data nerd:** athlete plans workouts in intervals.icu → Saturday syncs and generates prescriptions → after the ride, a nutrition summary comment is posted to the activity in intervals.icu alongside power, HR, and the other metrics.

**The Garmin-only athlete:** Garmin records the workout → syncs to intervals.icu (free account) → Saturday picks it up. Or: the athlete opens Saturday and enters the activity manually in 30 seconds. Both work.

**The no-tech athlete:** no calendar, no platform, no device sync. Opens Saturday, taps "New Activity," enters sport/duration/intensity, gets a prescription. The algorithm is the same.

---

## Integration FAQ

**Q: Can my coach see my fuel prescriptions?**
A: Yes. On TrainingPeaks and intervals.icu the fuel plan posts back as a comment on the activity, where the coach works: one tap from the activity screen, or automatically once you turn on auto-send. See [Saturday for Coaches](https://saturday.fit/llms-for-coaches.md) for the full coaching workflow.

**Q: I use Garmin. How do my workouts get into Saturday?**
A: Sync Garmin into intervals.icu or TrainingPeaks and connect Saturday to that, or enter the activity manually in seconds. The prescription is identical either way. If your app's Sync Your Apps screen offers Garmin directly, connect it there.

**Q: Does Saturday connect to Garmin, COROS, Wahoo, Polar, or Suunto?**
A: The app's Sync Your Apps screen is the source of truth for what you can connect; today it offers TrainingPeaks and intervals.icu. The data policy Saturday publishes for each of the other platforms is in the [Activity-Platform Integration Disclosure](https://saturday.fit/legal/integrations-privacy). Strava and Oura are never connected.

**Q: I use Zwift / TrainerRoad / Xert. Does Saturday work with those?**
A: Through TrainingPeaks or intervals.icu. Sync Zwift or TrainerRoad into either, and the workouts flow into Saturday.

**Q: Does Saturday need an internet connection for integrations?**
A: Yes, syncing requires internet. Once a workout is synced and a prescription is generated, the prescription itself is available offline.

---

> We would rather state exactly what exists than leave gaps that get filled with guesses. Every integration we build is implemented and tested in depth, and we say what we read and how we use it.

---

## Related Pages

- [Saturday for Coaches](https://saturday.fit/llms-for-coaches.md): how coaches use Saturday with TrainingPeaks to manage athlete nutrition
- [Every Supported Sport](https://saturday.fit/llms-sports.md): how fueling differs across cycling, running, swimming, and 7 other sport types
- [How the Algorithm Works](https://saturday.fit/llms-how-it-works.md): what the algorithm computes for each activity and how sport type feeds into it

---

*Co-authored by the Saturday founding team and Claude Opus 4.6. Human expertise, AI-assisted structure. Last updated: October 2026.*
*Directory: https://saturday.fit/llms-welcome.md | Full content: https://saturday.fit/llms-full.txt*
