This guide is general information, not legal advice. Confirm how the rules apply to you with your compliance team or counsel.
The short answer: to comply with the DPDP Act you need a current record of the personal data you hold and why, a notice and consent flow that meets the Rules, a working process for rights requests and grievances, reasonable security safeguards with contracts that bind your processors, a breach response that can meet a 72-hour reporting deadline, and retention rules that end in erasure. Children's data and Significant Data Fiduciaries carry extra duties. Everything else in this DPDP compliance checklist for companies is detail on how to do those things and prove you did them.
DPDP Rules 2025 timeline: what applies when
The Ministry of Electronics and Information Technology (MeitY) notified the Digital Personal Data Protection Rules, 2025 on 13 November 2025. The Act itself received Presidential assent on 11 August 2023, but most of it waited for these Rules. Commencement is staggered:
- From 13 November 2025: definitions and the provisions that set up the Data Protection Board of India.
- One year after notification (November 2026): registration and obligations of Consent Managers.
- Eighteen months after notification (mid-May 2027): the substantive duties of data fiduciaries, including notice, security safeguards, breach intimation, retention and erasure, children's data, Significant Data Fiduciary obligations and data principal rights.
Commentators give 13 May and 14 May 2027 as the date for the last stage, depending on how they count. Plan for the earlier one. Eighteen months sounds generous until you remember that a typical mid-sized company needs three to six months just to build an accurate data inventory, and that vendor contracts renew on their own calendar.
Who this DPDP compliance checklist is for
The Act applies to processing of digital personal data within India, and to processing outside India if it is connected to offering goods or services to people in India. If you run a consumer app, a lending or payments product, a health or edtech platform, an HR tech tool, or a B2B SaaS product used by Indian companies, it applies to you.
Work out your role per activity, not per company. You are a data fiduciary where you decide the purpose and means: your payroll, your marketing list, your customer accounts. You are a data processor where you process on someone else's instructions, which is the usual position for the data your customers load into your product. Fiduciaries carry the legal obligations. Processors carry them through contracts, and in practice the fiduciaries will expect you to meet most of the same standards.
Step 1: Map the personal data you hold
Every other step depends on this one. You cannot write an itemised notice, set a retention period or scope a breach without knowing what data sits in which system for which purpose.
- List processing activities, not databases. "Employee payroll", "loan underwriting", "product analytics" and "support tickets" are activities.
- For each activity, record the purpose, the categories of data and of people, the source, the systems and locations involved, recipients and processors, your role, the ground (consent or a legitimate use under Section 7), the notice that covers it, the retention rule, and whether children's data is involved.
- Interview the people who run each process. The marketing team knows about the webinar tool that IT never approved.
- Mark the activities where you are a processor and link them to the customer contract.
Owner: privacy lead, with each process owner signing off their rows.
Evidence to keep: the inventory with a version and approval date, interview notes, and the date of the last review.
Keep the inventory where the rest of the work happens
In BeAuditReady each processing activity carries its purpose, systems, processors, role, notice and retention rule, so notices, requests and erasure tasks link back to it. You can start from a questionnaire or a CSV import. There is no automatic data discovery; your process owners fill it in and approve it.
Step 2: DPDP notices and consent that meet the Rules
Where you rely on consent, the Act requires that it be free, specific, informed, unconditional and unambiguous, given by a clear affirmative action, and limited to the data needed for the stated purpose. A pre-ticked box or a bundled "I agree to everything" does not meet that test.
The DPDP Rules 2025 say the notice that goes with a consent request must:
- be understandable on its own, independent of any other information you give;
- use clear and plain language;
- give an itemised description of the personal data and the specified purpose for each item;
- describe the goods, services or uses that the processing enables; and
- give a link or other means to withdraw consent (as easily as it was given), exercise rights under the Act, and complain to the Data Protection Board.
The Act also lets the person read the notice in English or any language in the Eighth Schedule to the Constitution. For a consumer product with users across states, plan translations early.
Not every activity needs consent. Section 7 lists legitimate uses, such as data a person voluntarily gives for a specified purpose where they have not objected, and certain employment purposes. Record which ground you rely on for each activity in your inventory, and why.
Owner: privacy lead and product, with legal review.
Evidence to keep: each notice version with its effective date and approver, screenshots of the consent flow, consent and withdrawal records with timestamps, and the ground recorded for each activity.
Step 3: Data principal requests and grievances
Data principals can ask for a summary of their data and processing, the identities of other fiduciaries and processors you shared it with, correction, completion, updating and erasure. They can also nominate someone to act for them, and they must have a way to raise a grievance with you before going to the Board.
- Publish on your website or app how to make a request and what details you need to identify the person, such as a username or customer ID.
- Verify identity in proportion to the risk. You do not need an Aadhaar number to confirm that someone owns an email address.
- Break each request into tasks per system and per processor. One erasure request in a typical SaaS company touches the app database, the CRM, the support desk, the email platform and backups.
- Respond to grievances within a reasonable period. The Rules set an outer limit of 90 days, and you should aim well inside it.
- Publish the business contact details of your DPO, or of a person who can answer questions about your processing, and include them in your responses.
Owner: privacy operations or customer support, with engineering for fulfilment.
Evidence to keep: a case log with received, verified and responded dates, the tasks raised per system, who approved the response, and the response itself.
Step 4: Security safeguards and processor contracts
Section 8(5) requires reasonable security safeguards to prevent a personal data breach, and this is the failure that carries the highest penalty. The Rules list the minimum measures:
- encryption, obfuscation, masking or virtual tokens for personal data;
- access control over the computer resources that process it;
- logs, monitoring and review so that unauthorised access can be detected and investigated;
- backups and other measures to keep processing going if data is compromised;
- retention of those logs and related personal data for at least one year, unless another law says otherwise; and
- contracts with processors that require them to take the same safeguards.
If you already run an ISO 27001 ISMS or have a SOC 2 report, much of this exists. Check the one-year log retention specifically, because many teams keep application logs for 30 or 90 days. Our ISO 27001 guide covers the overlap.
Owner: CISO or head of engineering; legal or procurement for contracts.
Evidence to keep: encryption and access-control settings, log retention configuration, access review records, and a register of processors with signed data processing terms.
Step 5: Breach intimation under the DPDP Rules
Under the Act, every personal data breach must be reported to the Board and to each affected data principal. There is no materiality threshold in the text, so treat every confirmed breach as reportable and record your reasoning.
To affected data principals, without delay
- a description of the breach, including its nature, extent, timing and location;
- the likely consequences for them;
- what you have done and are doing to reduce the risk;
- safety measures they can take; and
- business contact details of a person who can answer their questions.
To the Data Protection Board
- an initial intimation without delay, describing the breach, its nature, extent, timing, location and likely impact; and
- within 72 hours of becoming aware (or longer if the Board allows on a written request), a detailed report covering the facts and circumstances, mitigation, findings about who caused it, remedial steps to prevent a repeat, and a report on the intimations sent to affected people.
Your other clocks do not stop. CERT-In's directions of 28 April 2022 require cyber security incidents to be reported within six hours of noticing them. An RBI-regulated entity has its own reporting line, and your enterprise customers may have contractual windows of 24 or 48 hours. Write all of these into one runbook so nobody has to decide under pressure which one comes first.
Owner: incident lead, privacy lead and legal.
Evidence to keep: the awareness timestamp, the notification assessment, each draft and who approved it, the sent intimations and receipts, and the post-incident review.
Step 6: Retention and erasure
Section 8(7) says you must erase personal data when the person withdraws consent or when it is reasonable to assume the purpose is no longer being served, unless a law requires you to keep it. You must also make your processors erase it.
The Rules make this concrete for three classes in the Third Schedule: e-commerce entities and social media intermediaries with at least two crore registered users in India, and online gaming intermediaries with at least fifty lakh. For these, data must be erased three years after the person last approached the fiduciary or exercised a right, counted from the later of that date and the Rules' commencement. At least 48 hours before erasure, the fiduciary must tell the person that their data will be erased unless they log in or otherwise make contact.
For everyone else, the work looks like this:
- Set a retention period per activity and data class, with the reason. Tax, labour and RBI rules often set minimums, so list the law you rely on.
- Keep the one-year minimum for logs from Step 4 in mind when you set short periods.
- Put legal holds on data linked to disputes, investigations or regulatory requests, and make sure a hold blocks erasure.
- Run erasure as approved tasks per system and get the system owner to confirm completion.
Owner: privacy lead with system owners.
Evidence to keep: the retention schedule with approvals, legal hold records, erasure tasks with completion attestations, and for Third Schedule entities, the 48-hour notices sent.
Step 7: Children's data and verifiable consent
The Act treats anyone under 18 as a child. Before processing a child's personal data you need the verifiable consent of a parent or lawful guardian, and you must not carry out tracking, behavioural monitoring or targeted advertising directed at children. The same verifiable consent rule applies to a person with a disability who has a lawful guardian.
The Rules ask you to check that the person giving consent is an identifiable adult. You can rely on identity and age details you already hold, or on details or a virtual token issued by an authorised entity, such as a DigiLocker-based token. The Fourth Schedule exempts some classes, such as clinical establishments, educational institutions and childcare or transport providers, for specific purposes.
Owner: product and privacy lead.
Evidence to keep: the age-gating design, the method used to verify the parent, consent records, and the exemption relied on, if any.
Step 8: Significant Data Fiduciary obligations
The Central Government can notify a fiduciary or class of fiduciaries as Significant Data Fiduciaries based on the volume and sensitivity of data, the risk to people's rights, and wider public interest factors. If you are notified, you must:
- appoint a Data Protection Officer based in India who reports to the Board of Directors or similar governing body;
- appoint an independent data auditor;
- carry out a Data Protection Impact Assessment and an audit once every twelve months, and give the Board the significant observations;
- check that algorithmic software you use to process personal data does not put data principals' rights at risk; and
- follow any restriction the government sets on transferring specified personal data outside India.
Large fintechs, health platforms and consumer apps should assume they may be notified and build the DPIA habit now.
Owner: DPO and the board.
Evidence to keep: the DPO appointment, DPIA reports with approvals, the independent audit report, and board minutes showing review.
DPDP Act penalties
The Schedule to the Act sets the maximum penalty for each kind of breach:
| Breach | Maximum penalty |
|---|---|
| Failure to take reasonable security safeguards to prevent a personal data breach | ₹250 crore |
| Failure to notify the Board or affected data principals of a breach | ₹200 crore |
| Breach of the additional obligations for children's data | ₹200 crore |
| Breach of the additional obligations of a Significant Data Fiduciary | ₹150 crore |
| Breach of any other provision of the Act or Rules | ₹50 crore |
| Breach of the duties of a data principal | ₹10,000 |
The Board considers the nature, gravity and duration of the breach, whether it was repeated, and what you did to limit it. A documented, working process counts in your favour when that assessment happens.
DPDP compliance checklist summary
| Work | Owner | Evidence to keep |
|---|---|---|
| Processing-activity inventory | Privacy lead, process owners | Approved, versioned inventory |
| Notices and consent | Privacy lead, product, legal | Notice versions, consent and withdrawal logs |
| Rights requests and grievances | Privacy operations | Case log, approvals, responses |
| Security safeguards | CISO, engineering | Settings, one-year log retention, access reviews |
| Processor contracts | Legal, procurement | Processor register, signed terms |
| Breach runbook | Incident lead, legal | Timestamps, drafts, intimations, receipts |
| Retention and erasure | Privacy lead, system owners | Schedule, holds, erasure attestations |
| Children's data | Product, privacy lead | Verification method, consent records |
| SDF duties, if notified | DPO, board | DPIA, audit report, minutes |
Review the whole list every quarter until May 2027 and twice a year after that. If you are also working towards SOC 2 or ISO 27001, the security and incident steps overlap, and our SOC 2 checklist shows where. For how BeAuditReady runs requests, notices, retention tasks and privacy incidents day to day, see the privacy and DPDP solution.
Sources: Digital Personal Data Protection Act, 2023 (No. 22 of 2023); Digital Personal Data Protection Rules, 2025, notified by MeitY on 13 November 2025; CERT-In directions under Section 70B of the IT Act, 28 April 2022.