What we mean by “cookies”
In the broad sense used here, the term covers HTTP cookies, HTML local storage entries with a similar purpose, and service worker caches that store static assets to speed up repeat visits. We only treat technologies as optional extras when privacy law expects consent for their non-essential use.
First-party means our domain sets the entry. Third-party means another provider’s script sets it during your session; we list those only when we deliberately integrate them after your consent for analytics or marketing measurement.
Who decides
The controller responsible for configuring this site’s consent tool is Detoxificationli at Aleksanterinkatu 13, 15110 Lahti, Finland. Operational questions about a specific tag often involve co-responsibility with a vendor; we document major partners in procurement files available on request.
Categories in plain language
Strictly necessary
Security tokens, load balancing cues, consent receipts, and session continuity without which interactive features would fail unpredictably. These do not carry optional advertising signals.
Analytics
Aggregated visit patterns, scroll depth bins, or anonymised navigation funnels to improve readability. We favour aggregate dashboards over raw behavioural dossiers.
Marketing
Attribution codes that connect informational campaigns to landing views, only where permitted and proportionate to the budget under review.
Functional extras
Optional conveniences such as remembering a font-size toggle if we ship that component later; they stay off unless you enable them distinctly.
When you reject optional categories, scripts gated behind the consent layer should remain dormant. Because browsers differ, we periodically verify using internal tests that no deferred tag fires early.
How consent is stored
The banner records your choice in local storage or a narrowly scoped cookie so the site does not prompt you on every subpage load. The record stores categories approved, a version identifier tied to this policy text, and a timestamp to know when to re-prompt after recommended intervals or after substantive code changes.
You may reopen preferences through “Cookie Settings” at any time. Clearing browser data removes the receipt until you decide again.
Managing through the browser
Browsers increasingly ship with global blocking settings or “do-not-track” flags. Those tools may interfere with necessary storage and hide parts of the consent interface. If a page misbehaves after aggressive blocking, temporarily allow session storage for this host or contact us for a manual alternative such as email enrollment outside the web flow.
Incognito windows start with empty storage each session; expect prompts to return unless you accept again during that session.
Typical duration
Session technologies expire when you close the browser unless a longer lifetime is essential for fraud prevention. Persistent preference tokens aim for twelve months or less unless a longer period is justified for audit continuity; vendors publish their own defaults where they apply.
A shorter automatic purge is preferable to indefinite hoarding. If you believe residual IDs linger too long, notify us with a screenshot of the relevant storage panel where possible.
Changes and references
We amend this page when toolchains shift or regulators clarify electronic communications interpretation. Material changes may reset the consent version string and trigger a fresh banner appearance even if prior acceptance exists.
See the Privacy Policy for the wider picture of processing activities and international transfers that might relate to analytics or marketing vendors.