<!--
@llm-meta
file: llms-legal.md
title: Legal — Privacy Policies, Terms, Coach Portal, DPA
description: Comprehensive legal-document reference for saturday.fit. Privacy policies, terms of service, EULA, coach-portal terms, coach privacy addendum, Data Processing Agreement template.
category: site-page
keywords: legal, privacy, terms, policy, EULA, DPA, MHMDA, GDPR, CCPA, CPRA, coach, marketplace, Stripe Connect
last-updated: 2026-10
related: llms-transparency.md, llms-homepage.md
-->

# Saturday Inc. — Legal Pages

> LLM context file for saturday.fit/legal

## Page Structure

The legal section index is at `/legal` and links to **11 separate documents**:

### App Policies (consumer-facing, mobile app + web)
- **App Privacy Policy** (`/app-privacy`) — Saturday: Pro Fuel & Hydration mobile app data handling
- **App Terms & Conditions / EULA** (`/app-terms`) — License and terms of use for the app
- **Saturday AI Disclaimer** (`/ai-disclaimer`): why Saturday AI, the in-app assistant, can give wrong answers, and how to check the ones that matter most (see [llms-ai-disclaimer.md](https://saturday.fit/llms-ai-disclaimer.md))

### Website Policies (saturday.fit visitors and purchasers)
- **Website Privacy Policy** (`/web-privacy`) — Data handling for saturday.fit visitors
- **Website Terms of Use** (`/web-terms`) — Terms governing saturday.fit website use

### Health Data
- **Consumer Health Data Privacy Policy** (`/health-data-privacy`) — Standalone policy compliant with WA My Health My Data Act (MHMDA), including 2024-2026 enforcement guidance

### Integrations
- **Activity-Platform Integration Disclosure** (`/legal/integrations-privacy`): which data Saturday reads from Garmin, COROS, Wahoo, intervals.icu, Polar, Suunto, TrainingPeaks and Ride with GPS, what it writes back, how it uses the data (including for machine learning), the legal basis, users' rights, attribution, consent and deletion

Effective October 24, 2026: COROS-derived fuel plans and comments can go to the athlete’s own connected TrainingPeaks or intervals.icu account, and their own AI assistant can read their COROS-derived activities and fuel plans through the Saturday connector for fitness and performance questions. Each output carries the COROS credit, device model, and "For fitness and performance purposes only. Not medical advice." COROS data remains unavailable through the Coach Portal, the Coach API, a coach’s roster connector, exports, or webhooks. Garmin data remains unavailable through the connector and Coach API.

### Coach Portal (coach.saturday.fit)
- **Coach Terms of Service** (`/legal/coach-tos`) — Coach portal terms covering tier subscriptions, Stripe Connect billing, athlete relationships, organization hierarchy, FTC endorsement compliance, scope-of-practice carve-outs
- **Coach Privacy Policy** (`/legal/coach-privacy`) — Athlete-data handling by coaches, GDPR controller/processor framing, sub-processor transparency, audit logging
- **Data Processing Agreement (DPA)** (`/legal/dpa`): template DPA for B2B customers, includes 2021 SCCs (Module 2) + UK Addendum 2022

### Commerce
- **Merch Return Policy** (`/merch-returns`) — all merch sales are final (made-to-order); items that arrive damaged or misprinted get a free replacement (photo within 14 days, no return needed)

## Languages

Every document above is also published in Spanish, French, Brazilian Portuguese, German and Japanese, at the same path under `/es/`, `/fr/`, `/pt/`, `/de/` and `/ja/` (for example `/pt/app-privacy`), and each localized index (`/es/legal` and so on) links to the documents in its language. On a translated page the link back to the index and the contact block are in that language, and links to other legal documents open their translations. The translated privacy policies and terms open with a note that the English version governs if the two differ.

## Key Legal Details

| Field | Value |
|---|---|
| Entity | Saturday Inc. |
| Address | 8 The Green, STE A, Dover DE 19901 |
| Contact | support@saturdaymorning.fit |
| Arbitration opt-out | legal@saturdaymorning.fit |
| Governing law | State of Delaware |
| Jurisdiction | Maricopa County, Arizona (for non-arbitration matters) |
| Arbitration venue | Phoenix, Arizona via JAMS |
| Minimum age | 14 (14-17 with a parent's or guardian's consent and supervision; higher where local law sets a higher age of digital consent) |
| Health data law | WA MHMDA (separate dedicated policy) |

## Data Collected (App)

- Email address, any other email addresses added to the account, display name, Firebase UID, authentication method (Google, Apple, email and password, or an emailed sign-in link)
- Health & biometric data: weight, sex, year of birth, sweat level, saltiness, fitness level, satiety, cravings, weight loss preference, eating disorder flag, fueling concerns (gut distress, cramps, faintness, heat tolerance, hunger, thirst, drinking resistance, performance), max carbs, usual carbs, swim PR
- Activity data: type, duration, intensity, thermal stress, nutrition consumed, ratings, notes, symptoms and sleep logged with an activity
- Where the athlete is, for rules that differ by place: the country the app connects from (the state for a few US states) and the App Store or Google Play account country, kept with the account; the app also reads the phone's region and time zone settings on the phone to decide which consent questions to show, and Saturday does not keep them
- Invitations: whose invite link an athlete joined through (to reward the inviter on the first subscription); on Android read from the Google Play install link, on iPhone from a one-time clipboard check on first launch for an invite code Saturday's invite page put there, which the app then clears
- Coaches: an athlete who shares the account with a coach lets that coach see their profile, activities, products, sleep entries, reports and plans while sharing, and change settings and activities where the relationship allows
- Trial-conversion estimate: a model trained on past free trials estimates, from the first five days (sign-in method, units, the chemistry answer, trial start, plans built), how likely a trial athlete is to subscribe; used only to choose who gets a personal note and to measure trial changes
- Device & technical: app version, OS version, crash data, analytics events
- Store country (App Store or Google Play account); on Android, the source, medium and campaign of the Google Play link that installed the app; first and latest subscription page view and the number of views. Used to understand which parts of Saturday work for whom and where. When Saturday tests versions of an offer (such as a free-trial extension), it records which version the account was given and when, kept 425 days after the latest one or until the account is deleted. When a plan is canceled, Saturday records when and the reason the store reports (Google Play's cancellation survey answer and any typed text, Stripe's reason and comment for a website plan, Apple's reason for a plan ending) on the purchase record; account deletion removes the typed text and keeps the reason codes. Health answers are not used to choose offers or in-app tips, except year of birth: athletes under 18 get marketing emails and some offers only if they opt in
- Usage analytics (Google Analytics for Firebase, linked to the account ID): Google keeps user-level data 14 months after the user's last activity in the app and event-level data 2 months. Saturday's copy of the events in Google BigQuery is kept until the account is deleted; then Saturday asks Google to delete the user's analytics (Google completes it within about two months) and deletes from its copy, within 4 days, the events recorded under the account and those from app installations only that account used
- Location: an approximate location is stored with each activity (city or region, coordinates rounded to about 1 km) for weather-based fueling. The app sends OpenWeatherMap and the phone's built-in place lookup (Apple on iPhone, Google on Android) a location rounded to about 1 km; App versions before 1.2.22 send OpenWeatherMap and the phone's place lookup the device's precise coordinates; support emails drafted in those versions include them too (1.2.22 rounds them to about 1 km). The device's precise coordinates are not stored with the activity. Athletes who connect TrainingPeaks, COROS, Polar, Suunto, Wahoo or Ride with GPS: Saturday keeps a copy of the workout data the platform sends, which includes the GPS route when the device recorded one, at the precision the platform sends; COROS, Polar, Suunto, Wahoo and Ride with GPS workouts also store the exact starting point with the activity, and the routes an athlete saved in Ride with GPS are kept with their tracks. No exact location is kept from intervals.icu; for athletes under 18, neither the route nor the exact starting point of a workout is kept, only a starting point rounded to about 1 km (saved routes keep their tracks)
- Marketing email (Klaviyo): an account joins email lists only after its email address is confirmed (Google or Apple sign-in at that address, or the confirmation link). Under 18 (age entered in the app or the store's age range): only with the in-app box ticked. In the EEA, UK or Switzerland (any of the store country, phone region, time zone or connection points there): only with the box ticked, an unticked box recording no; older app versions ask only on the Sign up screens, and with them an account Saturday's records place there is not subscribed without a yes. Accounts a coach created: only if the athlete opts in. Everyone else is subscribed once the address is confirmed and the app is opened, unless they unsubscribed at that address before. Boxes start unticked
- Third-party sync (user-initiated): TrainingPeaks, Intervals.icu, COROS (workouts from the past 3 months and every new one, each with its workout file and GPS route, and daily recovery data: resting heart rate, heart rate variability, sleep times, sleep heart rate, steps and calories), Polar (exercises with their samples and GPS route, Nightly Recharge recovery, sleep stages and score, and the Polar physical profile: weight, height, maximum and resting heart rate, heart rate thresholds and VO2 max), Suunto (workouts with their workout files, including GPS route and ambient temperature, and the daily sleep and recovery summaries Suunto sends), Wahoo (workouts with their summaries and workout files, with GPS route where recorded), Ride with GPS (rides from the past 3 months and every new or edited ride with its GPS track; saved routes: the 50 most recently updated at connect, then every new or edited one, with track, surface and the aid, water and food stops marked on it). A Ride with GPS training record (the result of any check of where the connection comes from, never an IP address; from which connection rides may train; any request to leave rides out) is kept while the account exists, including after disconnecting, and deleted with it
- Coaching: a record of each coaching relationship (which coaches can see the athlete's data, both people's names and emails, the access granted, whether the coach is the primary coach, how and when it began and ended), kept while both accounts exist, including after the relationship ends; reconnecting with the same coach replaces the old record; deleted when either account is deleted. A coach can write notes about the athlete, which the athlete never sees, and can share a note with the other coaches who can see the athlete's data; the coach, not Saturday, is the controller of these notes. They are kept until the coach's account is deleted. When the athlete deletes their account, the notes stay with the coach who wrote them: the athlete's account ID is removed and replaced with a code, only that coach sees them (under an anonymous athlete), and the note text is not edited, so it may still name the athlete
- Security log: account and security actions (for example signing in or returning to the app, switching accounts on a device, accepting or removing a coach, a coach inviting the athlete or changing their nutrition settings, Saturday staff signing in as the user on the coach website). Some entries record what changed, which can include names and email addresses. Most entries record the IP address, with the app's networking software name and version for app actions or the browser user agent for coach-website actions; entries about the key that signs the user back in on a new or restored phone record the phone model and a keyed code made from the IP address instead of the address. Each entry is deleted within a day after it is 1 year old, security entries (Saturday staff signing in as the user, privacy requests made on the coach website, API keys, signing sessions out, two-step verification, single sign-on, roles and permissions, device access, organization ownership transfers) after 2 years; deleting the account does not delete them earlier

## Data Collected (Website)

- Identity for purchasers: name, email
- Browser, network, device info
- IP address (anonymized where possible), pages visited, referral pages
- Stripe handles all payment data — Saturday never sees credit card numbers
- Marketing emails via Klaviyo follow the app account rules above; a website purchase alone does not add the buyer to an email list. A website purchase sends Klaviyo the buyer's email and purchase details (plan, price, currency, payment references, offer or campaign link); Klaviyo sends the redemption-code email when the purchase is not yet on an account, and Brevo sends the receipt with any sign-in link. A gift also sends Klaviyo the recipient's email, the buyer's name and message
- Gift purchasers provide the recipient's email address and an optional message
- Store reviews: rating, title, text, photos and the name entered are published. The email address is optional and never shown; Saturday keeps it for 180 days to contact the reviewer about the review, and keeps a one-way hash of it with the review so that deleting a Saturday account with that address also deletes the review. A Verified Buyer badge is set only by a Saturday moderator
- Merch orders (including the free T-shirt that comes with Lifetime): Stripe Checkout collects the name and shipping address; Saturday sends them, with the buyer's email address and the items ordered, to Printful (Printful, Inc.), which prints and ships the order as Saturday's processor, emails shipping updates, and gives the name and address to the delivering carrier. Stripe and Printful keep the name and address with the order; Saturday's own order record keeps the email address (not the shipping address) until 90 days after the order goes into production, and a one-way hash of the email address for a year after the latest merch order. Printful may handle orders through affiliates in other countries (such as Latvia, Poland, Spain and the UK); its data processing terms include the European Commission's standard contractual clauses
- Consultation bookings: name, email, the call's time and length, price, any coupon and payment references, and an optional topic, kept as the record of the call; 30 days after the call the call and booking-page links are removed from that record, a year after the call the topic. The call's Google Calendar event keeps its details. Consultations are a separate service from the app: deleting an app account does not delete consultation bookings, their calendar events or their notes
- Server logs: Google Cloud request logs (with IP address) 30 days; some Cloudflare services keep request logs 7 days
- Website analytics: Google Analytics keeps event data 2 months and user data 14 months after the last visit; Saturday's BigQuery copy of website events has no deletion date and is not linked to Saturday accounts

## Data Collected (Coach Portal)

- Coach identity: email, display name, Firebase UID
- Coach tier subscription details (Coach free, Pro Coach $12.99/mo, Head Coach $49.99/mo, Business $149/mo, Enterprise custom)
- Coach account data: your account profile, Portal settings, alert rules, personal groups, the invitations you sent, API keys, webhook endpoints and signing secrets, directory application, and public directory profile. Until your account is deleted. An API key that is revoked or expires is deleted 90 days after it stops working.
- Athlete-coach relationship records (linked via `shared_with_coach_uids`): kept while both accounts exist, including after the relationship ends; reconnecting replaces the old record; deleted when either account is deleted
- Coach notes: private notes a coach writes about an athlete (archived notes included), never shown to the athlete, shareable with the other coaches who have access to the athlete; kept until the coach's account is deleted. If the athlete deletes their account, the coach keeps them: the athlete's account ID is replaced with a code and only that coach sees them, under an anonymous athlete; the note text is not edited, so it may still name the athlete
- Stripe Connect account ID and status (Coach is merchant of record). Saturday deletes its record of your Stripe account ID and status when your Saturday account is deleted. Financial records and records held by Stripe follow their separate retention periods.
- Compliance dashboard data (computed real-time from athlete activity)
- Audit log: admin actions, impersonation events, user agent, the IP address for many Coach Portal actions, timestamps (append-only; entries are never changed and are deleted after 1 year, or 2 years for security entries; deleting an account does not delete them earlier). Only Saturday staff can impersonate a user
- Org membership and role assignments. When your account is deleted, your email address is also removed from organization membership records. The membership record and account ID may remain.
- Data controller split: Saturday is the controller of athletes' accounts and app data (including what a coach views or changes in them), coaching relationship records, coaching alerts, and the audit log and impersonation records. The coach is the controller of what the coach creates: notes about athletes, athlete accounts the coach creates until the athlete claims them, and roster organization (organization, members and roles, groups, roster order, per-athlete alert settings), and the billing arrangements the coach sets with athletes; Saturday is the coach's processor for that data under the DPA
- Billing arrangements between coach and athletes (kept at least 7 years after the transaction; no deletion scheduled after that)

## Third-Party Services

### Common to App + Website
- **Google Cloud / Firebase** (Google LLC) — Auth, Firestore, Analytics, Crashlytics, Performance, Cloud Functions
- **Stripe** (Stripe, LLC): web payments and Coach Connect billing
- **Sentry** (Functional Software, Inc.): error reporting for the website and the Coach Portal
- **Klaviyo** (Klaviyo, Inc.): email marketing communications. Receives name, email, account ID; sex, age group by decade, sports, fitness level, seriousness, sweat level and saltiness, a sample hourly fueling target; onboarding status, marketing choice, first workout, trial and subscription status and dates, purchases (plan, price, store, payment references, offer, campaign link or partner), failed payments and cancellations, offers sent, the app language, and the coach's name and access end date when a coach stops paying for the athlete's subscription; and what gift and invitation emails need; it also sends the redemption-code and gift emails after a website purchase. Klaviyo records email opens and link clicks. Who receives marketing email is set out under Marketing email above
- **Brevo**: account and service emails (sign-in links, password resets, address confirmations, receipts, subscription notices, consultation booking emails), Coach Portal emails (notices about invitations, take-over-account emails, alerts to a coach about athletes on the roster, messages, ownership, coverage, trial and account notices), and the follow-up offer after a consultation (only to people who get marketing emails). Brevo records opens and clicks with their IP address, and its terms let it also use this data to produce statistics for itself
- **Cloudflare** (Cloudflare, Inc.) — CDN, DNS, DDoS protection, Workers (link.saturday.fit, get.saturday.fit, and api.saturday.fit, which carries some app requests, the Coach API and the connector)

### Website-only
- **Printful** (Printful, Inc.): prints and ships merch orders (name, shipping address, email address, items ordered)

### App-only (user-initiated or transient)
- **TrainingPeaks** (Peaksware, LLC) — Workout sync via OAuth; imported workouts stay in the athlete's history until they delete them or their account, except where the Activity-Platform Integration Disclosure says a disconnect deletes them
- **Intervals.icu** — Workout sync via OAuth
- **OpenWeatherMap** (OpenWeather Ltd) — Weather data (GPS sent transiently)
- **Open Food Facts** — Product database (barcode lookups)
- **Google Gemini on Vertex AI** (Google LLC), as Saturday's processor: reads nutrition label photos, identifies TrainingPeaks workouts whose type and keywords do not show what kind of session they are (sent: title, description, pre-activity comment, tags, TSS method, step count, power present, and the workout type of strength and cross-training sessions; no name, email, or account ID), answers in the Saturday AI assistant (sent: the athlete's messages, their activity notes and, as needed, profile and weight, activities, symptoms, sleep and fueling plans), and writes the AI fueling reports and roster summaries a coach requests (sent: per-session summaries; for roster summaries, flagged athletes' names or emails). These features are only for athletes 18 and older; the Saturday AI assistant works only if the athlete allows AI features when the app asks, and a no sends none of this to Gemini. Google does not train on this data. 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; Saturday stores data on Google Cloud in the US. Athletes Saturday knows are in the EEA, UK, Switzerland or Connecticut are left out of the TrainingPeaks and coach-report uses unless they give permission in the app. The AI-written part of coach reports and roster summaries is paused until November 9, 2026.
- **Training large language models**: Saturday AI chats an athlete rates can help train the language model behind Saturday AI when the athlete is 18 or older and My Profile > Preferences shows chat training is on for them. Saturday uses no other personal data to train large language models and does not sell personal data for that purpose.
- **Apple App Store** + **Google Play Store** — In-app subscriptions
- **Apple Sign-In** + **Google Sign-In** — Authentication

### Coach Portal additions
- **Google Cloud Vertex AI** (Google LLC): AI fueling reports and roster summaries, from November 9, 2026 (see Gemini above)
- **Sentry** (Functional Software, Inc.): Coach Portal error reporting

## User Rights

- **MHMDA (Washington):** Confirm/access, withdraw consent, delete, appeal, for people the MHMDA covers, via the Consumer Health Data Privacy Policy
- **CCPA/CPRA (CA):** Know, delete, correct, opt out of sale/sharing, limit sensitive PI, non-discrimination
- **GDPR (EU/UK):** Access, rectify, erase, portability, restrict, object, lodge complaint with supervisory authority
- **Multi-state US:** Access, correct, delete, opt out of sale/targeted ads/profiling, appeal — for residents of CO, CT, VA, TX, OR, MT, IA, IN, TN, FL, MN, NJ, DE, MD, NH, RI
- **Universal:** Withdraw consent, request deletion, exercise rights via support@saturdaymorning.fit
- **Global Privacy Control (GPC):** Honored as a valid opt-out signal
- **International transfers:** Saturday stores data on Google Cloud in the US. Google LLC, Klaviyo, Stripe, Cloudflare and Sentry are certified under the EU-U.S. Data Privacy Framework, its UK Extension and the Swiss-U.S. Data Privacy Framework; Saturday itself is not. AI requests may be processed in Google data centers anywhere; Google's certification covers those onward transfers, and Google's Cloud Data Processing Addendum requires Google to protect the data wherever it processes it. Brevo stores data in the EU.

## Important Terms (App EULA)

- Limited, non-exclusive, non-transferable license
- No reverse engineering, sublicensing, or transferring
- Services provided "AS IS" with no warranties
- Liability capped at 12 months of fees paid
- Comprehensive assumption-of-risk for fitness/nutrition activities
- Saturday staff are not medical doctors; recommendations require user verification with healthcare provider
- Mandatory arbitration with class action waiver (JAMS, Phoenix AZ)
- 30-day arbitration opt-out window from first acceptance
- 14-day money-back guarantee on direct (Stripe) web purchases
- App store purchases: refunds via Apple/Google
- Termination: 14-day notice for company-initiated terminations with prorated refund
- User can terminate anytime; access continues through paid billing cycle

## Important Terms (Coach Portal)

- **Coach is merchant of record** for the payments athletes make to them through the Portal; Saturday's Stripe account processes those payments on the coach's behalf and transfers them to the coach's Stripe Connect account (US coaches only), on any coach tier
- **Independent contractor relationship** between coach and Saturday, with no employment, agency, or joint venture
- **Coach is independent of athlete**: Saturday facilitates the relationship but is not party to coach-athlete service contracts
- **Athlete data access follows each relationship's permissions**: coaches read the athlete's profile, activities, products and sleep entries, and change settings and activities where the relationship allows; they never see the athlete's integration tokens or purchase records
- **Controller roles**: Saturday is the controller of athletes' accounts and the data in them (also when a coach views or changes it in the Portal), coaching relationship records, coaching alerts, and the audit log and impersonation records; the coach is the controller of the notes they write, athlete accounts they create until the athlete claims them, their roster organization, and the billing arrangements they set with athletes, which Saturday processes for them under the DPA
- **Athlete consent comes before coach access**: the athlete accepts an invitation, confirms an in-person connection, or approves a handoff between coaches; a coach who creates an athlete's account represents that the athlete consented
- **Athlete revocation is immediate**, with no coach-side override
- **Platform fee**: 3% of each athlete payment (minimum $1.00), deducted before the transfer and shown in the Portal's billing pages; from the October 17, 2026 terms, Stripe's processing fee is also deducted and the coach bears it, including on refunds; a full refund carries no platform fee, and a partial refund keeps it only on the part not refunded
- **Disputes**: the coach bears the disputed amount and the dispute fees Stripe keeps (taken back from the transfer and the coach's Stripe balance; what Saturday cannot take is recovered from the coach's next payments, never below zero); a won dispute is paid back less the dispute fee Stripe keeps; a disputed payment cannot be refunded
- **Trial grants**: for athletes whose accounts the coach created; per-tier yearly allocations (Coach 2, Pro Coach 4, Head Coach 8, Business 20, Enterprise 100) resetting on the subscription anniversary, or on the free tier on the anniversary of becoming a coach as Saturday recorded it (else of the first extension); a tier change keeps the year's count; one 14-day extension per athlete for life
- **Organizations**: every coach account has one; Head Coach tier and above can create sub-organizations; eight default member roles; an owner can offer ownership to an active member, who has 7 days to accept (the former owner stays as Head Coach); when the last owner deletes their account, another Owner takes over (for a sub-organization without one, the owner of the nearest organization above it that has one; never a deleted account), an organization nothing else uses is deleted, and any other is dissolved with the organizations under it (memberships end, org-paid coverage enters the 14-day grace, members keep their own athletes)
- **Closing a coach account** ends the Coach Terms: billing arrangements cancel, coaching links end, and athlete accounts the coach created that the athlete never opened and nobody else has are deleted
- **Impersonation is Saturday staff only**: staff may view a coach's Portal as the coach sees it, to fix problems and improve it, with a written justification and a 30-minute limit; each view is recorded internally with who viewed which account and when
- **Audit log** entries are deleted after 1 year (2 years for security entries); on Business and Enterprise, the organization's owners and program admins can view its entries in the Portal
- **Terms updates** are published in the Portal, which asks each coach to accept; a coach who has never accepted must accept before using the Portal

## Important Terms (Website / Commerce)

- Auto-renewal disclosure compliant with CA Auto-Renewal Law (CARL) and FTC's Click-to-Cancel rule
- Mandatory arbitration with class action waiver (JAMS, Phoenix AZ)
- 14-day right of withdrawal for EU/EEA consumers (Consumer Rights Directive)
- 14-day money-back guarantee on direct subscription purchases
- Force majeure, severability, and survival clauses included

## DPA / Sub-processors

For B2B customers using the Coach Portal at scale, a Data Processing Agreement template is available at `/legal/dpa`. It includes:

- **2021 EU Standard Contractual Clauses** (Module 2: Controller-to-Processor)
- **UK International Data Transfer Addendum 2022**
- Sub-processor list with 30-day change notification + 14-day objection window
- Encryption: TLS 1.3 in transit, AES-256 at rest (GCP default)
- 72-hour breach notification commitment
- Audit log retention (1 year, or 2 years for security entries; entries are never changed after they are written), billing record retention (at least 7 years after the transaction)
- Standard data subject rights assistance
- Term: as long as the coach has a Coach Portal account, on any tier including the free Coach tier; cancelling or downgrading a paid tier does not end it
- Scope: only the data the coach creates (notes about athletes, athlete accounts the coach creates until the athlete claims them, roster organization, billing arrangements); Saturday is the controller in its own right of athletes' accounts and app data, which the DPA does not cover
- Termination: the coach ends the agreement by deleting their Saturday account (Close account page in the Portal, or the app), which deletes the whole account. Within minutes Saturday deletes the coach's notes, personal groups, roster order and alert settings, and the athlete accounts the coach created that the athlete never signed in to, used, connected an app to, claimed or paid for and that nobody else still has, and cancels the coach's billing arrangements. Each organization the coach owned passes to another Owner if it has one (a sub-organization without one passes to the owner of the nearest organization above it that has one; never to a deleted account), is deleted if nothing else uses it, and is otherwise dissolved with the organizations under it and kept without its name, owner and domains. Billing records, audit entries, membership records (without the email address) and groups created in an organization that continues are kept. Every other athlete account is not deleted

## Saturday Does NOT

- Sell user data
- Serve advertisements
- Share data with advertisers or data brokers
- Use sensitive personal information for ads on other companies' sites or apps, or for profiling unrelated to the service (a few profile details reach Klaviyo to make Saturday's own emails relevant)
- Use AI for any purpose that produces legal-significant decisions about users
- Track users across other websites for advertising purposes

## Saturday DOES

- Honor Global Privacy Control (GPC) signals as opt-out
- Notify the supervisory authority of a data breach within 72 hours where the GDPR requires, and affected users without undue delay where a breach is likely to put them at high risk
- Maintain a complete sub-processor list available on request
- Maintain audit logs of admin actions for forensic purposes
- Honor data subject rights requests within 30 days (or 45 days for CPRA, 60 days for appeals)
