DPDP Compliance Deadline 13 May 2027: What to Do Now
Where 13 May 2027 comes from in the DPDP Rules, which duties start that day, and how to work back from it to a start date for your compliance programme.
14 min readBy Sachin Shirish, Director
Reviewed by Pragya Dwivedi, Associate Director, CISM (ISACA), eWPTX (INE Security)
The DPDP compliance deadline of 13 May 2027 is not a date written into the Rules. It is arithmetic: the Rules were published on 13 November 2025 and most Data Fiduciary duties start eighteen months later. That leaves under six months from today. A full compliance programme for a startup or SME takes 13 to 23 weeks on our published timeline, so a company that has not started is already inside the window where the start date decides whether it finishes in time.
At a Glance
- Where the date comes from: Rule 1(4) of the Digital Personal Data Protection Rules, 2025 brings Rules 3, 5 to 16, 22 and 23 into force eighteen months after publication in the Gazette. The notification is dated 13 November 2025, so the date is 13 May 2027.
- What starts that day: notice, security safeguards, breach intimation, erasure, the published contact for questions, children's data, Significant Data Fiduciary duties, Data Principal rights and cross-border transfer.
- What has already started: the Rules on the Data Protection Board on publication, and Rule 4 on Consent Manager registration on 13 November 2026.
- The working-back figure: our programme for a startup or SME runs 13 to 23 weeks. Counting back from 13 May 2027, that is a start no later than 11 February 2027 at the short end, and 3 December 2026 at the long end.
- What to do this month: find out which personal data you hold and in what role, and book the gap assessment.
Where 13 May 2027 Comes From
The Ministry of Electronics and Information Technology published the Rules as G.S.R. 846(E), in a Gazette notification dated 13 November 2025. Rule 1 sets three commencement points, each counted from that publication rather than given as a calendar date.
Rules 1, 2 and 17 to 21 came into force on publication. Rules 17 to 21 deal with the Data Protection Board: its members' terms of service, its meetings, its functioning as a digital office and its staff. Rule 4, on the registration and obligations of Consent Managers, came into force one year after publication. Everything else that matters to an ordinary business, Rules 3, 5 to 16, 22 and 23, comes into force eighteen months after publication.
Eighteen months from 13 November 2025 is 13 May 2027. That is the date to plan against unless the Central Government amends the Rules, and an amendment would also be published in the Gazette of India, so that is where to check before you lock a plan.
What Comes Into Force on 13 May 2027
The table below lists the Rules that commence on 13 May 2027 and what each one asks of a Data Fiduciary. It is a map, not a substitute for the text: read the Rule itself before you design anything against it.
| Rule | What it requires | Who it lands on |
|---|---|---|
| Rule 3 | A notice that stands on its own, in clear and plain language, with an itemised description of the personal data and the specific purpose | Every Data Fiduciary relying on consent |
| Rule 5 | Conditions for processing by the State and its instrumentalities for subsidies, benefits and services | Government bodies |
| Rule 6 | Reasonable security safeguards at a minimum: encryption or similar, access control, logs and monitoring, backups, one-year retention of logs, contract terms with processors | Every Data Fiduciary |
| Rule 7 | Breach intimation to each affected Data Principal without delay, and to the Board, with a detailed report within seventy-two hours | Every Data Fiduciary |
| Rule 8 | Erasure after the prescribed periods for specified classes, with forty-eight hours' notice to the Data Principal | Data Fiduciaries in the Third Schedule classes |
| Rule 9 | A published contact for questions about processing | Every Data Fiduciary |
| Rules 10 to 12 | Verifiable consent for children and for persons with disabilities who have a lawful guardian, and the exemptions | Data Fiduciaries processing that data |
| Rule 13 | An annual Data Protection Impact Assessment and audit | Significant Data Fiduciaries |
| Rule 14 | Data Principal rights, and a grievance system that responds within a period not exceeding ninety days | Every Data Fiduciary |
| Rule 15 | Conditions on transfer of personal data outside India | Data Fiduciaries transferring data abroad |
| Rule 16 | Exemption for research, archiving and statistical purposes | Those relying on it |
| Rules 22 and 23 | Appeals to the Appellate Tribunal, and the Central Government calling for information | Process rules |
Two rows deserve attention because they take longest to build. Rule 6 asks for logs retained for a year, which means the logging has to be running well before the deadline if you want a year of history on the day. Rule 7 asks for a detailed report to the Board within seventy-two hours, which needs a procedure, named people and a rehearsal, not a policy document. Our guide to DPDP Act breach notification covers who must be told and when.
What Has Already Started
Two of the three commencement points have passed.
The Board provisions took effect on 13 November 2025. They do not create duties for a business, but they mean the body that will hear complaints and impose penalties has its rules of operation in place.
Rule 4 took effect on 13 November 2026. It governs who can register as a Consent Manager and what a registered Consent Manager must do. It does not require a Data Fiduciary to integrate with one. We cover that date and what it means for a business in the DPDP Consent Manager deadline, so we will not repeat it here.
The practical point is that the date that sets your workload is still 13 May 2027.
Working Backwards From 13 May 2027
A deadline only helps if it turns into a start date. Here is how we do that arithmetic, using the timeline we publish for our own DPDPA compliance programme.
For a startup with under ten thousand users, and for an SME or mid-size company, the full programme runs 13 to 23 weeks. For a startup, one to two of those weeks are the gap assessment. Large enterprises with subsidiaries and complex data flows are scoped individually, so there is no single figure to count back from; for them, start now.
Counting back from 13 May 2027:
- At 23 weeks, the latest start is 3 December 2026. This is the figure to use if you have many processing activities, several products, data held by many vendors, or children's data.
- At 13 weeks, the latest start is 11 February 2027. This is the figure only for a company with a small, well-understood data footprint and decisions made quickly.
Neither figure has a margin in it. Holidays, a procurement cycle, legal review of notices and the time your engineers actually have will all push the end date out. Treat 3 December 2026 as the realistic latest start for most companies, and plan to finish before 13 May 2027, not on it.
What to Do Now, in Order
The sequence matters more than the speed, because each step decides the scope of the next.
- Inventory personal data and roles. List each category of personal data, where it is stored, why you hold it, which vendors touch it, and whether you are the Data Fiduciary or a Data Processor for it. Everything else is scoped from this list.
- Run the gap assessment. Compare what you do today against the Act and the Rules that commence on 13 May 2027. The output is a prioritised list of gaps, not a report for a drawer.
- Start the long-lead items first. Logging with one-year retention, the breach procedure with Board and individual notification, and processor contract terms. These take the longest to build, and contract changes depend on the other side.
- Write notices and design consent. Rule 3 asks for an itemised description of the data and the specific purpose. That needs product, legal and engineering together, and it is usually the longest piece of review.
- Build the rights and grievance workflow. A way to receive requests, verify the person, act on them and respond, with a named owner and a published contact.
- Set retention and erasure. Tie each category to its purpose, and if you are in a Third Schedule class, build the forty-eight hours' notice before erasure.
- Test, then close out. Run a breach tabletop, push a rights request through end to end, and check that the evidence exists.
Our DPDP Act compliance checklist goes through each step in more detail, so this section does not repeat it.
Roles Change the Deadline's Weight
The date is the same for everyone, but what it means depends on your role.
If you are a Data Fiduciary, the duties in the table are yours by law, and the Data Protection Board can act on them. If you are a Data Processor for a customer's data, the Act places the duties on the customer, and the customer must engage you under a valid contract. Expect your Indian customers to send revised contracts and security questionnaires before 13 May 2027, asking for breach reporting, safeguards and deletion terms. A processor that has its answers ready wins those conversations; one that does not slows its customers down at the worst moment.
Most technology companies are both: a processor for customer data and a fiduciary for their own employees, applicants, website visitors and sales contacts. Plan for both.
What SecureRoot Does, and Does Not Do
We run the programme described above: data discovery and flow mapping, gap assessment against the Act and the Rules, a consent and notice framework, a Data Principal rights playbook and breach procedure, a retention schedule, and a readiness report. For an SME, the programme also covers implemented safeguards. Our guide range is from ₹1.5 lakh for a startup with under ten thousand users and ₹1.5 lakh to ₹8 lakh for an SME or mid-size company, with a fixed price in writing after scoping. A gap assessment on its own, for a startup, takes under two weeks and falls in a guide range of ₹40,000 to ₹1 lakh. What drives a DPDP price explains what moves a quote within those ranges.
Four limits. There is no DPDP certificate: no body is authorised to certify compliance with the Act, and we cannot certify yours. SecureRoot is not a CERT-In empanelled auditing organisation. We are not a law firm, and questions of legal interpretation belong with your counsel. And no programme guarantees an outcome before the Board; what it gives you is duties met and evidence that they were.
Frequently Asked Questions
Is 13 May 2027 the official DPDP compliance deadline?
It is the date the Rules produce, though they never print it. Rule 1(4) of the DPDP Rules, 2025 says that Rules 3, 5 to 16, 22 and 23 come into force eighteen months after the date of publication in the Gazette, and the Gazette notification is dated 13 November 2025. Eighteen months on from that publication is 13 May 2027. Those Rules carry most of the operational detail a Data Fiduciary needs, including notice, security safeguards, breach intimation, erasure, children's data and Data Principal rights. Two caveats apply. First, the date holds only while the Rules stay as published; the Central Government can amend them, and any amendment would appear in the Gazette of India, so check there before you finalise a plan. Second, the Act's own provisions commence through separate notifications, so for a precise legal position on any single duty, read the commencement notifications with your counsel.
What happens on 13 May 2027 if we are not ready?
From that date the Rules on notice, safeguards, breach intimation, rights and the rest are in force, and the Data Protection Board can inquire into a breach of the Act and impose the penalties the Act sets. There is no grace period written into the Rules after 13 May 2027, and no certificate or registration that a company files to show it is ready. What being unready looks like in practice is more ordinary: a breach with no procedure to notify the Board and the people affected, a rights request with no one to answer it, a notice that does not itemise the data, or customer contracts that ask for evidence you cannot produce. Each of those is a gap someone else can see. We do not predict how the Board will exercise its discretion, and nobody can promise a particular outcome. The safer course is to treat 13 May 2027 as the day the duties are live and to be finished before it.
How long does DPDP compliance take for a startup or SME?
On the timeline we publish for our own programme, a full programme for a startup with under ten thousand users, or for an SME or mid-size company, runs 13 to 23 weeks. For a startup, one to two of those weeks are the gap assessment. Where a company lands in that range depends on how many processing activities and products it has, how many vendors hold its personal data, whether it processes children's data, and how quickly its people can review notices and approve changes. A gap assessment bought on its own takes under two weeks for a startup and three to five weeks for an SME of up to five hundred thousand users. Large enterprises with subsidiaries and complex flows are quoted by phase rather than on a fixed timeline. These are our figures for our own work, not a statutory period; another adviser, or a team doing it in-house, will have its own pace.
When should we start to meet the 13 May 2027 date?
Count back from the deadline using a realistic programme length. At 23 weeks, the latest start is 3 December 2026; at 13 weeks, it is 11 February 2027. Neither date has any slack in it, so holidays, procurement, legal review of notices and engineering availability all push the finish later. For most companies with several products or many vendors, the honest latest start is early December 2026, and a company that starts in February 2027 is betting that nothing slips. The one piece of work that cannot wait is the personal data inventory, because it scopes everything else and costs little to begin. Rule 6 also asks for logs retained for a year, so logging that starts only in May 2027 will not have a year of history behind it on the day. Starting now buys you margin rather than speed, and margin is what usually runs out.
Can SecureRoot certify that we are DPDP compliant by 13 May 2027?
No. There is no DPDP certificate, and no body is authorised under the Act or the Rules to certify that a company complies. Anyone offering a certificate is offering a document of their own making, not a legal status. What we deliver is the programme: data discovery and a flow map, a gap assessment against the Act and the Rules, a consent and notice framework, a Data Principal rights playbook and breach procedure, a retention schedule and a readiness report, plus implemented safeguards for an SME. The readiness report records what was found, what was fixed and what evidence exists, which is what you show a customer asking about your DPDP position. We are also not a law firm, so interpretation of the Act belongs with your counsel. Compliance under the Act is a continuing state you maintain after 13 May 2027, not a test you pass once on that date.
Where to Start
Start with one list: every category of personal data you hold, where it is, why, and in what role. That list scopes the gap assessment and tells you which end of the 13 to 23 week range you are on. If you want it done against your own systems, request an assessment and we will give you a dated plan that finishes before 13 May 2027.
Free Checklist
Get the DPDP Act Checklist
Our DPDP Act checklist: the controls, evidence and decisions the programme turns on, marked up for your scope. Tell us where to send it.
One form, the same notice as every enquiry on this site.
Have a Question About This?
If this raised something specific to your environment, a scoping call is the fastest way to get a direct answer.
We reply within one business day.
See Every Published Price Band