Data Policy
This page covers how partners may and may not use data returned by Saturday’s API. The rules exist to protect athletes and Saturday’s intellectual property.Data license
Saturday grants partners a limited license to use API response data. This license is communicated programmatically via theX-Saturday-Data-License response header on every API response.
Permitted uses
Partners may use API response data for:- Displaying prescriptions and safety metadata to end users (athletes)
- Storing response data temporarily to serve your application’s UX
- Caching prescriptions for performance (cache invalidation on profile update)
Prohibited uses
Partners may not use API response data for:- Training machine learning or AI models
- Fine-tuning language models or other generative AI systems
- Building competing nutrition prescription algorithms
- Aggregating response data across athletes for statistical analysis or resale
- Reverse engineering Saturday’s calculation algorithms
- Redistributing response data to third parties
- Creating derivative databases from product catalog data
Response headers
The license header is set before authentication runs, so it appears on rate-limit rejections and auth failures too. Match on the header’s presence rather than parsing its text, which may be reworded.
Attribution requirements
Teaser tier (required)
When displaying teaser/free response data, partners must show “Powered by Saturday” attribution:- Text: “Powered by Saturday” visible near nutrition data
- Link: Attribution must link to
saturday.fitor the subscriptionsubscribe_url - Mark: use the “Powered by Saturday” logo where it fits; appropriately sized plain text is a valid fallback
X-Saturday-Data-Attribution: required, and repeat the same terms in the response body’s attribution object.
Full tier (required, lighter)
When displaying full data for subscribed athletes, show a compact “Powered by Saturday” mark wherever Saturday data appears. Placement is yours; presence is not optional.Logo and brand assets
Approved attribution assets (the “Powered by Saturday” mark, light and dark, horizontal and stacked, plus paste-ready snippets) live athttps://saturday.fit/brand. Partners must not modify the Saturday mark or use Saturday’s brand in misleading contexts.
Full placement, sizing, and per-surface rules: Brand & Attribution.
Safety disclaimer
Partners must include a visible disclaimer in their application stating that nutrition prescriptions are guidance, not medical instructions. Saturday provides sports nutrition recommendations based on physiological models, which are not medical advice.Required disclaimer language
Partners must display, at minimum:Nutrition recommendations are personalized guidance based on physiological models. They are not a substitute for professional medical evaluation. Consult a healthcare provider for medical dietary needs.
Safety data handling
Partners must NOT:- Strip, hide, or downplay safety metadata from responses
- Remove safety warnings before displaying data to athletes
- Override or modify Saturday’s risk levels
- Present prescriptions without safety context
Athlete data and privacy
Data controller vs. processor
- Partners act as data controllers for their athletes’ personal data
- Saturday acts as a data processor on behalf of the partner
GDPR compliance
Saturday provides endpoints for GDPR compliance:
Partners are responsible for responding to athlete data subject requests within the timelines required by applicable law.
Data retention
Saturday retains athlete data only for as long as the partner account is active, plus a 30-day grace period after deletion. After termination:- Partner must delete all cached Saturday response data within 30 days
- Athletes’ data remains available for GDPR export for 30 days, then is deleted
Product database protection
Saturday’s curated product database (186+ endurance nutrition products) is competitive intellectual property. The following protections apply:- All product queries require an
athlete_id. There is no anonymous product browsing. - Per-athlete rate limits apply on product endpoints. Queries past the limit are served with a progressive delay rather than an error, so a legitimate burst still works and a crawl does not.
- No bulk export. Product listing endpoints are cursor-paginated with a maximum page size of 10.
- All product access is logged with partner_id, athlete_id, and the query.