Home / Blog / DPDP Act checklist
Web DevelopmentDPDP Act Compliance Checklist for Indian Business Websites (2026)
The DPDP Act applies to any website that collects personal data from people in India, and that includes a simple enquiry form. For a business site, DPDP Act compliance mostly means a clear notice, real consent, safe storage, a way to withdraw and delete, and a plan for breaches.

India's Digital Personal Data Protection Act, 2023 has been law for a while, but it became practical on 13 November 2025, when the Government notified the DPDP Rules, 2025. The Rules spell out what a privacy notice must say, how security and breach reporting should work, and how obligations switch on in stages. If your business runs a website, a Shopify store, a WhatsApp enquiry button or even a Google Form, the DPDP Act is now part of your launch checklist.
Timing is the next question. In the notified schedule the main obligations apply from about 13 May 2027. In January 2026 MeitY reportedly sought industry views on cutting that 18 month window to 12 months, mainly for larger data fiduciaries. We found no notification confirming a shorter date, so treat May 2027 as the working deadline and check the current MeitY notice before you plan. Either way, a website cannot be fixed in a weekend, and a few months of preparation is sensible.
This guide is a working checklist for owners and managers, written by a web team rather than lawyers. It explains the DPDP Act in website terms: what to change on your forms, privacy policy, cookie banner, hosting and vendor list. It is general information, not legal advice, so have your lawyer review your final policy. For related groundwork, see our guide to legal and policy pages for Indian online stores.
What the DPDP Act means for a business website
The DPDP Act protects digital personal data: anything that identifies a person and is collected online, or collected offline and then digitised. On a website that means names, phone numbers, email addresses, delivery addresses, IP addresses tied to a user, login details and photos. It also covers data gathered by analytics and advertising tags when it can be linked to a person.
The law uses three terms you will see everywhere. The Data Principal is the person whose data it is, such as your customer or enquirer. The Data Fiduciary is the business that decides why and how the data is used, which is you. A Data Processor handles data on your behalf, such as your hosting company, email tool, payment gateway or CRM.
Under the law the fiduciary carries the responsibility, even when a processor holds the data. That one idea drives most of the checklist: you must know where visitor data goes and have the right arrangements with each vendor.
The Act also reaches beyond India in one case: if you offer goods or services to people in India from abroad, the law can apply to you. An overseas brand selling to Indian customers through a Shopify store should read this guide too.
DPDP Act timeline and penalties
The Rules were notified in November 2025 and switch on in phases. Based on the law-firm and government summaries we checked, the pattern is below. Confirm the final dates on the MeitY website before you commit to a plan, because a shorter timeline was floated in early 2026.
| Stage | What applies | Timing reported |
|---|---|---|
| Immediate | Data Protection Board set up and basic provisions | From 13 November 2025 |
| Consent managers | Registration of consent manager firms | About 12 months, so November 2026 |
| Main duties | Notice, consent, security, breach reporting, erasure, rights of users | About 18 months, so around 13 May 2027 |
On penalties, the schedule to the DPDP Act sets ceilings: up to ₹250 crore for failing to maintain reasonable security safeguards, up to ₹200 crore for failing to notify a breach or for breaching the duties around children's data, and up to ₹50 crore for most other contraventions. These are maximums, set by the Data Protection Board after an inquiry, not automatic fines. Still, they explain why even small businesses are being advised to tidy up early.
The older IT Act privacy rules (the SPDI Rules of 2011) continue to apply until the new duties begin, so a basic privacy policy is not optional today either.
Step 1: map the personal data your website collects
Every compliance checklist starts with a simple inventory. You cannot write an honest notice or delete data on request if you do not know what you hold. Open a spreadsheet and list every place data enters or leaves your site.
- Contact forms, quote forms and newsletter sign-ups, including the ones inside popups.
- Checkout, account creation and login on WooCommerce or Shopify.
- Live chat, WhatsApp click-to-chat and call-back widgets.
- Analytics, advertising pixels and heatmap tools.
- Booking, payment and CRM integrations that receive form entries by email or API.
- Comment sections, review plugins and job application pages.
For each item record four things: which fields you collect, why you need them, where they are stored (including email inboxes and spreadsheets), and who can see them. Many owners are surprised to find that enquiries sit in three places: the website database, an inbox and a staff member's phone.
This map is also the base for a good website security review, so the effort pays twice.
Step 2: write a DPDP Act privacy notice people can understand
The Act requires a notice before or when you ask for consent. Under the Rules it must be a clear, standalone message that lists in itemised form the personal data you collect and the specific purpose for each, and describes the goods or services that depend on the data. It must also give a way to withdraw consent, exercise rights and complain to the Board.
Compare that with the usual template privacy page, which says "we may collect information to improve our services". That vague wording is exactly what the new notice rules are meant to replace. A good notice is short, specific and plain.
- What we collect: name, phone, email, project details.
- Why: to reply to your enquiry and send a quote.
- How long we keep it: for example, 12 months after the last contact unless you become a customer.
- Who receives it: our hosting provider, email service and CRM.
- Your rights and how to use them: email address or form link.
The Act says a consent request should be available in English or any language listed in the Eighth Schedule of the Constitution, and should name a contact person. If your customers mostly read Hindi, offer a Hindi version of the notice. Our own privacy policy is an example of the kind of plain page to aim for, and you should adapt rather than copy it.
Not sure where your forms and tags stand? Ragnar Studio's can review your site against this DPDP Act checklist and list the fixes. See our website maintenance service or send us your URL.
Step 3: fix DPDP Act consent on forms, checkboxes and sign-ups
Consent under the DPDP Act must be free, specific, informed, unconditional and unambiguous, given through a clear affirmative action. For a web form, that translates into a few concrete rules.
- No pre-ticked boxes. The visitor must tick it, or press a button whose label makes the action clear.
- One purpose, one consent. Do not bundle "I agree to be contacted about my enquiry" with "send me offers". Marketing needs its own unticked box.
- Link the notice next to the button, not buried in the footer.
- Ask only for what you need. If you do not need a date of birth or an address to reply to an enquiry, remove those fields.
- Keep a record. Store the time, the form and the notice version the user accepted.
There is one grey area worth knowing. Section 7 of the Act lists legitimate uses where consent is not needed, and one covers data a person voluntarily provides for a stated purpose when they have not objected to its use. Lawyers differ on how widely this applies to a form you built and asked people to fill in, so the safer default is a short notice and a clear consent action next to the button. Whatever you rely on, use the data only for the purpose stated. Use it for newsletters or remarketing and you need fresh consent.
Improving forms also tends to help conversions, as we explain in our guide to getting more leads from your website.
Step 4: handle cookies, analytics and ad tags under the DPDP Act
The DPDP Act does not use the word cookie, and India has no separate cookie law. The practical reading is simple: if a cookie or tag collects personal data, or lets a vendor build a profile of an identifiable person, you need a lawful basis for it. For marketing and advertising tags, that basis is usually consent.
| Tool type | Examples | Safer approach |
|---|---|---|
| Essential | Cart, login, security | Load always, explain in the notice |
| Analytics | GA4, heatmaps | Load after consent, or anonymise IPs |
| Advertising | Meta pixel, Google Ads tags | Block until the visitor opts in |
| Embeds | YouTube, maps, chat | Load on click, or use privacy modes |
A cookie banner that only says "Accept" with no way to refuse does not meet the standard of free and specific consent. Offer an equal "Reject" or "Manage" option, and make the later withdrawal as easy as the original acceptance. If you run Shopify, our walkthrough on adding the Google tag to Shopify is a good point to also check which tags fire before consent.
Step 5: children's data under the DPDP Act
The Act treats anyone under 18 as a child. Before processing a child's personal data you need verifiable consent from a parent or lawful guardian, and you may not track or behaviourally monitor children or target advertising at them. The Rules describe how the parent's identity and age can be verified, and some classes of fiduciary, such as certain educational and healthcare services, get exemptions for specific purposes.
Most business websites are not aimed at children, so the practical question is whether you knowingly collect data from minors. School and college sites, tuition and coaching pages, kids' fashion stores, toy shops and gaming or quiz sites are the usual cases. If this is you, plan for age checks and a parent consent step, and avoid advertising pixels on those pages.
If you are a coaching business, see our solution page for coaching institute websites, which covers enquiry and admission flows where this matters.
Step 6: security, vendors and a breach plan
The Rules expect reasonable security safeguards. In plain terms for a website that means:
- HTTPS on every page, current WordPress core, themes and plugins, and strong admin passwords with two-step login.
- Encryption or masking of sensitive fields, and limited staff access to the form entries.
- Backups that are tested, and server and application logs kept so an incident can be investigated. The Rules refer to retaining such logs for one year.
- Contracts or written terms with each processor, covering security and deletion.
If personal data is breached, the fiduciary must inform each affected person without delay and tell the Data Protection Board. Per the Rules, a more detailed report to the Board follows within 72 hours of becoming aware. A one-page plan helps: who decides, who contacts users, who contacts the host, and which logs to preserve.
Treat plugins as the most common risk. Old form plugins are a frequent route in, so a regular update routine under a website maintenance plan is part of compliance, not just housekeeping.
Step 7: user rights, retention and deletion
Data Principals gain rights that your website needs a way to honour. The Act gives people the right to ask for a summary of the data you hold and who it was shared with, to correct or complete it, to have it erased, to grievance redressal, and to nominate someone to act for them in case of death or incapacity.
Build a simple process before the first request arrives.
- Publish a contact point (an email such as privacy at your domain) and name the person responsible.
- Verify the requester before sharing or deleting anything.
- Respond within a fixed internal deadline, and note it in the notice. The Rules reportedly allow up to 90 days to respond to rights requests, but aim to reply far sooner and check the current text.
- Delete from every place on your map: database, inbox, spreadsheets, CRM and backups when they rotate.
The Act also expects you to erase data when its purpose is served or consent is withdrawn, unless a law requires you to keep it, such as tax and invoice records. Write a retention schedule: enquiries that never convert, for example, might be removed after 12 months. Set a calendar reminder or an automated job so it actually happens.
DPDP Act quick reference checklist
Use this table to review your site in an afternoon. Anything marked "no" becomes a task.
| Area | Check | Done? |
|---|---|---|
| Data map | Every form, tag and integration is listed | Yes or no |
| Notice | Itemised, purpose-based and linked at the point of collection | Yes or no |
| Consent | Unticked boxes, separate marketing consent | Yes or no |
| Cookies | Ad and analytics tags wait for opt-in | Yes or no |
| Children | Age and parent consent flow if relevant | Yes or no |
| Security | Updates, backups, logs, access control | Yes or no |
| Vendors | Processor list and written terms | Yes or no |
| Rights | Contact point and deletion process | Yes or no |
Do not aim for perfection in one pass. A site that clearly follows this checklist in good faith is in a far better position than one that has done nothing.
Common DPDP Act mistakes on Indian websites
- Copying a foreign template. A GDPR policy pasted in without edits mentions the wrong laws and rights. Write for the Indian law and your real data flows.
- Calling the policy "done" when the forms still pre-tick marketing. The page and the behaviour must match.
- Forgetting plugins and tags. Chat widgets, popups and pixels send data to third parties that never appear in your policy.
- Collecting too much. Aadhaar, date of birth or full address on a simple enquiry form invites risk with no benefit.
- Keeping everything forever. Old enquiry sheets in shared drives are a breach waiting to happen.
- Having no one in charge. Name a responsible person even if you are a team of five.
Rules about significant data fiduciaries, who must appoint a data protection officer and run audits, apply to larger or higher risk organisations notified by the Government. Most small business sites will not be in that group, but a fast growing online store should watch for updates.
Getting your site DPDP Act ready with Ragnar Studio's
The website side of the DPDP Act is mostly practical work: rewriting forms, adding a consent banner, tightening plugins and hosting, and publishing a clear notice. Ragnar Studio's, which has delivered 900+ websites, can audit your site against this checklist, fix forms and tags, and set up maintenance so updates and backups do not slip. Our ₹5,999 / $139 five-page website can include a privacy page and consent-friendly forms on request, and larger stores are quoted after a short brief.
We are a web team, not a law firm. We build what your lawyer or consultant specifies, and we can suggest wording for you to have reviewed. Start on our contact page or WhatsApp +91 92865 18510, in English or Hindi. If your site collects data through chat, see our notes on adding an AI chatbot to your website for the privacy questions it raises.
Frequently asked questions
Does the DPDP Act apply to small business websites?
Yes. The DPDP Act applies to any business that processes digital personal data, whatever its size. A small site with an enquiry form is covered, although simpler duties apply than for large platforms. The Rules take a risk based view of security measures, but check the current text for any duties that apply to you.
When do the DPDP Act rules come into force?
The DPDP Rules were notified on 13 November 2025 and apply in stages. The main duties on notice, consent, security and breach reporting are due about 18 months later, around 13 May 2027. A proposal to shorten this window was reported in January 2026, but we found no notification confirming it, so check the latest MeitY notice.
What is the penalty under the DPDP Act?
The Act sets maximum penalties, going up to ₹250 crore for failing to keep reasonable security safeguards. Not reporting a data breach or breaching the children's data duties can reach ₹200 crore, and most other contraventions up to ₹50 crore. The Data Protection Board decides the actual amount after an inquiry.
Do I need a cookie banner under the DPDP Act?
The Act does not mention cookies by name, but if analytics or ad tags collect personal data, you need consent for them. A banner with equal Accept and Reject options, and tags that load only after opt-in, is the safest approach.
Is a contact form covered by the DPDP Act?
Yes, a contact form collects personal data. You should show a short notice near the button saying what you collect and why, ask only for needed fields, and use the details only for the stated reply. Marketing messages need a separate, unticked consent.
Do I have to delete a customer's data when they ask?
Generally yes. Under the Act, a person can withdraw consent and ask for erasure, and you must delete the data unless a law requires you to keep it, such as invoices for tax. Remember to delete from inboxes, spreadsheets and your CRM as well as the website.
Can I use my old GDPR privacy policy for the DPDP Act?
Not as it stands. GDPR wording refers to different bases, rights and regulators. Many ideas overlap, so a GDPR policy is a useful start, but you need to rewrite it for the DPDP Act, with an itemised notice, India-based contacts and a grievance process.
Does the DPDP Act apply to my Shopify or WooCommerce store?
Yes. Checkout, accounts, abandoned cart emails and payment data all involve personal data. List your apps and payment tools as processors, check what each tag collects, and publish a notice at checkout. See our legal pages guide for the policy set a store needs.
Start with the data map, then fix your forms and notice, and work through security and deletion in order. Being ready for the DPDP Act well before the deadline costs far less than a rushed rebuild. If you would like help, talk to Ragnar Studio's, or compare options on our pricing page.
Free quote
Tell us about your project
Fill this short form and send it on WhatsApp. We reply with questions or a quote. Nothing is charged on the website.
- Takes about two minutes
- Goes straight to Ragnar Studio's on WhatsApp
- Prefer email? Write to info@ragnarstudio.com
Services that help with this.
Website maintenance
Updates, backups and security checks that support compliance.
Explore →WordPress development
Consent-friendly forms, policy pages and cleaner plugin setups.
Explore →Shopify store development
Stores with clear policies, checkout notices and tidy app lists.
Explore →Website audit
A review of your site's forms, tags and technical health.
Explore →More from the blog
Ready to start your project?
Tell us what you need. We reply on WhatsApp with questions, next steps and a quote.