Quick answer
Under Rule 13(1) of the DPDP Rules, 2025, a Significant Data Fiduciary must undertake a Data Protection Impact Assessment (DPIA) and an audit once in every twelve-month period, counted from the date it is notified as an SDF. Under Rule 13(2), the person carrying out the DPIA and audit must furnish the Data Protection Board a report of significant observations. Rule 13 applies from 13 May 2027.
- A DPDP DPIA is mandatory only for Significant Data Fiduciaries, once they are notified under section 10 of the Act.
- The DPIA and the audit must be done once in every twelve months from the date of notification as an SDF.
- The person who carries out the DPIA and audit must send a report of significant observations to the Board.
- Rule 13 comes into force on 13 May 2027, eighteen months after the Rules were published.
- Ordinary Data Fiduciaries have no statutory DPIA duty, but a lightweight assessment is still useful evidence of reasonable safeguards.
Who this is for: Companies likely to be notified as Significant Data Fiduciaries, Data Protection Officers, Independent data auditors, CTOs and platform engineering leads, Risk and compliance teams
What is a DPIA under the DPDP Act and Rules?
A Data Protection Impact Assessment (DPIA) under India's DPDP framework is a periodic, documented assessment of how a Significant Data Fiduciary (SDF) processes personal data and what risks that processing creates for the rights of Data Principals. Section 10(2) of the DPDP Act lists the DPIA among the additional obligations of an SDF, alongside appointing a Data Protection Officer based in India and an independent data auditor.
The Act leaves frequency and reporting to the Rules. Rule 13(1) of the DPDP Rules, 2025 fills that gap: an SDF must, "once in every period of twelve months from the date on which it is notified as such or is included in the class of Data Fiduciaries notified as such", undertake a DPIA and an audit to ensure effective observance of the Act and the Rules.
Rule 13(2) then adds a reporting duty: the SDF must cause the person carrying out the DPIA and audit to furnish the Board a report containing the significant observations from both exercises.
Three points follow directly from the text:
- The obligation is annual, but the clock starts on the SDF's own notification date, not on a calendar or financial year.
- The DPIA and the audit are separate exercises that run together; one does not substitute for the other.
- The report to the Board goes from the assessor or auditor, so the SDF cannot quietly filter out uncomfortable findings.
Rule 13 is one of the rules that come into force on 13 May 2027. No SDF has been notified yet, so the first DPIA cycle can only start once the Central Government notifies an entity or class.
Who has to run a DPDP DPIA?
Only a Significant Data Fiduciary is legally required to run a DPIA. Under section 10(1) of the Act, the Central Government may notify any Data Fiduciary or class of Data Fiduciaries as an SDF based on factors such as:
- the volume and sensitivity of personal data processed;
- the risk to the rights of Data Principals;
- the potential impact on the sovereignty and integrity of India;
- the risk to electoral democracy;
- security of the State; and
- public order.
The Seventh Schedule to the Rules also lets an officer of MeitY call for information from a Data Fiduciary for "carrying out assessment for notifying any Data Fiduciary or class of Data Fiduciaries as Significant Data Fiduciary" (Rule 23). In practice, a request of that kind is an early signal that SDF designation is being considered.
Ordinary Data Fiduciaries have no statutory DPIA duty under the DPDP Rules. That said, many will still benefit from a lighter internal assessment, because it is the easiest way to show the Board that security safeguards under Rule 6 and retention choices under Rule 8 were reasoned rather than accidental.
| Entity | DPIA required? | Basis |
|---|---|---|
| Notified SDF | Yes, every 12 months | Rule 13(1) |
| Entity in a notified SDF class | Yes, every 12 months | Rule 13(1) |
| Ordinary Data Fiduciary | No statutory duty | — |
| Data Processor | No direct duty; supports its fiduciary | Contract under s.8(2) |
| Consent Manager | No DPIA; separate audit duty | First Schedule, Part B item 12 |
What should a DPDP DPIA cover?
The Rules do not prescribe a DPIA template, so the content has to be derived from what the DPIA is meant to test: effective observance of the Act and the Rules, and risk to the rights of Data Principals. A defensible DPDP DPIA should cover at least the following.
Processing inventory
- Every processing activity, its purpose, and whether it relies on consent (s.6) or a legitimate use (s.7).
- Itemised categories of personal data, mirroring the itemised description required in Rule 3 notices.
- Data Processors involved and the contract clauses on safeguards required by Rule 6(1)(f).
Rights and risk analysis
- Risks to access, correction, erasure, grievance and nomination rights (sections 11–14, Rule 14).
- Children's data and verifiable parental consent under Rule 10, including any Fourth Schedule exemptions relied on.
- Algorithmic software used to host, display, publish or share personal data, linking to the separate algorithmic due diligence duty in Rule 13(3).
Security and retention
- Encryption, masking, access control, logging and backup controls under Rule 6(1)(a)–(d).
- One-year log and data retention under Rule 6(1)(e) and Rule 8(3).
- Breach response readiness against the Rule 7 timelines.
Transfers and localisation
- Cross-border flows and any Central Government orders under Rule 15.
- Any data categories specified for localisation under Rule 13(4).
Each risk should end with an owner, a mitigation and a target date. Observations that remain open are the ones most likely to be "significant" for the Board report.
How is the DPIA different from the annual audit?
Rule 13(1) bundles the DPIA and the audit into one twelve-month cycle, but they answer different questions. Treating them as one document is a common mistake.
| Aspect | DPIA | Audit |
|---|---|---|
| Core question | What could go wrong for Data Principals? | Are we actually complying today? |
| Orientation | Forward-looking, risk-based | Evidence-based, point-in-time |
| Inputs | Data flows, purposes, new features, vendors | Logs, configs, contracts, tickets, samples |
| Typical output | Risk register with mitigations | Findings, non-conformities, remediation plan |
| Who does it | Internal privacy team or external assessor | Independent data auditor (s.10(2)(b)) |
| Board reporting | Significant observations (Rule 13(2)) | Significant observations (Rule 13(2)) |
The Act requires an SDF to appoint an independent data auditor to evaluate compliance. The DPIA can be performed by the DPO's team, but its significant observations still have to reach the Board through the person who carried it out.
A practical sequencing that works for most engineering-heavy organisations:
- Refresh the processing inventory and data-flow diagrams.
- Run the DPIA on the refreshed inventory and log risks.
- Let the independent auditor test controls, including the DPIA's mitigations.
- Consolidate significant observations into one report for the Board.
Running the DPIA first gives the auditor a risk map to test against, rather than a blank slate.
How do you make the DPIA evidence-ready in real systems?
A DPIA that lives only in a slide deck will not survive scrutiny. The strongest DPDP DPIAs are built on artefacts engineering teams already produce.
Data map from code and infrastructure
- Generate the inventory from schema registries, data catalogues and infrastructure-as-code, not from interviews alone.
- Tag tables and event streams with purpose and lawful ground; flag columns holding children's data.
- Record which Data Processors (cloud, analytics, messaging, LLM APIs) receive each dataset.
Control evidence
- Export key management and encryption-at-rest settings to show Rule 6(1)(a) controls.
- Pull IAM role reviews and privileged-access logs for Rule 6(1)(b).
- Show that access logs are retained for at least one year, as Rule 6(1)(e) and Rule 8(3) require.
- Attach backup and restore test results for Rule 6(1)(d).
Change triggers
Although Rule 13 sets a twelve-month cadence, risk changes faster. Add a lightweight DPIA trigger to your product process for:
- new categories of personal data or new purposes;
- new profiling, recommendation or ranking models;
- new cross-border processors;
- features aimed at, or likely to be used by, children.
The annual DPIA then becomes a consolidation of smaller assessments rather than a once-a-year scramble. Version every DPIA and keep the signed final copy, the risk register and the auditor's working papers together, because the Board may ask how a significant observation was resolved.
Common DPIA mistakes to avoid
Several mistakes recur when organisations adapt GDPR-era templates to the DPDP Rules.
- Copying a GDPR Article 35 template without changes. GDPR triggers a DPIA per high-risk processing operation; Rule 13(1) requires a periodic, organisation-level DPIA for SDFs. The DPDP DPIA must also cover DPDP-specific items such as verifiable parental consent, the Fourth Schedule, Rule 8 erasure and Rule 14 rights.
- Starting the clock on the wrong date. The twelve months run from the date of SDF notification, or inclusion in a notified class. Track that date in your compliance calendar.
- Merging DPIA and audit. Rule 13(1) requires both. An auditor's report alone is not a DPIA.
- Filtering the Board report. Rule 13(2) places the reporting duty on the person carrying out the DPIA and audit. Contracts with assessors should make that independence explicit.
- Ignoring processors. Section 8(1) keeps the fiduciary responsible for processing done on its behalf, so processor risks belong in the DPIA.
- Leaving out algorithmic systems. Rule 13(3) separately requires due diligence on algorithmic software. The DPIA is the natural place to record that analysis.
- No remediation tracking. An observation repeated across two cycles is harder to defend than one that was found and fixed.
Failure to meet SDF obligations can attract a penalty of up to ₹150 crore under the Schedule to the Act, decided by the Board after inquiry.
What to do before 13 May 2027
Rule 13 applies from 13 May 2027, and only once an entity is notified as an SDF. Organisations that expect designation can use the remaining months productively.
- Assess your designation risk. Map yourself against the section 10(1) factors: volume and sensitivity of data, risk to Data Principals, and public-interest impact.
- Appoint a DPO candidate. An SDF must have a DPO based in India, responsible to the board of directors. Identifying the person early lets them own the first DPIA.
- Shortlist independent auditors. Agree scope, independence and the obligation to report significant observations to the Board.
- Build the processing inventory now. It is needed anyway for Rule 3 notices, Rule 6 safeguards and Rule 8 retention.
- Run a dry-run DPIA. Treat the first internal exercise as a baseline. Findings fixed before notification are not significant observations later.
- Respond carefully to Rule 23 requests. A Seventh Schedule item 3 information call from MeitY concerns SDF assessment; route it to legal and the DPO candidate.
For the wider list of SDF duties, see Significant Data Fiduciary obligations, and for the overall dates, the DPDP Rules commencement timeline.
Further reading on suhasbhairav.com
- AI SkillsCursor Rules Template: GDPR Risk Assessment Tools from Website Forms and Data Flows
- BlogAudit-Ready AI provenance logging for compliance
- BlogCompliance testing for high-risk AI: governance
- AI LabBatuk sovereign AI chat workspace for Hash-chain audit evidence
- AI AutomationAI Automation for Risk Assessments in Legal and Compliance
Before 13 May 2027
Compliance checklist
Track SDF notification status
Monitor the Gazette for notifications under section 10 and record the exact notification date, because the twelve-month DPIA cycle runs from it.
Rule 13(1)
Build a processing inventory
List every purpose, lawful ground, data category and processor, generated from code and infrastructure where possible.
Rule 3; Rule 13(1)
Appoint an independent data auditor
Contract an auditor with clear independence and a duty to report significant observations directly to the Board.
Section 10(2)(b); Rule 13(2)
Assess algorithmic software
Include ranking, recommendation and moderation systems that handle personal data in the DPIA scope.
Rule 13(3)
Test security controls against Rule 6
Collect evidence of encryption, access control, logging, backups and processor contract clauses.
Rule 6(1)
Check localisation-specified data
Confirm whether any personal data specified by the Central Government must stay in India, including its traffic data.
Rule 13(4)
Maintain a remediation register
Assign owners and dates to every DPIA risk and audit finding, and carry open items into the next cycle.
Rule 13(1)
File the significant-observations report
Ensure the assessor and auditor furnish the report to the Board after each annual cycle.
Rule 13(2)
Key dates
DPDP Rules, 2025 published (G.S.R. 846(E)); Board rules in force
Rule 4 (Consent Managers) in force
Rule 13 SDF obligations, including the annual DPIA and audit, come into force
Answers
Frequently asked questions
Is a DPIA mandatory under the DPDP Act?
Is a DPIA mandatory under the DPDP Act?
A DPIA is mandatory only for Significant Data Fiduciaries. Section 10(2) of the DPDP Act lists the DPIA as an SDF obligation, and Rule 13(1) of the DPDP Rules, 2025 requires it once in every twelve months from the date of notification. Ordinary Data Fiduciaries have no statutory DPIA duty, though an internal assessment is good practice.
How often must a Significant Data Fiduciary conduct a DPIA?
How often must a Significant Data Fiduciary conduct a DPIA?
Once in every period of twelve months, counted from the date the entity is notified as a Significant Data Fiduciary or included in a notified class. The same cycle covers the audit. Rule 13 comes into force on 13 May 2027, and no SDF has been notified yet.
Who sends the DPIA report to the Data Protection Board?
Who sends the DPIA report to the Data Protection Board?
Rule 13(2) requires the Significant Data Fiduciary to cause the person carrying out the DPIA and audit to furnish the Board a report containing significant observations. The report therefore comes from the assessor or auditor, which supports independence and makes it harder to filter findings.
Is a DPDP DPIA the same as a GDPR DPIA?
Is a DPDP DPIA the same as a GDPR DPIA?
No. A GDPR Article 35 DPIA is triggered for specific high-risk processing operations, while a DPDP DPIA is a periodic, organisation-wide obligation for Significant Data Fiduciaries. A GDPR template can be a starting point, but it must be extended to cover DPDP-specific items such as verifiable parental consent, Rule 8 erasure and Rule 14 rights.
What happens if an SDF does not carry out a DPIA?
What happens if an SDF does not carry out a DPIA?
Breach of the additional obligations of a Significant Data Fiduciary can attract a penalty of up to ₹150 crore under the Schedule to the DPDP Act. The Board decides the amount after an inquiry, considering factors such as nature, gravity, duration and mitigation. Repeat findings across cycles weaken any mitigation argument.
Should ordinary companies run a DPIA anyway?
Should ordinary companies run a DPIA anyway?
It is sensible for any company handling large volumes of personal data or children's data. A short internal assessment documents why security safeguards under Rule 6 and retention choices under Rule 8 are reasonable, and it prepares the organisation if it is later notified as a Significant Data Fiduciary.
Does the DPIA need to include AI and algorithmic systems?
Does the DPIA need to include AI and algorithmic systems?
It should. Rule 13(3) separately requires a Significant Data Fiduciary to verify that technical measures, including algorithmic software used to host, display, publish or share personal data, are not likely to pose a risk to Data Principals' rights. The annual DPIA is the natural place to record that analysis.
Legal references and sources
- Digital Personal Data Protection Rules, 2025 — Rule 13(1) and 13(2) (official text)
- Digital Personal Data Protection Act, 2023 — Section 10 (official text)
- Digital Personal Data Protection Rules, 2025 — Rule 1(4) (commencement) (official text)
This guide explains the law for engineering and business teams. It is not legal advice; confirm how it applies to your organisation with qualified counsel, and check the Gazette for later notifications or amendments.
About the author

Suhas Bhairav
Systems architect and applied AI practitioner who designs production AI systems for Indian and global companies, with a focus on privacy-by-design under the DPDP Act and the EU AI Act.
Related guides
- DPDP Rules 2025Significant Data Fiduciary Obligations Under DPDP Rule 13Once notified, a Significant Data Fiduciary must run an annual DPIA and audit, report significant observations to the Board, vet its algorithms, and keep Government-specified data in India.
- DPDP Rules 2025Algorithmic Due Diligence for Significant Data FiduciariesRule 13(3) requires Significant Data Fiduciaries to verify that technical measures, including algorithmic software, are not likely to pose a risk to Data Principals' rights. Here is what that means in practice.
- DPDP Rules 2025DPDP Reasonable Security Safeguards Under Rule 6Rule 6 lists the minimum security safeguards every Data Fiduciary must take from 13 May 2027. Failure can attract a penalty of up to ₹250 crore, the highest in the DPDP Act.
- DPDP Act 2023DPDP Penalties Explained: What a Data Breach CostsThe full DPDP Act penalty schedule, from ₹10,000 to ₹250 crore per instance, the section 33(2) factors the Board weighs, and how penalties are imposed and appealed.
- DPDP Rules 2025DPDP Rules 2025 Timeline: What Applies From Nov 2025, Nov 2026 and May 2027The DPDP Rules commence in three phases. Here is exactly which rules and Act sections apply from 13 Nov 2025, 13 Nov 2026 and 13 May 2027, and what that means for planning.
- DPDP Rules 2025Appealing a Data Protection Board Order to TDSAT (Rule 22)Who can appeal a Data Protection Board order, the 60-day window in section 29, and how Rule 22 makes TDSAT appeals digital, with the TRAI Act fee paid by UPI.