Skip to main content
Home/DPDP Act/Chapter II — Obligations of Data Fiduciary/Section 10 — Additional Obligations of Significant Data Fiduciary
DPDP Act, 2023 · Chapter II · Section 10 of 44

Section 10: Additional Obligations of Significant Data Fiduciary

Section 10 closes out Chapter II with a heavier compliance tier reserved for organisations the government formally designates as Significant Data Fiduciaries — an India-based Data Protection Officer, an independent data auditor, and ongoing impact assessments and audits.

Effective from 13 May 2027Reviewed September 2026
StatusEffective 13 May 2027
Chapter II · Obligations of Data Fiduciary

Quick summary

In plain terms: The Central Government can notify any Data Fiduciary, or class of Data Fiduciaries, as a Significant Data Fiduciary based on factors like the volume and sensitivity of data they process, and the risk their processing poses to individuals, electoral democracy, public order, or India's sovereignty and security. Once notified, a Significant Data Fiduciary must appoint an India-based Data Protection Officer, appoint an independent data auditor, and carry out periodic Data Protection Impact Assessments and audits.

What Section 10 says

  • Sub-section (1) — the Central Government may notify any Data Fiduciary or class of Data Fiduciaries as a Significant Data Fiduciary, based on an assessment of relevant factors including (a) the volume and sensitivity of personal data processed; (b) risk to the rights of Data Principals; (c) potential impact on the sovereignty and integrity of India; (d) risk to electoral democracy; (e) security of the State; and (f) public order.
  • Sub-section (2)(a) — a notified Significant Data Fiduciary shall appoint a Data Protection Officer who (i) represents the Significant Data Fiduciary under the Act, (ii) is based in India, (iii) is responsible to the Board of Directors or similar governing body, and (iv) is the point of contact for the grievance redressal mechanism.
  • Sub-section (2)(b) — a notified Significant Data Fiduciary shall appoint an independent data auditor to carry out data audits evaluating the Significant Data Fiduciary's compliance.
  • Sub-section (2)(c) — a notified Significant Data Fiduciary shall undertake (i) periodic Data Protection Impact Assessments — a process describing Data Principals' rights, the purpose of processing, and an assessment and management of the risk to their rights; (ii) periodic audits; and (iii) any other prescribed measures.

Breaking it down

Sub-section (1) weighs six factors when deciding who to designate:

  • Volume & sensitivity of data
  • Risk to Data Principals' rights
  • Sovereignty & integrity of India
  • Electoral democracy
  • Security of the State
  • Public order

Once notified, three extra duties apply:

  • Sub-s. (2)(a)

    India-based DPO

    Represents the fiduciary, answers to the board, and handles grievances.

  • Sub-s. (2)(b)

    Independent auditor

    Evaluates compliance through periodic data audits.

  • Sub-s. (2)(c)

    Impact assessments

    Recurring DPIAs and audits, plus any other prescribed measures.

Significant Data Fiduciary status isn't self-declared. It's a formal Central Government notification under sub-section (1), based on the listed factors — an organisation doesn't decide for itself that it's “significant” and voluntarily opt into this tier; equally, it can't assume it's exempt just because it feels like an ordinary business, if the government's notification covers its class.

The six factors combine business-risk and national-interest considerations. Volume/sensitivity of data and risk to Data Principals are the kind of factors a typical data protection law would use; sovereignty, electoral democracy, State security and public order are distinctly India-specific additions, meaning a platform's political or civic footprint — not just its data volume — can be part of why it gets designated.

The DPO role has four specific, non-negotiable features. India-based, board-level accountability, formal representation of the Fiduciary under the Act, and being the actual point of contact for grievances — a compliance officer who ticks only some of these boxes (say, based outside India, or without real board-level standing) doesn't satisfy sub-section (2)(a).

Audits have to be independent, not internal. Sub-section (2)(b) requires the data auditor evaluating compliance be independent — an internal team marking its own work doesn't meet this requirement, distinguishing it from a general internal-audit function.

Impact Assessments are recurring, not one-time. Sub-section (2)(c)(i)'s periodic Data Protection Impact Assessment has to keep describing Data Principals' rights, the processing purpose, and risk assessment/management on an ongoing basis, not as a single document produced once at launch and shelved.

Why this section matters

Most of Chapter II applies uniformly to every Data Fiduciary. Section 10 is where the Act recognises that scale and sensitivity change the risk profile enough to warrant a heavier compliance structure — comparable to how larger or higher-risk organisations face additional governance requirements under many other regulatory regimes. For an organisation that might be designated, the practical question isn't just “are we compliant with Chapter II” but “could we stand up a DPO, an independent auditor, and a recurring impact-assessment process on short notice.”

Real-world example

Example

Kavach Pay, a large digital-payments platform processing financial data at national scale

Kavach Pay's board is briefed after industry reporting suggests large payments platforms are likely candidates for Significant Data Fiduciary notification.

  • Assessing likely designation — Kavach Pay processes high-volume, sensitive financial data nationally — squarely within factors (a) and (b) of sub-section (1) — so the board treats designation as a near-certainty to prepare for, not a remote possibility.
  • Building the DPO role in advance — rather than appointing an existing overseas privacy lead, Kavach Pay recruits an India-based DPO with direct board reporting, satisfying sub-section (2)(a) ahead of any formal notification.
  • Lining up an independent auditor — Kavach Pay engages an external audit firm, rather than relying on its internal compliance team, to satisfy the independence requirement in sub-section (2)(b) once notified.

Who needs to care about this section

  • Large-scale platforms handling sensitive or high-volume personal data — financial services, healthcare, large social or communication platforms — are the most likely candidates for Significant Data Fiduciary notification.
  • Boards and senior leadership — the India-based, board-accountable DPO requirement in sub-section (2)(a) is a governance change, not just a hiring decision.
  • Internal audit and compliance functions — sub-section (2)(b)'s independence requirement means the audit function itself needs restructuring, not just an added checklist.

Common questions

How do we know if our organisation will be designated a Significant Data Fiduciary?
The Central Government notifies specific Data Fiduciaries or classes of them under sub-section (1); it isn't something an organisation opts into or self-assesses definitively, though the listed factors (data volume/sensitivity, risk to rights, and the national-interest factors) give a reasonable basis for anticipating likely designation.
Can our existing Chief Privacy Officer, based outside India, serve as the Data Protection Officer under this section?
No — sub-section (2)(a)(ii) specifically requires the Data Protection Officer to be based in India.
Does the data audit required under sub-section (2)(b) have to be done by an outside firm?
It has to be independent, which in practice generally means an external or otherwise sufficiently separate auditor rather than the Significant Data Fiduciary's own internal compliance team evaluating itself.