India's data protection law has been on the books since August 2023, and for most online stores it has stayed in the "later" pile. Later now has a date. Most duties under the Digital Personal Data Protection Rules apply 18 months after the Rules were published in November 2025, which puts the deadline in May 2027.
Six months sounds like a lot. It is not, if the work includes rewriting checkout consent, finding every place customer data is copied to, and building a way to report a breach within 72 hours. Those are build tasks, not policy documents.
The law has been in the news lately for a different reason: news publishers have challenged parts of it in the Supreme Court, and the government has said it is open to changes to protect journalism. None of that changes what an online store has to do. This is that list.
This is a practical summary for store owners, not legal advice. Take your lawyer through the specifics.
When does what apply?
| Phase | Date | What applies |
|---|---|---|
| Immediately | 13 November 2025 | Definitions and the Data Protection Board |
| After 12 months | November 2026 | Registration and duties of Consent Managers |
| After 18 months | May 2027 | Notice, security safeguards, breach reporting, retention and erasure, contact details, children's data, data principal rights and the rest |
The government's own explainer describes an "eighteen-month period for phased compliance". MeitY floated shortening that window earlier this year, but no amendment had been notified when I wrote this. Plan for May 2027 and treat any earlier date as a risk to watch.
Does it apply to a small brand?
Yes. The core duties apply to any business that decides why and how digital personal data is processed. The law calls this a Data Fiduciary, and it sets no size threshold for the basic duties. If customers type their name, phone number and address into your checkout, you are one.
That data also travels. A typical D2C order touches the storefront, the payment gateway, the shipping partner, the WhatsApp or SMS tool, the email platform, the CRM, a reviews app and a spreadsheet someone exports every Monday. Each of those that processes data on your behalf is a Data Processor, and under the Act you remain responsible for what they do with it.
What does an online store need to build?
1. A map of where customer data goes
Every later step depends on this. List each system that collects or receives customer data, what data it holds, why, and who can access it. Include the exports. The spreadsheet on a laptop is usually the weakest point.
2. A proper consent notice
Under the Rules, the notice must be separate from other information, clear and in plain language. It must list the personal data collected and the specific purpose, and explain how to withdraw consent, exercise rights and complain to the Data Protection Board. It must be available in English and, on request, in any of the 22 languages in the Eighth Schedule.
For a store, the practical change is separating purposes. Using an address to deliver an order is one thing. Adding the same customer to marketing messages is another purpose, and it needs its own clear choice. A pre-ticked box buried in checkout will not do. The Act also requires that withdrawing consent be as easy as giving it, so "unsubscribe" cannot be harder than "subscribe".
3. Reasonable security safeguards
The Rules list the kind of measures expected: encryption, masking or obfuscation of personal data, access controls, logging and monitoring of access, backups and continuity, and keeping logs for at least a year. Your contracts with processors should require the same.
For most stores, that means: two-factor authentication on every admin panel, staff accounts that see only what their role needs, customer exports that are logged and limited, and logs you can actually search. Failing to maintain reasonable safeguards carries the highest penalty in the Act, up to ₹250 crore.
4. A breach plan that can meet 72 hours
If personal data is breached, you must tell affected customers without delay, in plain language: what happened, the likely impact, what you have done and who to contact. You must also tell the Data Protection Board, with a detailed report within 72 hours of becoming aware.
This sits alongside CERT-In's existing rule to report specified cyber incidents within 6 hours (see CERT-In's AI agent advisory). In practice, one incident plan should cover both clocks. Write down who decides, who drafts the customer message, and who files with whom, before you need it.
5. Retention and erasure rules
Personal data must be erased once its purpose is served, unless a law requires you to keep it, as tax and invoicing rules often do. The Rules add a fixed three-year limit and 48 hours' notice before erasure for certain large classes, including e-commerce entities with at least 2 crore registered users in India. Most D2C brands are well below that, but the general duty still applies: decide how long you keep each kind of data, and make the system actually delete it.
6. A contact point and a grievance process
You must publish contact details for privacy questions, a designated person or a Data Protection Officer, and respond to grievances within 90 days. Customers can ask to access, correct or erase their data. A shared inbox is fine, as long as someone owns it and requests are tracked.
7. Children's data, if it applies
Processing a child's data needs verifiable consent from a parent or guardian. If your store sells to parents, the buyer is usually an adult and this rarely applies. If accounts, apps or loyalty schemes can be used by under-18s, it does.
A six-month plan
| When | What |
|---|---|
| November | Map data: every system, export and processor. Name an owner for privacy |
| December | Rewrite the consent notice; separate order and marketing consent at checkout, signup and WhatsApp opt-in |
| January | Admin access review: two-factor authentication everywhere, role-based access, export logging |
| February | Processor contracts: gateway, shipping, messaging, CRM and apps. Remove tools nobody uses |
| March | Retention rules per data type, and deletion that actually runs |
| April | Breach plan covering CERT-In's 6 hours and the Board's 72 hours; a dry run; publish contact details and a grievance process |
The hardest month is usually the first. Most businesses find more copies of customer data than they expected.
Where we help
Most of this list is build work: consent at checkout, access controls, logging, deletion that runs, and fewer systems holding the same data. That is how we build Ecommerce Websites at INovaBeing, with data flows designed in from the start rather than added later.
If you do not yet know where your customer data goes, a Technology Diagnostic maps your systems, integrations and data flows. It is a sensible step one for the plan above.
What I take from this
The DPDP Act is often discussed as a legal project. For an online store it is mostly an engineering one. The law asks you to know where customer data is, use it only for what the customer agreed to, protect it, delete it when you are done, and say so quickly when something goes wrong.
None of that is unreasonable. All of it is hard to do in May if you start in April.




