Templates & playbooksUpdated 22 November 20269 min read

DPDP Compliance Roadmap to May 2027

A month-by-month DPDP compliance plan from December 2026 to 13 May 2027, when Rules 3, 5–16, 22 and 23 take effect: inventory, notices, security, breach, retention and rights.

By Suhas Bhairav · Reviewed against the DPDP Rules, 2025 (G.S.R. 846(E), 13 Nov 2025)

Today
22 November 2026
Core rules commence
13 May 2027
Board rules in force since
13 November 2025
Consent Manager rule in force since
13 November 2026
SPDI Rules / s.43A end
13 May 2027 (s.44(2))
Weeks remaining
About 24

Quick answer

The core DPDP Rules, covering notices, security, breach intimation, retention, children's data, rights and cross-border transfers, take effect on 13 May 2027, about six months from now. A realistic plan uses December 2026 for governance and scoping, January for data mapping, February for notices and consent, March for security and breach readiness, April for retention, rights and vendors, and early May for testing and launch.

  • Rules 3, 5 to 16, 22 and 23 commence on 13 May 2027, eighteen months after publication.
  • Rules 1, 2 and 17 to 21 have applied since 13 November 2025; Rule 4 since 13 November 2026.
  • Section 43A of the IT Act and the SPDI Rules continue to apply until 13 May 2027.
  • Data mapping is the critical path: notices, retention and breach readiness all depend on it.
  • Leave the last fortnight for testing and remediation, not for starting new workstreams.

Who this is for: Founders and CEOs, Chief compliance and privacy officers, CTOs and engineering leaders, Programme and project managers, Boards overseeing DPDP readiness

Where things stand on 22 November 2026

The DPDP Rules, 2025 were notified as G.S.R. 846(E) on 13 November 2025, with phased commencement under Rule 1:

PhaseRulesIn force
1Rules 1, 2 and 17–21 (definitions, Data Protection Board)13 November 2025
2Rule 4 (Consent Managers)13 November 2026
3Rules 3, 5–16, 22 and 2313 May 2027

Phase 3 is where nearly every obligation on a business lives: notice (Rule 3), security safeguards (Rule 6), breach intimation (Rule 7), retention and erasure (Rule 8), contact publication (Rule 9), children and guardians (Rules 10–12), Significant Data Fiduciary duties (Rule 13), rights (Rule 14), cross-border transfers (Rule 15), the research exemption (Rule 16), appeals (Rule 22) and government information requests (Rule 23). The corresponding sections of the Act also commence on 13 May 2027.

The transition

Section 44(2) omits section 43A of the IT Act from 13 May 2027. Until then, the SPDI Rules 2011 continue to apply. Run the DPDP programme without dismantling existing SPDI controls before the switch-over.

That leaves roughly 24 weeks. The plan below allocates them month by month.

December 2026: governance, scope and budget

Goal: a funded programme with owners and a clear scope.

  1. Board or leadership briefing. Explain the 13 May 2027 date, the penalty heads (up to ₹250 crore for security failures; ₹200 crore for breach notification and children's obligations) and the plan.
  2. Appoint an owner with authority across legal, security, engineering and product. Name deputies.
  3. Define scope: entities, products, data subject groups (customers, employees, candidates, children), and whether any processing falls within section 17(1)(d) for foreign clients.
  4. Assess special status: Third Schedule thresholds (2 crore users for e-commerce and social media; 50 lakh for online gaming) and likelihood of Significant Data Fiduciary notification.
  5. Budget and resourcing: privacy engineering time, tooling (consent, discovery, ticketing), external counsel and audit. See DPDP compliance cost drivers.
  6. Gap assessment kick-off: compare current SPDI-era practices against each Phase 3 rule.

Exit criteria: signed-off charter, RACI, budget, and a gap register with owners.

January 2027: data mapping and vendor list

Goal: know what personal data you hold, where, why, and who else touches it.

  1. System inventory: run discovery scans across cloud accounts, databases, SaaS tools and log pipelines.
  2. Processing activity register: purpose, lawful ground (consent or section 7 use), data items, systems, processors, locations and retention for each activity.
  3. Children and foreign data flags: tag datasets with under-18 users and data of individuals outside India.
  4. Vendor register: every processor, its role, location, contract status and security evidence.
  5. Log inventory: what logs exist, what they contain, and how long they are kept, because Rules 6(1)(e) and 8(3) require one-year retention.
  6. Quick wins: delete obviously unneeded exports, stale staging copies and orphaned buckets.
  7. Owner sign-off: each system and activity owner confirms their entries, so the inventory can be trusted as the source for notices in February.

Use the data mapping step-by-step guide.

Exit criteria: first-pass inventory covering all production systems, with a list of high-risk gaps prioritised for February to April.

February 2027: notices, consent and children

Goal: every collection point has a compliant notice and valid consent.

  1. Draft notices to Rule 3: standalone, plain language, itemised data, specified purposes and services, and routes to withdraw, exercise rights and complain to the Board. Start from the privacy notice template.
  2. Translate for the languages your users read, since section 5(3) gives the option of English or Eighth Schedule languages.
  3. Rebuild consent UX: per-purpose, unticked, unbundled from terms, with symmetric withdrawal under Rule 3(c)(i).
  4. Consent service: versioned, timestamped consent events and a runtime permission check.
  5. Children: age gate, parent verification under Rule 10, child-safe defaults under section 9(3), and analysis of any Fourth Schedule exemptions.
  6. Legacy users: plan the section 5 re-notice for consents obtained before commencement.
  7. Consent Managers: decide whether to integrate with any Consent Manager that the Board registers under Rule 4.

Exit criteria: notices approved, consent changes in development, child flows designed.

March 2027: security safeguards and breach readiness

Goal: Rule 6 controls in place and a tested Rule 7 process.

Security (Rule 6)

  • Encryption, masking or tokenisation of personal data at rest and in transit (6(1)(a)).
  • Access control: SSO, MFA, least privilege, quarterly access reviews (6(1)(b)).
  • Logging and monitoring of access to personal data with alerting (6(1)(c)).
  • Backups and tested restores (6(1)(d)).
  • One-year retention of the relevant logs and personal data (6(1)(e)).
  • Security clauses in processor contracts (6(1)(f)).
  • Policies, training and ownership (6(1)(g)).

Breach readiness (Rule 7)

  • Write the playbook with roles, deputies and decision rights.
  • Draft templates for the Board's initial intimation, the 72-hour detailed report and Data Principal messages.
  • Confirm you can contact affected users at scale through their account or registered channel.
  • Align with CERT-In's 6-hour reporting for specified cyber incidents.
  • Run a tabletop exercise.

See the breach response playbook.

Exit criteria: control gaps closed or on a dated plan; tabletop completed with lessons logged.

April 2027: retention, rights, contact and vendors

Goal: data lifecycle and Data Principal operations ready to run.

Retention and erasure (Rule 8)

  • Retention schedule per dataset, honouring the one-year minimum for personal data, traffic data and logs under Rule 8(3).
  • Deletion jobs for data whose purpose is served (section 8(7)), with processors instructed to erase too.
  • For Third Schedule platforms, the three-year inactivity clock and the 48-hour pre-erasure notice under Rule 8(2). See building the 48-hour notice.

Rights and grievances (Rule 14)

  • Publish request channels and the identifiers you need.
  • Publish a grievance response period not exceeding 90 days, and staff to meet it.
  • Build the access summary, correction, erasure and nomination workflows.

Contact (Rule 9)

  • Publish the contact person or DPO prominently; add it to every rights response.

Vendors

  • Sign or amend data processing agreements with security, breach notice, retention and erasure clauses.

Exit criteria: retention jobs running in staging, rights workflows tested end to end, contracts signed for critical processors.

1–13 May 2027: test, launch and evidence

Goal: go live on 13 May with evidence that controls work.

  • End-to-end tests: create a test user, give and withdraw each consent, file each rights request, trigger a simulated breach notice, and verify downstream systems behave correctly.
  • Network verification: confirm no marketing tag fires before consent in a clean browser.
  • Launch notices: publish new notices, privacy centre and contact details; start the re-notice campaign for legacy users.
  • Evidence pack: inventory, notices with versions, consent architecture, Rule 6 control evidence, breach playbook and tabletop record, retention schedule, DPAs, training records.
  • Switch-over: retire SPDI-only artefacts only after DPDP equivalents are live.
  • Hypercare: daily review of rights requests and consent metrics for the first weeks.

After 13 May 2027

Run quarterly control testing, refresh the inventory with each release, and track Government notifications under sections 10, 16 and 17(3). An annual cycle using the DPDP audit checklist keeps the programme from decaying.

Further reading on suhasbhairav.com

Before 13 May 2027

Compliance checklist

  1. Brief leadership and appoint an owner

    Secure sponsorship, a budget and a named programme owner in December 2026.

    Rule 1(4)

  2. Complete the data inventory

    Map systems, purposes, processors and retention by the end of January 2027.

    Rule 3(b)(i)

  3. Approve Rule 3 notices

    Finalise itemised, plain-language notices and translations in February 2027.

    Rule 3

  4. Ship consent and withdrawal changes

    Build per-purpose consent and symmetric withdrawal, with records.

    Rule 3(c)(i)

  5. Close Rule 6 control gaps

    Implement encryption, access control, logging, backups and contract clauses by March 2027.

    Rule 6

  6. Test the breach playbook

    Run a tabletop covering CERT-In and Rule 7 timelines before April 2027.

    Rule 7

  7. Implement retention and erasure jobs

    Apply one-year log retention and purpose-based deletion in April 2027.

    Rule 8

  8. Launch rights and grievance operations

    Publish channels, identifiers and a response period of up to 90 days.

    Rule 14

  9. Publish the contact person

    Display business contact details and include them in rights responses.

    Rule 9

  10. Assemble an evidence pack

    Collect documents and test results showing compliance on 13 May 2027.

    Section 8(1)

Key dates

  1. DPDP Rules notified (G.S.R. 846(E)); Rules 1, 2 and 17–21 in force

  2. Rule 4 (Consent Managers) in force

  3. Governance, scope, budget and gap assessment

  4. Data mapping, vendor register and log inventory

  5. Notices, consent UX, children's flows and translations

  6. Rule 6 security controls and Rule 7 breach readiness

  7. Retention, erasure, rights, contact person and vendor contracts

  8. End-to-end testing, evidence pack and launch preparation

  9. Rules 3, 5–16, 22 and 23 in force; section 43A of the IT Act omitted

Answers

Frequently asked questions

When do DPDP obligations for businesses start?

Most obligations start on 13 May 2027. Rule 1(4) brings Rules 3, 5 to 16, 22 and 23 into force eighteen months after the Rules were published on 13 November 2025. That covers notices, security safeguards, breach intimation, retention, children's data, rights, cross-border transfers and Significant Data Fiduciary duties.

Is six months enough to comply with DPDP?

For most organisations, yes, if work starts in December 2026 and the scope is controlled. Data mapping is the critical path, so complete it early. Large organisations with many products and legacy systems may need to prioritise high-risk processing and keep a dated remediation plan for lower-risk gaps.

Do the SPDI Rules still apply before May 2027?

Yes. Section 44(2) of the DPDP Act omits section 43A of the IT Act, which underpins the SPDI Rules 2011, but that omission is operative only from 13 May 2027. Until then, keep existing SPDI policies and security practices in place while building the DPDP programme.

What should we do first?

Appoint an accountable owner with authority across functions, brief leadership, and start the data inventory. Almost every obligation depends on knowing what personal data you hold, why, where and with whom. Without that map, notices, retention schedules and breach scoping will be guesswork.

Which DPDP rules are already in force?

Rules 1 and 2 and Rules 17 to 21, covering the Data Protection Board, have applied since 13 November 2025. Rule 4 on Consent Managers has applied since 13 November 2026. The remaining rules, which carry most business obligations, apply from 13 May 2027.

What happens if we are not ready on 13 May 2027?

The Data Protection Board can inquire into breaches and impose penalties after an inquiry, considering factors such as the nature, gravity and duration of the breach, and mitigation. A documented programme with prioritised, dated remediation is far better than no programme, and a voluntary undertaking under section 32 is available.

Legal references and sources

  • Digital Personal Data Protection Rules, 2025 — Rule 1 (commencement) (official text)
  • Digital Personal Data Protection Act, 2023 — Section 44(2) (official text)
  • Digital Personal Data Protection Rules, 2025 — Rules 3, 6, 7, 8, 9, 10 and 14 (official text)

This guide explains the law for engineering and business teams. It is not legal advice; confirm how it applies to your organisation with qualified counsel, and check the Gazette for later notifications or amendments.

About the author

Suhas Bhairav

Suhas Bhairav

Systems architect and applied AI practitioner who designs production AI systems for Indian and global companies, with a focus on privacy-by-design under the DPDP Act and the EU AI Act.