Cookie Policy

Vocabulary we rely on

A “cookie” is a name-value pair written by a server response. “Local storage” persists larger JSON objects client-side. “Pixels” are invisible requests counting impressions. Together we refer to them as stored technologies.

First-party versus third-party originators

Our domain issues first-party entries for consent receipts. Third-party hosts such as font networks may set technical tokens when your browser requests assets; those vendors operate under their own statements but only receive the headers intrinsic to an HTTPS GET.

Strictly necessary storage

• Session integrity tokens for contact submissions.
• Rate-limit counters to slow brute-force attempts.
• Load-balancer affinity labels mandated by infrastructure partners.

These items fall outside consent requirements when narrowly tailored under Section 25(2) TTDSG.

Functional preference storage

The banner writes a JSON object describing whether you accepted all categories, rejected optional tags, or customised analytics. Without it you would see repetitive prompts. The payload excludes message content from forms.

Analytics cohorts

When allowed, we may count page views, scroll depth milestones on long explainers, or outbound reference clicks. IP addresses are truncated at the edge where feasible. Aggregates feed editorial planning, not advertising auctions.

Marketing experiments

Occasionally we test compliant creative sequences for workshop announcements. Tags fire only after marketing consent equals true and never read health-related keywords from URLs.

Typical lifetimes

• Session cookies: expire when the browser closes.
• Consent anchors: twelve months unless you renew early.
• Analytics identifiers: up to thirteen months aligned with platform defaults.

Fonts, icons, and edge caches

Google Fonts and Remix Icon stylesheets load over TLS. Those requests expose ordinary metadata. Blocking them may alter typography without breaking informational copy.

Updating or revoking choices

Clearing site data resets the banner. You may also reject analytics mid-session via Cookie Settings; marketing tags halt on the next navigation event.

Browser-level hygiene

Safari Intelligent Tracking Prevention, Firefox Enhanced Tracking Protection, and Chromium privacy modes behave unpredictably with local storage. If functionality degrades, whitelist only this origin or contact us for PDF alternatives.

Guardians and school devices

Shared hardware should use browser profiles so students do not inherit parental consent states. We do not knowingly advertise to children.

Reach the privacy desk

Email service@purifythbio.world with “Cookie query” in the subject. Cross-read the Privacy Policy for legal bases and retention.