Quick answer
A DPDP-compliant privacy notice must, under Rule 3, be understandable on its own, use clear and plain language, give an itemised description of the personal data, state each specified purpose and the goods, services or uses it enables, and link to ways to withdraw consent, exercise rights and complain to the Data Protection Board. The template below covers each element and applies from 13 May 2027.
- Rule 3 sets minimum content; the template maps each clause to Rule 3(a), 3(b) or 3(c).
- Use a short consent notice at the point of collection and a full notice linked from it.
- Itemise personal data by category and tie each category to a specific purpose.
- The withdrawal route must be as easy as the way consent was given.
- Include the Rule 9 contact person and the Rule 14 request channel and identifiers.
- Section 5 requires notice to people whose consent was taken before commencement, as soon as reasonably practicable.
Who this is for: Founders writing their first privacy notice, In-house legal and compliance teams, Product managers owning sign-up flows, Privacy engineers building consent UIs, Agencies drafting notices for clients
What must a DPDP privacy notice contain?
Section 5 of the DPDP Act requires a notice to accompany or precede every request for consent. Rule 3 of the DPDP Rules, 2025, in force from 13 May 2027, specifies how that notice must be given.
| Rule | Requirement | Where the template covers it |
|---|---|---|
| 3(a) | Presented and understandable independently of any other information | Short notice is self-contained |
| 3(b) | Clear and plain language, a fair account enabling specific and informed consent | Whole template |
| 3(b)(i) | Itemised description of the personal data | Clause 2 |
| 3(b)(ii) | Specified purpose(s) and description of goods, services or uses | Clause 3 |
| 3(c) | Communication link to website or app, and other means, to: | Clauses 4–6 |
| 3(c)(i) | Withdraw consent, with ease comparable to giving it | Clause 4 |
| 3(c)(ii) | Exercise rights under the Act | Clause 5 |
| 3(c)(iii) | Make a complaint to the Board | Clause 6 |
Rule 9 (contact person) and Rule 14 (means and identifiers for rights requests, grievance period not exceeding 90 days) are separate publication duties, but the notice is the natural place to meet them.
Section 5(3) also requires that the Data Principal be given the option to access the notice in English or any language specified in the Eighth Schedule to the Constitution. Plan translations for the languages your users actually use.
Template 1: short consent notice (point of collection)
Use this on sign-up screens, forms and consent banners. Replace bracketed text. It must make sense without clicking through.
[COMPANY NAME] - How we use your data
We will collect: [name, mobile number, email address,
delivery address, order history, device identifier].
(Rule 3(b)(i))
We use it to: [create and manage your account; deliver
your orders; send order updates].
(Rule 3(b)(ii))
With your separate permission, we will also:
[ ] Send you offers by [WhatsApp / SMS / email]
[ ] Show you personalised recommendations
Leave these unticked if you do not want them.
You can withdraw consent at any time in
[Account > Privacy] or by replying STOP. It is as quick
as giving consent. (Rule 3(c)(i))
Your rights (access, correction, erasure, grievance,
nomination): [link to privacy centre]. (Rule 3(c)(ii))
You can complain to the Data Protection Board of India:
[link to complaint details]. (Rule 3(c)(iii))
Questions: [contact name/role, email, phone]. (Rule 9)
Full notice: [link]. Available in [languages].
Keep purpose tick boxes unticked by default and separate from acceptance of terms, so that consent stays free, specific and unbundled as section 6 requires.
Template 2: full privacy notice, clauses 1–3
Publish the full notice at a stable URL and link to it from every short notice.
PRIVACY NOTICE - [COMPANY NAME]
Version [x.y], effective [date]
1. WHO WE ARE
[Legal name], [registered address], is the Data Fiduciary
for the personal data described below.
2. PERSONAL DATA WE PROCESS (Rule 3(b)(i))
a. Identity and contact: name, mobile number, email
b. Account: username, password hash, preferences
c. Transactions: orders, invoices, payment reference
(we do not store full card numbers)
d. Delivery: address, delivery instructions
e. Device and usage: device ID, app version, IP address,
pages viewed, crash logs
f. Support: messages, call recordings [if any]
g. Marketing (only with consent): channel preferences,
campaign interactions
3. WHY WE PROCESS IT (Rule 3(b)(ii))
Purpose | Data | Ground
Provide account and orders | a-d | Data you provide
| | for this purpose
Security and fraud checks | b, e | [ground]
Customer support | a, f | Data you provide
Marketing messages | a, g | Your consent
Personalised suggestions | c, e | Your consent
Legal and tax records | a, c | Legal obligation
Name the actual goods, services or uses each purpose enables. "To improve our services" should be replaced by the specific feature, for example "to recommend products based on your past orders".
Template 2: full privacy notice, clauses 4–10
4. WITHDRAWING CONSENT (Rule 3(c)(i))
Where we rely on consent you can withdraw it at any time
at [Account > Privacy], via [link], or by [other means].
Withdrawal is as easy as giving consent. We will stop the
processing, and have our processors stop, within a
reasonable time. Processing before withdrawal remains
lawful.
5. YOUR RIGHTS (Rule 3(c)(ii); Rule 14)
You may request: a summary of your data and processing;
correction, completion, updating or erasure; grievance
redressal; and nomination of one or more individuals.
Make requests at [link/email]. To identify you we need
[registered mobile / email / customer ID].
We respond to grievances within [N] days (max 90).
6. COMPLAINTS TO THE BOARD (Rule 3(c)(iii))
If you are not satisfied with our grievance response, you
may complain to the Data Protection Board of India
[link to Board details].
7. CONTACT (Rule 9)
[Name or role], [email], [phone], [address].
8. SHARING
We use processors for [hosting, payments, delivery,
messaging] under contracts requiring security safeguards.
9. RETENTION
We keep data while the purpose is served or law requires,
and keep processing logs for at least one year.
10. CHILDREN
We do not knowingly process data of anyone under 18
without verifiable parental consent.
Clauses 8 to 10 go beyond the Rule 3 minimum but help users and reduce questions.
How to implement the notice in real systems
A notice is only compliant if the system behind it does what the notice says.
- Version everything. Store each notice version with an ID and effective date. Record the version shown with every consent event so you can prove what the person saw.
- Bind purposes to code. Each purpose in clause 3 should map to a purpose key enforced in the consent service, the tag manager and downstream jobs. If a purpose is withdrawn, the job that uses it must check consent before running.
- Render natively. On mobile, show the short notice in-app rather than as a web link, so it is presented independently as Rule 3(a) requires.
- Localise properly. Translate the notice, not only the UI chrome, and test with real users for plain-language comprehension.
- Keep the itemised list honest. Generate clause 2 from your data inventory so new fields cannot ship without the notice being updated. See data mapping and inventory.
- Re-notice legacy users. For consents given before the Act commenced, section 5 requires notice as soon as reasonably practicable. Trigger an in-app notice at next login and an email to dormant users.
Common mistakes in DPDP privacy notices
- Copying a GDPR notice. References to "legitimate interests", "lawful bases" or EU supervisory authorities do not match the DPDP Act. The Act has consent and a closed list of legitimate uses in section 7.
- Category lists that are not itemised. "Personal information such as contact details and other data" fails Rule 3(b)(i).
- Purposes without services. Rule 3(b)(ii) asks for a specific description of the goods, services or uses enabled, not just a purpose label.
- Hiding withdrawal. A notice that says "email us to withdraw" when consent was a one-tap action does not provide comparable ease.
- Missing the Board. Many legacy notices omit the right to complain to the Data Protection Board, which Rule 3(c)(iii) requires.
- Bundling consent with terms. A single "I agree to the terms and privacy policy" checkbox does not produce specific consent for each purpose.
- Promising what you do not do. Claims such as "we never share data" are risky if processors receive data. Describe sharing accurately.
Related: privacy notice requirements explained and designing consent and withdrawal UX.
Further reading on suhasbhairav.com
Before 13 May 2027
Compliance checklist
Make the short notice self-contained
Ensure it is understandable without opening any other document.
Rule 3(a)
Itemise every category of personal data
Generate the list from the data inventory and update it with each release.
Rule 3(b)(i)
Describe purposes with the services they enable
Replace generic purposes with concrete features and uses.
Rule 3(b)(ii)
Provide a withdrawal route as easy as consent
Offer an in-product toggle or equivalent one-step control.
Rule 3(c)(i)
Link to the rights request channel
State the means and identifiers needed to make a request.
Rule 3(c)(ii); Rule 14(1)
Include the Board complaint route
Tell users they can complain to the Data Protection Board of India.
Rule 3(c)(iii)
Publish the contact person
Give business contact details of the DPO or a person who can answer questions.
Rule 9
Offer the notice in Indian languages
Provide English and the Eighth Schedule languages your users need.
Section 5(3)
Version notices and log what was shown
Store the notice version with every consent event.
Section 6
Answers
Frequently asked questions
What must a DPDP privacy notice include?
What must a DPDP privacy notice include?
Under Rule 3, a notice must be understandable on its own, use clear and plain language, give an itemised description of the personal data, state each specified purpose and the goods, services or uses it enables, and provide a link and other means to withdraw consent, exercise rights under the Act and complain to the Data Protection Board.
Can I use my GDPR privacy policy for India?
Can I use my GDPR privacy policy for India?
Not without rework. A GDPR policy cites lawful bases such as legitimate interests and EU authorities that do not exist under the DPDP Act, and often lacks an itemised data list and the Board complaint route. Adapt it to the DPDP structure of consent, section 7 legitimate uses and Rule 3 content.
Does the notice need to be in Hindi or other languages?
Does the notice need to be in Hindi or other languages?
Section 5(3) requires that the Data Principal be given the option to access the notice in English or any language specified in the Eighth Schedule to the Constitution. Prioritise the languages your users actually read, and make sure translations convey the same itemised data, purposes and rights.
Is a single privacy policy page enough?
Is a single privacy policy page enough?
Usually not. Rule 3 requires the notice given with a consent request to be understandable independently, so a link alone to a long policy is weak. Use a short notice at the point of collection containing the essentials, and link to a full notice for detail.
When do I need to send notices to existing customers?
When do I need to send notices to existing customers?
Section 5 requires notice to Data Principals whose consent was given before the Act commenced, as soon as reasonably practicable. With core rules applying from 13 May 2027, plan an in-app and email re-notice campaign for existing users around that date, with an easy way to withdraw.
How often should the privacy notice be updated?
How often should the privacy notice be updated?
Whenever the data you collect, your purposes, your processors or your rights process change. Treat the notice as versioned product content: generate the data list from your inventory, record the version shown with each consent, and seek fresh consent where a new purpose is introduced.
Legal references and sources
- Digital Personal Data Protection Rules, 2025 — Rule 3 (official text)
- Digital Personal Data Protection Act, 2023 — Section 5 (official text)
- Digital Personal Data Protection Rules, 2025 — Rules 9 and 14 (official text)
- Digital Personal Data Protection Act, 2023 — Section 6 (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
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.
Related guides
- DPDP Rules 2025DPDP Privacy Notice Requirements Under Rule 3Rule 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.
- Templates & playbooksDesigning Consent and Withdrawal UX for DPDPUX and engineering patterns for DPDP-compliant consent and withdrawal: affirmative action, per-purpose choices, symmetric withdrawal under Rule 3(c)(i), and consent records.
- DPDP Act 2023DPDP Consent Requirements: Free, Specific, Informed and UnambiguousWhat valid consent means under section 6 of the DPDP Act and Rule 3: the five qualities, clear affirmative action, necessity, withdrawal parity and proof of consent.
- Templates & playbooksDPDP Data Mapping and Inventory: Step by StepA step-by-step method to build a DPDP data map and personal data inventory that feeds Rule 3 notices, Rule 6 security, Rule 7 breach scoping, Rule 8 retention and rights requests.
- DPDP Rules 2025DPDP Rule 9: Publishing Your DPO or Privacy ContactRule 9 requires every Data Fiduciary to publish the business contact of its DPO, or of a person who can answer privacy questions, on its website or app and in every rights response.
- DPDP Rules 2025DPDP Grievance Redressal: The 90-Day Response RuleRule 14(3) requires every Data Fiduciary and Consent Manager to publish a grievance response period of no more than 90 days and to build systems that meet it, from 13 May 2027.