Cookie Policy

Executive summary

Eloa operates this storefront on behalf of Skryxellrrwhron.world from 170 Cashel Street, Christchurch Central, Christchurch 8011, New Zealand. We split cookies into three commercial tiers mirrored by the consent banner you see on the first layer. Strictly necessary items cannot be toggled off because they protect both you and our infrastructure. Analytics and marketing remain disabled until you affirmatively opt in through Accept all or granular save actions.

Definitions we use consistently

A cookie is a small text file. Local storage and session storage are browser APIs that hold structured key-value pairs with JavaScript. Pixel tags are one-by-one images or scripts that report page views to analytics dashboards. Device IDs arise when mobile partners expose resettable advertising identifiers; we only discuss them if future apps launch. First-party means we set the technology from the same registrable domain you typed. Third-party means another company’s script executes in your browser while you remain on our pages.

Strictly necessary storage

Consent receipts store your answers with a version hash so regulators can verify which text you saw. Load-balancing cookies pin your encrypted session to a healthy server during traffic spikes. Security tokens may challenge automated bots through invisible proof-of-work challenges. These files typically expire in six to twelve months or sooner when you clear site data manually.

Analytics after opt-in

When you enable analytics we may count scroll depth, hero interactions, and product tile hovers to prioritise design iterations. IP truncation happens at collection where vendors support it. Reports roll up to weekday versus weekend trends rather than storing perpetual click trails per person. You can revoke analytics by reopening Cookie settings and saving with the box unchecked.

Marketing and attribution pixels

Marketing cookies help attribute sales to responsible campaigns so we do not overspend on placements that never reach interested readers. Partners must contractually limit repurposing. Dynamic creative optimisation might rotate headline variants; that still does not imply automated profiling under GDPR Article 22 for visitors who only browse.

Illustrative lifecycle timeline

• First visit loads necessary cookies immediately to render HTTPS and the consent modal.
• Visitor selects Accept all, Reject optional, or opens granular switches.
• Preference object syncs to local storage plus a server-side audit row.
• Optional tags initialise only after positive confirmation for their category.
• Returning sessions read the stored JSON blob to avoid repetitive prompts until expiry or policy version change.

Browser level controls

Major browsers let you block third-party cookies entirely or delete data every time you exit. Doing so might force the banner to reappear because we cannot read prior consent. Incognito windows isolate storage, which is helpful for troubleshooting but not for testing personalised offers. Smartphones expose OS-level ad tracking limits that complement—not replace—our web settings.

Review cadence

We benchmark this policy whenever we onboard a new tag manager container or change analytics vendors. The visible refresh date always reflects the current session clock: . Substantive changes trigger an email to active newsletter subscribers who consented to product notices.

Questions about cookies

Email ask@skryxellrrwhron.world with subject “Cookie question” and describe your browser version if you need practical troubleshooting. Physical mail may be directed to the Christchurch address listed in the Privacy Policy.