A customer agreed to receive promotional messages six months ago.
Since then, Legal has rewritten part of the privacy notice. Product has changed the preference screen. Marketing now wants to use some of the same customer data in a slightly different way.
Does that customer need to be asked again?
Sometimes yes. Sometimes no.
The answer should not depend on the notice version number alone. What matters is whether the processing the customer originally agreed to has materially changed.
That is the real challenge in consent lifecycle management. An organisation needs to know what the person agreed to, which purpose that choice covered, which notice they actually saw, and whether a later change still fits within that original decision.
A simple “consent = yes” field cannot tell you all of that.
A new notice does not automatically mean a new consent
Privacy notices change for ordinary reasons.
Legal may simplify a paragraph. A contact address may change. A translation may improve. Product may reorganise the preference screen so it is easier to understand.
Those changes should still be recorded.
But asking every customer to go through another consent journey after every small edit would create unnecessary friction and, over time, consent fatigue.
The more useful distinction is between changing the notice and changing what the organisation wants permission to do.
If the underlying purpose is unchanged and the new version simply explains the same processing more clearly, the organisation may decide that the existing consent can continue.
If the business introduces a genuinely new purpose, materially expands the processing, or changes something that was important to the person's original decision, the existing consent deserves much closer review.
A new document version is not automatically a new consent decision.
Start with what the person actually agreed to
Consent only has meaning when it is tied to something specific.
The Digital Personal Data Protection Act, 2023 describes consent as free, specific, informed, unconditional and unambiguous, given through clear affirmative action and connected to a specified purpose.
That principle matters far beyond legal wording. It affects how consent systems should be designed.
Suppose a customer agreed to receive promotional emails.
Months later, the organisation wants to use the same customer data for personalised partner offers.
Both activities may sit under “Marketing” internally, but that does not automatically make them the same purpose from the customer's perspective.
Now consider a different change. The organisation rewrites: “We use your email address to send product offers.”
into a clearer explanation of the same activity. The text changed. The underlying use did not. Those are two very different situations.
A useful consent system therefore needs to preserve more than the latest yes/no status. It needs the context behind that status.
Some notice changes are routine. Others change what the user originally agreed to.
Not every privacy notice update should trigger the same response.
Sometimes the change is little more than housekeeping. Legal rewrites a difficult paragraph in plain English, a contact address is updated, or a broken link is fixed. Those changes should still be versioned so the organisation has a reliable record of what was published and when.
But they do not automatically mean every existing user needs to be asked for consent again.
The situation becomes more interesting when the notice changes because the underlying processing has changed too.
For example, an organisation may have always used behavioural data for product analytics, but a new notice now explains that activity in more detail. If the processing itself is genuinely unchanged, this may simply be a clearer explanation of something the user had already agreed to.
If the new wording reflects a broader use of data, a different processing context, or a new purpose altogether, then the change is no longer just editorial.
Imagine data originally collected for one consent-based purpose is now going to be used for something materially different. Publishing a new notice version does not automatically make the old consent stretch to cover that new activity.
That is the point where Legal and Privacy need to look at the substance of the change and decide whether the existing consent still covers what the organisation now wants to do—or whether the user should be asked again.
Look at what changed, not just the version number
Teams can easily get stuck debating whether a change is “major” or “minor.”
Those labels are often too subjective to help.
A more practical review looks at four things:
| Area | What to check |
|---|---|
| Language | Did only wording, layout or translation change? |
| Purpose | Is the organisation doing something meaningfully different with the data? |
| Scope | Has the type of data, audience or processing context expanded? |
| User choice | Would the person's original decision still reasonably describe what the organisation now wants to do? |
This is not a statutory DPDP test.
It is an implementation discipline that helps Legal, Privacy, Product and Engineering discuss the substance of the change rather than letting a version number make the decision for them.
Re-consent and renewal are different ideas
These terms are often used as though they mean the same thing.
They do not have to.
Re-consent usually means asking for a new affirmative decision because the organisation has concluded that the existing consent is no longer sufficient for the proposed processing.
Renewal usually means refreshing an existing permission after a defined period or another lifecycle event.
That distinction is useful because there is no general rule in the DPDP Act saying that every consent must automatically expire after six months, one year or another universal period.
An organisation may choose to renew certain permissions periodically because of its own governance policy, risk assessment, customer context or another applicable requirement.
If it does, the system needs to support that policy.
What it should not do is invent an expiry simply because the notice version changed.
Do not rewrite history when the notice changes
This is one of the most important parts of consent versioning.
Imagine Priya gave consent for promotional communication on 12 January while Notice Version 3 was displayed.
In April, the organisation publishes Version 4.
If the April change does not require fresh consent, Priya's permission may remain active according to the organisation's approved decision.
But her January record should not suddenly say that she consented to Version 4.
She did not.
She saw Version 3.
That historical link matters.
A useful lifecycle record might look like this:
| Date | Purpose | Notice version | Event |
|---|---|---|---|
| 12 Jan | Promotional communication | v3 | Consent granted |
| 18 Apr | Promotional communication | v4 | Notice updated; existing state retained after review |
| 3 Jul | Personalised partner offers | v5 | Fresh choice requested |
| 4 Jul | Personalised partner offers | v5 | Consent granted |
This gives Privacy and Legal something much more useful than a single current-state field.
It gives them a timeline.
Overwriting the January record with the latest notice version might make the database look cleaner, but it destroys the history of what actually happened.
Current state and historical state answer different questions
Marketing usually wants a simple operational answer:
Can this customer currently receive this communication?
Privacy may need a different answer:
What exactly did this customer agree to, and which notice did they see at the time?
A good consent-management model needs to support both.
The current state helps systems act.
The history explains why that state exists.
AquaConsento's consent-management page describes purpose-level consent records with full version history and policy-version history tied to consent events. (aquaconsento.com)
That becomes particularly useful when teams are managing consent across changing purposes and notices rather than dealing with one static checkbox.
One notice change should not reset unrelated choices
A customer may have several active preferences.
They may agree to product analytics.
They may accept promotional emails.
They may decline an optional partner-sharing programme.
Now imagine the marketing notice changes because the organisation introduces a new form of personalisation.
That change should not automatically wipe or reset the customer's unrelated analytics preference.
This is where purpose-level consent becomes important.
AquaConsento's separate article on managing different consent states for different purposes explains why one person should not be reduced to a single blanket consent flag.
Versioning adds another layer.
The organisation needs to know both which purpose the person agreed to and which version of the information supporting that decision they actually saw.
A new vendor does not automatically mean everyone needs to be asked again
Vendor and processor changes can create similar confusion.
Suppose an organisation replaces one technical provider with another, but the underlying purpose and customer-facing processing remain materially the same.
That change does not automatically create a universal re-consent requirement.
Now take a different scenario.
The new arrangement also introduces a new use of personal data that falls outside the purpose originally presented to the user.
That needs a different assessment.
The right question is not:
“Did the vendor change?”
It is:
“Did the processing change in a way that affects the user's original choice?”
Legal and Privacy need to answer that question in context.
The technology should then implement the decision.
That separation matters because a consent platform should not be treated as a machine for making legal judgements simply because a configuration field changed.
“No response” should not become an ambiguous consent state
Re-consent creates a practical question that is easy to miss: what should happen when the user simply does nothing?
Imagine an organisation asks for fresh consent for a new optional purpose, but the customer ignores the prompt.
That silence should not be treated as permission.
At the same time, there is usually no reason to wipe out other, unrelated consent choices that are still valid.
The right outcome will depend on the purpose, the organisation’s policy and the legal position that applies. But whatever the decision is, the system should handle it consistently.
If one application treats “no response” as pending, another treats it as declined, and a third continues using the old state, the organisation will quickly end up with conflicting records.
That is why non-response needs a clearly defined status. The aim is not to force a decision from the user. It is to make sure every connected system understands the same thing when no new choice has been made.
Keep the legal timing accurate
There is also a current regulatory timing point that needs to remain clear.
As of 2 November 2026, the relevant substantive consent provisions in Sections 3–5 and most of Section 6 of the DPDP Act are scheduled to commence at the 18-month stage following the government's 13 November 2025 notification. (MeitY commencement notification)
Rule 3 of the Digital Personal Data Protection Rules, 2025, which deals with notice, also falls within the 18-month commencement group.
That means the operational practices discussed here should not be presented as though every one of them is already an operative statutory requirement in November 2026.
Some are implementation-readiness practices.
That distinction is important.
Preparing the architecture early can be sensible. Calling a future obligation a current legal requirement would not be.
Does the old “yes” still cover what happens now?
Notice versioning can easily become a technical discussion about versions, states and system records.
But the real question is simpler: is the organisation still doing what the person originally agreed to?
If the underlying purpose has not changed, asking the user again may add friction without adding much value.
If the purpose has changed, however, an old “yes” sitting in a database may no longer tell the whole story. The system may still show consent as active even though the new processing is different from the choice the person originally made.
That is why consent lifecycle management needs to preserve both the current state and the history behind it.
Teams should be able to see what the user agreed to, which notice or purpose applied at the time, and whether anything meaningful changed later.
When a genuinely new purpose is introduced, the organisation can then make a deliberate decision about whether a fresh choice is needed—without quietly stretching an older consent beyond what it originally covered.





