Skip to main content

Brand & Attribution

Building with Saturday is welcome, and we want athletes to know when Saturday’s nutrition intelligence is behind what they see. Attribution is how that works. It credits the engine doing the fueling math, keeps the athlete’s picture honest about where the numbers come from, and gives every partner surface a path back to Saturday for athletes who want full precision. This page is the single source for what to display, where, and how. The one-line requirement also lives in the API terms; the pixels live here so they can improve without reopening an agreement.

When attribution is required

Saturday’s freemium model sets the line. See Freemium Model for how teaser and full responses differ.
Safety metadata is never gated and never stripped. Whatever tier you show, the safety fields ship with it. Attribution rules govern the brand mark, not the safety data.

What to display

Refer to Saturday one of two ways, and no other:
  • “Powered by Saturday” wherever Saturday nutrition data appears.
  • “Compatible with Saturday” when you describe interoperability in prose without rendering data.
Two rules on the words:
  • Link the mark to https://saturday.fit (or to the subscribe_url from a teaser response, so the athlete lands on their own upgrade path). A linked mark is how a curious athlete finds full precision, and it is what Saturday gets in exchange for the nutrition intelligence you get free.
  • Plain text is a valid fallback. Where a logo will not fit, appropriately sized text reading “Powered by Saturday” satisfies the requirement.
Do not put “Saturday” in your product’s name, and do not imply Saturday developed, sponsored, or endorsed your app. Truthful, factual references to Saturday in your feature descriptions are fine.

Where it goes

Attribution sits with the data it credits, visible without interaction.
  • Place it directly beside or beneath the nutrition figures, above the fold, visually tied to the numbers it supports.
  • Never bury it in a tooltip, footnote, settings screen, “info” modal, or a collapsed or expandable panel. If the athlete can see Saturday’s numbers, they can see the mark without tapping anything.
  • For a list or feed of many entries, you may attribute once in a section header or footer, or once per entry. Either is fine as long as the mark travels with the data.
Scope it by surface: When your integration also relays a third party’s data alongside Saturday’s (for example a wearable’s device data), honor that source’s attribution too. Name the origin, not only the vendor.

How it should look

Saturday provides the “Powered by Saturday” mark stacked and horizontal, each in two variants, as a drop-in asset. Stacked is the primary form; use horizontal where vertical space is limited. Use the asset as shipped. The variant is named for the background it sits on, not for the artwork inside it. The -light files carry dark artwork for a light background, and the -dark files carry light artwork for a dark background. Choose from the background directly behind the mark, not from the viewer’s device theme.
Powered by Saturday
  • Minimum size: stacked, 32px tall on screen (40px or larger recommended), 12mm in print; horizontal, 16px tall on screen (20px or larger recommended), 6mm in print. Below that, use the plain-text form.
  • Clear space: keep open space around the mark equal to at least half the mark’s own height on every side. This scales with the mark, so there is one rule at every size.
  • Contrast: keep the mark legible against whatever sits behind it, using the variant rule above.
  • Do not recolor, restretch, rotate, animate, add effects to, or rebuild the mark, and do not use it, or any part of it, as your app icon or avatar. Preserve the original aspect ratio.
  • Keep your brand dominant. The Saturday mark appears near your own name, stays separate from it, and is never larger or more prominent than your own branding.
Do not rename or rebrand Saturday’s fueling terms and metrics. Call them what Saturday calls them so athletes carry one vocabulary across every app they use.

App icon for integration tiles

When your surface lists Saturday as an app or integration (an app directory, an integrations list, a connected-services tile), use the Saturday app icon rather than the attribution marks. The brand kit ships it at eight sizes, 24px through 1024px, in two shapes. Prefer the squircle files, pre-masked to the iOS-style continuous-corner shape: use that shape unless your platform already applies its own icon mask or your design system has a strong style reason for another one. The full-bleed square files exist for platforms that mask icons themselves. Use 48px or larger where the surface allows (24px is the floor), and do not recolor, crop, re-mask, or add effects. The icon identifies the Saturday app; the marks credit Saturday data. Both can appear on one screen doing different jobs.

Data license

Attribution rides alongside the data-use terms every response already carries in its X-Saturday-Data-License header, with X-Saturday-Data-Attribution added on teaser responses. Saturday’s prescriptions, product database, and knowledge base are proprietary: no training or fine-tuning of models on response data, no reverse-engineering the calculations, no reselling or building a derived database. Full terms: Data Policy.

If your use is commercial

Putting Saturday in front of other people commercially (a platform, an app in a store, a coaching business charging clients, anything that resells or bundles Saturday output) gets a brand review before launch. Send mockups or screenshots of the surfaces that show Saturday data to api@saturday.fit and we confirm the attribution reads well. The review applies to each new display surface, not to every build. Personal, single-account use skips this.

Example

Brand assets

Saturday brand kit

The “Powered by Saturday” and “Compatible with Saturday” marks (light and dark, stacked and horizontal, SVG and PNG) plus ready-to-paste HTML and Flutter snippets. Download the kit at saturday.fit/brand, or email api@saturday.fit and we will send it.

Reviews and changes

Saturday may review an integration for attribution compliance and ask for changes. Reach api@saturday.fit any time and we will help you get it right. Unresolved noncompliance may lead to suspension or termination of API access. Saturday may update these guidelines; the current version here governs.