Consent mechanics

Cookie Policy

Cookies and similar technologies help Scyxaronphep.world remember your choices, protect form submissions, and—only when you agree—measure how Elenor content resonates. This page translates vendor jargon into operational detail you can reference when auditing your browser storage.

Version anchored to

What counts as a cookie here

Beyond classic HTTP cookies, this policy covers local storage tokens, session storage entries, pixel tags, and server-set headers that persist preference state longer than a single request. If a technology stores a random identifier tied to your browser profile, we treat it like a cookie for transparency purposes even when marketing decks call it something else.

Controller contact

Tenancy T10a, Albany Mega Centre, 140 Don McKinnon Drive, Albany 0632, New Zealand.

Email ask@scyxaronphep.world with “Cookie inquiry” in the subject line for export or deletion questions that span multiple devices.

Three layers of deployment

Strictly necessary: Session integrity, bot throttling, load-balancer affinity, consent receipts, fraud velocity caps. They load regardless of banner interaction because disabling them would break active inquiry sessions mid-flight.

Analytics: Activated only after you press “Accept all” or enable the analytics toggle. They aggregate navigation funnels, Core Web Vital estimates, and error telemetry stripped of free-text payloads.

Marketing: Optional attribution helpers that tie visits to creative variants without automatically selling personal data. Frequency caps still apply when you later reject this category.

Retention clocks

Consent logs: twenty-four months for auditability.
Analytics session cookies: thirteen months rolling unless you clear storage earlier.
Marketing pixels: ninety days with automatic expiry unless a campaign contract specifies less.
Security beacons tied to incident response: up to twelve months during active investigations.

Your controls

Use our in-banner “Cookie settings” modal anytime by clearing site data and revisiting, or email support for a manual preference reset if synchronization across enterprise browsers failed. Browser-level “block all cookies” may still allow strictly necessary headers mandated by TLS or HTTP/3 stacks.

International vendors

Some tags load from content delivery networks with nodes outside New Zealand. We rely on Data Processing Agreements, SCCs, or UK IDTA modules as required. Vendor subprocessors receive only pseudonymous IDs tied to ephemeral campaign codes rather than raw order histories.

Policy refresh cadence

We review every ninety days or sooner when regulators publish new ePrivacy interpretations affecting dietary supplement advertising.

Incident communication

If a cookie vendor discloses unauthorized access, we evaluate whether the incident poses meaningful risk to your rights and notify affected individuals without undue delay.