[Analysis] Privacy Notice under the DPDP Act – Rule 3 Requirements | GDPR Comparison | Notice to Existing Customers

  • Blog|Company Law|
  • 11 Min Read

A privacy notice under the DPDP Act: section 5 and Rule 3 requirements, a GDPR comparison, notice versus policy, why acknowledgement is not consent, legacy consent and a two-part template.

  • By Taxmann
  • |
  • Last Updated on 16 November, 2026
A privacy notice tells a Data Principal what personal data a Data Fiduciary seeks and why, and how she can withdraw consent, exercise her rights and complain to the Data Protection Board of India. Section 5 of the Digital Personal Data Protection Act, 2023 (DPDP Act) requires one with or before every request for consent. Rule 3 of the Digital Personal Data Protection Rules, 2025 (DPDP Rules) requires it to stand on its own, itemise the data and tie each purpose to the goods or services it enables. Both apply from 13 May 2027.

Table of Contents

  1. What is a privacy notice under the DPDP Act?
  2. What must the notice contain under Rule 3?
  3. How does a DPDP notice compare with a GDPR notice?
  4. Is a privacy notice the same as a privacy policy?
  5. Does accepting a privacy notice amount to consent?
  6. When must the notice be given?
  7. What about consent obtained before the Act?
  8. How should a privacy notice be structured?
  9. Quick answers

1. What is a privacy notice under the DPDP Act?

A privacy notice is the document through which an organisation tells an individual what it does with her personal data. It is also called a transparency notice, a data protection notice or a fair processing notice. Under the DPDP Act, the notice the law requires is the one that comes with a request for consent. Section 5(1) provides that every request made to a Data Principal under section 6 for consent must be accompanied or preceded by a notice from the Data Fiduciary informing her of:

  • the personal data and the purpose for which it is proposed to be processed;
  • the manner in which she may exercise her rights under section 6(4) and section 13, that is, withdrawal of consent and grievance redressal; and
  • the manner in which she may make a complaint to the Data Protection Board of India (Board).

The Act’s own illustration is a customer who opens a bank account through a bank’s app or website and, to complete the Know-Your-Customer requirements, opts for a live, video-based identification process. The bank must accompany or precede its request for the personal data with a notice describing the data and the purpose of processing.

Abha Tiwari and Aditya Singhania draw out how this differs in design from the EU General Data Protection Regulation (GDPR). The GDPR treats the notice as an instrument of transparency, owed for all processing whatever its legal basis. The DPDP Act treats it as an instrument of consent, owed when consent is requested and aimed at enabling a specific and informed decision. That one difference explains most of what the Indian notice does and does not have to say.

2. What must the notice contain under Rule 3?

Rule 3 of the DPDP Rules sets three requirements.

  1. It must stand on its own. The notice must be presented, and be understandable, independently of any other information the Data Fiduciary has made, makes or may make available.
  2. It must give a fair account, in clear and plain language, of the details needed for specific and informed consent, including at the minimum an itemised description of the personal data, and the specified purpose or purposes with a specific description of the goods or services to be provided or uses to be enabled by the processing.
  3. It must give a route to act: the particular communication link for the Data Fiduciary’s website or app, or both, and a description of any other means by which the Data Principal may withdraw her consent, with the ease of doing so comparable to that with which she gave it; exercise her rights under the Act; and make a complaint to the Board.

The GDPR list is longer, but on two items the DPDP requirement is more exacting. Formulations that pass under the GDPR, such as “information you provide to us” or “contact and account details”, do not satisfy an itemisation requirement, and “to improve our services” is a category rather than a specified purpose. Itemisation cannot be drafted without a completed data map, so the requirement forces inventory work that most organisations otherwise defer. The same map feeds a record of processing activities.

The standalone rule is stricter than it first appears. It means the notice cannot be satisfied by a clause inside terms of service or by a cross-reference to a longer policy, and the authors observe that most existing consent flows and cookie banners fail on this ground rather than on content.

Section 5(3) adds a language requirement: the Data Principal must have the option to read the notice in English or any language listed in the Eighth Schedule to the Constitution, which recognises 22 languages. The authors treat this as an operational commitment rather than a drafting one, since 22 versions have to be kept in step and every amendment multiplies. Their advice is to draft the English text for translation: short sentences, no compound conditionals, no idiom.

3. How does a DPDP notice compare with a GDPR notice?

The GDPR asks for more items. The DPDP Act asks for fewer, including some the GDPR does not ask for at all. The comparison below is drawn from Annexure A of the book.

Item GDPR DPDP Act and Rule 3
Purpose of processing Required Required: section 5(1), Rule 3(b)(ii)
Description of the goods or services, or uses enabled No equivalent Required: Rule 3(b)(ii)
The personal data Categories only, and only on indirect collection Required, itemised: Rule 3(b)(i)
Rights and how to exercise them Required, itemised Required as to manner: section 5(1), Rule 3(c)(ii)
Right to withdraw consent Required where processing is consent-based Required, and withdrawal must be as easy as giving consent: section 5(1), Rule 3(c)(i)
Complaint to the regulator or the Board Required Required: section 5(1), Rule 3(c)(iii)
Grievance route within the organisation No equivalent Required: section 5(1), read with section 13
Link to the website or app, and other means No express equivalent Required: Rule 3(c)
Language No express multilingual requirement English or any language in the Eighth Schedule to the Constitution, at the individual’s option: section 5(3)
Legal basis, recipients, transfers abroad, retention period, automated decision-making Required Not required in the notice
Identity of the controller or Data Fiduciary Required Not expressly required, though a notice that does not identify the Data Fiduciary cannot give a fair account under Rule 3(b)

Two consequences follow. A single notice will rarely satisfy both regimes: a GDPR-compliant notice will usually contain everything the DPDP Act requires except itemisation, the goods and services description, the grievance route and the language obligation. And because the DPDP notice is tied to consent, a Data Fiduciary relying on a legitimate use under section 7 owes no statutory notice at all. The authors advise against treating that gap as a licence to stay silent: a notice is the first document a regulator asks for, and issuing one for legitimate-use processing costs nothing.

Taxmann.com | Learning

4. Is a privacy notice the same as a privacy policy?

The public document goes by several names, among them privacy notice, privacy policy, privacy statement and privacy disclosure. What it must not be confused with is the organisation’s internal data protection policy.

A privacy notice is external-facing: a transparency instrument directed by the Data Fiduciary to the Data Principal as a matter of legal obligation, not a commercial choice. A data protection policy is a governance document for the employees, contractors and others who process personal data. It sets standards of conduct, assigns roles and responsibilities, and provides the internal framework for procedures such as breach notification, rights handling and privacy impact assessments.

The book’s cautionary case is Air Sino-Euro Associates Travel Pte. Ltd., on which Singapore’s Personal Data Protection Commission imposed a penalty of SGD 47,000 in October 2025 after a cyberattack. The travel agency had an external privacy and data protection policy, but no internal policies, no data-handling procedures, no complaint-handling process and no way of telling its own employees their obligations. Drawing on its earlier decision in Stylez Pte. Ltd., the Commission reaffirmed that an external privacy policy, standing alone, is an empty promise.

5. Does accepting a privacy notice amount to consent?

No. Acknowledging or accepting a privacy notice does not constitute consent where consent is the legal basis relied on. In the book’s example, a retail chain tells customers at checkout that it has updated its privacy notice and that by continuing to shop they acknowledge having read it. Carrying on with the purchase only confirms receipt of information; it is not consent to the use of purchase history and browsing behaviour for personalised marketing.

Valid consent needs a separate, explicit and affirmative choice, such as an unticked checkbox or a clear opt-in within the loyalty account. Passive behaviour does not count: silence, not unchecking a pre-ticked box, or carrying on using a website without a clear prompt.

6. When must the notice be given?

With or before the request for consent, and from 13 May 2027. Section 5 and Rule 3 come into force on that date, eighteen months after the commencement notification of 13 November 2025, together with the rest of the substantive scheme. Until then, the enforcement risk for an ordinary Data Fiduciary continues to arise under section 43A of the Information Technology Act, 2000 and the Information Technology (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules, 2011 (SPDI Rules). The SPDI Rules require a privacy policy published on the website under Rule 4 and a notice at the point of collection under Rule 5(3). Section 43A is omitted on 13 May 2027 and the SPDI Rules fall with it. The post on the SPDI Rules and the DPDP Act sets the two regimes side by side.

A new purpose is not a notice change. The Act has no express provision on new purposes, but a new purpose needs fresh consent and therefore a fresh notice under section 5(1), which the individual may refuse. Republishing the full privacy notice is not enough. The authors contrast this with Europe, where a fresh notice suffices for a compatible new purpose. Purpose specificity at the outset therefore matters more in India, because a narrowly drafted original purpose triggers re-consent sooner.

7. What about consent obtained before the Act?

Section 5(2) covers it. Where a Data Principal gave consent before the Act commenced, the Data Fiduciary must, as soon as it is reasonably practicable, give her a notice of the personal data and the purpose for which it has been processed, the manner in which she may exercise her rights under section 6(4) and section 13, and the manner in which she may complain to the Board. It may continue processing until she withdraws her consent. The Act’s illustration is an e-commerce service that, on commencement, gives the notice by email, in-app notification or another effective method.

The authors work through four practical points.

  • No fixed deadline. The phrase “as soon as reasonably practicable” is deliberately flexible. They advise following up with two or three reminders at reasonable intervals.
  • Data collected without consent. The SPDI Rules required consent only for sensitive personal data, so much ordinary personal data, such as names, phone numbers and addresses collected for invoicing or delivery, was never subject to a consent requirement and may strictly fall outside section 5(2). The safer course is to notify all Data Principals, and to consider erasing the data of anyone who cannot be reached despite reasonable efforts, since the burden of proving valid consent rests with the Data Fiduciary.
  • Consent taken under the SPDI Rules. Often bundled into long terms of service and rarely itemised by purpose, such consent is unlikely to meet the standard in section 6 if scrutinised closely. The notice-and-opt-out mechanism of section 5(2) reduces that risk, because it lets legacy gaps be cured going forward.
  • Delivery. The law prescribes no specific mode; email, in-app notification and SMS are all practical channels. The obligation reads as one of reasonable communication, not guaranteed delivery: use current contact details, use more than one channel where appropriate, and keep records showing the steps taken. Relying on a single channel known to be ineffective would not meet the spirit of the requirement.

8. How should a privacy notice be structured?

As one full notice for transparency and a short, standalone notice at the point of consent. The drafting template in Annexure A is built that way.

  • Part A is a full privacy notice, drafted as a superset that carries everything the GDPR and section 5 with Rule 3 require. Its 13 headings run from who the organisation is and how to contact it, through the data collected, purposes and basis, sharing, transfers, automated decisions, rights, withdrawal of consent, complaints and children, to changes to the notice and languages.
  • Part B is a standalone consent notice for display where consent is requested. It must be readable without opening Part A, must not sit inside terms of service, must not be pre-ticked or bundled with anything else, and should let each purpose be refused separately.

The guidance on Part B is practical. List the exact items of data, not categories. Tie each purpose to a named service or feature. Make the Rule 3(c) link lead to routes for withdrawing consent, exercising rights and complaining to the Board, because a link to the full notice alone is a route to read, not a route to act. Keep it to one screen: if it will not fit, the processing is probably too broad rather than the notice too short.

Rule 3(c)(i) regulates the interface, not just the disclosure. Withdrawal must be comparably easy to giving consent, which is a design requirement that drafting alone cannot meet. The notice should also say what happens on withdrawal, because section 8(7) requires erasure unless retention is required by law, and a notice that is silent on the consequence invites the assumption that nothing happens.

Keep dated versions and a record of which version each user saw, with a timestamp. In any dispute the question is what the individual was shown when she decided, not what the notice says when the dispute arises, and the burden of showing valid consent falls on the Data Fiduciary.

An organisation can publish one unified notice or several specific ones, by product or service, by geography or by category of individual. Specific notices bring flexibility at the cost of complexity, so each needs a clearly defined scope, none may conflict with another, and the set as a whole must leave no processing activity uncovered. Layout matters as much as content: in December 2023 the Dutch data protection authority fined Uber €10 million, in part because the form for requesting access to one’s own data sat six menus deep in the help section of the driver app.

9. Quick answers

What must a privacy notice contain under the DPDP Act?

An itemised description of the personal data, the specified purpose tied to the goods or services it enables, and a link and other means to withdraw consent, exercise rights and complain to the Board. Section 5(1) and Rule 3 of the DPDP Rules set these requirements, and the notice must stand on its own in clear and plain language.

When must a privacy notice be given under the DPDP Act?

With or before every request for consent, under section 5(1). Section 5 and Rule 3 come into force on 13 May 2027.

Is there a deadline for notifying existing customers?

No fixed deadline. Section 5(2) requires the notice to Data Principals who consented before the Act commenced as soon as reasonably practicable, and the Data Fiduciary may continue processing until consent is withdrawn.

Can the consent notice be part of the terms of service?

No. Rule 3(a) requires the notice to be presented and understandable independently of any other information, so a clause inside terms of service or a cross-reference to a longer policy does not satisfy it.

Is accepting a privacy notice the same as giving consent?

No. Acknowledging a notice only confirms that information was received. Consent, where it is the basis relied on, needs a separate, explicit and affirmative choice, such as ticking an unticked box.

In which languages must a privacy notice be available?

In English or any of the 22 languages in the Eighth Schedule to the Constitution, at the Data Principal’s option, under section 5(3).

Does a DPDP privacy notice have to state the retention period or the recipients?

No. Retention, recipients, transfers abroad, legal basis and automated decision-making are not required in the DPDP notice, though a GDPR notice must cover them.

What is the difference between a privacy notice and a data protection policy?

A privacy notice is an external document owed to Data Principals by law. A data protection policy is an internal governance document that tells staff how to handle personal data and assigns responsibility.


Chapter 5 of Digital Personal Data Protection Law Practice and Compliance by Abha Tiwari and Aditya Singhania covers the notice under section 5 and Rule 3 and compares notice requirements across jurisdictions. Annexure A sets a DPDP notice against a GDPR notice item by item, with the reason each item matters and the European and UK decisions that illustrate it, and gives a two-part drafting template. Paragraph 2.10 deals with notice to Data Principals who consented before the Act and separates the privacy notice from the internal data protection policy.
Taxmann’s Act and Rule Comparator lets you open Rule 4 of the SPDI Rules, on the privacy policy, beside Rule 3 of the DPDP Rules, on the notice, and compare the two side by side.
Taxmann.com | Learning has a webinar held on 2 September 2023, “The Digital Personal Data Protection Act 2023 – Key Takeaways & Next Steps”, in which Abha Tiwari, a co-author of the book, discussed the Act with Kanishk Gaur and Lagna Panda, and Taxmann.com | Store has the Digital Personal Data Protection Act 2023 with Rules – Bare Act with Section Notes.
Related reading: lawful processing and consent · rights of Data Principals · the DPDP Act and the GDPR compared · scope and key definitions.
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 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.
Law stated as updated till October 2026.

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