DPDP Compliance Checklist: A Practical Starting Point
A plain-language checklist to organise your DPDP readiness work: data mapping, notices, consent, rights requests, security, vendors and ownership.
India’s Digital Personal Data Protection Act, 2023 (the DPDP Act) changes how organisations are expected to handle personal data. Many teams know they need to act but are not sure where to begin.
This checklist breaks readiness work into areas you can assign, track and discuss with your legal advisers. It deliberately avoids interpreting specific provisions. Use it to organise the work, and rely on qualified counsel for what the law requires of you.
1. Ownership
- One person is accountable for data protection across the organisation.
- Legal, IT, security, product and HR each have a named contact.
- There is a regular meeting or review where decisions are made and recorded.
- Leadership has seen the plan and agreed the budget for it.
Without clear ownership, privacy work drifts between teams and stalls.
2. Know your data
- You have an inventory of the systems that hold personal data, including spreadsheets, shared drives and backups.
- For each system you know what data it holds, whose data it is and why you hold it.
- You know which data is especially sensitive, such as financial, health or identity information.
- You know how data flows between systems and to outside vendors.
This map is the foundation for everything else. If it is hard to build by hand, see how to find the personal data hiding across your systems.
3. Purpose and minimisation
- Each use of personal data has a clear, written purpose.
- You have checked whether every field you collect is needed for that purpose.
- You have a retention period for each type of data, and a way to delete it when the period ends.
Collecting less is often the cheapest way to reduce risk.
4. Notices and consent
- People are told, in plain language, what you collect and why, before or when you collect it.
- Notices are available in the languages your users actually read.
- Where you rely on consent, it is recorded per purpose, with the notice version the person saw.
- People can withdraw consent as easily as they gave it, and withdrawal reaches every system that needs to know.
Ask your lawyer which of your activities need consent and which rely on other grounds.
5. Requests from individuals
- There is a clear channel for people to ask about their data or ask for it to be corrected or removed.
- You can verify the identity of the person making a request.
- You can find a person’s data across your systems in reasonable time.
- Each request and its outcome is recorded.
6. Security
- Access to personal data is limited to people who need it, and reviewed regularly.
- Sensitive data is encrypted, tokenised or otherwise protected. See tokenisation vs encryption vs masking.
- Access to sensitive data is logged.
- Copies in test environments, exports and spreadsheets are controlled.
7. Incidents
- There is a written plan for handling a breach of personal data.
- Everyone knows how to report a suspected incident, internally and quickly.
- The plan names who decides on notifications and who communicates with affected people.
- You have practised the plan at least once.
Your legal advisers can tell you who must be notified and when.
8. Vendors
- You have a list of vendors that receive personal data from you.
- For each, you know what data they receive, where they store it and how they protect it.
- Contracts have been reviewed by legal for data protection terms.
- You have a way to tell vendors when data must be corrected or deleted.
9. People and culture
- Staff who handle personal data have had practical training.
- Teams know what not to paste into AI tools. See using AI tools at work without leaking personal data.
- New projects ask “what personal data does this need?” at the design stage.
10. Evidence
- Decisions, assessments and changes are written down with dates and owners.
- You can show what notice a person saw and what they agreed to.
- Your records would make sense to someone outside the team.
Good records turn a stressful audit into a routine one.
How to use this list
Do not try to tick everything at once. Score each area as not started, in progress or done. Pick the two weakest areas and the one with the highest risk, and start there. Review progress monthly with your legal advisers, and update the list as your business and the regulatory guidance change.
HR teams can find a focused version of this in the DPDP Act for HR teams.
Sammati collects consent per purpose, handles the privacy requests people send you, and tracks the controls and evidence for standards such as ISO 27001 and SOC 2.
Explore SammatiQuestions people ask
Is this checklist enough to be compliant?
No. It is a way to organise the work and the questions. What your organisation must do depends on what data you hold, why you hold it and how you operate, so a lawyer should review your plan.
Where should a company start?
Start with a map of what personal data you hold, where it lives and why. Almost every other item on the list depends on that map.
How often should we revisit this?
Whenever you launch a product, add a major vendor or change how you use data, and at least once a year. Laws and guidance also change, so keep in touch with your legal advisers.