The Digital Personal Data Protection Act, 2023 (DPDP Act) changes how Indian organisations collect, use and protect personal data. Many teams know they need to act but are unsure where to begin. This roadmap breaks the work into phases you can assign to owners and track.
It is a planning guide, not legal advice. The Act is supported by Rules and commencement arrangements, so confirm the current status and deadlines with official government sources and your legal counsel before fixing your timetable.
What the DPDP Act expects from your organisation#
Under the Act, most businesses are Data Fiduciaries: they decide why and how personal data is processed. Individuals are Data Principals. Companies that process data on your behalf, such as cloud, payroll or marketing vendors, are Data Processors.
In practical terms, a Data Fiduciary needs to be able to show that it:
- Processes personal data only for a lawful purpose, based on consent or a permitted “legitimate use”.
- Gives clear notice about what data it collects and why.
- Lets people exercise their rights and handle grievances.
- Applies reasonable security safeguards.
- Reports personal data breaches to the Data Protection Board of India and affected individuals.
- Erases data when it is no longer needed, unless the law requires retention.
- Takes extra care with children’s data.
Some organisations may be notified as Significant Data Fiduciaries and carry additional duties. We cover those in Phase 4.
Phase 1: Set scope, ownership and a data map#
You cannot protect or justify data you cannot find. Start here.
- Appoint an accountable owner. Choose an executive sponsor and a day-to-day privacy lead. Involve legal, IT, HR, marketing, customer support and procurement.
- Define scope. List business units, products, apps, websites and group entities that handle personal data of individuals in India.
- Build a data inventory. For each process, record what data is collected, from whom, where it is stored, who can access it, which vendors receive it and how long it is kept.
- Record the purpose and basis. For each process, note whether you rely on consent or a legitimate use, and why.
- Run a gap assessment. Compare current practice to each obligation and rate gaps by risk and effort.
The output should be a data register and a prioritised gap list. Everything later depends on their accuracy.
Phase 2: Fix notice, consent and individual rights#
This is the most visible part of compliance, because customers and employees see it directly.
Notice and consent#
- Rewrite privacy notices in plain language. State the data collected, the purpose and how to exercise rights or complain.
- Review every collection point: web forms, mobile apps, onboarding, call recordings, HR forms and events.
- Make consent specific, informed and easy to withdraw. Avoid bundling unrelated purposes into one tick box.
- Keep a record of when and how consent was given, and which notice version the person saw.
- Work out where a legitimate use genuinely applies, and document the reasoning rather than defaulting to it.
Rights and grievances#
- Create a simple request process for access, correction, erasure and grievance redressal.
- Name a contact point and publish how to reach it.
- Define internal steps, owners and response targets, and log every request and outcome.
- Test that systems can actually find, correct and delete a person’s data across databases, backups policy and vendor platforms.
Phase 3: Strengthen security, breach response and vendor control#
The Act requires reasonable security safeguards to prevent personal data breaches. It does not prescribe a specific control set, so you need to choose and justify yours based on risk.
Common building blocks include:
- Access control based on least privilege, with regular access reviews.
- Encryption for data at rest and in transit where appropriate.
- Logging and monitoring of access to systems holding personal data.
- Secure development and change management for apps that collect data.
- Backup, recovery and retention rules aligned to your data register.
Organisations already working to ISO 27001 have a head start, because its risk-based control framework maps well to this requirement. Our article on what to look for in an ISO 27001 toolkit explains how that documentation is typically structured.
Breach response#
Prepare a written plan before you need it. It should cover how incidents are detected and escalated, who decides whether personal data is affected, how the Board and individuals are notified and who handles communications. Run a tabletop exercise at least once and fix what it exposes.
Vendors and processors#
- List every vendor that touches personal data.
- Put data protection terms in contracts: permitted use, security measures, breach notification to you, sub-processors, return or deletion at exit.
- Remember that the Data Fiduciary stays responsible for processing done on its behalf.
Phase 4: Handle children’s data and Significant Data Fiduciary duties#
Children’s data#
If you process data of anyone under 18, the Act requires verifiable consent from a parent or lawful guardian and restricts activities such as tracking, behavioural monitoring and targeted advertising aimed at children. Identify which products could involve minors and decide how you will verify age and consent.
Significant Data Fiduciaries#
The government may notify certain organisations as Significant Data Fiduciaries based on factors such as the volume and sensitivity of data processed. If this may apply to you, plan for additional obligations, including appointing a Data Protection Officer based in India, an independent data auditor, and periodic Data Protection Impact Assessments. Related guides:
Phase 5: Train people and keep evidence#
Compliance fails most often in daily habits, not policy wording. Make the programme repeatable.
| Activity | What good looks like |
|---|---|
| Training | Role-based sessions for support, HR, marketing and IT, with attendance records |
| Policies | Approved, versioned and communicated; reviewed on a set schedule |
| Data register | Updated whenever a new tool, vendor or process is introduced |
| Requests and incidents | Logged, tracked to closure and reviewed for trends |
| Internal review | Periodic checks against the gap list, reported to management |
Budget planning runs alongside all five phases. Our guide to what drives DPDP compliance cost will help you scope effort realistically.
Frequently asked questions#
Where should a small company start?#
Start with the data inventory and the privacy notice. Knowing what data you hold and telling people clearly how you use it gives you the base for consent, rights handling and retention. Then address security and breach response.
Does the DPDP Act apply to HR and employee data?#
The Act covers digital personal data generally, so employee and candidate data should be in your inventory. Some processing for employment purposes may fall under a legitimate use, but confirm the position with legal counsel and document your reasoning.
Can GDPR documentation be reused for DPDP?#
Partly. The two laws differ in scope, terminology and requirements, so documents must be adapted rather than copied. Many structures carry over well, such as data registers, notices, rights procedures and breach plans. Review all wording against the DPDP Act and its Rules.
If your organisation also handles data of people in the EU, the GDPR Toolkit provides 110+ editable templates, including policies, procedures, checklists and a gap assessment checklist, which can give you a structured starting point. For help planning your own DPDP roadmap, you can talk to the AdWiser team.

Leave a Comment