DPDP Rules 2025Updated 22 November 20269 min read

Significant Data Fiduciary Obligations Under DPDP Rule 13

Once 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.

By Suhas Bhairav · Reviewed against the DPDP Rules, 2025 (G.S.R. 846(E), 13 Nov 2025)

Provision
Rule 13(1)–(5); Act section 10
In force from
13 May 2027
DPIA and audit
Once every 12 months from notification
Report to
Data Protection Board (significant observations)
Localisation
Only data specified by the Central Government
Act duties
DPO based in India; independent data auditor
Penalty
Up to ₹150 crore for SDF additional obligations
Notified SDFs
None as of this update

Quick answer

Under Rule 13 of the DPDP Rules, 2025, a Significant Data Fiduciary must, once notified, undertake a Data Protection Impact Assessment and an audit every 12 months, have the assessor report significant observations to the Board, verify that technical measures including algorithmic software do not risk Data Principals' rights, and keep personal data specified by the Government, with related traffic data, within India. Rule 13 applies from 13 May 2027.

  • SDF status comes from Government notification under section 10 of the Act; no Significant Data Fiduciary had been notified as of this update.
  • Rule 13(1) requires a DPIA and an audit once in every 12 months, counted from the date of notification as an SDF.
  • Rule 13(2) requires the person conducting the DPIA and audit to give the Board a report of significant observations.
  • Rule 13(3) requires due diligence that technical measures, including algorithmic software, are not likely to risk Data Principals' rights.
  • Rule 13(4) requires Government-specified personal data and its flow's traffic data to stay in India, on a committee's recommendation.

Who this is for: Large platforms likely to be notified as SDFs, Boards and audit committees, Data Protection Officers, Model risk and AI governance teams, Cloud and infrastructure architects

What are the obligations of a Significant Data Fiduciary?

A Significant Data Fiduciary (SDF) is a Data Fiduciary, or a class of them, that the Central Government notifies under section 10 of the DPDP Act, based on factors including the volume and sensitivity of personal data processed, risk to Data Principals' rights, potential impact on the sovereignty and integrity of India, risk to electoral democracy, security of the State and public order.

The Act gives every SDF three duties: appoint a Data Protection Officer based in India and responsible to the board of directors or similar governing body; appoint an independent data auditor; and undertake periodic DPIAs and audits and other measures that may be prescribed.

Rule 13 adds four operational obligations:

Sub-ruleObligation
13(1)DPIA and audit once in every 12 months from notification
13(2)The assessor or auditor reports significant observations to the Board
13(3)Due diligence that technical measures, including algorithmic software, are not likely to pose a risk to Data Principals' rights
13(4)Government-specified personal data, and traffic data on its flow, not transferred outside India

Status: no SDF has been notified as of this update. Everything on this page applies "once notified". Rule 13 itself comes into force on 13 May 2027.

Rule 13(1) and (2): annual DPIA, audit and Board reporting

Rule 13(1) requires an SDF, once in every period of twelve months from the date it is notified as an SDF or included in a notified class, to undertake a Data Protection Impact Assessment and an audit to ensure effective observance of the Act and Rules.

Rule 13(2) requires the SDF to cause the person carrying out the DPIA and audit to furnish to the Board a report containing significant observations.

Points to note:

  • The clock is company-specific. It runs from notification, not from 13 May 2027.
  • Two exercises, not one. A DPIA assesses risk from processing; an audit tests whether controls work and the law is being observed. They can share evidence but have different outputs.
  • The assessor reports directly. The report of significant observations goes to the Board from the person who did the work, so management cannot filter it. Contract with the assessor and auditor on that basis.
  • "Significant observations" is not defined. Agree with the auditor in advance how findings will be graded, so expectations about what reaches the Board are clear.

The Act separately requires the auditor to be an independent data auditor. Select one without conflicts, for example not the firm that designed the controls being audited. See the DPIA guide.

Rule 13(3): algorithmic due diligence

Rule 13(3) requires an SDF to observe due diligence to verify that technical measures, including algorithmic software, adopted by it for hosting, display, uploading, modification, publishing, transmission, storage, updating or sharing of personal data are not likely to pose a risk to the rights of Data Principals.

The list of verbs is broad. It covers recommendation and ranking systems (display), content moderation (uploading, publishing), storage and replication systems, data-sharing pipelines and machine learning models that process personal data.

What due diligence can look like:

StepOutput
InventoryList of algorithmic systems that touch personal data, with owners
Risk screeningWhich systems affect rights: access, correction, erasure, consent withdrawal, grievance
TestingChecks that erasure and withdrawal propagate; tests for errors that misattribute data; checks on data exposure in outputs
DocumentationModel and system cards describing purpose, inputs, known limitations and controls
MonitoringOngoing metrics and incident tracking for each system
ReviewInclusion in the annual DPIA and audit

The Rule frames risk as risk to the rights of Data Principals under the Act. That is narrower than general AI ethics, so anchor tests to concrete rights: can a person's erasure request reach the model's training data, vector index and caches? See algorithmic due diligence.

Rule 13(4): data that must stay in India

Rule 13(4) requires an SDF to undertake measures to ensure that personal data specified by the Central Government, on the basis of the recommendations of a committee constituted by it, is processed subject to the restriction that the personal data and the traffic data pertaining to its flow are not transferred outside India.

Rule 13(5) says the committee is constituted by the Central Government for this purpose and includes officials from MeitY and may include officials from other Ministries or Departments.

What this does and does not mean:

  • It is not general localisation. It applies only to SDFs, and only to data categories the Government specifies after the committee's recommendation. No categories are specified in the Rules themselves.
  • Traffic data is included. Keeping the database in India is not enough if metadata about the flow of that data is processed abroad, for example by a foreign monitoring or CDN service.
  • The general rule for other data remains section 16 of the Act, which permits transfers except to countries the Government restricts, and Rule 15, which lets the Government set requirements on making data available to foreign States.

Practical step for a likely SDF: map where each category of personal data and its traffic data is stored and processed, including logs, backups, monitoring and support tools, so that you can respond quickly if a category is specified. See cross-border transfer.

How SDF designation is assessed

The SDF notification process sits in the Act, not the Rules, but the Rules support it in one place. Item 3 of the Seventh Schedule lists, as a purpose for which the Central Government may call for information under Rule 23, "carrying out assessment for notifying any Data Fiduciary or class of Data Fiduciaries as Significant Data Fiduciary". The authorised person is a MeitY officer designated by the Secretary.

So the likely sequence is:

  1. MeitY identifies candidates based on the section 10 factors.
  2. A designated MeitY officer may call for information under Rule 23 and the Seventh Schedule.
  3. The Central Government notifies the fiduciary or a class.
  4. The 12-month DPIA and audit clock starts from that notification.

Rule 8(3) requires every fiduciary to keep personal data, traffic data and processing logs for at least a year for Seventh Schedule purposes, which include this assessment. A company that may be assessed should expect requests for information on data volumes, categories and processing, and should be able to answer from its inventory.

Sector-specific analysis of which organisations might be notified is on the SDF criteria page. This page does not predict who will be notified.

How a likely SDF should prepare now

A large platform does not need to wait for notification to prepare, and the cost of preparing early is mostly the cost of good governance.

  1. Appoint a DPO-ready leader based in India with a reporting line to the board. If notified, the appointment becomes mandatory.
  2. Pre-qualify independent data auditors and agree the scope and grading of "significant observations".
  3. Run a baseline DPIA across major processing activities, so the first mandatory cycle is a refresh, not a first attempt.
  4. Build an algorithmic systems inventory with owners, purpose and rights-impact screening.
  5. Map data residency for personal data and its traffic data, including logs, backups, CDNs and support tools.
  6. Prepare for Rule 23 requests by keeping the data inventory current and the one-year archive under Rule 8(3) searchable.
  7. Brief the board. SDF obligations, including the DPO reporting line and auditor reports to the Board, are governance obligations.

The penalty for breach of the additional obligations of an SDF is up to ₹150 crore per instance under the Act's Schedule, in addition to penalties for other breaches such as security failures. The audit checklist is a practical starting point for the baseline.

Further reading on suhasbhairav.com

Before 13 May 2027

Compliance checklist

  1. Track SDF notifications

    Monitor the Gazette and MeitY for notifications naming your company or a class that includes it.

    Act section 10

  2. Prepare a DPO appointment

    Identify an India-based DPO who can report to the board of directors or equivalent body.

    Act section 10

  3. Pre-select an independent data auditor

    Choose an auditor without conflicts and agree how significant observations will be reported to the Board.

    Rule 13(1)–(2)

  4. Run a baseline DPIA

    Assess major processing activities now so the first mandatory annual cycle is a refresh.

    Rule 13(1)

  5. Inventory algorithmic systems

    List systems that host, display, publish, store or share personal data and screen them for rights impact.

    Rule 13(3)

  6. Map data and traffic data residency

    Record where personal data and its traffic data are stored and processed, including logs and backups.

    Rule 13(4)

  7. Prepare for assessment information requests

    Keep the data inventory and one-year archive ready for Seventh Schedule item 3 requests.

    Rule 23; Seventh Schedule

Key dates

  1. Rule 13 applies to any notified Significant Data Fiduciary

Answers

Frequently asked questions

What is a Significant Data Fiduciary under DPDP?

A Data Fiduciary, or class of fiduciaries, notified by the Central Government under section 10 of the DPDP Act based on factors such as the volume and sensitivity of data processed, risk to Data Principals' rights, impact on sovereignty and integrity, electoral democracy, security of the State and public order. No SDF had been notified as of this update.

How often must a Significant Data Fiduciary do a DPIA?

Once in every period of 12 months, counted from the date it is notified as an SDF or included in a notified class, under Rule 13(1). It must also undertake an audit in each 12-month period, and the person conducting them must report significant observations to the Board.

Does a Significant Data Fiduciary have to store data in India?

Only for personal data that the Central Government specifies on a committee's recommendation. Rule 13(4) requires that such data, and the traffic data about its flow, not be transferred outside India. It is not a general localisation requirement.

Must a Significant Data Fiduciary appoint a DPO?

Yes. Section 10 of the Act requires an SDF to appoint a Data Protection Officer based in India and responsible to its board of directors or similar governing body, and to appoint an independent data auditor. Other fiduciaries only need to publish a contact person under Rule 9.

What is algorithmic due diligence under DPDP Rule 13?

Rule 13(3) requires an SDF to verify that technical measures, including algorithmic software used for hosting, display, uploading, modification, publishing, transmission, storage, updating or sharing personal data, are not likely to pose a risk to Data Principals' rights. In practice this means inventory, testing, documentation and review.

What is the penalty for SDF non-compliance?

Up to ₹150 crore per instance for breach of the additional obligations of a Significant Data Fiduciary under the DPDP Act's Schedule. Other breaches, such as failure of security safeguards, carry their own penalties. The Board sets amounts after an inquiry.

Legal references and sources

  • Digital Personal Data Protection Rules, 2025 — Rule 13 (official text)
  • Digital Personal Data Protection Act, 2023 — Section 10 (official text)
  • Digital Personal Data Protection Rules, 2025 — Seventh Schedule, item 3 (official text)
  • Digital Personal Data Protection Act, 2023 — Schedule (penalties) (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

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.