What Happens to Consent When a Visitor Clears Cookies
Clear your cookies and your consent is gone. Not the record of it, if your CMP kept a server-side copy, but the browser's memory of it: the choice itself, the timestamp, the banner version. The next visit starts over, and the site asks again. That is the design working as intended, and it is also the reason consent is more fragile than most teams think.
Consent is usually stored in a cookie or in local storage. Both live in the browser, and both are wiped when the visitor clears them. Some CMPs store the consent state in a cookie; others use local storage. Either way, the browser is the only copy the site has unless the CMP also keeps a server-side record keyed to something sturdier than a cookie, like a logged-in account.
What clearing actually breaks
For a logged-out visitor, clearing cookies resets everything. The site cannot tell a first-time visitor from a returning one who cleared their storage, so it re-prompts. That is correct behavior, and it is also a measurement problem: the consent rate you report counts re-prompts as new decisions, and a visitor who clears cookies weekly is counted as a new visitor weekly.
For a logged-in visitor, the picture is better and more complicated. If the CMP ties consent to the account, the choice survives a cookie clear, because the site can look it up when the visitor logs in. But the lookup happens after login, and the tags that fire before login run without knowing the choice. The gap is short, usually a single page view, and it is exactly the page view a strict reading of the law cares about.
The re-prompt problem nobody measures
Every re-prompt is a chance for the visitor to answer differently, and a chance to get annoyed. Sites that re-prompt aggressively, because their consent cookie expires in days or because the storage keeps getting cleared, train visitors to click whatever dismisses the banner fastest. That is how a site ends up with a high accept rate and weak consent: not through a dark pattern, but through attrition.
The fix is boring. Set the consent cookie to last as long as your renewal policy allows, not the browser default. Keep a server-side record for logged-in users so a cookie clear does not erase the choice. And measure the re-prompt rate: how often the same visitor is asked again. If it is high, the problem is not the banner. It is the storage.
Keep reading: Consent Cookies: Expiry, Scope, and What Happens When They Die, Consent Renewal Intervals: How Often to Ask Again, and Cookiebot vs CookieYes for Small Sites cover the nearby cases in this series.
Frequently asked questions
Where is consent stored on a website?
Usually in a cookie or in local storage, both in the browser. Some CMPs also keep a server-side record, keyed to a logged-in account, which survives a cookie clear.
What happens when a visitor clears their cookies?
The browser's copy of the consent choice is gone, so the site re-prompts on the next visit. For a logged-out visitor the site cannot tell them from a first-time visitor.
Does clearing cookies delete the consent record?
Not necessarily. If the CMP keeps a server-side record, the evidence survives. What is lost is the browser's memory of the choice, which is what the site checks before tags fire.
How long should a consent cookie last?
As long as your renewal policy allows, not the browser default. A consent cookie that expires in days forces constant re-prompts, which trains visitors to dismiss the banner without reading it.