Free 30-minute AI & automation audit with a senior engineer. You keep the notes. Book yours

Software DevelopmentBackend Development 20 Nov 2026

DPDP Act Compliance Checklist for Software Teams: An Engineer's Guide

A DPDP Act compliance checklist for engineering teams: consent records, notices, retention, erasure, breach intimation, children's data and processors.

DPDP Act compliance for software teams means building controls into your apps for India’s Digital Personal Data Protection Act, 2023 and the DPDP Rules, 2025: itemized notices, provable consent and easy withdrawal, rights-request handling, purpose-based retention and erasure, security safeguards with one-year logs, breach intimation, children’s data protections and processor contracts with technical enforcement.

This is engineering guidance, not legal advice. Your legal counsel or Data Protection Officer should decide how the Act applies to your business; this checklist helps you build what they specify.

When do DPDP Act obligations apply?

The Act was passed in August 2023. The DPDP Rules, 2025 were notified on 13 November 2025 and come into force in phases:

Phase Date What applies
1 13 November 2025 Definitions and provisions to set up and run the Data Protection Board
2 13 November 2026 Registration and obligations of Consent Managers
3 13 May 2027 The main Data Fiduciary obligations: notice, consent, security safeguards, breach intimation, retention and erasure, children’s data, Significant Data Fiduciary duties, Data Principal rights, and penalties

As of November 2026, phases 1 and 2 are in force. The government has discussed shortening the runway for phase 3, so check the latest Gazette notifications rather than relying on any article, including this one. For engineering planning, treat 13 May 2027 as the latest possible date, not the target. Retrofitting consent and erasure into live systems takes months.

Who does the DPDP Act apply to?

It applies to processing of digital personal data in India, and to processing outside India where it relates to offering goods or services to people in India. Key roles:

  • Data Fiduciary: decides why and how personal data is processed. Usually your company.
  • Data Processor: processes data on the fiduciary’s behalf. Your cloud provider, email service, CRM, analytics or development vendor.
  • Data Principal: the person the data is about. For a child, this includes the parent or lawful guardian.
  • Significant Data Fiduciary (SDF): a fiduciary the government notifies as significant, based on factors such as volume and sensitivity of data. SDFs have extra duties.
  • Consent Manager: a platform registered with the Data Protection Board that lets people give, manage and withdraw consent across fiduciaries.

The DPDP engineering checklist

Use this as a working list. Each item should end with evidence: a ticket, a test, a log or a document.

1. Data inventory

  • List every system, database, bucket, log store and third-party service that holds personal data.
  • For each data element, record the purpose, lawful basis (consent or a legitimate use under the Act), retention period and who it is shared with.
  • Tag personal data fields in schemas (for example, a column comment or a data catalog entry) so new features cannot add personal data silently.
  • Include logs, analytics events, backups and AI prompts. These are where personal data hides.

2. Notices

  • Show a notice that stands on its own, in clear and plain language, before or at the time you ask for consent.
  • Itemize the personal data collected and the specific purpose for each item, and describe the goods or services enabled by the processing.
  • Include links to withdraw consent, exercise rights and complain to the Data Protection Board.
  • Make the notice available in English or any language in the Eighth Schedule of the Constitution, as the Act allows.
  • Version every notice, and store which version each person saw.
  • Capture consent per purpose, not as one bundled checkbox. No pre-ticked boxes.
  • Ask only for data necessary for the stated purpose.
  • Make withdrawal as easy as giving consent: if consent took one tap in the app, withdrawal should too.
  • Propagate withdrawal to every system and processor that relies on that consent, then stop processing (unless another law requires retention).
  • Be ready to accept consent and withdrawals from a registered Consent Manager.

A consent record should be immutable and queryable:

CREATE TABLE consent_event (
  id               UUID PRIMARY KEY,
  principal_id     UUID        NOT NULL,
  purpose_code     TEXT        NOT NULL,   -- e.g. 'order_fulfilment', 'marketing_email'
  action           TEXT        NOT NULL CHECK (action IN ('GRANTED','WITHDRAWN')),
  notice_version   TEXT        NOT NULL,
  channel          TEXT        NOT NULL,   -- web, android, ios, call_centre, consent_manager
  consent_manager  TEXT,                    -- set when received via a Consent Manager
  occurred_at      TIMESTAMPTZ NOT NULL DEFAULT now(),
  evidence         JSONB                    -- request ID, UI build, locale
);
-- Append only: grant INSERT and SELECT, never UPDATE or DELETE, to the application role.

Current consent state for a person and purpose is the latest event. History is never rewritten.

4. Data Principal rights

The Act gives individuals the right to information about processing, correction, completion, updating and erasure, grievance redressal and nomination.

  • Publish how people can make requests, on your website or app.
  • Build one request queue for access, correction, erasure, nomination and grievance requests, with identity verification.
  • Track every request against its deadline. The Rules set an outer limit of 90 days for responding to grievances; set your internal SLA well inside that.
  • Automate the “access” response: a report of the personal data you process and the processors you share it with.
  • Publish the business contact information of your Data Protection Officer (for SDFs) or a person who can answer questions about processing.

5. Retention and erasure

  • Define a retention period per purpose and data class, approved by legal.
  • Erase personal data when the purpose is served or consent is withdrawn, unless another law requires you to keep it (tax, banking and telecom rules often do).
  • Run scheduled erasure jobs that cover primary databases, search indexes, caches, data warehouses and object storage, and record what was erased.
  • Decide how backups are handled: shorter backup retention, crypto-shredding with per-tenant or per-user keys, or documented expiry.
  • Instruct processors to erase too, and collect confirmation.
  • Certain large e-commerce, online gaming and social media platforms must erase data of inactive users after a set period and warn the user at least 48 hours before erasure. Check whether your platform falls into a listed class.
  • Keep the processing logs the Rules require for at least one year, even after the underlying data is erased. Design log formats so that this does not mean keeping full personal data.

6. Security safeguards

The Rules list minimum reasonable security safeguards. In engineering terms:

  • Encrypt personal data in transit and at rest; use masking, obfuscation or tokenization where full values are not needed.
  • Enforce role-based access, least privilege and MFA for admin and production access.
  • Log access to personal data, monitor for unauthorized access, and keep those logs for at least one year.
  • Maintain backups and a tested restore process so data stays available after an incident.
  • Put these safeguards into contracts with your processors.

7. Breach detection and intimation

  • Alert on signals of a breach: unusual exports, access from new locations, mass reads, disabled logging.
  • Keep an incident runbook with named owners.
  • On becoming aware of a personal data breach, inform each affected Data Principal and the Data Protection Board without delay, describing what happened, the likely consequences, mitigation and a contact point.
  • Send the Board a detailed report within 72 hours of becoming aware, unless the Board allows longer.
  • Remember CERT-In’s separate cyber incident reporting direction (six hours for reportable incidents) still applies. Build one workflow that serves both.
  • Generate affected-user lists from your data inventory, not by hand on the night.

8. Children’s data

The Act defines a child as anyone under 18.

  • Obtain verifiable consent from a parent or lawful guardian before processing a child’s data. The Rules describe verification using reliable identity and age details or a virtual token, for example through a DigiLocker-style service.
  • Do not track, behaviorally monitor or target advertising at children.
  • Do not process children’s data in ways likely to harm their well-being.
  • Check with counsel whether an exemption for your class of fiduciary and purpose applies (the Rules list some, for example for certain education and healthcare purposes). Build the age gate anyway.

9. Processors and vendors

  • Engage processors only under a valid contract that covers security, breach notification to you, erasure and sub-processors.
  • Keep a register of processors per purpose. Your rights-request “access” response depends on it.
  • Technically limit what each processor receives: send IDs instead of names, minimize fields in webhooks and analytics events.
  • Review AI and LLM providers as processors: what they log, how long they retain prompts, and in which region.
  • Watch cross-border transfers. The Act allows transfers except to countries the government restricts, and sectoral rules (for example, RBI’s payment data storage requirements) still apply.

10. Significant Data Fiduciaries

If you are notified as an SDF, expect extra duties: an India-based Data Protection Officer, an independent data auditor, a periodic Data Protection Impact Assessment and audit, due diligence that algorithmic software does not risk Data Principals’ rights, and possible restrictions on transferring specified data outside India. Build audit evidence into your systems early; it is much harder to reconstruct later.

What are the penalties under the DPDP Act?

The Act’s Schedule sets maximum penalties per instance: up to ₹250 crore for failing to take reasonable security safeguards to prevent a breach, up to ₹200 crore for failing to notify a breach or meet children’s data obligations, and up to ₹50 crore for other breaches of the Act or Rules. The Board decides actual amounts based on factors such as nature, gravity and mitigation.

From our projects

We build these controls as part of our DPDP Act compliance engineering service, alongside your legal counsel. The patterns come from platforms we have already shipped:

  • FinAIQ, our AI accounting platform, isolates each firm’s data with PostgreSQL row-level security and keeps audit history tables, soft deletes and role- and folder-level permissions across 79 data entities.
  • Sikka Exchange runs document-and-selfie KYC through a purpose-built review console with audit logs and webhook logs.
  • FlexySure captures digital KYC with document upload and national-ID verification.

Most DPDP work lands in existing backend services and mobile apps, which is why we treat it as engineering, not paperwork.

If you want a second pair of eyes on your DPDP plan, we offer a free 30-minute review of your data flows and gap list. Get in touch and bring your counsel’s requirements; we will tell you what it takes to build them.

FAQ

Is the DPDP Act in force now?

Partly. As of November 2026, the Data Protection Board provisions and Consent Manager registration are in force. The main Data Fiduciary obligations apply from 13 May 2027 unless the government changes that date.

No. The Act also allows certain legitimate uses without consent, such as data a person voluntarily provides for a specified purpose, employment purposes and legal obligations. Your counsel should decide which basis applies to each purpose, and your systems should record it.

How fast must we report a personal data breach?

Inform affected people and the Data Protection Board without delay, and send the Board a detailed report within 72 hours of becoming aware. CERT-In’s six-hour reporting direction may also apply.

Does the DPDP Act require data localization?

Not generally. Transfers outside India are allowed except to countries the government restricts, but Significant Data Fiduciaries and sectors such as payments may face stricter rules.

Is a privacy policy enough for DPDP compliance?

No. You also need versioned notices, consent records, working withdrawal, rights workflows, erasure jobs, security logs and a breach process, built into your software.

Free AI audit Let’s talk