Controller. Wluzarinjrex.world · Jernbanetorget 4B, 0154 Oslo, Norway · ask@wluzarinjrex.world
1. What we mean by cookies and similar tags
A cookie is a small file or record that a server instructs your browser to keep, typically holding a pseudonymous token, a preference, or a consent record. Similar technologies include local storage slots, session storage, pixel trackers that return a Set-Cookie header, and software development kits embedded in mobile web wrappers if we ever ship them.
Cookies may be session-bound, expiring when you close the browser, or persistent, expiring on a fixed schedule or when you erase them manually. First-party cookies originate from our hostnames; third-party cookies originate from domains loaded as embedded resources such as analytics scripts or social widgets.
2. Who sets cookies on this property
We place first-party cookies for session continuity, load-balancer affinity, and consent receipts. Selected vendors acting as independent or joint controllers may deposit additional cookies when you opt in to their categories. Those vendors issue their own transparency documents, which we link when their scripts load.
First-party focus
We prioritise first-party cookies because they reduce cross-site tracking surface while keeping essential reliability.
Third-party restraint
Marketing tags load only after a positive marketing toggle unless a service is strictly necessary for payment authorisation.
3. Strictly necessary cookies and legal exemption
These identifiers are essential to deliver a service you explicitly request, such as remembering items in a cart across pages, maintaining secure server pinning, storing CSRF defences on form posts, or recording whether you have already answered the consent banner so we do not nag you on every navigation.
Under ePrivacy implementing laws, strictly necessary storage does not require consent, though we still document it here for transparency. You cannot disable these via our banner because disabling them would break checkout or security flows.
4. Functional and comfort-enhancing storage
Functional cookies remember choices such as language, density of FAQ accordions you expanded last visit, or accessibility toggles we may introduce later. Where EU regulators classify such storage as non-essential, we collect consent before setting them; where national guidance treats low-intrusion UI memory as strictly ancillary, we may rely on limited exemption.
5. Analytics and performance measurement
When you enable analytics, we or our vendors may set cookies that bind page views into pseudonymous sessions, estimate scroll depth, or measure JavaScript error rates. IP truncation and coarse geo-aggregation reduce identifiability. Aggregated reports rarely expose individual journeys.
Legal basis: consent under Art. 6(1)(a) GDPR paired with national ePrivacy consent for non-essential access to stored information in your terminal equipment.
6. Marketing, attribution, and social pixels
Marketing cookies may help attribute a later purchase to an earlier ad click, build exclusion audiences, or cap how many times you see the same creative. They fire only if you accept the marketing category. You can later withdraw consent through the same settings overlay or by clearing site data.
7. Local storage, session storage, and IndexedDB
We may store consent JSON snapshots or offline fallback messages in localStorage when cookies are restricted by enterprise browsers. Session storage holds ephemeral tokens during a single tab lifecycle. We avoid IndexedDB unless a future feature requires structured offline caching, in which case we will amend this policy.
8. Lifetimes, rotation, and refresh
Necessary session cookies expire in minutes to hours. Persistent analytics cookies may last up to thirteen months aligned with vendor defaults unless we shorten them. Marketing pixels vary by network; some refresh identifiers on every auction. We periodically purge stale consent records from backups according to the Privacy Policy retention grid.
9. Managing consent mid-visit
Use “Cookie settings” on the banner or contact us to request a reset link. Accept-all and reject affordances are equally visible as required by fairness norms emerging from European Data Protection Board guidance. Withdrawing consent does not affect processing already performed lawfully before withdrawal.
10. Browser-, OS-, and extension-level controls
Major browsers let you block third-party cookies globally, delete data on exit, or compartmentalise sites into containers. Use those tools if you want defence-in-depth beyond our banner. Blocking all cookies indiscriminately may prevent login or order completion.
11. Global Privacy Control and legacy DNT headers
We monitor emerging standards such as Global Privacy Control. If your browser sends a recognised opt-out signal for sales or sharing where legally binding, we honour it to the extent technically feasible. Legacy “Do Not Track” headers lack uniform interpretation; we treat them as a hint to minimise optional tags but not as a substitute for granular consent where required.
12. Updates and direct questions
When we onboard a new subprocess or materially extend analytics, we update this page and may re-prompt for consent if prior choices did not cover the new processing. The date at the top updates automatically to today whenever you load the page, signalling the build you are reading. For archival PDF snapshots, contact the privacy inbox.