Is a notice the same as a privacy policy?
Not quite. A privacy policy is usually one long page about everything you do. A DPDP notice is what you show a person at the moment you ask for their consent, about the data you are collecting there and why (Section 5(1)). Rule 3 of the DPDP Rules, 2025 says it must be understandable on its own, without reading your terms or another document. You can keep a full privacy policy as well, but a link to it doesn't replace the notice.
A business with several forms, such as a newsletter sign-up, a checkout and a job application, usually needs a short notice for each, because the data and purposes differ.
What must the notice contain?
Rule 3 requires, in clear and plain language:
- an itemised description of the personal data you collect, field by field, not "your information";
- the specified purpose for processing it, and a specific description of the goods or services the processing makes possible;
- the link to your website or app, and any other way, through which the person can withdraw consent as easily as they gave it;
- how they can exercise their rights under the Act: access, correction and erasure, grievance and nomination;
- how they can complain to the Data Protection Board.
Section 8(9) adds the contact details of your Data Protection Officer, if you have one, or of a person who can answer questions about your processing. People must be able to read the notice in English or any of the 22 languages in the Eighth Schedule to the Constitution (Section 5(3)). Offer the languages your customers actually use.
A template you can adapt
Replace everything in [square brackets]. Delete any line that doesn't apply rather than leaving it vague.
How [Business name] uses your personal data
We ask for the details below so we can [describe the service, e.g. deliver your order and send you updates about it]. You can say no to anything marked optional, and we will still [provide the service].
| What we collect | Why | Required? |
|---|---|---|
| [Name] | [To address your order and invoice] | [Required] |
| [Mobile number] | [To send delivery updates by SMS] | [Required] |
| [Email address] | [To send your invoice] | [Required] |
| [Email address] | [To send offers and new products, about twice a month] | [Optional] |
Who else sees it. We share it only with companies that help us provide the service: [e.g. our delivery partner, payment gateway and email provider]. They may use it only for that.
How long we keep it. [Until your order is complete and returns have closed, and invoices for as long as tax law requires.]
Changing your mind. You can withdraw consent for anything optional at any time at [link], or by [replying STOP / emailing address]. It takes effect within [number] days. What we did before you withdrew stays lawful.
Your rights. You can ask us for a summary of your data and who we shared it with, ask us to correct or erase it, nominate someone to act for you, or raise a grievance, at [link to request page]. We reply within [number, at most 90] days.
Questions. Contact [name or role] at [email] or [phone].
Complaints. If you aren't satisfied with our reply, you can complain to the Data Protection Board of India at [the Board's website].
Where should the notice appear?
- Right where you collect the data: beside the form or checkout, before the person submits it.
- With one unticked checkbox per optional purpose, next to the item it covers. Required items need no checkbox if the service can't work without them, but they still go in the notice.
- On your requests page and linked from your footer, so people can find it again.
What about customers you already have?
If people consented before the Act took effect, you must send them a notice with the same contents as soon as reasonably practicable, for example by email or an in-app message (Section 5(2)). You may keep processing their data until they withdraw. Keep a copy of what you sent and when.
Common mistakes
- Vague purposes such as "to improve our services" or "for business purposes". Name the actual use.
- Bundling marketing consent into the terms of service.
- Collecting fields you don't use. If the purpose doesn't need it, don't ask.
- Notices only in English when your customers mainly use another language.
- Changing the wording without keeping the old version. If consent is questioned, you must prove what the person saw (Section 6(10)).
The notice obligations apply in full from 13 May 2027. CyberLetics builds notices with the Rule 3 fields, keeps every version with its translations, and links each consent record to the exact version the person saw. The free website scan is a quick first check of what your site exposes today.