← All news and guides
Data protection

Significant Data Fiduciary Readiness: What to Prepare Before Any Designation

Section 10 and Rule 13 in plain English: who could be designated, the DPO, the independent auditor, the yearly DPIA and where AI fits. Start before May 2027.

Mono Team ·

A long empty boardroom table with a single closed folder at its head and tall windows letting in late afternoon light.

Short answer: as of 20 November 2026, we have found no notification designating any company as a Significant Data Fiduciary, but the Central Government can designate any Data Fiduciary or class of them under Section 10 of the DPDP Act, and the law sets no number that tells you whether you are one. If you are designated, you need a Data Protection Officer based in India, an independent data auditor, and a Data Protection Impact Assessment (DPIA) and audit once in every twelve months, with a report of significant observations sent to the Data Protection Board. The duties start on 13 May 2027. Most of the evidence can be built now, before any notice arrives.

This post is for engineering, security and compliance leads at companies that could plausibly be designated: large platforms, lenders, health and education companies, and anyone holding sensitive data at volume. It covers what the Act and Rules say, what to prepare, and where AI systems fit. It is not legal advice. Whether you could be designated, and what a duty means for your business, is for your counsel.

What is a Significant Data Fiduciary, and who decides?

A Significant Data Fiduciary (SDF) is a Data Fiduciary, or a class of Data Fiduciaries, that the Central Government has notified under Section 10 (Section 2(z)). You cannot become one by size alone. The Government has to notify you, or the class you belong to.

Section 10(1) says the Government decides "on the basis of an assessment of such relevant factors as it may determine", including:

  • the volume and sensitivity of the personal data you process
  • the risk to the rights of Data Principals
  • the potential impact on the sovereignty and integrity of India
  • the risk to electoral democracy
  • the security of the State
  • public order

The Act and Rules give no user count, turnover or data volume. Nobody can tell you from the text whether a given company will be caught, and we would not trust anyone who says they can.

One thing is already in the Rules. From 13 May 2027, when it comes into force, Rule 23 and the Seventh Schedule let the Central Government require any Data Fiduciary to furnish information, within a period it specifies, for the purpose of carrying out the assessment for notifying a company as an SDF. So the first sign of designation could be a request for information, not a notification. Have a person who knows where that request goes.

Has any company been designated yet?

As of 20 November 2026, we have found no notification designating any company or class of companies as an SDF. We will update this post if that changes.

ItemPositionSource
DesignationPosition: None found as of 20 November 2026Source: Our check of the Gazette and dpbi.gov.in
Start of the SDF dutiesPosition: 13 May 2027, with the other core dutiesSource: DPDP Rules, 2025, Rule 1(4) (Rule 13 starts eighteen months after publication)
Penalty ceilingPosition: Up to ₹150 crore for breaching the extra SDF dutiesSource: Schedule to the Act, item 4
Possible exemptionPosition: The Government may notify fiduciaries, including startups, as exempt from Section 10Source: Section 17(3)

The penalty is a ceiling. The Board imposes a penalty only after an inquiry, and weighs the facts. Section 17(3) is a power, not a rule: we have not relied on any exemption notification, and you should not either until you have seen one in the Gazette.

What extra duties does a Significant Data Fiduciary have?

Section 10(2) and Rule 13 add five groups of duties on top of the duties every Data Fiduciary has.

DutySourceWhat it asks for
Data Protection OfficerSource: Section 10(2)(a)What it asks for: An individual who represents you under the Act, is based in India, is responsible to your Board of Directors or similar governing body, and is the contact for grievance redressal
Independent data auditorSource: Section 10(2)(b)What it asks for: An auditor to carry out a data audit and evaluate your compliance with the Act
DPIA and audit every twelve monthsSource: Section 10(2)(c); Rule 13(1)What it asks for: A DPIA and an audit "once in every period of twelve months", counted from the date you are notified
Report to the BoardSource: Rule 13(2)What it asks for: You must cause the person who carries out the DPIA and audit to furnish a report of significant observations to the Data Protection Board
Due diligence on technical measuresSource: Rule 13(3)What it asks for: Verify that technical measures, including algorithmic software, for hosting, display, uploading, modification, publishing, transmission, storage, updating or sharing of personal data are not likely to pose a risk to Data Principals' rights
Restricted transfersSource: Rule 13(4)What it asks for: Keep personal data the Government specifies, and the traffic data about its flow, inside India

In October 2026 a Removal of Difficulties Order (S.O. 5458(E)) changed "periodic audit" in Section 10(2)(c)(ii) to "periodic data audit", so both audit duties in Section 10 are about a data audit. Rule 13(2) names the "Board", which the Act defines as the Data Protection Board of India. Briefing your own board of directors on the same findings is good practice, and the DPO's line to that board is a legal requirement.

What makes a Data Protection Officer valid under Section 10?

Four tests come straight from the Act. The DPO must be an individual, must be based in India, must be responsible to your board or equivalent governing body, and must be the point of contact for grievances. A team mailbox or an overseas group privacy lead does not meet them.

Do not confuse this with Rule 9. Rule 9 applies to every Data Fiduciary. It says you must publish on your website or app, and put in every reply to a rights request, the business contact information of the DPO "if applicable", or of a person who can answer questions about the processing. If you are not an SDF, you still need that person from 13 May 2027, when Rule 9 comes into force. Name them now, because the same person is the natural starting point for the SDF role.

Check these before you choose the person:

  • Access. Can they see the data map, vendor list and logs without asking three teams?
  • Reporting line. Can they reach the board directly, and is it written down?
  • Conflicts. Will they be marking their own work? The Act does not say a DPO must be free of other duties, so ask counsel about the risk if the same person runs engineering or security.
  • Grievance capacity. Can they own the grievance queue, with the rights-request records behind it?

Our rights-request workflow post covers the records the grievance contact will need.

Who can be the independent data auditor?

The Act says an "independent data auditor" who evaluates your compliance with the Act. It does not define independence, set qualifications, or create an approved list. We found no degree, licence, accreditation or empanelment requirement in the Act or Rules, and, as of 20 November 2026, no Board guidance. Read our guide to who can do a DPDP audit for the full comparison.

Until the Government or the Board says more, a prudent test for independence is whether the auditor has any stake in the result. A team that built or fixed your controls should not be the one that audits them. If you use a firm to prepare, ask counsel whether the same firm can then be the independent auditor. Mono's readiness work is preparation. It is not the independent audit, and Mono is not a certification body or a law firm.

When you brief an auditor, give them the scope in writing, the evidence list below, and read access to the systems that hold personal data. An auditor cannot evaluate a system nobody told them about, which is why the data map comes first.

What goes into the annual DPIA and audit?

Section 10(2)(c)(i) defines the DPIA as a process made of a description of the rights of Data Principals and the purpose of processing, and an assessment and management of the risk to those rights. It adds "such other matters ... as may be prescribed". We found no further matters in Rule 13, so the Section 10 definition is the checklist.

Build one repeatable pack per processing activity. A workable structure:

Section of the packWhat it holdsEvidence to attach
Description and purposeWhat it holds: What data, whose, why, for how long, and which specified purpose in the noticeEvidence to attach: Data map entry, notice version, retention rule
Rights of Data PrincipalsWhat it holds: How each right works for this activity: access, correction, erasure, grievance, nominationEvidence to attach: Request workflow, sample closed tickets, grievance contact
Risk to those rightsWhat it holds: What could go wrong for the person, how likely, how badEvidence to attach: Risk register with owner and date
Controls and managementWhat it holds: What reduces each risk, and what is left overEvidence to attach: Rule 6 safeguards, access reviews, vendor contracts, logs
DecisionWhat it holds: Who accepted the remaining risk, and whenEvidence to attach: Signed record, date, review date

The audit then tests whether the pack matches what the systems do. Expect an auditor to ask for samples, not statements: a real consent record, a real erasure ticket, a real vendor instruction, and the logs that show them. If your records live in five tools with no common key, fix that first. Our DPDP technical audit post lists the deliverables of that kind of work, and the gap assessment is how it starts.

Why does Rule 13(3) matter for AI systems?

A narrow aisle between tall server racks in a dim data hall, rows of small green status lights fading into soft shallow focus.

Rule 13(3) is the clause most relevant to AI. It asks an SDF to observe due diligence that the "technical measures including algorithmic software" it adopts for handling personal data are "not likely to pose a risk to the rights of Data Principals". The text lists hosting, display, uploading, modification, publishing, transmission, storage, updating and sharing of personal data.

The Rule does not use the word AI. On our reading, a recommendation ranker, a feed, a scoring model or an LLM feature that displays, modifies or shares personal data falls in the same family of measures. Counsel should confirm how far the clause reaches for your products. What it asks for is due diligence, so what you need is a record that you looked, tested and decided.

An AI due diligence file, kept per feature, would hold:

  • An inventory. Every model, ranker and AI feature that touches personal data, including features that employees use on their own, found through a shadow AI audit.
  • A data flow for each one. What personal data goes in, where it is processed, which vendor sees it, and what is stored. Our DPDP-compliant AI architecture post shows the shape.
  • A risk test. What harm to a person you checked for, such as wrong decisions, exposure of one person's data to another, or output that cannot be explained, and the result.
  • Change control. A record of each model, prompt or data-source change, and who approved it.
  • Monitoring. Logs and review of outputs, with a named owner and a date of the last review.
  • Vendor evidence. For each processor, the contract, the data location and the retention terms, as set out in our DPDP and AI tools guide.

Keep each AI file short and dated. An auditor reading a file that was last touched at launch will conclude the due diligence stopped there.

What does Rule 13(4) mean for where data is stored?

Rule 13(4) lets the Central Government, on a committee's recommendation, specify personal data that an SDF must process without transferring it, or the traffic data about its flow, outside India. The Act and Rules have no general data localisation rule, and this power applies only to SDFs. As of 19 November 2026 we found no order specifying any data. Until there is one, there is nothing to comply with, but there is something to prepare: know where each category of personal data, and its logs, is stored and processed, and be able to change a region or vendor without rebuilding a feature.

How do I prepare for designation without waiting for a notice?

An empty boardroom with a long pale wooden table and a row of identical chairs, late afternoon light through tall windows, one chair pushed slightly back.

Work from the cheapest, most useful items. Most are needed for the 13 May 2027 duties anyway, so they are not wasted if you are never designated.

StepWhat to doOutput
1. Data mapWhat to do: List every system, vendor and AI feature that holds or touches personal data, with ownersOutput: One register, reviewed on a schedule
2. Name the contactWhat to do: Appoint the Rule 9 contact, and decide who would be the Section 10 DPOOutput: A named person, a board reporting line on paper
3. DPIA templateWhat to do: Adopt the pack structure above and run it on your two riskiest activitiesOutput: Two completed DPIAs
4. Rule 6 evidenceWhat to do: Collect encryption, access control, logging and backup evidence for each systemOutput: An evidence folder per system
5. AI due diligence filesWhat to do: Create the per-feature files for every AI system that handles personal dataOutput: One file per feature
6. Auditor shortlistWhat to do: Decide the independence rule, and talk to firms that did not build your controlsOutput: A shortlist and a scoping note
7. Data location mapWhat to do: Record where data and logs are stored and processed, and how fast you could moveOutput: A region and vendor table
8. Board paperWhat to do: Brief the board on the designation risk, the duties and the budget linesOutput: A dated board note

Start with steps 1 and 2, which cost the least and unblock the rest. Our DPDP compliance service covers the build, and the self-check is a quick way to see which of the core duties you have not started.

What this post does not cover

It does not say whether you will be designated, whether a particular tool or feature is within Rule 13(3), or whether an exemption applies to you. Those are legal questions, and they go to your counsel. It does not describe any final Board guidance, because we have found none on SDFs. If the Government notifies a designation, sets Rule 13(4) data, or the Board issues guidance, the position here will change.

Sources: Digital Personal Data Protection Act, 2023, Sections 2(z), 10, 17(3), 36 and the Schedule (item 4). Digital Personal Data Protection Rules, 2025, Rules 1(4), 9, 13, 23 and the Seventh Schedule, notified 13 November 2025. Digital Personal Data Protection (Removal of Difficulties) Order, 2026, S.O. 5458(E), 5 October 2026. Last reviewed 20 November 2026.

FAQ

Has any company been designated a Significant Data Fiduciary in India?

As of 20 November 2026, we have found no notification designating any company or class of companies as a Significant Data Fiduciary under Section 10 of the DPDP Act. The extra duties in Section 10(2) and Rule 13 start on 13 May 2027, with the other core duties. We will update this post if the Central Government designates a fiduciary or a class.

What makes a company a Significant Data Fiduciary under the DPDP Act?

Only a notification by the Central Government. Section 10(1) says it assesses factors that include the volume and sensitivity of personal data processed, the risk to the rights of Data Principals, and the potential impact on the sovereignty and integrity of India, electoral democracy, security of the State and public order. The Act and Rules set no numeric threshold, so size alone does not decide it.

What must a Significant Data Fiduciary do under the DPDP Act and Rules?

It must appoint a Data Protection Officer based in India who is responsible to its board and is the grievance contact, and appoint an independent data auditor. Rule 13 adds a Data Protection Impact Assessment and an audit once in every twelve months, a report of significant observations to the Data Protection Board, due diligence on algorithmic and other technical measures, and any data localisation the Government specifies.

How is the Data Protection Officer different from the contact every company must publish?

Rule 9 makes every Data Fiduciary publish the business contact information of a Data Protection Officer, if applicable, or of a person who can answer questions about the processing. Only a Significant Data Fiduciary must appoint a Data Protection Officer under Section 10(2)(a), who must be an individual based in India and responsible to its board. Naming the Rule 9 contact now is a sensible first step.

Does Rule 13 apply to AI systems?

Rule 13(3) asks a Significant Data Fiduciary to verify that technical measures, including algorithmic software, used to host, display, modify, store or share personal data are not likely to pose a risk to Data Principals' rights. It does not name AI. On our reading, recommendation, scoring and LLM features that handle personal data are the kind of measures it covers. Keep a dated due diligence file per feature and ask counsel how far the clause reaches.

Can an auditor who helped me prepare also be my independent data auditor?

The Act requires an independent data auditor but does not define independence or set qualifications. Our view is that a team that built or fixed your controls should not also audit them, because it would be marking its own work. Ask your counsel to confirm the position for your business before you appoint anyone.

Get your evidence ready before any designation.