Cookie & Consent Policy
Consent defaults, updates, and revocation
Last updated: March 24, 2026
This rollout uses basic consent mode. On monetized families, Google tags do not load at all in the EEA, the UK, or Switzerland until the CMP reports an explicit result.
The accepted CMP contract for this project is fixed: Google-certified CMP, web support, and IAB TCF v2.3 compliance. Operationally, no non-v2.3 CMP path is allowed here.
For explicit grant, the implementation keeps the required basic consent mode boot order: load the Google tag, call consent default with denied storage, immediately call consent update with granted storage, and only then run config, page view tracking, and the AdSense bootstrap. Explicit deny keeps both GA and AdSense unloaded.
TCF v2.3 migration is treated as complete by February 28, 2026 in this project, even though some Google help pages phrase the CMP-side deadline as March 1, 2026. The stricter project rule wins.
Non-applicable regions still wait for CMP bootstrap readiness. If the CMP reports ready + not_applicable, tags can load immediately without waiting for visible consent UI. If no ready signal arrives within 3000ms, that page view stays fail-closed and logs an internal compliance guardrail event instead of failing open.
Consent revocation entry point
Use the button below to reopen the live CMP entry point. If consent is revoked after tags were previously granted, the site performs a hard reload so the page returns to a clean denied state before any further interaction.
This phase keeps ads off the home page, blog, projects, LinkedIn posts, support, and legal pages. Advertising is limited to the monetized tools and AI model families described in the ad disclosure.