Consent Renewal Intervals: When Asking Again Is Required and When It Is Just Nagging
There is no universal expiry date for consent, but there are clear renewal triggers: a material change in purposes or vendors, a long gap the guidance in several countries puts at six to thirteen months, and any change in what the notice says. Renewal outside those triggers, on a short nag cycle, trains visitors to click accept to make the banner stop, which devalues the consent itself.
The triggers that genuinely require renewal
A new purpose is the clean trigger. Consent given for analytics does not extend to a new advertising programme, a new category of sharing, or a new vendor whose processing differs in kind. The renewal ask in that case is not a courtesy re prompt; it is the first valid ask for the new processing, and the processing must not start for existing visitors until they answer it.
Time alone is the softer trigger. Guidance in a number of European countries treats consent older than roughly six to thirteen months as due for refresh, on the reasoning that memory fades and contexts change. Treat those figures as working defaults to adopt and document, not as statutory cliffs, and let your strictest market set the interval for the shared banner rather than running four clocks.
Renewal that is only nagging
Re asking on every visit after a refusal, or on a cycle of days, has a name in the guidance: it is pressure, and consent collected under banner fatigue is consent a regulator can discount. The refusal deserves the same storage respect as a grant, held for the same interval, and a returning visitor who refused should meet no banner at all until a genuine trigger fires.
Watch the metrics temptation here. A team measured on consent rate will always drift toward shorter refusal memory and more frequent re asks, because both raise the number. The rate going up after a renewal change is not evidence of better consent. It is often evidence of the opposite, and the audit trail will show the change that produced it. Our records guide, Banner Fatigue: Repeat Prompts Train Visitors to Consent to Anything, covers how renewal events should be logged.
Writing a renewal policy you can defend
The policy fits in a short paragraph: the interval you apply and why, the change based triggers that override the interval, the rule that refusal is stored for the same period as acceptance, and the owner who approves changes to any of it. File it with the consent records configuration, and make sure the platform settings match the paragraph, because the settings are what a technical audit will read.
When renewal fires, the banner should say what changed in plain terms: we added a purpose, we changed a vendor, your previous choice needs a fresh answer. A renewal banner that pretends to be a first ask annoys the visitor and misdescribes the legal position, since prior processing under the old consent was lawful and the new ask covers new ground.
Keep reading: Banner Fatigue: Repeat Prompts Train Visitors to Consent to Anything A/B Testing Tools Are Data Collection Too: Consent for Experimentation Platforms Consent Banner A/B Tests: What You Can Test Without Breaking the Law.
Frequently asked questions
Does consent expire after a set time?
Most laws set no fixed expiry, but guidance in several European countries treats six to thirteen months as a reasonable refresh point, and any material change in purposes or vendors requires a fresh ask regardless of age. Adopt an interval, document the reasoning, and apply it consistently.
Do we need new consent when we change a vendor?
If the new vendor's processing is materially different, yes: a different category of sharing or a new purpose needs its own consent. A like for like replacement performing the same processing under the same purposes is normally covered, provided the notice and vendor list are updated.
Can we ask again soon after someone refuses?
Re asking quickly after refusal is treated as pressure and undermines the freedom of the original choice. Store refusals for the same interval as grants. Only a genuine change in purposes or vendors justifies an earlier re ask, and it should explain what changed.
What should a renewal banner say?
Say what changed and why a new answer is needed: a new purpose, a new vendor category, or the age of the previous choice. Do not present it as a first ask. Visitors answer more honestly, and the record reads better, when the renewal is described accurately.