Cookie Policy

1. What “cookies” include here

HTTP cookies (first-party identifiers placed by domains we operate), partitioned storage surfaces where browsers expose them under privacy sandbox regimes, selectively synchronized local caches that remember consent palettes, ephemeral session relays when multi-step questionnaires progress, service-worker retained offline shells that never contain medical intake forms, cryptographic hash fragments supporting CSRF deterrents—all fall within this nomenclature if they resemble cookie-like semantics for regulatory conversations.

We avoid Flash LSO reservoirs, undeclared supercookies from ISP injection partners, ultrasonic cross-device pings, or canvas fingerprint overlays beyond widely disclosed measurement toggles awaiting your explicit signal.

2. Category-by-category narrative

Strictly necessary & security-first cookies: Load balancers annotate routes, TLS session resumes remain compact, brute-force lockers monitor repeated authentication attempts, cryptographic nonces thwart tampering on contact forms—all processed under legitimate-interest balancing tests when EU audiences enable them.
Aggregated analytics (opt-in): Sampling surfaces scroll-depth bins, aggregated language preferences, referrer headers trimmed to coarse sources, anomaly counters when sudden bot swarms saturate infrastructure. Pseudonymous IDs rotate monthly when vendors permit.
Marketing preference harmonization (opt-in): Harmonizes pacing for optional mailings correlating offline ticket purchases recorded via printed QR codes—not cross-site behavioral dossiers exploiting sensitive categories.

3. Persistence layers and rotation cadence

Session-critical cookies dissipate instantly when browsers close cleanly. Twelve-month horizons cap typical consent remembrance unless you reset preferences earlier via banner buttons. Analytics cohort tagging keys refresh after vendor-driven thirty-day sunsets when global privacy signals demand faster obliteration bursts.

Seasonal audits every March revalidate aggregator vendor lists powering cookie banners mirrored on staging environments beforehand.

Incident playbooks prescribe immediate cookie revocation when compromise indicators appear even if supervisory guidance has not mandated public disclosure timelines yet.

4. Harmonization with advertisement surfaces

Informational creatives appearing on curated networks must land on policy-aligned landing experiences. Paid campaigns therefore rely on sanitized UTM fingerprints rather than intrusive retargeting tags unless mirrored consent dialogs capture explicit affirmative signals—not pre-checked boxes—for each partner environment.

Remarketing exclusions propagate through audience suppression lists synced nightly with advertising APIs when someone withdraws discretionary marketing allowances through our Preference Center equivalents.

5. Browser-level controls versus studio controls

You may shred site data aggressively through Chromium, Gecko, or WebKit settings; doing so resets consent palettes and occasionally logs you out mid-form. Dedicated toggles atop this Cookie Policy recap Accept All / Reject / Cookie Settings interplay so you rarely need brittle manual interception alone.

When browsers ship Global Privacy Controls or analogous signals, ingestion middleware maps them proportionally—not as silent wholesale consent for experimental categories silently expanding scope.