DPDP Compliance Checklist for Indian Businesses (2025)
The Digital Personal Data Protection Act 2023 imposes a specific set of obligations on every business that collects personal data from Indian residents. This checklist covers the 12 steps required to reach baseline compliance, ordered by regulatory priority. Each item explains what is required, why it matters, and what a failure to comply looks like in practice.
Who this checklist is for
This checklist is written for any Indian business that collects personal data from customers, users, or employees: e-commerce companies, SaaS platforms, FinTech and HealthTech firms, EdTech companies, professional services firms, and startups. The DPDP Act applies regardless of company size. If you have a website with a contact form, a signup page, or an analytics tool running, you are a Data Fiduciary under the Act.
Items are tagged by urgency: Critical items are directly tied to the highest penalty exposure and are the first things the Data Protection Board is likely to examine. Important items are required by the Act but carry lower immediate penalty risk. Good practice items are required or strongly recommended but are operational rather than immediately penalisable.
The DPDP compliance checklist
Your privacy policy must be publicly accessible on your website and cover: what personal data you collect, why you collect it, how long you keep it, who you share it with, what rights users have (access, correction, erasure, nomination), how to withdraw consent, how to submit a grievance, and your breach notification commitment. It must be written in plain language, not legal boilerplate. Link to it from your website footer and all data collection forms.
CriticalEvery Data Fiduciary must designate a named Grievance Officer and publish their name and a contact mechanism (email address) on the website. The Grievance Officer receives and resolves complaints from users about how their personal data is handled. No specific qualification is required. You can appoint any employee to this role. The contact details must be published — it is not sufficient to list a generic contact email. The CompliSeal scanner checks for a published Grievance Officer as one of its 13 checkpoints.
CriticalBefore collecting personal data, you must present a consent notice that specifies: what data is being collected, for what purpose, for how long, and to whom it will be disclosed. Consent must be free, specific, informed, and unambiguous. Bundling consent into terms and conditions is not valid. For each distinct purpose (analytics, marketing, service delivery), consent must be obtained separately. The consent notice must be in plain language and, where required, in Indian scheduled languages.
CriticalUsers must be able to withdraw consent as easily as they gave it. This means providing a clear, accessible way for users to revoke consent for any or all processing purposes at any time. A preference centre on your website or a link in your privacy policy to a withdrawal form both satisfy this requirement. Once consent is withdrawn, processing for those purposes must stop. The Consent Banner SDK in CompliSeal provides this automatically through a preference centre.
CriticalUsers have four rights under the DPDP Act: the right to access a summary of their personal data, the right to correct inaccurate data, the right to erasure, and the right to nominate a successor. You must have a documented process for receiving, tracking, and responding to these requests within a reasonable time. Publish the submission mechanism (typically a form or email address) in your privacy policy. CompliSeal provides a public intake form and a dashboard to manage requests with deadline tracking.
CriticalYou must notify the Data Protection Board of a significant personal data breach promptly after discovery. DPDP Rules 2025 prescribe a 72-hour window for Board notification. You must also notify the affected Data Principals. Before a breach occurs, document your incident response process: who is responsible, how to assess severity, what to include in the notification, and where to submit it. Preparing notification templates in advance is strongly recommended. CompliSeal's Breach Response module provides a 72-hour countdown and pre-drafted notification templates.
CriticalA consent banner that appears before any non-essential cookies or tracking scripts run is required under the DPDP Act. The banner must allow users to accept or decline each category of processing (necessary, analytics, marketing, preferences) separately. Third-party tracking scripts such as Google Analytics or Meta Pixel must be blocked until the user consents. Every consent event must be logged with a timestamp and a user identifier for audit purposes. The CompliSeal Consent Banner SDK handles all of this with a single script tag.
ImportantYou are responsible under the DPDP Act for how your Data Processors (vendors who handle personal data on your behalf) process that data. This requires a written Data Processing Agreement with each processor specifying: what data they process, for what purposes, the security measures they have in place, their sub-processor arrangements, their breach notification obligations to you, and their data deletion procedures on contract end. Review agreements with your analytics provider, CRM, email platform, cloud storage, and payment gateway as a priority.
ImportantA RoPA is a documented inventory of every type of personal data your organisation collects and processes. For each processing activity, record: the data categories, the purpose, the legal basis, the data processors involved, the retention period, and any international transfers. While a RoPA is explicitly mandated only for Significant Data Fiduciaries, maintaining one is strongly recommended for all businesses. It forms the foundation for your privacy policy, your DPIA assessments, and your vendor DPAs, and it is the first document the Data Protection Board will ask for in an investigation.
ImportantA DPIA is required for Significant Data Fiduciaries and is best practice for any business before launching a high-risk processing activity: large-scale profiling, processing sensitive personal data, sharing data with new third parties, or implementing new tracking technologies. A DPIA documents the necessity and proportionality of the processing, the risks to individuals, and the controls in place to mitigate those risks. Complete and record a DPIA before launching any significant new data processing activity.
ImportantProcessing personal data of individuals under 18 requires verifiable parental or guardian consent. Behavioural tracking and targeted advertising directed at minors are prohibited under the DPDP Act. If any part of your platform is accessible to or targeted at users under 18, you need an age verification mechanism, a separate parental consent flow, and a children's-specific privacy policy section. The CompliSeal Children's Data module generates the required documents and assesses your current compliance gaps.
Critical (if applicable)DPDP compliance is not a one-time activity. Your privacy policy must be updated when processing purposes change. Vendor DPAs must be renewed. Consent banners must be reviewed when new processing is introduced. Staff handling personal data should be trained. DPIAs for high-risk activities should be reviewed annually. Set up a compliance calendar with recurring tasks to ensure these obligations do not fall through the gaps. CompliSeal's Compliance Calendar comes pre-loaded with standard DPDP recurring tasks.
OngoingPriority order summary
If you are starting from scratch and need to prioritise, address items in this order:
| Priority | Item | Why first |
|---|---|---|
| 1 | Publish a Grievance Officer | Scannable by Google, immediately visible to regulators |
| 2 | Publish a complete privacy policy | Required before any data collection; checked by the scanner |
| 3 | Add a consent notice before data collection | Every data collection event without consent is a violation |
| 4 | Set up a consent withdrawal mechanism | Directly linked to the consent obligation |
| 5 | Create a DSAR process | Every unanswered rights request is a separate penalty exposure |
| 6 | Prepare a breach response plan | Cannot be created after a breach has occurred |
| 7 | Install consent management on your website | Technical implementation of consent obligations |
| 8 | Review vendor DPAs | You are liable for your processors' handling of your users' data |
| 9 | Create a RoPA | Foundation for all other compliance documentation |
| 10 | Conduct a DPIA for high-risk processing | Required before launching new high-risk activities |
| 11 | Children's data (if applicable) | High penalty exposure; no grace period |
| 12 | Ongoing compliance calendar | Prevents compliance from degrading over time |
Use the CompliSeal compliance scanner to check your website against 13 DPDP requirements automatically. It takes under two minutes and produces a scored report showing exactly which items from this checklist your website currently fails. Free to use, no credit card required.
Common mistakes to avoid
Consent bundled with terms and conditions
Consent obtained as part of agreeing to terms of service is not valid consent under the DPDP Act. Consent must be separate, specific to each purpose, and revocable at any time without penalty to the user. A pre-ticked checkbox in a sign-up form does not constitute valid consent.
Generic Grievance Officer contact
Publishing a general support@yourcompany.com address as the Grievance Officer contact is insufficient. The Grievance Officer must be a named individual with a dedicated contact mechanism. Publishing a name with a role-specific email address (such as grievance@yourcompany.com) is the correct approach.
Privacy policy not updated after changes
Many businesses publish a privacy policy once and do not update it when new processing activities are introduced, when processors change, or when the stated purposes expand. Your privacy policy must accurately reflect your current data practices. Review it whenever you introduce a new product feature that collects additional data, change analytics providers, or add a new marketing channel.
Treating compliance as a one-time project
Compliance is an ongoing operational function. Vendors change, processing activities evolve, regulations are updated, and breaches can occur at any time. Treat it as a continuous process with regular review points, not a one-off documentation exercise.
This checklist is a practical guide based on the DPDP Act 2023 and DPDP Rules 2025. It does not constitute legal advice. For complex compliance situations, sensitive data categories, cross-border transfer arrangements, or regulatory proceedings, consult a qualified legal professional.
Tools and resources
Check your current DPDP compliance score
CompliSeal scans your website against 13 DPDP requirements and shows you exactly which items on this checklist you currently pass or fail. Free to start, no credit card required.
Run Free Compliance Scan