
Consent Withdrawal Under the DPDP Act: What it Actually Means, and Why Consent Managers Matter?
Summarize this blog with :
The right to withdraw consent is an important part of India's Digital Personal Data Protection (DPDP) Act, 2023. It gives individuals greater control over how their personal data is used and requires businesses to stop consent-based processing within a reasonable time when consent is withdrawn, subject to applicable legal exceptions. However, honouring a withdrawal request involves more than providing an option to revoke consent. It requires coordination across internal systems, third-party processors, vendors and data management platforms.
This blog explores what the law requires, the operational challenges businesses may face, and how registered Consent Managers can support transparent and accountable consent management.
Understanding Consent Withdrawal Under the DPDP Act
Think about the last time you signed up for an online service. You probably entered a few details, ticked a consent box and moved on. But what happens to that information afterwards? Where is it stored, who has access to it, and how long does an organisation continue using it?
For most users, these details remain largely out of sight.
India's Digital Personal Data Protection (DPDP) Act, 2023, aims to change that by giving individuals greater control over their personal data. One of its important provisions is the right to withdraw consent at any time, with the process being as easy as giving it in the first place.
For individuals, this provides a meaningful way to exercise control over their personal information. For businesses, however, it introduces an important operational responsibility: ensuring that a withdrawal request is recognised and acted upon across the systems and third parties involved in processing personal data.
And that is where the real challenge begins.
What Does Section 6 of the DPDP Act Say About Consent Withdrawal?
Section 6 of the DPDP Act, 2023, establishes the framework for consent. It also explains what happens when an individual decides to withdraw it.
Here are the key provisions businesses should understand.
Section 6(4): Understanding the Right to Withdraw Consent
A Data Principal (the individual to whom personal data relates) has the right to withdraw consent at any time when consent is the basis for processing their personal data.
The Act also establishes an important principle: withdrawing consent should be as easy as giving it.
For example, if an individual provides consent through a single click, the organisation should not make them navigate multiple screens, submit lengthy forms or contact customer support just to withdraw it.
The withdrawal mechanism should be accessible and straightforward.
Section 6(5): What Happens to Personal Data After Consent Withdrawal?
Withdrawing consent does not automatically invalidate processing that was lawfully carried out before the withdrawal.
The provision also states that the consequences of withdrawal are borne by the Data Principal. The Act illustrates this through an online shopping example: withdrawing consent may affect the individual's ability to place future orders, but it does not prevent the organisation from processing the information necessary to fulfil an order that has already been placed and paid for.
This distinction is important. Withdrawal applies going forward; it does not automatically undo legitimate processing that has already taken place.
Section 6(6): Data Fiduciary Responsibilities After Consent Withdrawal
Once consent is withdrawn, the Data Fiduciary (the organisation determining the purpose and means of processing personal data) must, within a reasonable time, stop processing that individual's personal data and ensure that its Data Processors do the same.
There is an important exception: processing may continue where it is required or authorised under the DPDP Act, the Rules or another applicable Indian law.
In practical terms, an organisation cannot simply update its own records and assume that the obligation has been fulfilled. It must also address the processing activities carried out by vendors, service providers and other processors acting on its behalf.
Section 6(7)–6(9): The Role of Consent Managers Under the DPDP Act
The Act provides for individuals to give, manage, review and withdraw consent through a Consent Manager.
A Consent Manager is an entity registered with the Data Protection Board of India. It is accountable to the Data Principal and must operate in accordance with the prescribed requirements.
The registration and operational framework is set out under Rule 4 of the DPDP Rules, 2025, along with the First Schedule.
Section 6(10): Accountability and Proof of Consent
The responsibility of demonstrating that valid consent was obtained rests with the Data Fiduciary.
If a question arises in a proceeding regarding consent-based processing, the organisation must prove that the required notice was provided and that consent was obtained in accordance with the Act and Rules.
This makes proper documentation essential. Businesses need reliable records of consent, the notice presented to the individual and the associated consent history.
Taken together, these provisions make consent withdrawal more than a user-facing feature. It is an obligation that must be supported by appropriate processes, systems and accountability.
Why Consent Withdrawal Is an Operational Challenge for Businesses?
From a user's perspective, withdrawing consent should be simple. Click a button, confirm the choice and move on.
For a business, however, the process can be considerably more involved.
Personal data rarely stays in one place. It may move between customer relationship management (CRM) platforms, marketing tools, analytics systems, cloud environments, data warehouses and external service providers.
When an individual withdraws consent, the organisation must identify which processing activities depend on that consent and ensure that the relevant systems and processors act accordingly.
Consider a typical business environment:
CRM systems: Customer records and communication preferences may need to be updated to prevent further consent-based processing.
Marketing automation platforms: Email, SMS and other promotional communication workflows may need to be stopped.
Analytics platforms: Behavioural data processing that relies on the withdrawn consent may need to cease.
Data warehouses: Relevant processing workflows and data access arrangements may need to be reviewed and updated.
Third-party vendors: Service providers and other processors handling the individual's data must receive and act on the appropriate instructions.
The challenge is ensuring that these actions are coordinated and completed within a reasonable time.
For instance, if a user withdraws consent on a website but the marketing platform continues sending promotional emails because it has not received the updated preference, the organisation has a process gap.
Similarly, if a third-party processor continues using the data after receiving no effective withdrawal instruction, the organisation may struggle to demonstrate that it has fulfilled its responsibilities.
This is why businesses should not treat consent withdrawal as an isolated website function. It needs to be supported by an integrated approach to consent management, data governance and vendor oversight.
Real-time or near-real-time synchronisation can help reduce delays and improve operational control. While the Act does not prescribe a universal real-time deadline, organisations should design their systems to propagate withdrawal instructions promptly, maintain traceable records and minimise continued processing after a request.
What Is a Consent Manager Under the DPDP Act?
A Consent Manager provides a structured mechanism through which individuals can give, manage, review and withdraw consent across participating Data Fiduciaries.
Under Rule 4 of the DPDP Rules, 2025, Consent Managers must meet prescribed registration conditions and operate an interoperable platform. The First Schedule also specifies their responsibilities, including maintaining records of consent granted, denied or withdrawn, as well as the notices associated with consent requests.
So, what does this mean for individuals and businesses?
1. How a Consent Manager Platform Simplifies Consent Management
Rather than managing consent separately across multiple platforms, individuals can use a Consent Manager's platform to manage their consent interactions with participating Data Fiduciaries.
This creates a more organised approach to reviewing and withdrawing consent.
2. Better Visibility and Accountability
Consent Managers must maintain records of consent-related activities, including consent given, denied or withdrawn and the notices associated with those requests.
They must also provide individuals access to these records. Under the First Schedule, such records must generally be maintained for at least seven years, subject to the applicable provisions.
This can help establish a clearer record of consent-related decisions and support accountability.
3. An Interoperable Consent Management Framework
The Rules require Consent Managers to operate an interoperable platform that enables individuals to give, manage, review and withdraw consent.
This is an important step towards making consent management more consistent across participating organisations.
However, businesses should not assume that using a Consent Manager automatically fulfils all their obligations. The Data Fiduciary remains responsible for acting on withdrawal requests within a reasonable time and ensuring that its Data Processors cease the relevant processing, unless a legal exception applies.
4. Key Consent Manager Benefits: Building Trust Through Accountability
Consent Managers must act in a fiduciary capacity towards Data Principals and comply with prescribed requirements relating to security, transparency, audits and conflicts of interest.
Their accountability to individuals is an important part of the framework.
For businesses, this creates a more structured consent management ecosystem, but it does not remove the need for strong internal governance and technical readiness.
What Businesses Need to Do to Prepare for DPDP Consent Management?
The DPDP framework follows a phased implementation timeline. The Consent Manager registration framework came into effect on 13 November 2026, while the principal consent-related obligations under Section 6 and most of the remaining substantive compliance requirements are scheduled to come into effect on 13 May 2027.
The time between these milestones should be used to assess existing practices and address gaps before the main obligations become enforceable.
Here are four areas businesses should prioritise.
1. Review the Existing Consent Withdrawal Process
Start by examining how individuals currently give and withdraw consent across websites, mobile applications and other customer-facing platforms.
Check whether the withdrawal process is as accessible and straightforward as the consent process. Identify any unnecessary steps, manual dependencies or delays that could prevent a request from being actioned promptly.
2. Assess System Integration and Data Flows
Map where personal data is collected, stored, shared and processed.
Identify the systems that rely on consent, the teams responsible for managing them and the third-party platforms involved. Assess whether withdrawal instructions can be communicated and acted upon consistently across these environments.
Where possible, consider automated workflows and API-based integration to minimise manual intervention and delays.
3. Review Third-Party and Vendor Arrangements
Businesses remain responsible for ensuring that their Data Processors cease the relevant processing after consent is withdrawn, subject to applicable legal exceptions.
Review vendor agreements, data processing arrangements and operational procedures. Ensure that responsibilities for receiving, acknowledging and acting on withdrawal instructions are clearly defined.
It is equally important to establish how compliance will be monitored and evidenced.
4. Strengthen Consent Records and Audit Trails
Maintain reliable records of consent-related activities.
These should ideally capture:
The date and time consent was obtained.
The notice presented to the individual.
The purpose for which consent was obtained.
The date and time of withdrawal, where applicable.
The systems and processors notified.
Evidence that the relevant processing activities were stopped or appropriately addressed.
A well-maintained audit trail can help organisations demonstrate accountability and respond more effectively to regulatory enquiries.
Making Consent Withdrawal Work Under the DPDP Act
The right to withdraw consent is an important step towards giving individuals greater control over their personal data. But its effectiveness will depend on how well organisations translate this right into everyday business operations.
For businesses, the challenge is not simply to provide a withdrawal option. It is to ensure that the request is recognised, communicated and acted upon across the entire data processing ecosystem.
Consent Managers will play an important role in supporting this framework by providing an interoperable and accountable mechanism for consent management. However, organisations must also take responsibility for their internal systems, third-party relationships, data governance practices and audit readiness.
Ultimately, DPDP compliance is not just about obtaining consent. It is about respecting an individual's choice throughout the data lifecycle.
As organisations prepare for the upcoming compliance milestones, building the right technical and governance foundations today will be essential to managing consent responsibly tomorrow.
At 63SATS Cybertech, this focus on practical readiness aligns with the broader work of strengthening enterprise cybersecurity, data governance and privacy frameworks. Through its cybersecurity and governance expertise, 63SATS supports organisations in addressing the technical and operational considerations involved in building a more secure and accountable digital environment.


