Cookie policy

Effective from 01/01/2026

DRAFT. This site has the same pair of tools ready that apogeaconsulting.com/politica-cookies (the site currently in production, checked 2026-10-16) already uses — Google Analytics 4 and Microsoft Clarity, with an in-house banner with equally visible options — but it isn’t active today: src/config/analitica.ts has the IDs set to null, so tools/gen-headers.mjs doesn’t open any third-party domain and no script loads. Replicating the same pair of tools is the most reasonable default while Jesús hasn’t decided otherwise (see CLAUDE.md); turning it on means filling in two values, not writing new code.

What would be activated (off today)

Cookie	Provider	Purpose	Duration	Consent required
`apogea.analytics-consent.v1`	Apogea	Store the chosen analytics preference	Until changed or browser data cleared	No
`_ga`, `_ga_*`	Google Analytics 4	Distinguish sessions/users, browsing statistics	Up to 2 years	Yes
`_clck`, `_clsk`	Microsoft Clarity	Behavioural metrics, heatmaps, session recordings	Variable, up to 1 year	Yes

The banner gives equally visible accept/reject options. Neither GA4 nor Clarity are inserted into the page until acceptance — consent isn’t requested only after they’ve already loaded.

Technical cookies

Strictly necessary for the site to work (for example, one that remembers your language choice, if added). These don’t require consent.

Turning analytics on

Add PUBLIC_GA4_ID and/or PUBLIC_CLARITY_ID as repo secrets in GitHub (no code change, no commit needed — see .github/workflows/deploy.yml and src/config/analitica.ts): the next build opens exactly the right domains in the CSP, the banner starts rendering, and this page stops saying “off.” Before doing that: confirm the legal text above has passed the pending review (see /privacidad/).