After analytics is turned off
Using AI assistance to check the browser state after someone withdraws consent.
Work from 4 November 2026.
When I asked Codex to audit analytics on my personal site, I included a visitor who had already accepted tracking and then changed their mind. A fresh browser wouldn’t show what happened to the cookies from that earlier choice.
The audit found a gap. Withdrawing permission stopped future tag loads, but two Google Analytics cookies remained in the browser.
Codex updated the consent handling and repeated the sequence. Accept analytics, visit a page, withdraw permission, then navigate again. The cookies were removed, the rejection persisted and no optional analytics requests appeared on the following page. Existing saved preferences remained compatible.
My contribution was setting the scope and asking for browser evidence before and after consent. Codex made the implementation change and ran the checks. The useful evidence was the sequence of actions, the storage contents and the network requests.
That result covers the paths and browsers examined during the audit. It doesn’t establish what happens in every browser, and it doesn’t mean data already received by an analytics service has been erased.