App Privacy Policy

Saturday: Pro Fuel & Hydration App (by Saturday Inc.)
Effective October 24, 2026

Our Commitment to Your Privacy

Saturday Inc. ("Saturday," "we," "us," or "our") builds the Saturday: Pro Fuel & Hydration app to help athletes fuel and hydrate better. We collect personal data so we can improve the prescription of fuel and hydration recommendations to you as an individual user, and to understand which parts of Saturday work for whom. We also use what you enter and record in the app to train Saturday's shared models, except data from athletes under 18 and the health data of athletes Saturday's records do not place outside the EU or EEA, the UK, Switzerland, Washington, and Nevada, unless they say yes in the app (Activity-Platform Integration Disclosure, Section 6).

We do not sell your data. We do not serve ads. We do not share your data with advertisers. We exist to help you perform better, and your data stays in service of that goal.

This Privacy Policy explains what we collect, why we collect it, who processes it on our behalf, and what rights you have. If you also use our website (saturday.fit), please see our Website Privacy Policy. If you are a Washington State resident or the app processes your health data, please also see our Health Data Privacy Policy.

Data Controller

Data Controller: Saturday Inc.
8 The Green, STE A, Dover, DE 19901
Contact person: Alex Harrison
Contact email: support@saturdaymorning.fit

What We Collect and Why

We collect data to personalize your nutrition, fuel, and hydration recommendations. Here is what we collect.

Identity & Account Data

We collect your email address, any other email addresses you add to your account, display name, Firebase UID, and authentication method (Google Sign-In, Apple Sign-In, email and password, or a sign-in link we email you) so we can create and secure your account, communicate with you, and sync your data across devices.

Health & Biometric Data

We collect health and biometric data so we can calculate personalized fuel, hydration, and electrolyte recommendations tailored to your body and activity level. This includes:

Body data: weight, sex, year of birth
Sweat profile: sweat level, saltiness
Fueling profile: eating disorder flag, weight loss preference, fitness level, satiety, cravings, carb intake range, usual carb consumption
Fueling concerns: gut distress, cramps, faintness, heat tolerance, hunger, thirst, drinking resistance, performance concerns
Sport-specific: swim PR (used for intensity estimation)

Activity Data

We collect data about your athletic activities so we can provide real-time and post-activity fueling analysis. This includes: activity type, duration, intensity, thermal stress, nutrition consumed during activity, notes, ratings, and the symptoms and sleep you log with an activity.

Device & Technical Data

We collect app version, operating system version, crash data, and analytics events so we can fix bugs, monitor app stability, and improve the experience for all users. Our servers also log the IP address each request comes from (see Data Retention). To apply rules that differ by place, we also keep the country your app connects from (for a few US states whose rules differ, the state) and the country of your App Store or Google Play account. The app also reads your phone's region and time zone settings, without keeping them, to decide which consent questions to show you.

Store Country, How You Found Us, and Subscription Page Views

We record the country of your App Store or Google Play account; on Android, how you found Saturday (the source, medium and campaign named in the Google Play link that installed the app); and when you open the subscription page (the first and latest time, and how many times), so we can understand which parts of Saturday work for whom and in which countries. When we test versions of an offer, such as a free-trial extension, we also record which version you were given and when, so you keep getting the same one and we can compare the versions; we keep this for 425 days after the latest one, or until you delete your account. When a plan is canceled, we record when, and the reason the store reports: your answer to Google Play's cancellation survey and anything you typed in it, the reason and any comment Stripe records for a website plan, or the reason Apple gives for a plan ending, such as a cancellation or a billing problem. We do not use your health answers to choose the offers or in-app tips we show you, with one exception: we use your year of birth so that athletes under 18 get marketing emails and win-back offers only if they opt in, and do not get our cancellation or free-trial offers.

Security Log

We keep a security log of actions taken on Saturday accounts. Each entry records who acted, what they did, which account or record it affected, and when. Some entries also record what changed, which can include names and email addresses. The entries about your account include actions you take, such as signing in or returning to the app (which records that your device may switch back to your account), switching between accounts on your device, accepting or declining a coach's invitation, and removing a coach, and actions others take that concern you, such as a coach inviting you or changing your nutrition settings, or Saturday staff signing in as you on our coach website. Entries about the key that signs you back in on a new or restored phone record a code made from your IP address instead of the address, which lets us tell whether two of these actions came from the same address without keeping the address, and, when you set up or use the key, your phone model. Other entries for actions in the app record your IP address and the name and version of the software the app connects with. Entries for actions you take on our coach website record your IP address and your browser's description (its user agent). We use the log to protect accounts and to investigate security incidents and disputes.

Location Data

When you record an activity, your device's location is used to fetch local weather (temperature, humidity, wind) so we can tailor your sweat-rate and hydration calculations to the conditions you actually trained in. The app sends an approximate location, rounded to roughly a one-kilometer area, to OpenWeatherMap for that lookup and to your phone's built-in place lookup (Apple's on iPhone, Google's on Android) to find your city or region; older versions of the app send both your device's precise coordinates. Your device's precise coordinates are not stored with your activity. When you email us from the app's support option, the email the app drafts also includes your device's location, rounded to about 1 km (older versions of the app include your precise coordinates); you can delete it before you send. We do save an approximate location with each activity, your city or region and coordinates rounded to roughly a one-kilometer area, so your weather-based fueling keeps getting more accurate for you over time. It is never sold or shared with advertisers, and it is deleted whenever you delete the activity or your account.

If you connect TrainingPeaks, COROS, Polar, Suunto, Wahoo or Ride with GPS, we also keep a copy of the workout data the platform sends us. When your device recorded GPS during a workout, that copy includes your route, at the precision the platform sends, which depends on your device and its settings. For workouts from COROS, Polar, Suunto, Wahoo and Ride with GPS, we also save the exact starting point (the first location your device recorded) with the activity. We keep the routes you saved in Ride with GPS too, each with its track (see Third-Party Sync Data). Our Activity-Platform Integration Disclosure describes how long we keep this data and what disconnecting a platform does. We keep no exact location from intervals.icu. If you are under 18, we remove your route and exact starting point from the workout data we keep, and save only a starting point rounded to about 1 km; saved routes keep their tracks.

Third-Party Sync Data

If you connect a third-party platform, we receive data from that service to provide integrated fueling recommendations:

TrainingPeaks: profile data (name, email, weight, sex, birth month, time zone, preferred units, whether your account is Premium, and your TrainingPeaks coach's ID if you have a coach) and planned and completed workout data (user-initiated OAuth connection)
Intervals.icu: planned and completed workouts with their data streams, and wellness data (heart rate variability, resting and sleeping heart rate, sleep, readiness, VO2 max, weight) (user-initiated OAuth connection)
COROS: completed workouts from the past 3 months and every new one (sport, start and end time, duration, distance, pace, cadence, steps, calories, and the watch that recorded them), the workout file behind each one (heart rate, power, cadence, elevation, temperature, and GPS route), and daily recovery data (resting heart rate, heart rate variability, sleep start and end times, sleep heart rate, steps, and calories) (user-initiated OAuth connection)
Polar: completed exercises with their samples and GPS route, Nightly Recharge recovery (including heart rate variability), sleep (stages and score), and your Polar physical profile (weight, height, maximum and resting heart rate, heart rate thresholds, and VO2 max) (user-initiated OAuth connection)
Suunto: completed workouts and the workout file behind each one (including GPS route and ambient temperature), and the daily sleep and recovery summaries Suunto sends (sleep duration and stages, sleep heart rate, heart rate variability, sleep quality, recovery balance, and stress state) (user-initiated OAuth connection)
Wahoo: completed workouts with their summaries and the workout file behind each one (power, heart rate, cadence, speed, temperature, and GPS route where recorded) (user-initiated OAuth connection)
Ride with GPS: rides from the past 3 months and every new or edited ride (name and description, sport, start time, duration, distance, speed, elevation, heart rate, power, cadence, temperature, calories, the device that recorded it, gear, photo details, and the town, region, and country) with the GPS track behind each one, and your saved routes: the 50 most recently updated when you connect, then every new or edited one (name, sport, distance, elevation gain and loss, the route's track with elevation, surface, and road type, its unpaved share, town, region, and country, and the aid, water, and food stops marked on it) (user-initiated OAuth connection)

Any activity platform you connect is covered in full by the Activity-Platform Integration Disclosure, which lists each platform, what we read, what we write back, and what disconnecting does.

Product Scans

When you scan a product barcode or photograph a nutrition label, we keep the barcode, the photo, and the nutrition details read from it in our product database, so we can build and check the product information every athlete sees. For up to 90 days, a scan can also carry your account ID and email address, and its photo's file name your account ID; after that, they name you only by a random code, which a separate record links to your account. Within 24 hours of your deleting your account, we delete your label photos, remove your account ID, email address and that code from your scans, and delete the record that links the code to you; the barcodes and nutrition details stay, with nothing linking them to you.

Invitations From Other Athletes

If you join through another athlete's invite link, we record whose invite it was, so we can reward them when you subscribe. To carry the invite through the app store, on Android the app reads the invite code from the Google Play link that installed it, and on iPhone it checks your clipboard once, when you first open the app, for an invite code our invite page put there, and removes it.

Coaches You Share With

If you share your account with a coach, that coach can see your profile, your activities, and the reports and plans built from them for as long as you share, and, with the permissions you give, create and edit your activities and change your nutrition settings. Our Coach Privacy Policy describes what coaches can see.

Partner Platforms (Saturday API)

Some coaching and training platforms integrate Saturday's nutrition engine through our API. If you use one of these platforms and the email on your Saturday account matches the email the platform has on file for you, we may link the two records so your existing Saturday subscription unlocks full-precision data inside that platform too — you never pay twice for the same thing. The only information the platform learns from this link is your subscription tier (whether full precision is unlocked) — never your payment details, purchase history, or Saturday profile data. Matching uses exact email equality only, anything ambiguous is reviewed by a human before any link is made, and the unlock ends automatically when your subscription lapses. Once your accounts are linked, the fueling-profile details you have already saved in Saturday (such as your weight, sweat profile, and fueling preferences) may be used at calculation time to fill in any answers the partner platform is missing, so your numbers there are as accurate as in Saturday — those stored values are used only to compute your fueling and are never shown to the partner unless you turn on the "share my fueling profile" option.

Coaching

If you connect with a coach on Saturday, we keep a record of each coaching relationship: which coaches can see your data, your name and email address and the coach's, the access you gave the coach, whether the coach is your primary coach, and how and when the relationship began and ended. A coach can also write notes about you, which you cannot see, and can share a note with the other coaches who can see your data. Your coach, not Saturday, is the controller of these notes, and we store them for your coach. Our Coach Privacy Policy describes what coaches can see and do.

What We Do NOT Collect

For clarity and transparency:

We do not collect or store credit card numbers (payments are handled entirely by Apple, Google, or Stripe)
We do not use your device to record where you go: we use its location only as described in Location Data above. The exact locations we keep come from workouts a platform you connect sends us, and from support emails sent from older versions of the app, which include your device's precise coordinates
We do not sell data to any third party
We do not share data with advertisers
We do not serve ads of any kind

Third-Party Services

We use the following third-party services to operate and improve the app. Each service receives only the data it needs to perform its function.

Firebase / Google Cloud (Google LLC)

Firebase Authentication: manages your sign-in credentials and account security
Cloud Firestore: stores your profile, activities, and preferences
Firebase Analytics: records how the app is used, as usage events linked to your account ID rather than your name or email address, so we can understand how people use the app and what to improve; Firebase also estimates the country and region of each session from its IP address. On Android, Firebase also collects your phone's advertising ID unless you turned off ads personalization in your phone's settings
Firebase Crashlytics: collects crash reports so we can identify and fix bugs quickly
Firebase Performance Monitoring: measures app speed and responsiveness

Klaviyo (Klaviyo, Inc.)

We use Klaviyo for email communications including onboarding, tips, offers, and product updates. Klaviyo receives your name, email address, and account ID; from your profile, your sex, age group by decade (worked out from your year of birth), sports, fitness level, seriousness, sweat level and saltiness, and a sample hourly fueling target (fluid, sodium, and carbohydrate); and whether you have finished onboarding, your email marketing choice, when you logged your first workout, your free-trial and subscription status and dates, your purchases (plan, price, store, payment references, the offer you redeemed, and the campaign link or partner that brought you), failed payments and cancellations, the offers we send you, your app language, and, if a coach stops paying for your subscription, the coach's name and the date your access ends, so we can send relevant, personalized messages. Klaviyo also records when you open our emails and which links you click. When you buy a gift, or a coach or another athlete invites you, Klaviyo also receives what that email needs, such as the names and email addresses involved and any gift message.

We add your account to our email lists only after you confirm your email address: signing in with Google or Apple at that address confirms it, and for an email and password account we email you a confirmation link. If you are under 18, judged by the age you enter in the app or the age range the App Store or Google Play reports, you get marketing emails only if you tick the box in the app; if we know neither within an hour after you create your account, we treat you as an adult until we do. If your App Store or Google Play country, or your phone's region or time zone, points to the European Economic Area, the United Kingdom, or Switzerland, the app asks too, and you get marketing emails only if you tick the box; leaving it unticked is a no. If the place you connect from points there, we also do not subscribe you without a yes. Older versions of the app ask only when you create your account with a Sign up option on a phone set to a region there, and with them we do not subscribe you without a yes if our records place you in one of these countries. If a coach created your account, you get them only if you opt in yourself. Otherwise, once your address is confirmed and you open the app, we subscribe you, unless you unsubscribed from our emails at that address earlier. The boxes start unticked, and you can unsubscribe at any time.

Brevo (Sendinblue Inc.)

Brevo delivers our account and service emails, such as sign-in links, password resets, email address confirmations, receipts, and notices about your subscription, and the emails the Coach Portal sends, such as the email that lets you take over an account a coach created for you and, if you are on a coach's roster, alerts to your coach about your sessions. After a consultation with us, Brevo also delivers our follow-up offer, which we send only if you get our marketing emails. Brevo receives each recipient's name and email address and the content of the email, records when an email is opened and which links are clicked, with the IP address they came from, and its terms let it also use this data to produce statistics for itself.

Cloudflare (Cloudflare, Inc.)

Cloudflare carries some of the app's requests to our servers, such as connecting and disconnecting apps like TrainingPeaks and your choices about AI features, runs our invite and download links, and protects our community forum from attacks. It processes each request's IP address, headers and contents to deliver it.

Community forum (forum.saturday.fit)

Our community forum runs Discourse, open-source forum software, on our Google Cloud servers. When you open the forum from Saturday, you sign in with your Saturday account, and the forum receives your account ID, email address, display name, a username made from your email address, your profile photo if you have one, and your subscription type. What you post there is visible to other members.

Stripe (Stripe, LLC)

Stripe processes payments for web-based purchases. We send Stripe your email address to create a checkout session. Stripe handles all credit card data directly — we never see or store your card number.

Apple App Store & Google Play Store

In-app subscriptions are managed entirely by Apple and Google. We receive purchase confirmation receipts but do not have access to your payment method details.

Google / Apple Sign-In

If you choose to sign in with Google or Apple, the authentication provider shares your name and email with us to create your account. Apple Sign-In allows you to hide your email address.

TrainingPeaks (Peaksware, LLC)

If you choose to connect TrainingPeaks, we read your planned and completed workouts and profile information so you can see fueling recommendations alongside your training plan, and we post your fuel plan back as a comment on your workout only when you send it or turn on auto-send. This connection is user-initiated via OAuth and can be disconnected at any time. If you allow it in the app, we also learn from your completed TrainingPeaks workouts and what you log about them to improve our predictions (see the Activity-Platform Integration Disclosure).

Intervals.icu

If you choose to connect Intervals.icu, we read your planned and completed workouts, their data streams, and wellness data. We post your fuel plan back as a comment on your completed activity only when you send it or turn on auto-send. For a planned workout, the app also sets the planned carbohydrates per hour on its calendar entry to your plan's figure when the entry has no figure or still has the one Saturday set, and replaces a figure you or your coach entered only if you tell it to. This connection is user-initiated via OAuth and can be disconnected at any time.

OpenWeatherMap (OpenWeather Ltd)

At the time of an activity, we send OpenWeatherMap your location rounded to about 1 km (older versions of the app send your device's precise GPS coordinates) to retrieve temperature, humidity, and weather conditions for sweat rate calculations. We do not keep the coordinates we send; from this lookup, we keep only an approximate (~1 km) location with your activity to improve your weather-based fueling over time.

Open Food Facts

When you scan a product barcode, we query the Open Food Facts database to look up nutrition information. Open Food Facts receives the barcode only.

Google Gemini on Vertex AI (Google LLC)

We use Google's Gemini models, through Google Cloud Vertex AI, for the features below. Google processes this data for us as our processor under its cloud data-processing terms and does not use it to train its models.

Nutrition label photos: when you photograph a nutrition label, we send the photo to Gemini to read the product's nutrition information, so you can log it quickly. With it we send at most your country, from your phone's region setting or your App Store or Google Play account, to help Gemini read the label; your name, email address, and account ID are not sent. We keep the photo in our product database (see Product Scans).
TrainingPeaks workouts: when the type and keywords of a connected TrainingPeaks workout do not tell us what kind of session it is, or how hard a strength session is, we send Gemini its title, description, pre-activity comment, tags, TSS calculation method, number of structured steps, whether it has power data, and, for strength and cross-training sessions, its workout type, so it can identify the session. Your name, email address, and account ID are not sent.
Saturday AI: when you use Saturday AI, the in-app assistant, we send Gemini your messages, the notes you wrote on your activities, and, as it needs them, your profile and weight, activities, symptoms, sleep, and fueling plans. When a coach you share your account with asks Saturday AI about you in the app, we send Gemini the coach's messages and, as it needs them, the same details about you that the coach can see.
Coach reports: if you are on a coach's roster and your coach requests an AI-written fueling report or 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, sleep hours, and symptoms you reported. A roster summary also includes the name of each athlete who needs attention (or their email address when no name is set) and the reason.

Saturday AI works only if you allow AI features when the app asks. If you say no, we send none of this to Gemini. These features are only for athletes 18 and older. When you rate one of Saturday AI's answers, that chat may help train Saturday's assistant, but only if every connected source it draws on may be used for training (see the Activity-Platform Integration Disclosure). 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.

Training large language models: we collect the Saturday AI chats you rate so they can help train the language model behind Saturday AI, as described above. We use no other personal data to train large language models, and we do not sell personal data for that purpose.

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 session summaries for coach reports to Gemini unless you give your permission in the app. We work this out from the country (for Connecticut, the state) your app connects from and the country of your App Store or Google Play account. This does not apply to label photos.

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 International Data Transfers).

Legal Basis for Processing (GDPR)

We process your personal data under the following legal bases:

Contract performance: Processing your account, activity, and health data is necessary to provide the fueling and hydration service you signed up for.
Consent: Health/biometric data processing is based on the consent you give when you create your account, which you can withdraw at any time by deleting your account. Where the app asks whether you want marketing emails (see Klaviyo above), we send them only if you tick the box, based on that consent, which you can withdraw at any time by unsubscribing.
Legitimate interest: Analytics, crash reporting, and performance monitoring help us maintain and improve the service for all users. The security log helps us protect accounts and investigate security incidents and disputes. Where we subscribe you to marketing emails without asking (see Klaviyo above), we send them on this basis, and you can unsubscribe at any time.
Legal obligation: We retain purchase records as required by tax and accounting law.

Automated Decision-Making

The app uses algorithms to generate personalized nutrition, fuel, and hydration recommendations based on your profile data, activity data, and environmental conditions. These recommendations are the core purpose of the service. They are not used to make decisions that produce legal effects or similarly significant effects on you. You can always override or ignore any recommendation, and you can contact us if you have questions about how your recommendations are calculated.

We also use a model, trained on past free trials of athletes 18 and older, that estimates from the first five days of your free trial (how you signed in, the units you chose, your answer to how much you enjoy chemistry, when you created your account and when your trial started, and the fueling plans you built) how likely you are to subscribe. We make the estimate only to choose who gets a personal note from us during the free trial and to measure which changes to the trial help. It does not change your recommendations, your price, or what you can use in the app.

Data Retention

We keep your data for the periods below. Where a period runs until you delete your account, our deletion process removes the data within minutes of the deletion, and a daily check removes anything it missed.

Account & profile data: kept while you have an account; deleted within 24 hours of your deleting your account
Activity data: kept while you have an account. When you delete an activity, or your account, we delete the activity, including our analytics copies, within 24 hours, and the original file a platform sent us for it within 32 days. Data from a connected platform follows the Activity-Platform Integration Disclosure.
Ride with GPS training record: our record of whether your Ride with GPS rides may help train our models: the result of any check of where your connection comes from (the country and US state, whether your App Store or Google Play account is a US one, what kind of network you connected over, and the reasons for any exclusion; never your IP address), the connection from which your rides may train or the reconnection that stopped it, and any request you made to leave your rides out. Kept while you have an account, including after you disconnect Ride with GPS, and deleted with it.
Coaching relationship records: while both your account and the coach's account exist, including after the relationship ends. If you connect with the same coach again, the new record replaces the old one. They are deleted when either account is deleted
Notes a coach wrote about you: until the coach's account is deleted. They are not deleted when the relationship ends or when you delete your account (see Account Deletion below)
Purchase records (what you bought, when, the price, the store's transaction reference, your account ID and, for a canceled plan, when and why it was canceled): at least 7 years after the purchase, for tax and accounting. No deletion is scheduled after that. When you delete your account, we remove your email address and anything you typed when canceling from them
Error logs & crash data: our error logs keep your account ID for 90 days. After that we keep only their technical details: the type of error, the stack trace showing where in the app it happened, the app and operating system versions, the date and hour, and the rest of the error message reduced to short codes and words from a fixed list of standard error wording. Your account ID, email addresses, other identifiers and every word outside the stack trace that is not on that list, such as a name or something you typed, are removed, and we do not attempt to link what remains to anyone. We also keep a daily count of each kind of error, labelled with its message reduced the same way. Google keeps the crash reports Firebase Crashlytics collects for 90 days, then starts deleting them.
Server logs: 30 days. They can include your account ID, your email address and your IP address.
Security log: each entry is deleted within a day after it is 1 year old, and security entries within a day after they are 2 years old. Security entries cover Saturday staff signing in as you, privacy requests made on our coach website, API keys, signing sessions out, two-step verification, single sign-on, roles and permissions, transfers of a coaching organization's ownership, and device access (the records made when you sign in or return to the app, which let your device switch back to your account, and switching between accounts). Deleting your account does not delete these entries; they are deleted on this schedule
Usage analytics (Google Analytics for Firebase, linked to your account ID): Google keeps user-level data for 14 months after your last activity in the app and event-level data for 2 months. We keep our copy of these events in Google BigQuery until you delete your account. When you delete it, we ask Google to delete your usage analytics, which Google completes within about two months, and within 4 days we delete from our copy the events recorded under your account and those from app installations only your account used
Free-trial record: when you delete your account, we keep a one-way code made from your email address, not the address itself, together with the date your free trial ended and the date you deleted your account, for 3 years (2 years if you deleted your account from an older version of the app). We cannot read your email address from the code; we use it only to check whether a new account uses the same address, so a free trial is used once. Nothing else about you is kept in it. Older versions of the app send us the address itself when you delete your account; we replace it with the code and delete the address within 24 hours.
Product scans: barcodes, nutrition-label photos, and the details read from them stay in our product database. Your account ID and email address stay with a scan for at most 90 days, after which the scan names you only by a random code (see Product Scans). Within 24 hours of your deleting your account, we delete your photos, remove your account ID, email address and that code from your scans, and delete the record that links the code to you; the barcodes and nutrition details stay, with nothing linking them to you.
Email provider record: your profile at Klaviyo (the details listed above). Within 24 hours of your deleting your account, we ask Klaviyo to delete it, unless another Saturday account that signs in with the same email address uses it by then, or you subscribed to our emails other than through the app and are still subscribed (see Account Deletion). Klaviyo keeps a record of the email address of each profile it deletes.
Email delivery records: Brevo keeps a record of each email it delivers for us: the recipient's address, the subject, the sender, delivery events and a copy of the email. We keep these while you have an account. Within 24 hours of your deleting your account, we ask Brevo to delete its records of emails sent to your account's confirmed email addresses, unless another Saturday account uses the address; Brevo completes this within 3 days.
Community forum account: kept while you have an account. Within 24 hours of your deleting your account, we anonymize it (see Account Deletion).
Disaster-recovery 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 (purchase records are kept as above). We use the backups only to restore service after a failure and to carry out deletions, such as removing a platform's data from them. When we restore from one, we first list the account deletions, platform disconnections and activity deletions made since it was taken, and apply them again after the restore.

When a period above ends, we delete the data from our live systems. Copies in our database backups are deleted within 84 days after that, and copies in our data warehouse within 100 days. After deletion, rights of access, erasure, rectification, and data portability cannot be exercised for data that no longer exists.

Account Deletion

You can permanently delete your account in the app: Menu > My Profile > "Permanently Delete Your Account." You confirm three times and sign in again before anything is deleted.

When you delete your account, we delete, within 24 hours:

Your user profile and all preferences
All activity data, including the data from every platform you connected, and every platform connection
Your coaching relationship records, including ended ones
Your Firebase Authentication account
Your profile at our email provider, Klaviyo (we ask Klaviyo to delete it, unless another Saturday account that signs in with the same email address uses it, or you subscribed to our emails other than through the app and are still subscribed)
Your app usage analytics: we ask Google to delete them, which Google completes within about two months, and we delete our copy in our analytics warehouse within 4 days
Brevo's records of the emails we sent to your account's confirmed email addresses (we ask Brevo to delete them, which it completes within 3 days)
Your identity on the community forum: we anonymize your forum account, replacing your username, name, email address, profile and recorded IP addresses. Your posts stay visible under an anonymous name; delete them in the forum first if you do not want them kept.
Your label photos, and your account ID and email address on your product scans
Our error logs that carry your account ID

If you subscribed to our emails other than through the app and are still subscribed, deleting your account does not unsubscribe you: we remove your name, your account ID and the app details listed above from your Klaviyo profile and keep your email address and your subscription, which you can end at any time by unsubscribing. Klaviyo offers no way to delete a profile's past events, so the profile keeps the record of the emails we sent you and of past app events, such as your first workout or a purchase, some of which carry your account ID.

An error log from a failed sign-in records the email address that was typed, not an account ID. We delete those that contain one of your account's confirmed email addresses along with your account; in any others, the email address is removed by the time the log is 90 days old.

We keep the following after deletion, for the periods in Data Retention above: purchase records without your email address or anything you typed when canceling (at least 7 years, legal requirement), the free-trial record (a one-way code made from your email address, not the address itself, your free-trial end date and the date you deleted your account, for 3 years, or 2 years if you deleted your account from an older version of the app, to prevent repeat free trials), error logs whose account ID had already been removed, which hold only their technical details and nothing linking them to you, crash reports in Firebase Crashlytics (Google keeps them for 90 days, then starts deleting them; a report from some versions of the app can include your account ID or a code made from it), server logs (30 days), security log entries (1 year, or 2 years for security entries), the record of any privacy request you made to us (2 years), app usage analytics at Google until Google completes their deletion (about two months), product scans with nothing linking them to you, your forum posts under an anonymous name, notes a coach wrote about you, a record of the deletion under your account ID saying when it was requested and what each step removed (no deletion date), Klaviyo's record that it deleted your profile, which keeps your email address, and copies in backups (up to 84 days) and in our analytics warehouse (up to 100 days).

We also end any subscription you bought on our website, remove your name, email address, phone number, addresses and saved cards from your Stripe customer record (Stripe keeps the payment records), and withdraw Saturday's access to your connected platforms. Subscriptions bought through Apple or Google are billed by them: cancel them in your App Store or Google Play settings. Workouts and fueling plans Saturday added to a connected platform stay in your account there until you delete them.

Notes a coach wrote about you stay with the coach who wrote them. When you delete your account, we remove your account ID from the notes and mark them with a code instead, and the coach then sees them under an anonymous athlete. From then on, only the coach who wrote them can read them. We do not edit what the coach wrote, so a note may still mention you by name.

International Data Transfers

Saturday Inc. is based in the United States. If you use Saturday from outside the United States, you give your data directly to us there, and we store it on Google Cloud servers in the United States. Google, Klaviyo, Brevo, Stripe and Cloudflare process data for us under data processing terms that require them to keep it secure and limit how they may use it. Google LLC, which hosts our systems and runs the AI features described above, Klaviyo (email), Stripe (payments) and Cloudflare (network) 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. The AI requests described above go from our servers in the United States to Google, which may process them in its data centers in any country. Google's certification under these frameworks covers those onward transfers, and Google's Cloud Data Processing Addendum requires Google to protect the data wherever it processes it. You can ask for a copy of these safeguards at support@saturdaymorning.fit.

Consultations you book with us on our website are a separate service from the app. Deleting your app account does not delete your consultation bookings, their calendar events or their notes; the Website Privacy Policy says how long we keep them.

Children's Privacy

The Saturday app is not intended for use by anyone under the age of 14. We do not knowingly collect personal data from children under 14. In some European countries the law sets an older age for using an online service without a parent's consent: 15 in Czechia, Denmark, France (including its overseas regions), Greece and Slovenia, and 16 in Croatia, Germany, Hungary, Ireland, Liechtenstein, Luxembourg, the Netherlands, Poland, Romania and Slovakia. If your App Store or Google Play account is in one of these countries and you give an age under it, the app shows a notice that Saturday is for athletes of that age and up, and signs you out. If you are under 14, please do not use the app or provide any personal information. If the App Store or Google Play tells the app that you are under 13, the app shows only a notice that Saturday is for athletes 14 and up (older in the countries above), and signs you out. If a parent or guardian tells us at support@saturdaymorning.fit that their child under 14 has given us data, we delete the child's account and data.

Data Security

We implement appropriate technical and organizational security measures to protect your data, including encryption in transit (TLS) and at rest, Firebase security rules that limit who can read your data, and access controls limiting staff access to personal data. No system is perfectly secure, but we take reasonable steps to protect your information.

Data Breach Notification

If a data breach affects your personal 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, or within the time applicable state law requires.

Your Rights

Depending on where you live, you may have some or all of the following rights regarding your personal data:

Access: Request a copy of the personal data we hold about you.
Correction: Request that inaccurate data be corrected.
Deletion: Request that we delete your personal data (subject to legal retention requirements).
Portability: Receive your data in a structured, commonly used, machine-readable format.
Restrict processing: Request that we limit how we use your data.
Object to processing: Object to processing based on legitimate interests or for direct marketing.
Withdraw consent: Where processing is based on consent, withdraw it at any time.
Lodge a complaint: File a complaint with your local data protection authority.

To exercise any of these rights, email support@saturdaymorning.fit. We will respond within 30 days (or sooner if required by applicable law). These requests are free of charge.

Appeal Process

If we deny a privacy rights request, we will explain why. You may appeal the decision by emailing support@saturdaymorning.fit with "Appeal" in the subject line. We will respond to appeals within 60 days. If you are not satisfied with the outcome, you may contact your state attorney general or relevant data protection authority.

Information for California Residents (CPRA)

This section applies to California residents under the California Consumer Privacy Act as amended by the California Privacy Rights Act ("CPRA"). These provisions supplement the rest of this privacy policy.

Categories of Personal Information Collected

Identifiers: name, email address, Firebase UID, IP address, and on Android the advertising ID Firebase collects
Sensitive personal information: health data (weight, sex, biometric indicators used for fueling recommendations)
Internet or electronic network activity: app usage data, analytics events, crash reports, security log entries
Geolocation data: approximate location (~1 km, stored with activities for weather-based fueling); routes and exact starting points in workouts from platforms you connect (see Location Data); your device's location, rounded to about 1 km (precise in older versions of the app), is sent for the weather lookup and is not stored with your activity
Inferences: fueling recommendations derived from your profile and activity data, and an estimate of how likely you are to subscribe after your free trial (see Automated Decision-Making)

How We Use Sensitive Personal Information

We use sensitive personal information (health and biometric data) to provide and improve the fueling and hydration service you requested, including training the models behind its recommendations, and to tailor the product emails we send you (see Klaviyo above). We do not use sensitive personal information for advertising or for profiling unrelated to the service.

Sale and Sharing

We do not sell your personal information. We do not share your personal information with third parties for cross-context behavioral advertising. We have not sold or shared personal information in the preceding 12 months.

Your California Privacy Rights

Right to know: what personal information we collect, use, disclose, and sell
Right to delete: request deletion of personal information
Right to correct: request correction of inaccurate personal information
Right to limit sensitive personal information: direct us to limit the use of sensitive personal information to what is necessary for the service
Right to opt out of sale/sharing: we do not sell or share, but you may exercise this right at any time
Right to non-discrimination: we will not discriminate against you for exercising these rights

To exercise these rights, email support@saturdaymorning.fit. We will confirm receipt within 10 business days and respond within 45 days, with a possible extension to 90 days if necessary.

Global Privacy Control

We recognize and honor the Global Privacy Control (GPC) signal. If your browser or device sends a GPC signal, we will treat it as a valid opt-out request for the sale or sharing of personal information.

Information for Residents of Other US States

Residents of Colorado, Connecticut, Virginia, Texas, Oregon, Montana, Iowa, Indiana, Tennessee, Florida, Minnesota, New Jersey, Delaware, Maryland, New Hampshire, Rhode Island, and other states with comprehensive privacy laws have rights similar to those described above, including the rights to access, correct, delete, and port your data, and to opt out of the sale of personal information, targeted advertising, and profiling. To exercise these rights, email support@saturdaymorning.fit.

If we deny your request, you have the right to appeal. See the Appeal Process section above.

Additional Disclosures for Nevada Residents

Nevada law (NRS 603A.340) provides consumers the right to opt out of the sale of personal information. We do not sell your personal information. If you wish to submit an opt-out request, contact support@saturdaymorning.fit.

Additional Disclosures for European Data Subjects (GDPR)

If you are in the European Economic Area, the United Kingdom, or Switzerland, you have the rights described in the Your Rights section above. Additionally:

You have the right to lodge a complaint with your local supervisory authority.
Transfers of your data to the US are described in International Data Transfers above.
We will respond to rights requests within 30 days.

Global Privacy Control & Do Not Track

We recognize and honor the Global Privacy Control (GPC) signal as a valid opt-out preference. If your browser sends a GPC signal, we treat it as an opt-out of the sale or sharing of personal information.

Regarding the older "Do Not Track" (DNT) browser signal: there is no industry-wide consensus on how to respond to DNT. We do not currently alter our data practices in response to DNT signals, but we do honor GPC as described above.

Health Data Privacy

The Saturday app processes health-related data to provide its core fueling and hydration recommendation service. For residents of Washington State and other jurisdictions with specific health data privacy requirements, please see our standalone Health Data Privacy Policy for additional disclosures under the My Health My Data Act (MHMDA) and similar laws.

Changes to This Privacy Policy

We may update this policy from time to time. When we do, we will update the effective date at the top of this page. For material changes, we will notify you via email or an in-app notice before the changes take effect. Your continued use of the app after changes constitutes acceptance, but we will seek new consent where required by law.

Definitions

Personal Data: Any information that directly or indirectly identifies or could identify a natural person.
Usage Data: Information collected automatically through the app, including device type, operating system, app version, analytics events, and crash data.
User: The individual using the app.
Data Controller: Saturday Inc., which determines the purposes and means of processing personal data.
Data Processor: A third party that processes personal data on behalf of the Data Controller (e.g., Firebase, Klaviyo, Brevo, Stripe). Brevo may also use this data as a controller to produce statistics for itself, and Stripe acts as a controller for some payment data, for example to prevent fraud and meet its legal duties.
Health Data: Data related to your physical health, body measurements, or biometric indicators, collected to provide the fueling and hydration service.