Compliance · India

India’s DPDP countdown: what every business must do before May 2027.

The DPDP Rules, 2025 are now law, and the clock is running. Here’s the phased timeline, the real penalty exposure, and a practical checklist to be demonstrably ready before the deadline.

SemperWise Research Desk 7 min read Compliance
ISO 27001 SOC 2 DPDP HIPAA One control set · 31 mapped categories Access review Scan history Change log Training Evidence collected continuously, not before the audit

For two years, India’s Digital Personal Data Protection (DPDP) Act, 2023 sat on the books without operational rules — a law with teeth but no bite date. That changed in November 2025, when the Ministry of Electronics and Information Technology (MeitY) notified the Digital Personal Data Protection Rules, 2025. The rules convert a broad statute into concrete obligations, and they set a phased clock that ends in mid-2027.

If your organisation collects the personal data of a single Indian resident — a customer email, an employee’s Aadhaar-linked record, a lead-form entry — this timeline now applies to you. The good news: you have a runway. The catch: most businesses badly underestimate how much groundwork “consent, notice, breach-response and vendor governance” actually requires.

The phased timeline, in plain English

The rules take a staggered approach so that startups and smaller enterprises can adapt rather than face overnight liability:

  • November 2025 — Foundational provisions live. The Data Protection Board of India is established, and the framework for registering Consent Managers is switched on.
  • Around November 2026 — The Consent Manager framework becomes operational. Entities that want to act as Consent Managers must be registered with the Board.
  • 13 May 2027 — Full compliance deadline. The substantive obligations and the penalty regime become enforceable for all covered businesses (“Data Fiduciaries”).

In other words, you have until mid-2027 to be demonstrably compliant — and enforcement, once it begins, is not gentle.

Why the penalties should be a boardroom conversation

The DPDP framework carries some of the steepest data-protection penalties in Asia. Failure to implement “reasonable security safeguards” can attract a penalty of up to ₹250 crore, and failure to notify a personal-data breach properly can reach up to ₹200 crore. These are per-instance ceilings assessed by the Data Protection Board — not aggregate annual caps like some global regimes.

₹250 CrMax penalty — inadequate security safeguards
₹200 CrMax penalty — breach notification failure
72 HoursDeadline to report a breach to the Board
13 May 2027Full compliance deadline

For a mid-sized Indian SaaS company or hospital network, a single mishandled breach can therefore become an existential financial event. This is precisely why data protection has moved from a legal footnote to a governance priority.

The breach-notification rule that trips people up

Under the rules, when a personal-data breach occurs, a Data Fiduciary must promptly notify the Data Protection Board and every affected individual, and follow up with a detailed report to the Board within 72 hours (extendable only on justified request). “Promptly” means without avoidable delay — not “after the incident-response dust settles.”

The operational reality: you cannot report a breach in 72 hours if you cannot detect one in 72 hours. Detection, logging and a tested incident-response playbook are the real prerequisites hiding behind this clause.

Your practical DPDP readiness checklist

Drawing on the compliance guidance now circulating among Indian and international law firms, here is a pragmatic sequence:

  1. Map your data.

    Inventory every place personal data is collected, processed, stored and shared — across HR, marketing, product and third-party tools. You cannot protect what you have not mapped.

  2. Rebuild consent and notice.

    Issue clear, standalone privacy notices that state the purpose, data categories, retention period and an easy withdrawal mechanism. Consent must be informed, unambiguous and freely given.

  3. Fix vendor contracts.

    Update Data Processing Agreements so every processor is contractually bound to DPDP-grade security and breach cooperation.

  4. Harden security controls.

    Encryption, access control, logging and monitoring are the backbone of the “reasonable security safeguards” standard.

  5. Stand up a grievance process.

    Appoint a Data Protection Officer / grievance contact and commit to resolving complaints within statutory timelines.

  6. Handle children’s and guardians’ data carefully.

    Verifiable parental or guardian consent is required for processing children’s data.

  7. Write and rehearse a breach-response plan.

    A 72-hour clock is unforgiving; tabletop exercises turn a plan into a reflex.

  8. Get a gap assessment.

    An independent review tells you where you actually stand versus where you think you stand.

Turn a deadline into a competitive advantage

Companies that treat DPDP as a checkbox will scramble in early 2027. Companies that treat it as a trust signal — provable data hygiene, mapped processing, a rehearsed breach playbook — will win enterprise deals that increasingly require exactly this evidence.

SemperWise Research Desk

Compliance & Regulatory Research

Tracks primary sources — regulator notifications, standards bodies and audit guidance — and turns them into practical checklists our delivery teams use on live engagements. Every figure is checked against its original source before publication.

Next step

Talk to us about your next assessment.

A 30-minute call, then a scope document with what is in, what is out and what it costs. No obligation, and no charge for the conversation.