For years, Indian businesses running websites had relatively light formal obligations around personal data compared with businesses in Europe. That has changed. The Digital Personal Data Protection Act, 2023, usually called the DPDP Act, sets out a comprehensive framework for how organisations collect, use, store and protect digital personal data. The rules implementing the Act were notified in November 2025, with obligations coming into force in phases over the following months.
Every business website collects personal data: names and email addresses from contact forms, phone numbers from enquiry forms, addresses and order details from online stores, IP addresses in logs and analytics. That makes the DPDP Act relevant to almost every Indian business with a website, from a small clinic to a large e-commerce store, and to foreign businesses processing data of people in India in connection with offering goods or services to them.
This article explains the key concepts in practical terms and the steps WordPress site owners can take. It isn’t legal advice. Rules, timelines and official guidance continue to develop, so check the current position and consult a qualified professional for your specific situation.
Key terms in plain language
- Data principal: the individual the data is about, such as your customer or website visitor.
- Data fiduciary: the organisation that decides why and how personal data is processed. If you run a business website, that’s usually you.
- Data processor: an organisation that processes data on your behalf, such as your hosting company, email marketing service or CRM provider.
- Personal data: any data about an individual who can be identified by or in relation to it.
- Consent manager: a registered entity that helps individuals give, manage and withdraw consent, a concept introduced by the Act.
The main obligations, translated for websites
1. Give clear notice
Before or when collecting personal data based on consent, you must tell people what data you’re collecting and why, how they can exercise their rights and how to complain. The notice must be clear and understandable on its own, and people should be able to access it in English or one of the languages in the Eighth Schedule of the Constitution.
On a website, that means:
- A clear privacy notice, written in plain language
- Short notices near forms explaining what the form data will be used for
- Links to the full notice wherever data is collected
2. Get valid consent where consent is the basis
Under the Act, consent must be free, specific, informed, unconditional and unambiguous, given through a clear affirmative action, and limited to the data necessary for the specified purpose. It must be as easy to withdraw consent as it was to give it.
For websites, this has practical implications:
- No pre-ticked boxes for marketing or optional processing.
- Separate consent for separate purposes. Agreeing to be contacted about an enquiry shouldn’t automatically mean agreeing to marketing emails.
- Easy withdrawal. Unsubscribe links in every marketing email, and a simple way to withdraw other consents.
- Collect only what’s needed. If a contact form asks for a date of birth that you never use, remove the field.
The Act also recognises certain legitimate uses where consent isn’t required, such as when someone voluntarily provides data for a specific purpose and hasn’t objected. How these apply depends on the situation, which is one reason professional advice is valuable.
3. Protect the data
Data fiduciaries must take reasonable security safeguards to prevent personal data breaches. For a WordPress site, that’s the familiar security basics, now with legal weight:
- HTTPS across the whole site
- Up-to-date WordPress core, plugins and themes
- Strong passwords and two-factor authentication for administrators
- Limited access to data, with appropriate user roles
- Secure, encrypted backups
- Careful choice of plugins and processors
- Logging and monitoring to detect incidents
4. Report breaches
If a personal data breach occurs, the Act requires notifying the Data Protection Board and affected individuals, in the form and manner prescribed by the rules. A hacked WordPress site that exposes customer data is exactly the kind of event this covers. Have an incident response plan that includes assessing whether personal data was affected.
5. Respect data principals’ rights
Individuals have rights including access to information about their data, correction and erasure, grievance redressal and nominating someone to exercise rights on their behalf. You need a way to receive and handle these requests, such as a dedicated email address or form, and a process for responding within the timeframes set by the rules.
WordPress’s built-in personal data export and erasure tools, under the Tools menu, help with requests concerning data stored in WordPress. Remember that data may also live in your email inbox, CRM, email marketing platform and backups.
6. Delete data when it’s no longer needed
Personal data should be erased once the purpose is served and consent is withdrawn, unless retention is required by law. That means setting retention periods: for example, deleting old form submissions after a defined period, removing inactive accounts and not keeping data indefinitely just in case.
7. Manage processors through contracts
You remain responsible for data processed on your behalf. Use processors you trust and have appropriate agreements with them. Hosting, email delivery, payment gateways, analytics and CRM providers all count.
8. Children’s data
Processing personal data of children, defined as under 18, requires verifiable consent from a parent or lawful guardian, and certain processing, such as tracking, behavioural monitoring and targeted advertising directed at children, is restricted. Websites for schools, tutoring, children’s products and similar services need particular care.
A practical checklist for WordPress sites
- Map your data. List every form, plugin and service that collects personal data, what it collects and where it goes.
- Remove unnecessary fields. Collect only what you need.
- Update your privacy notice in plain language, covering purposes, rights, grievance contact and processors.
- Add short notices to forms, linking to the full notice.
- Separate marketing consent with an unticked checkbox and record when and how consent was given.
- Review cookies and trackers. Load non-essential trackers only with consent where required, using a consent management tool.
- Set retention periods and clean up old data in WordPress, email and other tools.
- Strengthen security and document your safeguards.
- Create a process for requests and grievances, with a named contact.
- Prepare a breach response plan, including notification steps.
- Review processors and their data protection terms.
Plugins and tools that help
- Form plugins with consent checkboxes, entry retention settings and integration with WordPress privacy tools
- Consent management plugins that block non-essential scripts until consent is given and log consent
- Security plugins for hardening, monitoring and login protection
- WordPress privacy tools for export and erasure requests
No plugin makes a site compliant on its own. Compliance depends on what you collect, why and how you handle it.
What about businesses outside India?
The Act applies to processing of digital personal data within India, and to processing outside India if it’s in connection with offering goods or services to people in India. Businesses outside India with Indian customers should review whether and how it applies to them.
Staying current
Because the rules are being implemented in phases and further guidance may follow, set a reminder to review your compliance periodically, and follow updates from the Ministry of Electronics and Information Technology and the Data Protection Board. Treat this as an ongoing process, not a one-time task.
A worked example: a coaching institute
A coaching institute in Jaipur ran a WordPress site with an enquiry form, a free demo class registration, a WhatsApp chat button, Google Analytics, Meta advertising pixels and a student login area. Many of the people filling in forms were parents enquiring for their children, and some students using the login area were under 18.
Their review started with mapping each data flow. The enquiry form asked for date of birth, which they never used, so it was removed. The demo registration form gained a short notice explaining that details would be used to schedule the class and follow up about courses, with a separate unticked checkbox for promotional messages. Advertising pixels were reviewed with particular care because of the student audience, and the institute decided to stop loading them on pages aimed at students. A grievance contact was added to the privacy notice and footer, and a simple request form was created for access and correction requests. Old enquiry entries more than a year old were deleted, and the form plugin was configured to remove entries automatically after that period.
None of these steps required major technical work. Most of the effort went into understanding what the site collected and deciding what was genuinely needed.
Frequently asked questions
Does the DPDP Act apply to small businesses?
Generally yes, if they process digital personal data. Some exemptions may apply to certain categories as notified by the government, so check current rules.
Do I need a cookie banner under the DPDP Act?
The Act focuses on consent and notice for personal data processing. Where trackers process personal data based on consent, you’ll need a way to obtain and manage that consent, which in practice often means a consent tool.
Is a privacy policy enough?
A privacy notice is required, but compliance also involves consent practices, security, retention, rights handling and breach response.
What are the penalties?
The Act provides for significant financial penalties for breaches of its obligations, with amounts depending on the nature of the violation. Check the current schedule in the Act.




