Statute spine · Data fiduciary

DPDP Act, 2023: obligations of data fiduciaries

Audience: privacy owners, product, legal-ops · Part of the chapter map · Last reviewed: March 2026

See also: Compliance portal · Official resources · Guides index

This page is an implementation-facing spine for the Act’s cluster of obligations that fall primarily on data fiduciaries—the party that decides why and how personal data is processed. It is not a substitute for reading the notified statute, rules, and official commentary; confirm exact section numbers and commencement dates in primary law.

Treat this cluster as your program backbone: if notice, consent, purpose limitation, security, retention, and vendor boundaries are weak here, downstream rights-handling and regulator-facing readiness will stay fragile.

Checklists and workflows that map to fiduciary-side duties—run after you confirm current rules and commencement.

What this cluster covers (in plain English)

The Act organizes most operator-facing duties around lawful processing, transparency, consent or deemed consent where applicable, general protection of personal data, specific expectations when children are involved, and elevated expectations for certain significant data fiduciaries. Your job is to translate each theme into owners, systems, and evidence—not slide decks.

What to do next (operational sequence)

  1. Inventory and scope — Identify processing that qualifies as digital personal data in your context and where your organization acts as fiduciary versus as a processor for someone else’s purposes.
  2. Purpose and basis mapping — For each material flow, document purpose, categories, retention intent, and the lawful pathway your counsel supports (consent, legitimate uses, or other bases as legally applicable).
  3. Notice and UX alignment — Align real collection points (forms, apps, helpdesk, imports) with what your notice promises; eliminate silent expansion of purposes.
  4. Security and retention reality check — Verify access controls, logging where appropriate, backup retention, and deletion mechanics match policy—not aspirational diagrams.
  5. Children and high-risk journeys — Flag product surfaces that may reach minors or guardians; design reviews before “we will fix it later.”
  6. SDF-style discipline early — Even if classification is uncertain, adopt documentation and review cadence that scales if expectations rise.

Further reading (primary and hub)