Cookie Policy

Controller: Phefxirevorghalx, Jernbanetorget 4B, 0154 Oslo, Norway. Contact: contact@phefxirevorghalx.world. Last updated: 25 March 2026.

This Cookie Policy supplements the Privacy Policy. It explains how we deploy cookies and similar technologies on https://phefxirevorghalx.world in line with the ePrivacy Directive as implemented in Norway and the GDPR.

1. What cookies are

Cookies are small text strings stored on your device when a site sets them through your browser. Similar technologies include pixels, local storage, session storage, and software development kits inside embedded content.

2. How we obtain consent

When you first visit, a banner offers "Accept all", "Reject", and "Cookie settings". Strictly necessary cookies load regardless because they enable core functionality. Analytics and marketing cookies fire only after you opt in or save custom settings permitting those categories. Your choice is stored locally in localStorage under the key cookie_prefs with a timestamp so we know when to revalidate preferences.

3. Categories in detail

3.1 Strictly necessary

Purpose: maintain secure sessions, remember cookie decisions, balance traffic, and deter basic automated abuse. Typical names: consent flag, routing token, CSRF defence token. Duration: session to thirteen months depending on security vendor policy. Legal basis: GDPR Article 6(1)(f) for network security plus Article 6(1)(c) where telecommunications law mandates retention.

3.2 Analytics

Purpose: measure aggregate page views, scroll depth, and conversion funnels without selling raw identifiable logs. Typical vendors: privacy-oriented analytics suites configured for IP truncation. Duration: up to twenty-five months if you consent, otherwise not activated. Legal basis: consent per Article 6(1)(a).

3.3 Marketing

Purpose: attribute advertisement clicks, cap frequency, and build anonymised lookalike cohorts if partners require measurement. Duration: between ninety days and twenty-four months. Legal basis: consent. You may withdraw through the cookie settings or industry opt-out portals where applicable.

4. Third-party embeds

If we embed payment badges or social follow buttons, those providers may set their own cookies governed by their policies. We minimise embeds on Enerlith landing pages to reduce unexpected tracking.

5. Browser controls

Major browsers let you delete cookies, block third parties, or alert you before storage. Blocking strictly necessary cookies may break checkout or consent memory. Consult documentation for Chrome, Firefox, Safari, Edge, or Brave.

6. Do Not Track

There is no uniform legal standard for DNT headers. We prioritise the explicit choices saved through our banner over legacy headers.

7. Data subject rights

Cookie identifiers may constitute personal data. You may request access or deletion subject to exemptions for legally mandated logs described in the Privacy Policy.

8. Updates

When we introduce a new vendor or materially extend retention, we refresh this Policy, bump the "Last updated" date, and may prompt returning users through the banner.

9. Session replay and heatmaps

If we configure session replay tools after consent, masked DOM snapshots help diagnose broken buttons. Such vendors sign data processing agreements limiting staff access and retention to ninety days unless an incident review extends storage.

10. Server-side logs

Web servers store IP addresses and user-agent strings independently of cookies for security. Those logs follow retention in the Privacy Policy even when you reject marketing cookies.

11. Consent withdrawal

Deleting non-essential cookies from your device or clearing site data removes many identifiers but not historical server backups immediately; we process deletion tickets within thirty days.

12. Children

The Site does not knowingly trigger behavioural ads against profiles of minors. Age gates in checkout aim to block purchases by Buyers below eighteen.

13. Contact

Email contact@phefxirevorghalx.world or write to the postal address in the header of this page with "Cookie question" in the subject line.