Cookies and similar technologies
This list describes first-party storage we use and how choices flow to Google Tag Manager (GTM). You can change your analytics choice from the cookie banner or via Manage cookies in the site footer when the banner has already been dismissed.
Consent storage
| Name | Purpose | Duration | Strictly necessary |
|---|---|---|---|
SelfFool.TrackingConsent |
Stores accept / decline (Accept all / Deny all) or granular v2:statistics:marketing with 0/1 (e.g. v2:1:0). HttpOnly. |
About 13 months | Yes |
Conditional tags (via GTM)
When you click Accept all, we update Google Consent Mode and your browser reloads so measurement tags fired through GTM can use allowed storage categories. When you choose Reject all, non-essential measurement remains denied in Consent Mode; GTM may still load, but configured tags should respect the denial (configure triggers on Consent Mode / custom events as needed).
| Layer | Typical vendors / tools | When active |
|---|---|---|
| Google Tag Manager container | GTM loader (GTM-TZTRVK2F) and tags you configure inside GTM (for example GA4, Clarity, ads pixels). |
Always loaded; tags inside should gate on consent / your GTM triggers. |
| Analytics & measurement | As configured in GTM (e.g. GA4, Microsoft Clarity). | After Accept all (Consent Mode update), not after Reject all for denied categories. |
GTM / dataLayer events we push
cmp_interactionwithcmp_action:accept,decline,preferences_save, ormanage_open— use as custom-event triggers.- Google
gtag('consent', 'update', …)runs on accept/reject to align tags with stored choice.
For legal text and retention, see the Privacy Policy.