New

The new HostCloud is live. Web Hosting for ₹1 for your first month.

Web Hosting for ₹1 · first month

Claim offerClaim
Compliance & Privacy

DPDP privacy notice: what to include on your website (with a template)

Under India's DPDP Act, a privacy notice is not just a footer link. It has to tell people what you collect, why, how to exercise their rights and how to complain. Here is what to include, how to word it and a fill-in template.

5 November 2026 · 9 min read
DPDP privacy notice: what to include on your website (with a template)

DPDP privacy notice: what to include on your website (with a template)

TL;DR: Under the Digital Personal Data Protection Act, a notice has to accompany or come before any request for consent, and it has to be written in clear, plain language. Based on the Act and summaries of the 2025 Rules, a good notice lists the specific personal data you collect, the purpose of each use, what the person can do to exercise their rights and withdraw consent, and how to complain to you and to the Data Protection Board. It should be easy to find, easy to read and, where you ask for consent, available in English or in any of the languages in the Eighth Schedule of the Constitution. This guide gives you a section-by-section checklist and a template. It is general information, not legal advice.

People mix these up.

  • Privacy notice. The message you give a person when you collect their data, telling them what happens to it. Under the DPDP Act, this goes with your request for consent.
  • Privacy policy. The fuller document on your site describing your practices. Many businesses use one page for both, which is fine if it covers the notice requirements and is easy to find.
  • Consent. The person's agreement to specific processing, given through a clear affirmative action such as ticking an unticked box.

A notice does not replace consent. It is what makes consent informed. For a general-purpose policy, see our guide to what a privacy policy and terms of service should cover. This post focuses on what the DPDP notice adds.

What the notice has to say

Summaries of the Act and the Rules describe the required content along these lines:

  1. An itemised description of the personal data you collect. Not "information you provide", but "name, mobile number, email address, delivery address".
  2. The specific purpose for which each item is processed, and the goods, services or uses the processing enables.
  3. How the person can exercise their rights, including withdrawing consent, and a way to contact you to do so. The route should be as easy as the one used to give consent.
  4. How to complain to the Data Protection Board of India if the person is not satisfied.

Check the exact wording of the Rules before finalising, because summaries differ in detail.

Checklist diagram of the sections of a DPDP privacy notice: what we collect, why, who gets it, how long we keep it, your rights and how to complain

Section-by-section checklist

Use these headings. Each one answers a question a visitor might have.

1. Who we are. Your business name, address and contact details for privacy matters. A named contact or role is best.

2. What we collect. A list of data items, grouped by where you collect them: contact form, checkout, newsletter, account creation, support chat, cookies and similar trackers. Include data collected automatically, such as IP address and device information, if you store it.

3. Why we collect it. One line per purpose: "to process your order", "to reply to your enquiry", "to send you our newsletter if you ask for it", "to measure how the site is used". Do not use catch-all purposes like "to improve our business" without explaining.

4. What happens if you do not give it. If a field is optional, say so. If you cannot provide a service without it, say that too.

5. Who we share it with. Categories of recipients such as payment processors, delivery partners, email service providers, hosting providers and analytics providers. Name them where practical.

6. How long we keep it. A retention period or the rule used to decide it, for example "for the duration of your account plus 90 days", or "as long as the law requires for accounting records".

7. Your rights. Access to a summary of your data, correction and erasure, withdrawal of consent, grievance redressal and the right to nominate someone to act for you if you die or become incapacitated.

8. How to use your rights. The email address or form to use, what you will ask for to verify identity and how long you will take to respond.

9. How to withdraw consent. The exact steps: an unsubscribe link, a cookie settings button, an email address. Keep it as easy as saying yes.

10. How to complain. Your grievance contact first, then the Data Protection Board of India if the issue is not resolved.

11. Children. State whether the service is meant for people under 18 and, if not, what you do if you learn that a child has signed up. If it is, describe how you obtain verifiable parental consent.

12. Security. A short, honest statement of the safeguards you use. Avoid claims you cannot support, such as "military-grade security".

13. Changes and date. The date of the last update and how you will tell people about changes.

Where to show it

  • At the point of collection. A short notice and a link next to every form, checkout and sign-up box, not only in the footer.
  • In the cookie banner. The banner should link to the full notice and explain each category of cookies.
  • In the footer and account area. A permanent link on every page, and in account settings for logged-in users.
  • Before the data is submitted. The notice has to be available when you ask for consent, not afterwards.

For tracker and banner configuration, read our guides on DPDP cookie consent for WordPress and cookie consent plugins compared.

Plain language: how to write it

The Act asks for clear and plain language. Some practical rules:

  • Use short sentences and everyday words. Say "we keep your order details for seven years because the law requires it", not "data shall be retained in accordance with applicable statutory obligations".
  • Put the important points first and use headings and bullet lists.
  • Avoid legal jargon unless you explain it.
  • Do not hide opt-outs in the middle of long paragraphs.
  • Test it: ask someone who is not in your business to read it and tell you what you collect and how they would complain.

Language options

The Act provides that a request for consent should be made available in English or in any language listed in the Eighth Schedule of the Constitution. If your customers mostly speak Hindi, Tamil, Marathi, Bengali or another listed language, offering the notice in that language is both helpful and consistent with the Act. A translated notice must say the same thing as the English one, so have a competent translator check it.

For a WordPress site, a multilingual plugin can show the notice in the visitor's language. Keep every version updated at the same time.

A fill-in template

Replace the bracketed parts. Delete anything that does not apply, and add what is missing.

PRIVACY NOTICE
Last updated: [date]

Who we are
[Business name], [address]. For privacy questions, contact [name or role] at [email].

What we collect and why
- Name, email, phone: to reply to your enquiry. Collected through our contact form.
- Name, address, phone, payment status: to process and deliver your order.
- Email address: to send our newsletter, only if you tick the box.
- IP address, device and pages visited: to keep the site secure and to measure how it is used,
  only for analytics if you accept analytics cookies.

If you do not give us this
You can leave optional fields blank. We cannot process an order without your delivery details.

Who we share it with
[Payment gateway], [courier], [email service], [hosting provider], [analytics provider],
only as needed for the purposes above.

How long we keep it
[Enquiries: 12 months]. [Order records: 7 years, as required for accounting]. [Newsletter: until you unsubscribe].

Your rights
You can ask to see a summary of your data, correct it, delete it, withdraw consent, or
nominate someone to exercise your rights on your behalf.

How to use your rights or withdraw consent
Email [address] or use [link]. We will confirm your identity and respond within [X] days.
To withdraw cookie consent, use [Cookie settings link]. To stop emails, use the unsubscribe link.

How to complain
Contact [grievance contact]. If we do not resolve it, you can complain to the Data Protection Board of India.

Children
Our services are not meant for people under 18. If you think a child has given us data, contact us and we will delete it.

Security
We use [HTTPS, access controls, backups, regular updates] to protect your data.

This template is a starting point. A lawyer should review the final version for your business.

Keeping the notice accurate

A notice that does not match what your site really does is worse than none.

  • Review every quarter. Add or remove tools as your stack changes.
  • Update when you add a plugin. A new chat widget, pixel or form plugin may collect new data.
  • Match the cookie banner. The categories in the banner and the notice should agree.
  • Keep a dated archive. Save previous versions in case you are asked what you told people at a given time.
  • Scan your site. Use your browser's network tab, or a scanner, to see which third parties receive data, and check they appear in the notice.

Common mistakes

  • A generic template with the wrong details. Copying another company's policy usually describes tools you do not use.
  • Only a footer link. The notice needs to be available when consent is requested.
  • Vague purposes. "To improve user experience" explains nothing.
  • Burying withdrawal. If it takes three steps to withdraw and one click to accept, you have a problem.
  • Forgetting to name processors. At least list the categories.
  • No grievance contact. People need a real route to complain.
  • Never updating it. The notice goes out of date as your site changes.

FAQs

What is a DPDP privacy notice?

The message you give a person when asking for consent, telling them what personal data you collect, why, how to exercise their rights and how to complain.

Is a privacy policy the same as a notice?

Not exactly. The policy is the fuller document. Many sites use one page for both, provided it contains everything the notice requires and is shown when consent is requested.

Does the notice have to be in English?

Consent requests should be available in English or in any language in the Eighth Schedule of the Constitution. Offer your customers' own language where you can.

Where should I show the notice?

Next to every form and sign-up box, in your cookie banner, in the footer and in account settings.

How detailed must the data list be?

Itemised and specific. List the actual data items rather than a general phrase such as "information you provide".

Do I need a notice if I only have a contact form?

Yes. A contact form collects personal data, so you need a notice that explains what you do with it.

When do these rules apply?

Published timelines say the main obligations begin on 14 May 2027. See our DPDP deadline checklist and confirm dates with the official Rules.

Can I use a free template?

You can start with one, but edit it to match your real data flows, and have a lawyer check it. A copied policy that does not match your site can cause trouble.

Conclusion

A DPDP-ready notice says what you collect, why, who gets it, how long you keep it, how people use their rights and how to complain, in plain language, shown when consent is requested. Start from the template, fit it to what your site actually does and review it whenever your tools change.

HostCloud gives Indian websites the secure hosting foundation that privacy compliance depends on. See the plans at https://hostcloud.in.

Sources:

Related posts