How Often Should a Consent Banner Reappear for Returning Visitors?
Banner frequency is where consent theory meets visitor patience. Ask too rarely and your records age past defensibility. Ask too often and visitors learn that the banner is an obstacle to click through, which is its own compliance problem and quietly poisons the quality of every choice you collect.
This guide sets out a frequency policy that holds together: one interval for recorded choices, a separate rule for dismissals, and material change as the only legitimate override.
One interval, both answers
Pick a renewal interval that fits your markets, six to twelve months covers most guidance, write it in your consent policy, and apply it identically to people who accepted and people who refused. The asymmetry is the trap: many sites renew refusals monthly hoping to convert them, while acceptances coast for years. That pattern is visible in your own data and it reads, accurately, as pressure. A calendar rule applied to everyone is boring, explainable, and the version you want quoted back to you in a complaint.
Dismissal is not a choice
A visitor who closed the banner without choosing has not consented and has not refused. Non essential tracking stays off for them, but re-showing the banner after a modest interval, a few weeks or a return visit pattern you define, is reasonable because no decision exists yet. Keep the distinction clean in your tooling: dismissed, refused, and accepted are three states with three different re-prompt rules. Tools that merge dismissed into refused, or worse into accepted after a timeout, are creating records you cannot defend.
Material change overrides the calendar
A new tracker category, a significant new recipient, or a rewritten notice restarts the clock for the affected choices regardless of when the last answer was given, because the old answer did not cover the new processing. Scope the re-ask to what changed: returning visitors should see their previous settings preserved, the change highlighted, and only the new processing held back until they respond. Blanket resets that wipe careful granular choices teach visitors that granularity is pointless, and they respond by refusing everything next time.
Signed in users should not be chased across devices
If a customer is signed in, their recorded choice should follow the account, so the banner does not reappear on every phone, laptop, and borrowed tablet. Where local records and the account record conflict, apply the more restrictive until the user actively edits their settings. Show the current state and its date inside account privacy settings; transparency there prevents the support tickets and suspicion that come from a banner that seems to ignore what someone already decided.
Related reading
These earlier guides cover connected questions in more depth: Consent in Booking Engines: Hotels, Travel, and the Third Party Maze, The Requests Your Page Makes Before Anyone Touches the Banner, and Consent Proof for Small Sites: The Minimum Record That Actually Holds Up.
Frequently asked questions
What interval do regulators expect?
There is no single mandated number. Several authorities reference six to twelve months as reasonable for consent validity, and the defensible position is a stated interval applied consistently, rather than a specific figure. Pick one, document the reasoning, and follow it.
Can we re-ask after a refusal if we add a cookie category?
Yes, a material change is a legitimate trigger even after a refusal, but only the new category needs a fresh answer. The previously refused categories stay refused unless the visitor changes them; the new prompt is not a second bite at the whole decision.
Does clearing cookies reset the banner fairly?
It resets the record because the record lived in the browser, and the banner will reappear. That is expected behavior, and one reason signed in experiences should store consent server side where the relationship allows it.
Should the banner return after a site redesign?
A redesign alone is not a material change in processing. If the redesign changed what data is collected or who receives it, re-ask for that reason and say so in the prompt. Cosmetic relaunches do not justify resetting everyone choices.