DPDP Act Compliance Checklist: A Readiness Walkthrough for Indian Businesses
A practical, specialist-free checklist for India's Digital Personal Data Protection Act — obligation by obligation, with the evidence each one actually needs.
India's Digital Personal Data Protection Act, 2023 (the DPDP Act) changed the baseline for every business that handles personal data of people in India — which, in practice, means almost every business. Unlike sector rules that apply to a few, the DPDP Act applies horizontally: if you collect a name, an email, a phone number, or a customer record, you are a Data Fiduciary with obligations attached.
Most mid-sized Indian companies do not have a privacy office. They have an ops lead, an HR manager, and a founder who now owns a compliance question they did not sign up for. This checklist turns the Act's obligations into a readiness walkthrough you can run without a specialist — the same structure as a full compliance readiness assessment, scoped to DPDP.
First, Know Which Side of the Act You Are On
The Act uses two core roles. A Data Principal is the individual whose data is processed. A Data Fiduciary is the entity that decides why and how that data is processed — that is you. Some organisations are additionally classified as Significant Data Fiduciaries based on the volume and sensitivity of the data they handle, and carry extra obligations such as appointing a Data Protection Officer, commissioning independent audits, and conducting data protection impact assessments. Before anything else, make an honest call about whether your scale puts you in that category, because it changes your checklist materially.
The DPDP Readiness Checklist
Work through each obligation below. For each row, the question is not "do we have a policy?" but "can we produce evidence that it operates?" — the distinction that separates a readiness that survives scrutiny from one that does not.
| Obligation | What you need in place | Common gap |
|---|---|---|
| Notice at the point of collection | A clear, itemised notice stating what data you collect, the purpose, and how a Data Principal exercises rights and withdraws consent | Generic privacy policy that does not map to the data actually collected per form |
| Consent — free, specific, informed, unambiguous | A consent record per purpose, with withdrawal as easy as the original opt-in | Pre-ticked boxes, bundled consent, no withdrawal mechanism |
| Purpose limitation | A register mapping each data set to the specific purpose it was collected for | Data reused for new purposes (marketing, analytics) without fresh consent |
| Data Principal rights | A working channel for access, correction, and erasure requests, plus a named grievance contact | Rights listed in the policy but no owner, no log, no turnaround target |
| Processor contracts | Written agreements binding every vendor that processes data on your behalf | Tail vendors and SaaS tools onboarded with no data-processing clause — see how to run a vendor evaluation |
| Children's data | Verifiable parental consent before processing a child's data, and no behavioural tracking of children | Age not captured at signup, so the obligation cannot even be triggered |
| Breach response | A documented procedure to notify the Data Protection Board and affected Data Principals, tested at least once | Runbook exists on paper, never rehearsed, no notification templates ready |
| Erasure and retention | A process to delete data when consent is withdrawn or the purpose is served | No retention schedule; data kept indefinitely by default |
Grade Each Gap by Evidence, Not Optimism
As you complete the table, grade every line the way an auditor would. A control backed by current, produceable evidence is solid. One where the artifact exists but is stale or partial is indicative. One your team believes is handled but cannot document is needs data — and in a regulatory context, a control you cannot evidence is functionally a control you do not have.
The penalties under the Act are severe enough — running into hundreds of crores of rupees for serious breaches — that the gap between "we think we are fine" and "we can demonstrate it" is exactly the gap worth closing first.
Sequence Remediation by Risk
You will not close everything at once, and you should not try. Rank gaps by regulatory exposure: an unlogged consent trail and an untested breach procedure carry more risk than an un-formalised retention schedule. Assign each high-risk gap an owner, a date, and a definition of done that names the evidence artifact proving closure. If your organisation has no compliance function at all, the companion guide on running a compliance gap analysis without a compliance team covers how to assign and sequence this work across people who already have day jobs.
This checklist is decision-support, not legal advice. The DPDP Act and its implementing Rules carry specifics and timelines that should be confirmed with qualified Indian legal counsel for your situation.
Running the DPDP Diagnostic in Under Four Minutes
Walking this checklist manually — obligation by obligation, form by form, vendor by vendor — is a week of work for someone learning the Act as they go. Treeng's Compliance Scanner runs the same structured diagnostic against your answers in under four minutes, surfacing gaps, rating each by severity, and attaching an explicit evidence grade — solid, indicative, or needs data — to every finding. You get a prioritised gap list ready to hand to your team or your counsel, without the consulting invoice.
Ready to run it on your own data?
Run your DPDP readiness check →