DPDP India Timeline to May 2027: A Builders’ Checklist

DPDP India Timeline to May 2027: A Builders’ Checklist

3 min read

DPDP · India · compliance · timeline · checklist

Authors

PandaONE Team

Consent Manager registration is open now; broader data-principal rights and fiduciary obligations land in May 2027. What engineering and security should finish before then.

DPDP is not a single “go live” flip. The Act (No. 22 of 2023 — MeitY PDF) allows different commencement dates for different provisions (s.1(2)). Consent Manager registration is already operational news; a major block of data principal rights, data fiduciary obligations, and DPBI inquiry/penalty processes is reported to take effect May 13, 2027.

This checklist is for founders, eng leads, and security owners — not counsel. Portal news: Consent Manager registration.

The two clocks

ClockWhat it means for builders
NowConsent Manager ecosystem standing up; DPBI portal accepting registrations; public list of approved managers later
May 2027Rights + obligations + enforcement machinery widely expected to bind day-to-day product behavior

Treat “now” as architecture time. Treat “2027” as exam day.

Builders’ checklist (ship before the rush)

1. Data map (2–3 weeks)

  • List systems that store personal data: app DB, analytics, support, billing, logs, backups.
  • Mark India data principals vs other regions if you are multi-geo.
  • Flag children’s data or age-gated products (DPDP has special rules).
  • Every collection point: purpose stated, consent free/specific/informed (where required).
  • Withdrawal path that stops processing, not only hides a banner.
  • Prefer machine-readable consent state you can audit later (Consent Managers will push this further — explained here).

3. Principal rights plumbing

Build or verify APIs/workflows for:

  • Access / export of personal data
  • Correction
  • Erasure (and what “erasure” means across replicas)
  • Nomination / account recovery edge cases

4. Security safeguards

“Reasonable security safeguards” is not a slogan. For SaaS that means:

  • Authn/authz that survives IDOR-class bugs
  • Encryption in transit / at rest where appropriate
  • Secrets hygiene, admin path hardening
  • Proof that controls work — scanners alone are weak evidence

More detail: DPDP fiduciary security safeguards. Continuous offensive coverage: AI Security Engineer.

5. Breach notification playbook

  • Detection → triage → who notifies DPBI and affected principals
  • RACI, templates, counsel contact, evidence pack
  • Tabletop once before 2027

6. Vendor & subprocessors

  • Who processes PII for you (email, CRM, cloud, LLM providers)?
  • Contracts and DPA language that match your DPDP posture
  • Know where data physically/logically lives

What “good” looks like 90 days out

  • Written data map reviewed by eng + product
  • Consent withdrawal tested end-to-end on staging
  • At least one proof-backed assessment of PII-bearing apps/APIs this year (VAPT India context)
  • Breach tabletop notes stored where on-call can find them

Avoid these traps

  • Buying a policy PDF and calling it done
  • Ignoring logs/backups in erasure workflows
  • Waiting for Consent Managers to “solve” your own fiduciary duties
  • Treating May 2027 as the first day to inventory data

Keep reading

Confirm dates and obligations against official MeitY / DPBI publications — this checklist tracks public reporting and will need updates as rules evolve.

Sources & further reading

Featured on ScrollLaunchFeatured on CodeHype