Transparency layer
Cookie Policy
This page names what we store in the browser, why you see a consent tray, and how to revoke access without losing access to strictly necessary functions. Pair it with the Privacy Policy for a fuller picture of personal data.
What counts as a cookie here
We use the word “cookie” to include HTTP cookies, HTML5 web storage entries, service-worker cache labels, and pixel tags that behave like cookies for measurement. Some items are set directly by our domain; others are set by tools we load only after you opt in.
Why EU and Danish law matter
Denmark implements the ePrivacy Directive alongside the GDPR. Storage or access to information on your terminal equipment generally requires informed consent unless the storage is strictly necessary to provide a service explicitly requested by you. That is why essential security cookies can load immediately while analytics wait.
Labels like “Analytics” in our banner map to the definitions below. Vendor names may rotate as we re-tender services, but categories stay stable.
Strictly necessary cookies
These support load balancing hints, bot mitigation tokens, and the JSON object that remembers whether you already answered the consent prompt. They also keep form tokens aligned when you submit the contact page. Disabling them via browser settings may break navigation or repeat prompts.
Analytics cookies
When enabled, aggregated statistics help us learn which sections of the rest-and-activity library readers open, how far they scroll on long essays, and whether mobile layouts introduce accidental taps. We configure tools to reduce precision where possible, such as truncating IP addresses at the routing layer when vendors support it.
Marketing and attribution cookies
If you enable marketing storage, campaign identifiers may record that an advertisement contributed to a visit. We do not use those signals to change editorial wording on informational pages, and we do not sell lists built from cookie IDs.
Local storage mirrors
Consent snapshots may duplicate in localStorage for resilience when cookies clear independently. Deleting site data removes both layers.
Typical lifetimes
- Session identifiers
- Removed when the browser session ends unless a vendor specifies longer rotation for stability.
- Consent receipts
- Twelve months from last interaction unless you renew earlier.
- Optional analytics
- Between thirteen and twenty-six months depending on vendor defaults; we review dashboards quarterly.
Third-party controllers or joint arrangements
Some measurement vendors act as independent controllers for aggregated statistics. Their own policies apply in addition to ours. We only enable such tags after consent where Danish law requires it.
How to change your mind
Use the site banner, the “Cookie preferences” modal, or the footer link “Update cookie preferences.” Browser settings can also block categories wholesale, though that might interfere with embedded media or checkout redirection flows.
Versioning
When we add a materially new category, we prompt visitors to reconfirm consent where necessary. Historical summaries remain available on request for business-to-business clients who maintain audit trails.