Introduction and storytelling
Imagine each cookie as a courteous assistant that remembers whether you already dismissed a banner, whether your session still qualifies as authenticated, or whether you prefer dark mode once we ship that toggle. Assistants can overstay their welcome, so Norwegian and European privacy law forces us to tell you exactly who hired them and how long they stay.
If a technology processes personal data, GDPR applies in parallel with ePrivacy norms. We therefore pair this document with our Privacy Policy so you can jump between granular tracking detail and broader processing context.
Legal framework snapshot
Strictly necessary cookies rely on the storage and access exemption for operations requested by you or technically indispensable for a service explicitly chosen. Analytics and marketing cookies require informed consent under the Norwegian Electronic Communications Act implementing the ePrivacy Directive, unless future harmonized EU rules redefine exemptions.
GDPR overlap
Identifiers inside cookies may qualify as personal data when combined with server logs. We describe those combinations in data protection impact assessments stored in Oslo.
Consent proof
We log banner decisions with timestamp, abbreviated IP hash, and policy version. Logs reside in the EEA and inherit the same security stack described under Security in the Privacy Policy.
Types of technologies we reference
- HTTP cookies: classic key-value pairs exchanged between browser and server.
- Local storage: larger key-value persistence within your browser for UI preferences when strictly necessary.
- Session storage: temporary tab-scoped storage for multi-step forms.
- Pixel tags: single-pixel requests that measure email opens when marketing cookies are accepted.
We do not use so-called “device fingerprinting” as a primary analytics input on this marketing site.
Categories on this domain
Strictly necessary
Includes load balancing tokens, CSRF protections, cart resurrection identifiers, accessibility contrast selections, and the cookie consent record itself. These cannot be switched off through our interface because doing so would break the product experience or violate security baselines.
Analytics
Optional scripts help us understand aggregate navigation paths, error rates, and performance budgets. They fire only after opt-in through the cookie banner or when you reopen settings and enable them.
Marketing
Optional tags measure conversions for responsible ad platforms, build lookalike audiences only when permitted, and attribute affiliate referrals. Declining this category never blocks checkout.
Typical durations
| Category | Maximum reference lifetime |
|---|---|
| Consent metadata | Thirteen months rolling |
| Session security | Browser session or twelve hours idle |
| Analytics identifiers | Vendor default up to twenty-four months unless shortened by us |
| Affiliate attribution | Ninety days unless network rules demand less |
Durations reset when you clear cookies manually; we cannot delete copies stored on third-party servers beyond contractual erasure requests.
Your control console
Reopen the consent layer through the website footer link when we publish one, or clear storage through browser settings. Major browsers offer “block third-party cookies,” incognito defaults, and per-site exceptions we encourage you to explore.
- Chrome: Settings, Privacy and security, Cookies.
- Safari: Preferences, Privacy, Manage Website Data.
- Firefox: Settings, Privacy & Security, Cookies.
Industry opt-out pages are linked from partner policies when marketing cookies are active.
Vendor due diligence
Each analytics or advertising vendor signs a data processing agreement, lists subprocessors, and provides contact details for privacy escalations. We review their documentation when renewal occurs and when regulators issue new adequacy decisions.
How we announce updates
Material changes trigger a fresh consent prompt where law demands it and at minimum a changelog entry on this page with an updated effective stamp rendered dynamically at load time.
Contact
Questions about cookies belong in the same mailbox as broader privacy topics: ask@traxylonox.world, Sofienberggata 6, 0551 Oslo, Norway.