DPDP Rules 2025Updated 22 November 20269 min read

DPDP Privacy Notice Requirements Under Rule 3

Rule 3 sets the minimum content and form of a DPDP consent notice: standalone, plain language, itemised data, specified purposes and links to withdraw, exercise rights and complain.

By Suhas Bhairav · Reviewed against the DPDP Rules, 2025 (G.S.R. 846(E), 13 Nov 2025)

Provision
Rule 3(a), (b), (c); Act section 5
In force from
13 May 2027
Form
Standalone, clear and plain language
Minimum content
Itemised data, specified purposes, goods/services/uses
Required links
Withdraw consent, exercise rights, complain to Board
Legacy consents
Notice as soon as reasonably practicable (Act s.5)
Penalty band
Up to ₹50 crore ("any other provision")

Quick answer

Under Rule 3 of the DPDP Rules, 2025, a notice must be understandable on its own, in clear and plain language, and include at minimum an itemised description of the personal data, the specified purposes and the goods, services or uses enabled, plus a link and other means to withdraw consent as easily as it was given, exercise rights and complain to the Board. It applies from 13 May 2027.

  • Rule 3 applies from 13 May 2027 and governs every notice given under section 5 of the DPDP Act to obtain consent.
  • The notice must be standalone: understandable independently of any other information the fiduciary has made or may make available.
  • It must itemise the personal data collected and state each specified purpose and the goods, services or uses that processing enables.
  • It must give a link to the website or app and describe means to withdraw consent, exercise rights and complain to the Board.
  • Withdrawal must be comparable in ease to giving consent, which is a product design requirement, not only a legal text requirement.

Who this is for: Product managers and UX designers, Legal and privacy teams, Growth and marketing teams, Mobile and web engineers, Founders of consumer apps

What must a DPDP privacy notice contain?

Rule 3 tells a Data Fiduciary how to give the notice that section 5 of the Act requires before or when asking for consent. It has three limbs.

Rule 3(a): standalone. The notice must be presented, and be understandable, independently of any other information that the fiduciary has made, is making or may make available. A notice that only makes sense if read with your terms of service fails this test.

Rule 3(b): a fair account in clear and plain language. It must give the details necessary for the Data Principal to give specific and informed consent, including at minimum:

  1. an itemised description of the personal data; and
  2. the specified purpose or purposes of processing, and a specific description of the goods or services to be provided or uses to be enabled by that processing.

Rule 3(c): the routes out. It must give the particular communication link to the fiduciary's website or app, or both, and describe any other means by which the Data Principal may:

  • withdraw consent, with ease comparable to that with which consent was given;
  • exercise her rights under the Act; and
  • make a complaint to the Board.

Rule 3 applies from 13 May 2027. It sets a floor ("at the minimum"), so extra clarity is allowed; vagueness is not.

What "itemised description" means in practice

"Itemised" is the word that breaks most existing privacy policies. A sentence such as "we collect contact, usage and device information" groups data into broad buckets. An itemised description lists the actual items.

Vague (fails)Itemised (better)
Contact informationFull name, mobile number, email address
Usage dataPages viewed, search queries, timestamps of sessions
Device informationDevice model, OS version, app version, advertising ID
Payment dataLast four digits of card, UPI ID, transaction reference
LocationApproximate city from IP; precise GPS only during delivery

Pair each item with its purpose. Rule 3(b)(ii) asks for the specified purpose and a specific description of what processing enables. "To improve our services" is not specific. "To recommend products based on your past orders" is.

An engineering trick that keeps notices accurate: generate the itemised list from your data inventory or schema registry, not from a hand-maintained document. When a team adds a field to the sign-up form, the inventory changes, and the notice can be regenerated and reviewed. Drift between what you collect and what the notice says is the most common way notices become non-compliant after launch. The data mapping guide covers building that inventory.

Withdrawal must be as easy as consent

Rule 3(c)(i) requires the notice to describe how to withdraw consent, "with the ease of doing so being comparable to that with which such consent was given". Section 6(4) of the Act states the same principle. This is a UX obligation, and auditors will test it by counting steps.

Practical comparability tests:

  • Same channel. If consent was a toggle in the app, withdrawal should be a toggle in the app, not an email to a support address.
  • Same number of steps. One tap to consent should not mean five screens and a retention offer to withdraw.
  • Same visibility. A prominent consent banner paired with a buried withdrawal option fails.
  • Granularity. If consent was given per purpose, withdrawal should be possible per purpose.

On withdrawal, section 6(6) of the Act requires the fiduciary, within a reasonable time, to stop processing and to cause its Data Processors to stop. So the withdrawal toggle needs a back end: a consent state store that downstream systems, including analytics, marketing platforms and AI pipelines, actually read.

Note the interaction with Rule 8(3). Withdrawal stops processing for the withdrawn purpose, but the fiduciary must still retain the associated logs for one year for Seventh Schedule purposes. Design these as separate states. See consent and withdrawal UX.

Passing the standalone test

Rule 3(a) is the provision that will most often force a redesign, because many companies rely on a long privacy policy linked from the footer.

A notice passes the standalone test when a person who reads only the notice can answer:

  1. What data about me will be processed?
  2. For what purposes, and what will I get?
  3. How do I withdraw, exercise my rights and complain?

Design patterns that work:

  • Layered notice at the point of consent. A short notice on the consent screen covers the Rule 3 minimum in full, with a link to a longer policy for those who want more. The short layer must be complete on its own; the long layer adds detail, not missing elements.
  • Purpose cards. One card per purpose, each listing the data items it uses and a toggle.
  • Persistent access. The same notice should be reachable later from account settings, so the Data Principal can review what she agreed to.

Avoid: notices that say "as described in our Privacy Policy" in place of content, notices that mix terms of service with consent language, and notices that change meaning depending on documents the user has not seen. The notice template gives a structure that meets Rule 3.

Notices for existing users and legacy consents

Section 5(2) of the Act covers consent given before the Act's commencement. The fiduciary must give such Data Principals a notice as soon as reasonably practicable, and may continue processing until she withdraws consent.

From 13 May 2027 that legacy notice must also meet Rule 3. For a company with a large existing base, this is a migration project:

  1. Segment the base. Identify which users consented under old flows and which purposes each consent covers.
  2. Draft Rule 3 notices per segment. Itemise data and purposes as they actually exist today, not as they were described when the user signed up.
  3. Deliver through the user account. In-app or in-product delivery, backed by email or SMS to registered contact details, creates an auditable record.
  4. Record delivery. Log which notice version each user received and when.
  5. Offer withdrawal in the same message. The notice must describe withdrawal, so make it actionable.

Do not use the legacy notice to expand purposes silently. If you now process data for something the original consent did not cover, you need fresh consent or a section 7 legitimate use for that new purpose. See DPDP consent requirements.

Building a notice system engineers can maintain

Treat notices as versioned configuration, not as static pages.

A minimal data model:

TableKey fields
notice_versionid, language, purposes[], data_items[], links (withdraw, rights, Board), published_at
purposeid, description, data_items[], lawful_ground
consent_eventuser_id, notice_version_id, purpose_id, action (given / withdrawn), channel, timestamp

Rules of thumb:

  • Immutable versions. Never edit a published notice. Publish a new version and record which version each consent was given against.
  • Link checks in CI. The withdraw, rights and Board complaint links are mandatory under Rule 3(c), so test them on every deploy.
  • Consent state as a service. Downstream systems query one source of truth rather than copying flags into many databases.
  • Retain consent events. They are your evidence that notice was given and consent obtained, which section 6(10) of the Act puts on the fiduciary to prove.

If you work with a registered Consent Manager, its platform must keep a record of notices preceding or accompanying consent requests under First Schedule Part B item 3(b). Keep your own records too; a Consent Manager is an additional channel, not a replacement for your accountability.

Further reading on suhasbhairav.com

Before 13 May 2027

Compliance checklist

  1. Inventory every point where you ask for consent

    List sign-up, checkout, permissions prompts, marketing opt-ins and AI feature opt-ins, with the data and purpose at each.

    Rule 3(b)

  2. Itemise the personal data in every notice

    Replace category labels with concrete data items, generated from your data inventory where possible.

    Rule 3(b)(i)

  3. State specific purposes and what each enables

    Tie every purpose to a described good, service or use; remove generic phrases such as improving services.

    Rule 3(b)(ii)

  4. Add the three mandatory routes

    Include a link to the website or app and a description of means to withdraw consent, exercise rights and complain to the Board.

    Rule 3(c)

  5. Test withdrawal parity

    Count steps and channels for giving and withdrawing consent and make them comparable.

    Rule 3(c)(i)

  6. Version and log notices

    Store immutable notice versions and record which version each consent event used.

    Act section 6(10)

  7. Plan legacy notices for existing users

    Send Rule 3-compliant notices to users who consented before commencement, as soon as reasonably practicable.

    Act section 5(2)

Key dates

  1. Rule 3 notice requirements apply to all Data Fiduciaries

Answers

Frequently asked questions

What should a DPDP privacy notice include?

At minimum, an itemised description of the personal data, the specified purposes of processing, a specific description of the goods, services or uses enabled, a link to the website or app, and a description of how to withdraw consent, exercise rights and complain to the Data Protection Board. It must be standalone and in clear, plain language.

When does Rule 3 of the DPDP Rules apply?

Rule 3 comes into force on 13 May 2027, eighteen months after the Rules were published on 13 November 2025. From that date every notice given to obtain consent under section 5 of the DPDP Act must meet its requirements.

Can my existing privacy policy serve as the DPDP notice?

Usually not without changes. Rule 3 requires the notice to be understandable on its own, with an itemised list of data and specific purposes. A long policy that groups data into broad categories and relies on other documents typically fails. A layered approach with a complete short notice at the point of consent works better.

Does the DPDP notice need to explain how to complain to the Board?

Yes. Rule 3(c)(iii) requires the notice to describe the means by which the Data Principal may make a complaint to the Data Protection Board of India, alongside how to withdraw consent and exercise her rights.

What does withdrawal comparable to giving consent mean?

It means withdrawing consent should take a similar effort, channel and number of steps as giving it. If consent was a single in-app toggle, withdrawal should be an in-app toggle too, not an email request or a multi-step flow. Rule 3(c)(i) and section 6(4) of the Act both require this.

Do I need to send new notices to existing users under DPDP?

Yes, where you rely on consent obtained before the Act commenced. Section 5(2) requires a notice to such users as soon as reasonably practicable, and from 13 May 2027 that notice must meet Rule 3. You may continue processing until the user withdraws consent.

Legal references and sources

  • Digital Personal Data Protection Rules, 2025 — Rule 3 (official text)
  • Digital Personal Data Protection Act, 2023 — Section 5 (notice) (official text)
  • Digital Personal Data Protection Act, 2023 — Section 6 (consent) (official text)

This guide explains the law for engineering and business teams. It is not legal advice; confirm how it applies to your organisation with qualified counsel, and check the Gazette for later notifications or amendments.

About the author

Suhas Bhairav

Suhas Bhairav

Systems architect and applied AI practitioner who designs production AI systems for Indian and global companies, with a focus on privacy-by-design under the DPDP Act and the EU AI Act.