AMLEGALSDPDPAVibe Data Privacy
HomeDPDPA InsightsConsent Management Under DPDPA
Vibe Data Privacy

Consent Management Under DPDPA

Navigating the Architecture of Lawful Processing

"Personal data may be processed by a Data Fiduciary only in accordance with the provisions of this Act and for a lawful purpose for which the Data Principal has given her consent."

DPDPA Section 4(1)

The Consent Paradigm Shift

The Digital Personal Data Protection Act 2023 fundamentally recalibrates how organisations approach consent. Unlike prior regulatory frameworks that tolerated implied consent or bundled permissions, DPDPA mandates explicit, informed, and freely given consent with granular purpose specification. This shift carries profound operational implications for businesses processing personal data of Indian residents.

Section 6 establishes the foundational principle: consent must be free, specific, informed, unconditional, and unambiguous. The burden lies squarely on the Data Fiduciary to demonstrate not merely that consent was obtained, but that the consent artifact meets statutory standards. Rule 3 further prescribes the manner of giving notice, requiring accessibility in English and 22 scheduled Indian languages upon request.

The withdrawal mechanism under Section 6(4) introduces a critical operational requirement. Withdrawal must be as simple as the consent mechanism itself. Organisations cannot erect procedural barriers that effectively deter Data Principals from exercising this right. The asymmetry between consent acquisition and withdrawal constitutes a compliance failure.

Key Provisions

Section 6(1)

Consent Characteristics

Consent must exhibit five characteristics: free, specific, informed, unconditional, and unambiguous. Each element is independently assessable, and failure on any ground vitiates the entire consent.

Section 5 read with Rule 3

Notice Requirements

Prior to or at the time of seeking consent, Data Fiduciaries must provide notice containing: personal data categories, processing purposes, withdrawal mechanism, and grievance redressal contact. The notice must be in clear, plain language.

Section 6(4)

Withdrawal Parity

The withdrawal mechanism must be as accessible as the consent mechanism. If consent is obtained through a single click, withdrawal cannot require multiple steps, form submissions, or waiting periods.

Section 2(g) read with Rule 4

Consent Manager Framework

Data Principals may manage consent through registered Consent Managers. This intermediary layer creates new compliance interfaces for Data Fiduciaries integrating with Consent Manager platforms.

Implementation Realities

Consent management platforms require integration with 22 language support systems to meet Rule 3 requirements for scheduled language accessibility.

Legacy consent records obtained under prior frameworks may not satisfy DPDPA standards. The transition strategy must address re-consent protocols.

Purpose creep triggers re-consent obligations. Any processing beyond the originally specified purpose requires fresh consent acquisition.

Consent artifacts must be retained with timestamp, version, and language metadata for regulatory audit purposes.

Withdrawal requests must propagate through processing chains, including to Data Processors, within operationally reasonable timeframes.

Implementation Challenges

Bundled Consent Disaggregation

Practice Note: Many organisations historically obtained single consent for multiple processing purposes. DPDPA requires granular, purpose-specific consent. The disaggregation exercise involves mapping existing consent artifacts to specific purposes and identifying gaps requiring re-consent.

Dynamic Consent Interfaces

Practice Note: User interfaces must dynamically present consent options based on Data Principal preferences and prior consent history. Static consent forms fail to meet the specificity requirement where processing purposes vary.

Cross-Platform Consent Synchronisation

Practice Note: Organisations with multiple touchpoints face synchronisation challenges. A consent withdrawal on one platform must reflect across all processing systems without manual intervention.

VIBE Framework Application

V

Verification

Audit consent collection mechanisms against Section 6 characteristics. Validate notice content against Rule 3 requirements.

I

Implementation

Deploy consent management platforms with multilingual capability and withdrawal parity. Integrate with Consent Manager APIs.

B

Benchmarking

Measure consent withdrawal rates, average withdrawal processing time, and re-consent conversion rates.

E

Enforcement

Establish internal controls for consent validity checks before processing. Implement automated blocking for expired or withdrawn consent.

Statutory References

DPDPA Section 4DPDPA Section 5DPDPA Section 6DPDP Rules 2025 Rule 3DPDP Rules 2025 Rule 4

Compliance Assessment

This analysis represents general guidance. Your organisation's compliance posture requires assessment against specific processing activities.

Get in Touch