Necessary storage
Necessary cookies or similar local storage may be used to deliver the site securely, balance traffic, remember a privacy choice, prevent abuse, or preserve a setting that a reader explicitly requests. The current consent control uses the versioned key pmg_consent_v1 and stores only granted or denied; it does not store calculator inputs or sensitive data. Unknown or corrupted values are removed and treated as denied.
A hosting or security provider may receive request metadata such as IP address, browser, device, requested page, time, and security signals even when optional cookies are declined. Browser settings can block storage, but blocking strictly necessary functions may prevent a preference or security decision from being remembered.
Analytics and advertising
Analytics is denied by default. The privacy-gated consent mode v2 sequence keeps analytics and all three advertising signals denied before load. Only a build with analytics enabled, a valid GA4 measurement ID, and an explicit granted choice can load it; then only analytics storage becomes granted. If permitted, default GA4 web collection can include users and session statistics, approximate geolocation, browser and device details, and a _ga client ID; see Google’s GA4 data collection reference.
AdSense loader code is absent, not merely inactive. No Google advertising script, request, or ad-slot markup is emitted even if an ads flag and syntactically valid publisher ID are supplied. Task 15 or a later activation review must add an approved Google-certified CMP/TCF and advertising-consent integration before introducing loader code, then re-check cookie guidance, publisher disclosure requirements, and the Google Privacy Policy.
Change your preference
Use Cookie settings in the footer to review, allow, deny, withdraw, or revoke analytics consent. Revocation returns all four consent mode signals to denied and prevents loading on future pages. If GA4 already loaded on the current page, it cannot be unloaded, so the status message asks the reader to reload to stop that current page session. Clearing site data also removes the stored preference.
This custom control does not replace a Google-certified consent management platform. Before publisher ads are served in the EEA, United Kingdom, or Switzerland, a certified CMP and the required regional flow must be implemented. Google’s consent mode overview, consent setup guide, EU User Consent Policy, policy help, Guidelines for using Privacy & messaging, Google-certified CMP requirements, and Google Publisher Policies describe those boundaries.