Data Protection | DPDP Rules 2025
DPDP Rules 2025: The Compliance Timeline Indian Businesses Are Working Against
For two years after the Digital Personal Data Protection Act was passed in 2023, Indian companies had a convenient excuse for inaction. The Act existed, but the Rules that would make it operational did not. That excuse disappeared on 13 November 2025, when the Ministry of Electronics and Information Technology notified the Digital Personal Data Protection Rules, 2025 through Gazette notification G.S.R. 846(E). The countdown that began that day is now more than halfway through, and most organisations we speak to have used very little of it. If your DPDP compliance programme is still a slide in a governance deck rather than a funded project, the remaining window is tighter than it looks.
What makes this regime unusual is that it does not arrive all at once. The Rules commence in three distinct stages, and a lot of confusion in the Indian market comes from treating them as a single deadline. Teams that have mapped their data privacy obligations against the correct stage are budgeting sensibly. Teams that have not are either panicking about requirements that do not yet apply, or relaxing about requirements that already do. The same confusion shows up when companies assume an existing ISO 27701 certificate automatically satisfies the statute, which it does not, although it covers a meaningful share of the groundwork.
Table of Contents
What actually commenced in November 2025
The first tranche was structural rather than operational. Rules 1, 2 and 17 to 21 took effect immediately on notification. Their practical consequence was the formal establishment of the Data Protection Board of India, along with the provisions governing how the Board is composed, how it conducts proceedings, and how complaints reach it.
For most businesses this imposed no direct obligation. It did, however, create the body that will eventually decide whether you complied, and it opened the channel through which individuals can raise grievances. The regulator has existed since November 2025. The substantive duties it will enforce simply had not switched on yet.
What changed on 13 November 2026
Twelve months after notification, Rule 4 and Section 6(9) came into force. These govern the registration of Consent Managers, the entities that will let an individual grant, review and withdraw consent across multiple organisations from a single interface.
This milestone is widely misread. Rule 4 does not require an ordinary business to register as anything, to appoint a Consent Manager, or to rebuild its consent flows. It applies to the narrow class of companies that intend to operate as Consent Managers themselves, and the bar is deliberately high: incorporation in India under the Companies Act 2013, audited net worth of at least two crore rupees, demonstrable technical and operational capacity, fit-and-proper management, and genuine independence from the Data Fiduciaries whose consent it carries.
The relevance for everyone else is indirect but real. From 13 May 2027, individuals acquire the right to route their consent decisions through a registered Consent Manager. Any organisation that cannot ingest and act on a withdrawal arriving through a third party interface will be unable to honour that right. Vendor claims deserve scrutiny here, because a consent management platform sold as software is not the same thing as a Consent Manager registered with the Board.
The deadline that matters: 13 May 2027
The bulk of the regime, Rules 3 and 5 to 16 along with Rules 22 and 23, commences on 13 May 2027. This is the date on which notice requirements, consent standards, security safeguards, data principal rights, breach notification duties and the Board's penalty powers all become live together.
| Stage | Date | What commences | Who it binds |
|---|---|---|---|
| Phase 1 | 13 Nov 2025 | Rules 1, 2, 17 to 21: Data Protection Board constituted, procedural provisions | The regulator |
| Phase 2 | 13 Nov 2026 | Rule 4 and Section 6(9): Consent Manager registration | Companies seeking Consent Manager status |
| Phase 3 | 13 May 2027 | Rules 3, 5 to 16, 22, 23: notice, consent, safeguards, rights, breach reporting, penalties | Every Data Fiduciary processing personal data in India |
What the final phase actually requires
Three features of the final phase deserve particular attention. Rule 3 sets out what a privacy notice must contain and requires it to stand on its own, written in plain language rather than buried inside terms of service. Rule 7 governs breach notification, including an obligation to inform affected individuals within 72 hours once the Board has been notified. Rule 10 imposes verifiable parental consent requirements for processing children's data, which materially affects edtech, gaming, and consumer platforms with younger user bases.
No exemption by size
There is no size exemption. A forty person SaaS company in Pune carries the same core obligations as a listed bank, which is a sharp departure from how Indian regulation usually scales. The penalties run to two hundred and fifty crore rupees for the most serious categories of failure, and the Board is already operational rather than being stood up alongside enforcement.
How the Rules sit alongside sectoral regulation
Indian organisations rarely face the DPDP Act in isolation. Banks and NBFCs already operate under RBI directions on data localisation, outsourcing and cyber incident reporting. Hospitals and diagnostic chains work within health record frameworks. Insurers answer to IRDAI, and listed entities to SEBI. None of those regimes is displaced by the DPDP Act, and in several places the obligations stack rather than overlap neatly.
The reporting clocks are the clearest example. An organisation that suffers a personal data breach may owe CERT-In a report within six hours under the 2022 directions, the Data Protection Board a notification under Rule 7, and affected individuals a communication within seventy two hours of that notification. A sectoral regulator may want its own report on a different timetable. Companies that treat breach notification as a single legal task usually discover during their first real incident that it is four tasks with four audiences and four formats.
Overlapping reporting clocks
Retention is the second friction point. Several Indian laws require records to be held for defined periods, while the DPDP Rules require erasure once the specified purpose is no longer being served. These are reconcilable, but only if retention schedules are written at the level of individual data categories rather than as a blanket policy. A statement that the company keeps everything for eight years because tax law says so will not survive scrutiny when applied to marketing contact lists.
What a realistic programme costs
Budget conversations tend to stall because leadership expects either a software purchase or a legal opinion, and the work is neither. For a mid sized Indian company, the effort divides roughly into discovery and data mapping, policy and notice redesign, technical remediation around access control, logging, consent capture and erasure, contract renegotiation with processors, and training. Discovery is usually underestimated and technical remediation is usually the largest line.
The useful planning assumption is that remediation takes longer than assessment. An organisation starting a readiness assessment now has time to finish both before May 2027. An organisation starting the assessment in late 2026 will likely be implementing fixes under deadline pressure, which is where cost and disruption climb.
Where Indian companies are losing time
Across the readiness assessments we run, the delays cluster in a small number of predictable places.
- Nobody owns the programme. Privacy sits between legal, IT and security, and work stalls in the gaps between them.
- The data inventory does not exist. Organisations cannot state, with evidence, what personal data they hold, where it sits, which vendor touches it, or why it was retained.
- Consent was collected historically under terms that would not meet the Rule 3 notice standard, and nobody has decided whether to re-consent or re-paper.
- Processor contracts have not been reviewed. A data fiduciary remains accountable for what its vendors do, and most existing agreements were not drafted with the DPDP Act in mind.
- Erasure is theoretical. Deleting a record from a production database rarely deletes it from backups, analytics warehouses, CRM exports and shared drives.
- Breach response has not been rehearsed against a 72 hour clock.
Using the remaining months well
The sequence that works is unglamorous. Begin with discovery, because every other decision depends on knowing what you actually hold. Classify what you find, then map each category to a lawful basis and a defined retention period. Only then redesign notice and consent, because redesigning them before you know your processing landscape produces a notice that does not describe reality.
Where existing certification helps
Security safeguards can run in parallel, and this is where existing certification earns its value. An organisation with a working ISO 27001 management system has already built access control, logging, incident response and vendor assessment processes that Rule 6 expects. The gap is usually narrower than leadership fears, provided the scope of the certificate actually covers the systems holding personal data.
Multinational groups should resist the assumption that an existing European programme transfers cleanly. The GDPR comparison is useful as a starting point, but consent under the Indian statute is a narrower instrument, the legitimate interest basis familiar from Europe has no direct equivalent, and the notice requirements are prescriptive in ways the GDPR is not.
Final Thoughts
If you want an independent read on where your organisation stands against the May 2027 obligations, our consulting team runs structured DPDP readiness assessments that produce a gap register, a remediation plan and a realistic cost estimate. Talk to us before the deadline compresses your options.
Frequently Asked Questions
When is the DPDP compliance deadline in India?
Full substantive compliance is due on 13 May 2027, eighteen months after the DPDP Rules 2025 were notified on 13 November 2025. That is the date on which notice, consent, security safeguards, data principal rights, breach notification and the Board's penalty powers all take effect together.
Have the DPDP Rules actually been notified, or are they still in draft?
They are final. The draft was published for consultation on 3 January 2025, and the Rules were notified on 13 November 2025 through Gazette notification G.S.R. 846(E).
Does my company need to register as a Consent Manager?
Almost certainly not. Rule 4 registration applies to companies that want to operate as Consent Managers, an infrastructure role requiring India incorporation and audited net worth of at least two crore rupees. Ordinary Data Fiduciaries do not register.
Is there a grace period after May 2027?
No grace period has been announced, and none should be assumed. The eighteen month transition was itself the grace period, and the Data Protection Board has been operational since November 2025.
Do small companies get an exemption?
The Act does not exempt organisations by size or turnover. Certain startups may receive relief from specific obligations by government notification, but the core duties around notice, consent, security and breach reporting apply regardless of headcount.
What are the penalties for non-compliance?
The DPDP Act provides for penalties of up to two hundred and fifty crore rupees for the most serious failures, including inadequate security safeguards that result in a personal data breach.








