Activity-Platform Integration Disclosure

Saturday Inc. ("Saturday," "we," "us," "our") builds personalized fuel and hydration prescriptions for endurance athletes. To make them sharper, you can connect a fitness platform or device account so we can read your training data and send your fueling plan back to it (Section 3). This page sets out which platforms connect, what we read from each, what we write back, how we use the data, the legal basis for doing so, what we display, how we protect the data, how long we keep it, and how you stay in control.

1. What This Disclosure Covers

This disclosure covers Saturday's activity-platform integrations: connections to Garmin, COROS, Wahoo, intervals.icu, Polar, Suunto, TrainingPeaks, and Ride with GPS. Sync Your Apps in the Saturday app lists the platforms you can connect; for each platform named here, this disclosure describes what happens once you connect it. It does not cover the data you enter in the app yourself (that is the App Privacy Policy and the Consumer Health Data Privacy Policy), nor the Saturday connector for AI assistants and the Coach API (that is the Connector & API Privacy Disclosure).

Throughout, "you" and "your" mean the athlete who connects an account. You connect and disconnect each integration yourself, and each one reads only your data. Saturday Inc. is the data controller for the connected-platform data described here: we decide why and how it is processed. Each connected platform is an independent controller of the data on its side.

2. What We Read, Per Platform

Our integrations read your training history: completed workouts and, where the platform offers them, planned workouts and daily wellness data such as heart-rate variability, sleep, and resting heart rate. We use your completed workouts to compute your fuel, hydration, and electrolyte prescriptions, and we store the daily wellness data listed below with your account. From each platform we read only the categories listed below, and we read nothing from a platform you have not connected. (For what we write back, see Section 3.)

Your connected workouts are shown to you (and to a coach whose roster you join) and used to compute your prescriptions. Sections 5 and 6 describe how Saturday's AI features use connected data, and whether that data also trains Saturday's models is set out above and in Section 6. We do not connect to, import from, or train on Strava or Oura.

3. What We Write Back

Saturday writes the fueling plan it calculated for your session to your account on intervals.icu, TrainingPeaks, or Garmin, as set out below. It does not send your name, email address, or body measurements.

For sessions based on COROS data, Saturday can send fuel plans and comments to your own connected TrainingPeaks or intervals.icu account. These outputs carry the COROS credit, device model, and fitness label in Section 4.

• intervals.icu. 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.
• TrainingPeaks. A comment on the matching workout with your fueling plan, one for each workout in a multi-sport session, when you tap Send on the activity, or on its own if you turn on Auto-send nutrition to TrainingPeaks in Preferences. TrainingPeaks does not let apps edit a comment, so each updated plan Saturday sends appears as a new comment.
• Garmin. While you are a Saturday member, when you accept a fueling plan for a single-sport session, Saturday may add it to your Garmin Connect calendar on the day you plan to train, through Garmin's Training API, as a workout named "Saturday Fuel Plan". The workout carries the session's sport and planned duration, your plan's carbohydrates, fluid, and sodium per hour, and one step for each planned drink or feed, at its planned minute (for example, "Gel + 150ml Bottle 1"). If you change the plan, Saturday replaces that workout rather than adding a second one. Saturday sends Garmin no routes or courses.
• What stays there. Comments and workouts Saturday has added stay on the platform under your control, including after you turn off auto-send or disconnect, and you can delete them there.
• Nothing else. We write only to the account you connected. We never write to anyone else's account or to a public feed, and we never change a recorded activity's training data (power, heart rate, distance, or the workout you did). We do not write to COROS, Wahoo, Polar, Suunto, or Ride with GPS.

4. Attribution: Whose Data You're Looking At

When Saturday shows you data from a connected platform, or a recommendation built from it, we credit the source:

• Garmin. "Garmin" and the device model that recorded the activity (for example, "Garmin Forerunner 965"), read from the activity itself.
• COROS. "Powered by COROS" and the device model (for example, "Powered by COROS · PACE 3"), in the app, no less prominently than any other source's attribution on the same screen. Recommendations built from COROS data carry the label "For fitness and performance purposes only. Not medical advice." The same credit, device model, and label appear on fuel plans and comments sent to your own TrainingPeaks or intervals.icu account and in answers from your own AI assistant through the Saturday connector.
• TrainingPeaks, intervals.icu, Wahoo, Polar, and Suunto. An icon for the platform appears beside each workout imported from it in your activity list.

5. AI-Transparency Statement (Garmin and COROS)

This section is our AI-transparency statement for Garmin and COROS data.

(a) That we use AI, and for what purpose

Saturday uses machine-learning models to improve its fuel, hydration, and electrolyte recommendations. Saturday's AI chat and the AI fueling reports coaches request use Google's Gemini (Section 6).

(b) Garmin data and AI

Garmin data is left out of every AI feature unless you turn on "Garmin data in AI" in the app (My Profile > Sync Your Apps). When it is on, Saturday's AI chat, the AI that reads the notes you write about your workouts, and the AI fueling reports your coach requests can use your Garmin workouts and the fueling plans built from them. The chat can be given each workout's ID, sport, date, time, duration, intensity, device and title, the settings you chose for it, its fueling plan, what you logged about it, and what is on the screen you have open; the AI that reads a note about a workout gets that workout's sport, date, time, duration, intensity, settings, fueling plan, and what you ate and drank; coach reports get the session summary described in Section 6. None of them is given activity streams or GPS routes. Google processes this for Saturday and does not use it to train its models. When it is off, these features are not given any of it; they are told only that you connected Garmin and that your Garmin details are left out, and a coach who requests an AI report is told that your Garmin sessions are not included. Garmin data is not available to AI assistants connected through the Saturday connector or our Coach API, whether this is on or off.

(c) Consent and withdrawal

We ask before we turn this on, on a screen that explains it, and we record your choice. You can turn it off at any time in the same place, which stops its use and removes the AI reports and chat answers built from your Garmin data. What Saturday's AI noted from a note you wrote about a Garmin workout stays with that workout, and AI features are not given it while this is off. Disconnecting Garmin also turns it off.

(d) Training

We do not use Garmin data to train our models, and chats with Saturday's AI that used your Garmin data are not used for training. Before we would use Garmin data for training, we will describe that use here and ask for your separate consent in the app. Turning on "Garmin data in AI" does not allow it. COROS data trains our models only as Section 6 describes.

(e) COROS

Saturday's AI chat, including a coach's chat about you in the Saturday app, can use your COROS workouts as it uses those from other platforms (Section 6), and its answers built from them carry the COROS attribution and label in Section 4. The AI fueling reports coaches request in the Coach Portal do not include COROS workouts. Through your own Saturday connector, your AI assistant can read your COROS-derived activities and fuel plans to answer your fitness and performance questions, with the COROS credit, device model, and fitness label in Section 4. COROS data remains unavailable through the Coach API, a coach's roster connector, the Coach Portal, exports, or webhooks.

We will update this statement when the law, our practices, or Garmin's or COROS's policies change.

6. How We Use the Data

• To serve you. We use every connected platform's data to compute and show your prescriptions and training context, and to send your fueling plan to your intervals.icu, TrainingPeaks, or Garmin account (Section 3).
• 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.
• Your coach. If you share your Saturday account with a coach, that coach can see your activities and the reports and plans built from them, including those from connected platforms, for as long as you share. Your coach sees your COROS workouts in the Saturday app, not in the Coach Portal.
• Wahoo's use of your data. Separately from how Saturday uses it, Wahoo may use the data it provides for its business purposes, under Wahoo's terms. We disclose this because the Wahoo agreement requires it; it does not change how Saturday uses your Wahoo data.
• What we never do. We do not sell your data, "share" it for cross-context behavioral advertising, use it for advertising, or share it with data brokers. We do not build leaderboards or cross-athlete benchmarks from a platform's data, and we use it for no purpose other than those above.
• Rated chats. When you rate an answer from Saturday AI, that chat may help train Saturday's assistant, only if you are 18 or over and only if every connected source it draws on may be used for training under the list above; chats that draw on COROS data do not. If you subscribe, you can turn this off at any time in My Profile > Preferences. If Saturday's records place you where the law requires your yes first (the EU or EEA, the UK, Switzerland, Washington, Nevada, or Connecticut), or wherever Saturday cannot tell where you are, this starts off and you can take a yes back without a subscription.

Learning from your TrainingPeaks, COROS, Polar, and Ride with GPS workouts

Saturday learns from your completed workouts on these apps only if you allow it, separately for each app. After you log a finished workout, the app asks once, in one question, about every one of these apps you have workouts from that it has not asked about yet; your answer counts for each app separately, and you can change each one at any time in My Profile > Preferences. If your health data would otherwise stay out of training (Section 6), the same question also asks whether Saturday may learn from the health answers you give in the app. Some Ride with GPS rides train without the ask (Section 6). We do not ask athletes under 18 and do not use their workouts this way.

With your permission we use those workouts (sport, date, duration, distance, climbing, effort, and heart rate) and what you log about them (what you ate and drank, how it felt, and any symptoms), keyed to an internal ID number rather than your name or email address, to predict how long workouts take and how much fuel they need. We never sell your workouts or use them for advertising.

If you turn it off for an app, we leave that app's workouts out of any training from then on. Models already trained stay in use. Your workouts stay in your account and keep shaping your plans either way.

AI processing by Google

Saturday uses Google's Gemini models, through Google Cloud Vertex AI, for the uses of connected-platform data below. Google processes this data for us as our processor under its cloud data-processing terms, does not use it to train its models, and returns each result to Saturday. Data from Garmin is sent only if you turn on "Garmin data in AI" (Section 5).

• Identifying the sport of a TrainingPeaks workout. When a TrainingPeaks workout does not tell us its sport (a "custom" or "other" workout that our keyword list cannot place, or a brick workout whose legs we need to identify), we send that workout's title, description, pre-activity comment, tags, TSS calculation method, number of structured steps, and whether it has power data to Gemini, which returns the sport. No name, email address, or account ID is sent. This applies only to TrainingPeaks workouts.
• Coach reports. If you are on a coach's roster and your coach requests an AI-written fueling report or a roster summary, we send Gemini a summary of your recent sessions: date, sport, duration, how closely you followed your fluid, carbohydrate, and sodium plan, your rating, how you entered your report and how complete it was, the sleep hours you entered, and symptoms you reported. A roster summary also includes the name of each athlete who needs attention (or their email address or internal account number when no name is set) and the reason. Activity streams, GPS routes, and device details are not sent. Sessions from COROS are left out.
• Saturday's AI chat. If you, or your coach in the Saturday app, use Saturday's AI chat, Gemini receives the messages and the account, profile, and activity details it needs to answer, including your connected workouts, the fueling plans built from them, and what is on the screen open in the app. When you write a note about a workout, Gemini also reads it with that workout's sport, date, duration, intensity, settings, fueling plan, and what you ate and drank, to record any symptoms and how your fueling went. If you pick the Leda or Schedar voice for the chat, the text of its answers also goes to Google's Gemini API to be read aloud; Google processes that text for us under its terms for paid Gemini API services, does not use it to improve its products, and keeps it for a limited time only to detect abuse.

If we know you are in the European Economic Area, the United Kingdom, Switzerland, or Connecticut, we do not send your TrainingPeaks workouts or your sessions to Gemini for the first two uses unless you give your permission in the app.

For processing on Vertex AI, Google may keep a request and its response for up to 24 hours to speed up similar requests, and may keep a request its safety systems flag for up to 90 days, only for abuse and safety monitoring. These requests may be processed in Google data centers in any country (see Section 10).

If you connect an AI assistant to your Saturday account through the Saturday connector (for example Claude), or your coach connects one with access to their roster, that assistant can read your activities and fueling data, and its provider (for example Anthropic) handles that data under its terms. Through your own Saturday connector, your AI assistant can read your COROS-derived activities and fuel plans to answer your fitness and performance questions, with the COROS credit, device model, and fitness label in Section 4. Garmin data is not available through the connector. Neither Garmin nor COROS data is available through a coach's roster connector or our Coach API; the assistant may be told that some details are hidden. See the Connector & API Privacy Disclosure.

7. Legal Basis, Automated Decisions, and Our Models

Legal basis for processing (GDPR / UK GDPR)

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

• Performance of a contract (Art. 6(1)(b)): to read your connected activities and compute the prescriptions you signed up for, and to send your plan back as Section 3 describes.
• 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.

Automated decision-making and profiling (Art. 13(2)(f) / Art. 22)

Saturday's prescriptions are produced by algorithms that profile your training data to estimate your fluid, sodium, and carbohydrate needs. That is the core function you asked for. The logic, in plain terms: we combine your body metrics and stated preferences with the intensity, duration, and environmental conditions of each session (and, where we use them, patterns our models learned across many athletes) to compute a recommended intake. These recommendations are guidance you can always override or ignore; they are not used to make decisions that produce legal effects or similarly significant effects on you, so they are not solely automated decision-making under Article 22. If you have questions about how your recommendations are calculated, or want a person to review them, contact us.

Your data and our models

When Saturday trains a model on athletes' data, that data is keyed to an internal ID number rather than your name or email address. When you delete data, withdraw a consent, or object, we leave that data out of all future training. Models already trained stay in use. The model that predicts how long a workout takes learns only from kinds of workout, by sport and subtype, that at least 20 adult athletes have done. Your identifiable data is deleted as Section 9 describes. We train only where each source's terms allow it, and we honor each source's deletion rules.

8. Consent & Withdrawal: Every Source

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. We obtain your affirmative consent before we collect from a connected source. Letting AI features use your Garmin data (Section 5), and letting your workouts train our models where Section 6 asks for your OK, are separate choices you make. You can withdraw at any time:

• Disconnect in Saturday. In Sync Your Apps, tap ⋮ beside the platform, then No, Unlink Me, then Yes, Disconnect. We stop syncing and delete the access credentials we hold, and where the platform supports it (COROS, Garmin, Wahoo, Polar, intervals.icu, and Ride with GPS) we also revoke Saturday's access there. What happens to imported data depends on the platform (Section 9).
• Revoke at the source. You can also remove Saturday in the platform's connected-apps settings. Garmin tells us when you do. COROS does not, so we check the status of every connected COROS account with COROS several times a day. Once we learn of it, we treat it as a disconnect in Saturday. For the other platforms, no new data arrives after you remove Saturday there; to have imported data deleted where Section 9 says a disconnect deletes it, also disconnect in Saturday.
• Turn off "Garmin data in AI" at any time, without disconnecting, in My Profile > Sync Your Apps (Section 5).
• 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.
• Withdraw model-training consent for Garmin, once we ask for it, in the app, without disconnecting (Section 5).
• Stop the comments Saturday posts on its own to intervals.icu or TrainingPeaks, without disconnecting, by turning off auto-posting or auto-send for that platform in Preferences (Section 3). Saturday stops setting carbohydrates per hour on intervals.icu, and stops adding workouts to Garmin Connect, when you disconnect that platform.

9. Deletion, Retention & Your Rights

Disconnecting an integration ends the connection: we stop syncing, delete the access credentials we hold, and, where the platform lets us, revoke our access. What happens to imported data depends on what that platform's terms require of us. We do that and no more, so your training history stays yours wherever it can. You can delete any of it yourself at any time: delete the activity in the app, email support@saturdaymorning.fit, or delete your account, which removes everything.

• While you stay connected. We keep the data we import for as long as you keep your Saturday account.
• COROS. Within 24 hours of your disconnecting in Saturday, or of our finding that you removed Saturday from your COROS account or closed it, we delete the COROS measurements, files, and access credentials. Your fueling reports and the plans Saturday made for you stay in your account with the COROS measurements removed. Nothing from COROS is kept longer than 90 days after either event.
• Garmin. Within 24 hours of your disconnecting Garmin, or of Garmin telling us that you removed Saturday or withdrew your permission, we delete the Garmin data and access credentials. Your fueling reports and plans stay, with the Garmin measurements removed.
• 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.
• Polar, Suunto, intervals.icu, and TrainingPeaks. When you disconnect, we stop syncing and delete the access credentials we hold (Section 8). The workouts in your account stay there, marked with their source, until you delete them or your account. The exception is workouts imported before the October 23, 2026 version of this disclosure took effect: our pages then said that disconnecting deletes your data within 24 hours, and we keep that promise for them. When you disconnect one of these platforms, we delete the workouts imported from it before that version took effect within 24 hours of the disconnect reaching our servers.
• Ride with GPS. When you disconnect, we stop syncing and delete the access credentials we hold (Section 8). The rides and routes we imported stay in your account until you delete them or your account. A ride you delete in Ride with GPS stays in Saturday. While you stay connected, a route you delete there is removed from Saturday too, unless an activity in Saturday uses it.
• A single activity. When you delete an activity in the app, we delete it from your account and from our analytics warehouse within 24 hours. The original file a platform sent us for that workout is deleted within 32 days, or sooner when that platform's data is deleted under the bullets above or with your account.
• Your Saturday account. Deleting your account deletes everything above, from every platform, within 24 hours, and ends every connection.
• Backups and dated copies. Deleted data can remain for up to 84 days in our disaster-recovery backups, and for up to 100 days in our analytics warehouse, in the dated copies of our database we keep there for internal analysis and in the recovery copies Google BigQuery keeps, until they expire. We use the backups only to restore service after a failure, and before we restore from one, we re-apply the account deletions, disconnections, and activity deletions made since it was taken.
• Your rights (GDPR / UK GDPR). You have the right to access the data we hold about you (Art. 15); to rectify inaccurate data (Art. 16); to erase it (Art. 17); to restrict our processing (Art. 18); to data portability, meaning to receive the data you gave us in a structured, commonly used, machine-readable format and have it sent to another controller where technically feasible (Art. 20); and to object to processing, including any processing based on legitimate interests (Art. 21). Where processing is based on consent, you can withdraw that consent at any time. You also have the right to lodge a complaint with your local supervisory authority (data protection authority).
• Your rights (US state law). Depending on your state, you have rights to know, access, delete, and correct your data, to opt out of any sale or "sharing," and to limit the use of sensitive personal information. Saturday does not sell your data and does not use it for cross-context behavioral advertising, so there is nothing to opt out of, but you may exercise the right at any time. We treat connected activity and wellness data as sensitive personal information and use it only for the purposes in Section 6.
• Consumer health data (Washington MHMDA, Nevada SB 370, Connecticut). Connected activity and wellness data is "consumer health data" under these laws. We collect and share it only with your consent or as necessary to provide the service you requested; we never sell it. You may confirm what we collect and with whom we share it, withdraw consent, and request deletion, and you may appeal a declined request. Our Consumer Health Data Privacy Policy governs these rights in full.
• How to exercise them. You can disconnect any integration in Sync Your Apps, and delete an activity or your whole account in the app. For a copy of your data, a correction, or any other request, email support@saturdaymorning.fit. We confirm receipt and respond within the time the applicable law requires (for example, within one month under the GDPR and within 45 days under US state privacy laws, extended only where the law allows). We will not discriminate against you for exercising any of these rights, though withdrawing consent for an integration ends the personalization that depended on it.

10. Security, Sub-Processors & International Transfers

Security of processing

We protect connected-platform data with technical and organizational measures that include encryption in transit (TLS) and at rest, Firestore security rules and access controls that limit who and what can read your data, and verification of the notifications platforms send us so that we act only on genuine ones. No system is perfectly secure, but we take reasonable, current steps to protect your information.

Sub-processors

Connected-platform data flows between the platform's API, Saturday's API, and Saturday's infrastructure on Google Cloud. Our sub-processors for this data act as processors on our behalf under data-processing agreements: Google, for Google Cloud (application hosting, data storage, and our analytics warehouse), Vertex AI on Google Cloud (the Gemini models behind the AI processing in Section 6), the Gemini API (the chat voices in Section 6), and Firebase (app analytics and crash reports; app analytics events can include a workout's sport, duration, and intensity, but from app version 1.2.22 the app keeps a Garmin or COROS workout's values, the platform's name, and the workout's ID out of analytics and crash reports); and Cloudflare, Inc., which carries traffic to and from our API at api.saturday.fit, including the notifications connected platforms send us. We do not sell or redistribute connected-platform data. The connected platforms themselves (Garmin, COROS, Wahoo, intervals.icu, Polar, Suunto, TrainingPeaks, Ride with GPS) are independent controllers of the data on their side, not Saturday's sub-processors.

Email. Brevo (Sendinblue SAS, France) and Klaviyo, Inc. (United States) deliver Saturday's emails. When an email concerns a session from Garmin or COROS, it carries none of that session's details: a coach alert links to the Coach Portal, and a session attached to a coach's message appears only as a note to open the Saturday app. When it concerns a session from another connected platform, it does not carry the platform's measurements: at most it names the session by its date and sport, says how closely the fueling plan was followed, and repeats what the athlete reported about it (a rating or symptoms); the details stay in Saturday. We share connected-platform data with a service provider only when it is needed to provide Saturday, only under written terms at least as protective as our agreements with those platforms, and we remain responsible for what the provider does with it. We never add connected-platform data to email marketing profiles, segments or advertising audiences.

International data transfers

Saturday Inc. is based in the United States. If you connect an integration from outside the United States, your connected-platform data comes to us there, and we store it on Google Cloud servers in the United States. Where a platform's agreement with us includes the European Commission's Standard Contractual Clauses for that transfer, those clauses apply to it. Our service providers process connected-platform data for us under contracts that require them to protect it at least as well as this disclosure does. Google LLC, which hosts our systems and runs the AI processing in Section 6, and Klaviyo (email) are certified under the EU-U.S. Data Privacy Framework, its UK Extension and the Swiss-U.S. Data Privacy Framework, which the European Commission, the UK Government and the Swiss Federal Council recognize as providing adequate protection for data sent to certified US companies. Brevo stores data in the European Union. The AI requests in Section 6 may be processed in Google data centers anywhere in the world; where that is a country without such recognition, the European Commission's Standard Contractual Clauses (controller to processor) in Google's Cloud Data Processing Addendum apply, with the UK and Swiss adjustments. You can ask for a copy of these safeguards at support@saturdaymorning.fit.

11. Children's Data

Saturday and its integrations are not directed to children under 14, and we do not knowingly let a child under 14 connect a fitness platform or device account. Where local law sets a higher minimum age of digital consent (up to 16 in some EEA and UK jurisdictions), that higher age applies, and we do not knowingly collect a child’s personal data below that age without verifiable parental consent. If we learn that we have collected connected-platform data from a child under 14, we will delete it promptly. A parent or guardian who believes their child has connected an account should contact us using the details at the foot of this page.

12. Data Breach Notification

If a breach affects connected-platform data, we will notify the relevant supervisory authority within 72 hours of becoming aware of it where the GDPR requires, and we will notify affected users without undue delay where the breach is likely to result in a high risk to them. As a provider of a health service not covered by HIPAA, we also comply with the US FTC Health Breach Notification Rule and applicable state breach-notification laws, including notifying affected individuals and regulators within the times those laws require.

13. Changes to This Disclosure

If we add a new integration, change what an existing one reads or writes, or change how we use connected data, we will update this page and its effective date, and, where the change is material, tell you by email or in the app before it takes effect and seek renewed consent where the law requires it.