Lawful Processing and Consent under DPDP Act 2023

  • Blog|Company Law|
  • 20 Min Read

Consent under the DPDP Act from section 6: the five attributes of valid consent, the notice that must come first, withdrawal as easy as giving consent, the Data Fiduciary’s burden of proof, and when section 7 allows processing without consent.

  • By Taxmann
  • |
  • Last Updated on 16 November, 2026

Consent under DPDP Act

Personal data may be processed under the DPDP Act only for a lawful purpose and on one of two grounds: the consent of the Data Principal, or a legitimate use listed in section 7. Where consent is the ground, section 6(1) sets the standard. Consent under the DPDP Act must be free, specific, informed, unconditional and unambiguous, given through a clear affirmative action, and limited to the personal data necessary for the specified purpose. The request must be accompanied or preceded by a notice, withdrawal must be as easy as giving consent, and if consent is questioned in a proceeding, the Data Fiduciary has to prove it. Taxmann’s Digital Personal Data Protection treats the five attributes as constitutive requirements: if any one is missing, the consent is invalid and the processing has no lawful basis. The consent provisions apply from 13 May 2027.

Table of Contents

  1. What are the lawful grounds for processing personal data under the DPDP Act?
  2. What makes consent valid under section 6 of the DPDP Act?
  3. What happens if consent is invalid?
  4. What must the notice say, and when must it be given?
  5. How should consent be collected and managed across systems?
  6. How can consent be withdrawn, and what happens next?
  7. Who must prove consent, and what records does that require?
  8. When is processing without consent allowed?
  9. How should the lawful basis be recorded?
  10. What do auditors most often find?
  11. Quick answers

1. What are the lawful grounds for processing personal data under the DPDP Act?

Two: consent and certain legitimate uses. Section 4(1) provides that a person may process the personal data of a Data Principal only in accordance with the provisions of the Act and for a lawful purpose, either with the consent of the Data Principal or for certain legitimate uses. There is no third option; every processing activity must be mapped to one of the two grounds. Where the GDPR offers six lawful bases, the DPDP Act compresses them into two (Chapter 3).

The purpose must itself be lawful. Section 4(2) defines a lawful purpose as any purpose which is not expressly forbidden by law, so the Act has no closed list of permitted purposes, and consent cannot cure a purpose the law forbids. A retailer may, with valid consent, use a customer’s email address to send offers for its products; it could not use the same data to exclude customers on a discriminatory basis prohibited by law (para 3.1).

Consent and legitimate use are alternatives, not cumulative: an organisation needs one or the other for a processing activity, not both. The choice has consequences. Relying on consent brings in the notice requirement under section 5, the consent requirements under section 6 and the possibility of withdrawal under section 6(4), which would require processing to stop. Relying on a legitimate use means satisfying the conditions of the applicable clause of section 7, and the withdrawal mechanism does not apply. An employer that relies on consent for an optional wellness survey must stop if an employee withdraws; the same employer processing payroll under section 7(i) faces no equivalent risk (para 3.1).

Stopping processing is not the same as deleting the data. Retention and erasure are governed separately, by section 8(7), the Third Schedule and Rule 8 (para 3.1), and are covered in data retention and erasure.

2. What makes consent valid under section 6 of the DPDP Act?

Section 6(1) requires the consent given by the Data Principal to be free, specific, informed, unconditional and unambiguous with a clear affirmative action. It must signify an agreement to the processing of her personal data for the specified purpose, and it must be limited to such personal data as is necessary for that purpose. The book stresses that the attributes must be present simultaneously and that each carries its own operational requirement (para 3.2):

Attribute What it means What fails the test
Free No coercion, pressure or undue influence. A service cannot be made conditional on agreeing to processing that it does not need A telemedicine app that also asks for the phone contact list; under the illustration to section 6(1), the consent covers only the telemedicine services
Specific The consent relates to a defined processing activity and a defined purpose A blanket consent covering all present and future processing by the Data Fiduciary
Informed The Data Principal has the information needed to understand what she is agreeing to, which ties consent to the notice under section 5 A hospital that hands over the privacy notice with the discharge papers, days after the patient signed a consent clause in the admission form (para 4.1)
Unconditional The consent is not subject to conditions extraneous to the processing Consent bundled with terms of service, so the service cannot be used without accepting every purpose; the book maps the Irish Data Protection Commission’s findings on such bundles to this attribute and to “free” (para 3.2.1)
Unambiguous, with a clear affirmative action No room for doubt about her intention. The Data Principal must act: click a button, check an unchecked box, sign a form or make a verbal declaration Pre-ticked boxes, silence, inactivity and opt-out mechanisms, such as a pre-ticked box sharing the customer’s phone number with third-party marketing partners

The pre-ticked box point matches the Court of Justice of the European Union in Planet49 GmbH (2019), which held that a pre-ticked checkbox is not valid consent (para 3.2).

The last element builds data minimisation into consent. The consent is legally limited to the data the purpose needs, even if the Data Principal is willing to give more, so the Data Fiduciary must work out what the purpose actually requires before it designs the consent mechanism (para 3.2).

Section 6(2) severs what the law does not allow: any part of a consent that infringes the Act, the Rules or any other law is invalid to that extent. In the illustration, an insurer obtains consent to process personal data for issuing a policy and to the policyholder waiving her right to complain to the Data Protection Board. The waiver is invalid; the consent for the policy stands (para 3.2).

“Explicit consent” is not a term the Act uses; section 6(1) speaks of a clear affirmative action. The section notes in Appendix B add that the action can be the conduct itself in the right context: filling in a membership form that explains its purposes can amount to a clear expression of consent, without a separate written agreement. Silence and pre-ticked checkboxes never qualify (Appendix B, section note 6.1).

One group needs more than section 6(1). Before processing any personal data of a child, or of a person with disability who has a lawful guardian, section 9(1) requires the verifiable consent of the parent or lawful guardian, a stricter standard than section 6(1), which does not require the identity or status of the person consenting to be verified (para 7.1). See children’s data and verifiable parental consent.

3. What happens if consent is invalid?

The processing loses its lawful basis. The book is emphatic that the five attributes are not descriptive standards that merely guide drafting; they are constitutive requirements. If any one is absent, the consent is invalid, and the processing that rests on it is processing without a lawful basis under section 4(1) (para 3.2.1).

The exposure follows from that (para 3.2.1):

  1. Processing without a lawful basis is a breach of the Act, with a penalty of up to Rs. 50 crore under the residual category in the Schedule.
  2. If the invalid consent relates to a child’s personal data, the breach falls under section 9, with a penalty ceiling of Rs. 200 crore.
  3. If a personal data breach occurs while data is being processed on invalid consent, the organisation faces both the security safeguard penalty under section 8(5), of up to Rs. 250 crore, and the underlying lawfulness penalty.

European enforcement shows that the risk is not hypothetical. In 2022 the French Commission Nationale de l’Informatique et des Libertés fined a major technology platform EUR 150 million because accepting cookies took one click while refusing them took several steps through layered menus, an asymmetry the book maps directly to the comparable-ease standard in section 6(4) of the DPDP Act (para 3.2.1).

The practical test the book recommends is to check each attribute on its own (para 3.2.1):

  1. Free: the Data Principal is not penalised for refusing, and essential services are not withheld because she declines non-essential processing.
  2. Specific: each purpose is presented separately and can be accepted or declined on its own.
  3. Informed: the notice under section 5 and Rule 3 is delivered before or alongside the consent request.
  4. Unconditional: no extraneous conditions are attached.
  5. Unambiguous: the affirmative action can only reasonably be read as agreement to the specified processing.

A failure on any one of these renders the consent invalid for the purpose to which the failure relates (para 3.2.1).

4. What must the notice say, and when must it be given?

Before or with the consent request, never after. Section 5(1) requires every request for consent to be accompanied or preceded by a notice. A Data Fiduciary that collects consent first and sends the notice later is in breach of section 5(1), however thorough the notice (para 4.1).

The notice must tell the Data Principal three things: the personal data and the purpose for which it is proposed to be processed; how she may withdraw consent under section 6(4) and seek grievance redressal under section 13; and how she may complain to the Board (para 4.1). Rule 3 adds requirements of form (paras 4.1.1 to 4.1.3):

  1. It must be understandable on its own, without cross-references to terms of service or a general privacy policy (Rule 3(a)).
  2. It must give, in clear and plain language, an itemised description of the personal data and the specified purpose, with a specific description of the goods or services to be provided or the uses to be enabled. “To improve our platform” is not specific enough (Rule 3(b)).
  3. It must give the particular communication link, and any other means, for withdrawing consent, exercising rights and complaining to the Board (Rule 3(c)).

The Data Principal must have the option to read the notice, and the consent request, in English or any of the twenty-two languages in the Eighth Schedule to the Constitution (sections 5(3) and 6(3)); the obligation is to offer the choice, not to display every language at once (para 4.2). Where consent was given before the Act commenced, section 5(2) requires a notice as soon as reasonably practicable. It is an information exercise, not a re-consent exercise, and processing may continue until the Data Principal withdraws (para 4.3). Drafting the notice is covered in the privacy notice under Rule 3.

Taxmann.com | Research | Subscribe Now!

5. How should consent be collected and managed across systems?

As evidence. Because section 6(10) puts the burden of proving consent on the Data Fiduciary, the mechanism must record the affirmative action and store it so that it can be retrieved and verified. At a minimum it should capture the identity of the Data Principal, or enough information to link the consent to her; the purpose or purposes consented to; the categories of personal data covered; the version of the notice in effect; the timestamp; and the method of affirmative action, whether a button click, a checkbox, a signature or a verbal declaration (para 4.4).

Granularity is a design requirement, not a preference. Where personal data is processed for several purposes, consent must be specific to each, so a single mechanism that bundles several purposes into one affirmative action does not meet section 6(1). The Data Principal must be able to consent to each purpose separately, and the Data Fiduciary must be prepared to provide the service even if she accepts some purposes and declines others, unless a declined purpose is genuinely necessary for the service (para 4.4). Pre-ticked checkboxes, bundled consents and consent obtained through continued use of a service do not satisfy the clear affirmative action requirement (para 4.9.1).

Section 6(3) governs presentation. Every request for consent must be in clear and plain language, must offer English or any Eighth Schedule language, and must give the contact details of the Data Protection Officer, where applicable, or of another person authorised to respond to the Data Principal on her rights (para 4.4.1).

Where consent touches several systems, the withdrawal side matters as much as the collection side. The withdrawal mechanism must be integrated with the processing systems so that a withdrawal event automatically starts the cessation workflow; one that only records the event in a log is “a user interface without a backend” (para 4.9.2). The book also recommends periodic integrity checks comparing the consent database with processing logs, to confirm that every processing activity is supported by a valid, unrevoked consent (para 4.9.4). Its test for any mechanism: if a Data Principal challenges consent before the Board, can the organisation produce a record showing exactly what she agreed to, when, under which notice and through what action (para 4.9.1)?

Consent can also be routed through a Consent Manager. Under section 6(7), the Data Principal may give, manage, review or withdraw consent through one; it is accountable to her and acts on her behalf (section 6(8)), and it must be registered with the Board (section 6(9)). A Data Principal who has consented separately to a bank, an insurer and a lending app could see all three on one dashboard and withdraw the lending app’s consent without logging into that app (para 4.7). The registration provisions have been in force since 13 November 2026 (para 1.6) and are explained in Consent Managers under the DPDP framework.

6. How can consent be withdrawn, and what happens next?

At any time, and as easily as it was given. Section 6(4) gives the Data Principal the right to withdraw consent at any time, with the ease of doing so comparable to the ease with which consent was given. A withdrawal route that requires a letter, a call to a customer service centre or a multi-step verification that was not needed at the time of consent fails that test (para 4.5).

If an e-commerce platform obtains consent for marketing emails through a single checkbox at checkout, the user should be able to withdraw by unchecking the same box or clicking a one-step unsubscribe link; making her log in, navigate to account settings and submit a separate request would not be comparable ease (para 4.5). The book recommends documenting the steps, screens, clicks and elapsed time of both journeys as evidence of compliance (para 4.9.2).

Section 6(5) allocates the consequences. They are borne by the Data Principal, and the withdrawal does not affect the legality of processing carried out before it. In the illustration, a customer who has ordered and paid for goods then withdraws consent: the platform may stop enabling her to use the app, but may not stop the processing needed to supply the goods already ordered and paid for (para 4.5).

Section 6(6) imposes the corresponding duty: within a reasonable time, the Data Fiduciary must cease, and cause its Data Processors to cease, processing her personal data, unless processing without consent is required or authorised under the Act, the Rules or any other law in force in India. “Reasonable time” is not defined. The book reads it contextually, as hours or days where cessation is a configuration change and longer for complex multi-vendor chains, but never an indefinite delay or a cessation that comes only after the Data Principal escalates the matter to the Board (para 4.5).

Two points complete the picture. Ceasing processing and erasing the data are separate obligations. Erasure is governed by section 8(7)(a), under which the withdrawal of consent is one of two triggers, the other being the point at which it is reasonable to assume that the specified purpose is no longer being served, whichever is earlier; after that, the only permissible ground for retaining the data is compliance with another law (para 8.1). And the withdrawal right applies only to consent-based processing. Where the ground is a legitimate use under section 7(a), section 6(4) does not apply, although the Data Principal can indicate that she does not consent to the use, which also requires processing to stop (para 3.5).

7. Who must prove consent, and what records does that require?

The Data Fiduciary. Section 6(10) provides that where consent is the basis of processing and a question arises in a proceeding, the Data Fiduciary is obliged to prove that a notice was given and that consent was obtained in accordance with the Act and the Rules. The Data Principal does not have to prove that she did not consent (para 4.6).

The book draws three design consequences from this reversal of the burden (para 4.6):

  1. The consent record must be immutable. Neither the Data Fiduciary nor anyone within its organisation should be able to alter, delete or backdate it after the fact.
  2. The record must carry the notice version in effect at the time of consent, because proving consent “in accordance with the Act and the Rules” means showing that the notice met section 5 and Rule 3. A consent record that cannot be linked to its notice is incomplete evidence.
  3. The consent infrastructure should be treated like financial accounting records: designed for integrity, access-controlled, backed up and periodically tested for completeness. Building it costs a fraction of being unable to prove consent in a Board proceeding where the maximum penalty for the underlying breach may extend to Rs. 250 crore.

Each consent record should hold the Data Principal’s identity or identifier, the notice version identifier, the specific purpose or purposes, the categories of personal data, the timestamp and method of the affirmative action and, where applicable, the device identifier or IP address. A withdrawal record should hold the timestamp and method of withdrawal and the date on which processing actually stopped. The records belong in a system with access controls that prevent operational staff from modifying or deleting them (para 4.9.4).

Translations are evidence too. A mistranslated notice preserved on record may show that the Data Principal was told something different from what the Act requires, which the book treats as a greater compliance risk than having no translation at all (para 4.2).

The burden is express only for consent, but the book reads the framework as implying one for legitimate uses: the record should state the section 7 clause relied on, the facts supporting it and any supporting document, such as the statutory provision behind a section 7(d) disclosure. Records made at the time, rather than reconstructed after a Board inquiry under section 28 has begun, are what make a position defensible (para 3.6).

Taxmann's Digital Personal Data Protection Act 2023 with Rules – Bare Act with Section Notes

8. When is processing without consent allowed?

Only where one of the nine legitimate uses in section 7 applies. Each ground is specific, several carry their own conditions, and an organisation relying on one must identify the precise clause and satisfy the conditions embedded in it (para 3.3):

Clause Processing without consent is allowed Example in the book
7(a) For the specified purpose for which the Data Principal voluntarily provided her personal data, where she has not indicated that she does not consent to its use A pharmacy customer asks for the payment receipt to be sent to her mobile phone (para 3.3.1)
7(b) For the State and its instrumentalities to provide or issue a prescribed subsidy, benefit, service, certificate, licence or permit, subject to the conditions in the clause A maternity benefits programme, and eligibility for other prescribed benefits (para 3.3.2)
7(c) For the State and its instrumentalities to perform any function under law, or in the interest of the sovereignty and integrity of India or the security of the State Tax administration, regulatory inspection and criminal investigation (para 3.3.3)
7(d) For fulfilling a legal obligation on any person to disclose information to the State or its instrumentalities A bank furnishing a suspicious transaction report to FIU-IND under the Prevention of Money-laundering Act, 2002 (para 3.3.4)
7(e) For compliance with a judgment, decree or order under Indian law, or a foreign judgment or order relating to a contractual or civil claim Court-ordered disclosures and compliance with arbitration awards (para 3.3.5)
7(f) For responding to a medical emergency involving a threat to the life or an immediate threat to the health of the Data Principal or any other individual An unconscious patient brought to an emergency department (para 3.3.6)
7(g) For measures to provide medical treatment or health services during an epidemic, outbreak of disease or other threat to public health A contact-tracing application during a pandemic (para 3.3.7)
7(h) For measures to ensure the safety of, or provide assistance or services to, any individual during a disaster or a breakdown of public order Floods, earthquakes, industrial accidents and riots (para 3.3.8)
7(i) For purposes of employment or of safeguarding the employer from loss or liability, or for providing a service or benefit sought by an employee Payroll, and examining access logs to investigate a suspected data leak (para 3.3.9)

The list is exhaustive. The DPDP Act has no general legitimate interests ground of the kind in Article 6(1)(f) of the GDPR, and no balancing test. If processing does not fall within one of the nine clauses, consent under section 6 is the only available basis. Analytics on customer behaviour to improve service quality is the book’s example of a purpose an organisation may consider legitimate but cannot pursue without consent or a specific section 7 ground (para 3.3.10).

The Act sets no hierarchy between the two grounds, so the choice is the Data Fiduciary’s, but the ground must genuinely fit the facts. Section 7(a) cannot be claimed for data obtained from a third-party broker, because the data was not voluntarily provided, and section 7(i) cannot be stretched to employee processing outside its purposes (para 3.5). Relying on consent for processing the organisation cannot afford to stop, such as processing needed for legal compliance or contractual performance, creates an instability that a section 7 ground would avoid (para 3.5). The book’s advice is to assess section 7 grounds first and use consent only where no legitimate use is available (para 3.8).

A legitimate use replaces consent and nothing more. Employee onboarding data needs no consent under section 7(i), but the security safeguards under section 8(5) and Rule 6 still apply (para 3.7.2). Each clause and its conditions are examined in legitimate uses under section 7, and the employment ground in employee data and workplace monitoring.

9. How should the lawful basis be recorded?

In a lawful basis register, which the book calls the foundational compliance document for this area. It maps each processing activity to its ground, consent under section 6 or the specific clause of section 7, and records the reason for the classification. It should be built at the level of individual processing activities, not business functions or data categories, because one function can involve several activities resting on different grounds (para 3.7.1).

At a minimum, each entry should record the processing activity, the categories of personal data, the categories of Data Principals, the lawful basis, the facts supporting the classification, the date of the determination and the person who made it. A consent entry should cross-refer to the consent record and the notice version; a legitimate use entry should cite the statutory provision, contractual clause, court order or other instrument relied on (para 3.7.1). The book’s illustrative register shows how the classifications work in practice (Figure 3.1, para 3.7.3):

Processing activity Lawful basis Reason
Customer order fulfilment Section 7(a) The customer voluntarily provides the data at checkout for the specified purpose of order delivery and has not indicated any objection
Promotional email campaigns Section 6 consent Marketing is a separate purpose, not inherent in the purchase, so it needs specific, granular consent, with withdrawal through a one-click unsubscribe
Employee payroll Section 7(i) Salary payment is a purpose of employment
GST return filing Section 7(d) A statutory obligation under the CGST Act to file returns containing customer transaction data
Suspicious transaction reporting to the FIU Section 7(d) A reporting obligation under the PMLA, with processing restricted to preparing and filing the report
Customer analytics for service improvement Section 6 consent A purpose separate from service delivery, with no section 7 ground available, so it needs specific consent; withdrawing it does not affect access to the service

Classify before processing begins; a classification made only when a complaint or inquiry forces the question is less credible (para 3.7.2). Review the register at least annually and whenever an activity changes materially. Data provided under section 7(a) loses that basis if it is put to a purpose that was not apparent when it was provided, and employee data loses section 7(i) if it is processed for unrelated purposes after the employment ends. The book expects a current, well-documented register that can be produced promptly to influence how the Board exercises its discretion on the quantum of any penalty under section 33(2) (para 3.7.4).

10. What do auditors most often find?

An auditor will test the lawful basis framework for completeness, accuracy, currency and consistency: whether every processing activity in the data inventory has a register entry, whether each classification is factually supportable, whether the register has been reviewed on schedule, and whether it matches the notices, the consent mechanisms and the processing actually performed (para 3.8). On notice and consent, the auditor will check the Rule 3 requirements, the timing of the notice, whether consent records are immutable and linked to notice versions, whether withdrawal meets the comparable-ease test, and whether consent is granular rather than bundled (para 4.10).

The findings that recur, with the book’s preventive measures (paras 3.8 and 4.10):

Finding Prevention
No documented lawful basis, usually for legacy processing, vendor processing under informal arrangements or ad hoc processing by business units Make the assessment part of change management and sweep existing activities to close the gaps
Consent used where a section 7 ground was available, creating unnecessary withdrawal risk Assess section 7 grounds first and use consent only where no legitimate use is available
Consent records not linked to notice versions Embed the notice version identifier in the consent record schema
Notice not standalone, relying on the terms of service for key details Draft the notice as a self-contained document and review it against Rule 3(a)
Purpose described too vaguely, such as “to improve services” Link each purpose to specific goods, services or uses, as Rule 3(b)(ii) requires
Withdrawal takes more steps than consent Document the two journeys and equalise the step count
Transitional notices not delivered to Data Principals who consented before commencement Run the section 5(2) rollout as a tracked project with delivery confirmation
Register never reviewed, or inconsistent with the published notices Put the review in the compliance calendar and reconcile the register with the notices at each review

The evidence the book lists includes a notice version register with effective dates, sample consent records showing their link to the notice version, screenshots or recordings of the consent and withdrawal interfaces with a documented comparison of the two journeys, and transitional notice delivery records (para 4.10). The audit itself is covered in how a DPDP compliance audit is conducted.

11. Quick answers

What must precede the processing of personal data under the DPDP Act?

A lawful ground. Under section 4(1), personal data may be processed only for a lawful purpose, either with the consent of the Data Principal or for a legitimate use under section 7. Where consent is the ground, it must be free, specific, informed, unconditional and unambiguous, given through a clear affirmative action, and the request for it must be accompanied or preceded by a notice under section 5(1).

What are the consent requirements under section 6 of the DPDP Act?

Section 6(1) requires consent to be free, specific, informed, unconditional and unambiguous with a clear affirmative action, to signify agreement to processing for the specified purpose, and to be limited to the personal data necessary for that purpose. All five attributes must be present together. Consent that is conditional, bundled or inferred from silence or a pre-ticked box is not valid.

When is processing without consent allowed under the DPDP Act?

Only for one of the nine legitimate uses in section 7: data voluntarily provided for a specified purpose; State subsidies, benefits, services, certificates, licences and permits; State functions, sovereignty and security; legal obligations to disclose information to the State; compliance with judgments and orders; medical emergencies; epidemics and other threats to public health; disasters and breakdowns of public order; and employment. The grounds in section 7(b) and (c) are available only to the State and its instrumentalities. There is no general legitimate interests ground.

Does the DPDP Act require explicit consent?

The Act does not use the term explicit consent. Section 6(1) requires a clear affirmative action, such as clicking a button, checking an unchecked box, signing a form or making a verbal declaration. Pre-ticked boxes, silence, inactivity and opt-out mechanisms do not count as consent.

How can consent be withdrawn under the DPDP Act?

At any time, and as easily as it was given, under section 6(4). If consent was given with one checkbox, withdrawal should take one checkbox or a one-step unsubscribe link. The Data Fiduciary must then, within a reasonable time, stop processing and make its Data Processors stop, unless a law requires or authorises the processing (section 6(6)). Processing carried out before the withdrawal remains lawful (section 6(5)).

Who bears the burden of proving consent under the DPDP Act?

The Data Fiduciary. Under section 6(10), where consent is the basis of processing and a question arises in a proceeding, it must prove that a notice was given and that consent was obtained in accordance with the Act and the Rules. That is why consent records must be immutable and linked to the notice version in force when consent was given.

Are there different types of consent under the DPDP Act?

Section 6(1) sets the standard that every consent must meet. What varies is the route and the person giving it: consent may be given directly or through a Consent Manager registered with the Board (section 6(7) and (9)), and for a child or a person with disability who has a lawful guardian, section 9(1) requires the verifiable consent of the parent or lawful guardian. Consent given before the Act commenced continues until withdrawn, subject to a notice under section 5(2).

Is consent needed for marketing emails under the DPDP Act?

In the book’s analysis, yes. In its illustrative lawful basis register, promotional email campaigns rest on consent under section 6, because marketing is a separate purpose that is not inherent in the purchase. The consent must be specific and granular, and withdrawal should be possible through a one-click unsubscribe. Fulfilling the customer’s order, by contrast, can rest on section 7(a).

When do the consent provisions of the DPDP Act apply?

From 13 May 2027. Notification G.S.R. 843(E) of 13 November 2025 brings sections 3 to 5, section 6(1) to (8) and (10), and sections 7 to 10 into force on that date, together with Rule 3 on notice. Section 6(9) and Rule 4, on the registration of Consent Managers, came into force on 13 November 2026.


This article draws on Chapters 3 and 4 of Taxmann’s Digital Personal Data Protection – An Essential Guide to India’s DPDP Law by CA Narasimhan Elangovan (2026 Edition), which examine the two grounds for lawful processing under sections 4, 6 and 7, the attributes of valid consent and the consequences of invalid consent, the boundary between consent and legitimate use, the lawful basis register, the notice obligation under section 5 and Rule 3, the consent mechanism, withdrawal, the burden of proof under section 6(10) and the Consent Manager framework. It also draws on Chapter 1 on commencement, Chapter 7 on children’s data, Chapter 8 on erasure, and Appendix B, which sets out the Act with section notes. Law stated as updated till 15 September 2026.

The DPDP Act, 2023, the DPDP Rules, 2025 and the notifications of 13 November 2025 are available on Taxmann.com | Research under Indian Acts and Rules.

Related reading: overview of the DPDP Act · scope and key definitions · rights of Data Principals · obligations of Data Fiduciaries · cross-border data transfers · breach, enforcement and penalties · the DPDP Act compliance checklist for businesses · the DPDP Act and the IT Act · the DPDP Act and the EU GDPR · startups and SMEs · FinTech and BFSI · healthcare and HealthTech.

More in this series: the SPDI Rules and the DPDP Act · the Record of Processing Activities (ROPA) · the incident response plan · data retention and erasure · the privacy notice under Rule 3 · the data processing agreement · data localisation and cross-border transfers · employee data and workplace monitoring · exemptions under the DPDP Act · legitimate uses under section 7 · the Data Protection Board of India · how a DPDP compliance audit is conducted · Significant Data Fiduciary obligations · Consent Managers under the DPDP framework · personal data breach intimation under Rule 7 · handling Data Principal rights requests · Data Fiduciary, Data Processor or both · children’s data and verifiable parental consent.

Disclaimer: The content/information published on the website is only for general information of the user and shall not be construed as legal advice. While the Taxmann has exercised reasonable efforts to ensure the veracity of information/content published, Taxmann shall be under no liability in any manner whatsoever for incorrect information, if any.

Leave a Reply

Your email address will not be published. Required fields are marked *

Everything on Tax and Corporate Laws of India

To subscribe to our weekly newsletter please log in/register on Taxmann.com

Author: Taxmann

Taxmann Publications has a dedicated in-house Research & Editorial Team. This team consists of a team of Chartered Accountants, Company Secretaries, and Lawyers. This team works under the guidance and supervision of editor-in-chief Mr Rakesh Bhargava.

The Research and Editorial Team is responsible for developing reliable and accurate content for the readers. The team follows the six-sigma approach to achieve the benchmark of zero error in its publications and research platforms. The team ensures that the following publication guidelines are thoroughly followed while developing the content:

  • The statutory material is obtained only from the authorized and reliable sources
  • All the latest developments in the judicial and legislative fields are covered
  • Prepare the analytical write-ups on current, controversial, and important issues to help the readers to understand the concept and its implications
  • Every content published by Taxmann is complete, accurate and lucid
  • All evidence-based statements are supported with proper reference to Section, Circular No., Notification No. or citations
  • The golden rules of grammar, style and consistency are thoroughly followed
  • Font and size that's easy to read and remain consistent across all imprint and digital publications are applied