Storage atlas

Plain-language companion to the consent banner

Cookie Policy

Cookies are small text strings your browser stores when a site responds with Set-Cookie headers or when similar storage APIs (for example localStorage for remembering your consent choices) are used lawfully. This page names the families of storage we employ on musclesrpurify.world, why they exist, how long they linger, and how you can change your mind after the first visit.

Nothing here authorises covert cross-site tracking across unrelated industries. If you see a partner tag that does not match this directory, tell us—unplanned scripts are treated as security incidents until proven otherwise.

HTTPS only Granular toggles No paywall on rights

Names below are functional labels, not product trademarks. Durations are defaults; your browser may flush earlier if you clear site data. Regulatory labels (strictly necessary versus optional) determine whether the first-visit banner asks permission.

Family
Role
Typical lifespan
Session integrity
Binds your visit to encrypted server state so forms, consent receipts, and authenticated areas stay coherent; includes anti-replay nonces.
Session to 24 hours
Preference echoes
Remembers reduced-motion or high-contrast selections you explicitly request so we do not re-query on every page load.
Twelve months unless cleared
Analytics blur
Optional. Collects coarse scroll depth and approximate time-on-page buckets after noise injection so we can retire articles nobody reads.
Six to thirteen months
Creative rotation
Optional. Remembers which illustrative banner variant you already saw so we do not flip layouts every refresh in an irritating loop.
Up to ninety days

How consent maps to code paths

When you land without a stored decision, we show a banner with Accept All, Reject, and Cookie Settings. Rejecting disables optional analytics and marketing channels but never blocks the cookies that keep the site from falling over. Opening settings reveals switches that mirror the headings in our matrix. Saving writes a JSON object to localStorage keyed to this domain so the banner does not nag you on every subsection.

If you delete site data, preferences reset and the banner reappears—that is expected behaviour, not an attempt to wear you down. We would rather you make a conscious choice than silently inherit a profile you did not approve.

Similar technologies we might mention in audits

Content delivery networks may set performance cookies that respect the same consent state. Some embedded video players load only after you click—they may set their own strictly necessary tokens. We keep an internal register of such embeds so privacy reviews stay traceable.

Tools you already have in the browser

Beyond our switches, every major browser ships global controls for blocking third-party cookies, erasing site data, or sending do-not-track hints. Those hints are not legally binding everywhere; we treat them as contextual signals but still rely on explicit consent for optional storage where required.

  • Firefox, Safari, Edge, and Chrome each document “cookies and site data” screens with screenshots.
  • Private browsing windows discard session cookies once you close the window—ideal for borrowing someone else’s device.
  • If you automate testing with headless browsers, exclude this domain from unrealistic bot floods so rate limits do not lock out classmates.

Youth-directed pages

Movement education programmes may occasionally be purchased by guardians for household use. We still design consent prompts for adult comprehension. Guardians supervising shared devices should use operating-system profiles or filtered browsers aligned with household rules.

Review cadence

We schedule cookie inventories after each substantive redesign, when onboarding a new subcontractor that touches front-end bundles, or when regulators publish enforcement notes that materially change interpretations. Older versions of this page can be emailed to you upon request for compliance comparisons.