[Analysis] Significant Data Fiduciary under the DPDP Act – Notification Criteria | DPO | Independent Audit | DPIA | Localisation

  • Blog|Company Law|
  • 20 Min Read

Significant Data Fiduciary obligations under section 10 and Rule 13: the six notification criteria, the four conditions governing the Data Protection Officer, the annual independent data audit and DPIA with Board reporting, the Rule 13(3) algorithmic risk assessment and the localisation power.

  • By Taxmann
  • |
  • Last Updated on 16 November, 2026
A Significant Data Fiduciary is not a self-assessed category. Section 10(1) makes it a discretionary act of the Central Government, exercised by notification on the basis of six enumerated factors, with no quantitative threshold attached to any of them. Once notified, the organisation takes on a Data Protection Officer who must be based in India and responsible to the governing body, an independent data auditor, an annual Data Protection Impact Assessment and audit with a report of significant observations to the Board, verification that its algorithmic software does not pose a risk to Data Principal rights, and data localisation for categories the Central Government may specify. Taxmann’s Digital Personal Data Protection notes the penalty exposure for getting the assessment wrong, or for not making it at all: up to Rs. 150 crore.

Table of Contents

  1. What is a Significant Data Fiduciary?
  2. How does an organisation become one?
  3. What additional obligations follow from the designation?
  4. What does the Data Protection Officer requirement actually demand?
  5. What does the independent data audit involve?
  6. What must the DPIA contain, and how often is it due?
  7. What does the algorithmic risk assessment under Rule 13(3) require?
  8. Is data localisation in force?
  9. How should the annual cycle be run?
  10. Should an organisation assess its status before being notified?
  11. What does an auditor test, and what goes wrong?
  12. Quick answers

1. What is a Significant Data Fiduciary?

The DPDP Act applies to every Data Fiduciary, regardless of size, sector or the volume of personal data it processes. The general obligations under sections 4 through 9, covering notice, consent, security safeguards, breach notification, retention, erasure and children’s data protections, are universal. Section 10 introduces a second tier of regulation that applies only to a subset of Data Fiduciaries designated by the Central Government as Significant Data Fiduciaries (para 10, opening).

The rationale is that risk is not uniform. Taxmann’s Digital Personal Data Protection puts it in terms that make the tiering intuitive: a neighbourhood clinic processing the personal data of a few hundred patients presents a different risk profile from a digital payments platform processing the financial data of hundreds of millions of users. The additional obligations are calibrated to the elevated risk that the larger entity’s processing creates (para 10, opening).

The book also notes where the DPDP Act diverges from the GDPR in getting to the same place. The GDPR triggers specific obligations by reference to the nature of the processing: a Data Protection Impact Assessment is required under Article 35 whenever processing is likely to result in a high risk to rights and freedoms, and a Data Protection Officer must be appointed under Article 37 where core activities involve regular and systematic monitoring on a large scale or large-scale processing of special categories of data. The DPDP Act consolidates these obligations into a single designation that triggers a comprehensive set of additional requirements, rather than applying each requirement independently on the basis of separate risk assessments (paras 10, opening and 10.1).

That produces a clearer binary, as the book observes: an entity either is or is not a Significant Data Fiduciary. It also concentrates the designation decision in the executive rather than distributing it across self-assessment by individual controllers (para 10.1).

2. How does an organisation become one?

By notification, and only by notification. Section 10(1) provides that the Central Government may notify any Data Fiduciary or class of Data Fiduciaries as a Significant Data Fiduciary, on the basis of an assessment of such relevant factors as it may determine. The provision then enumerates six factors the Central Government may consider (para 10.1):

Clause Factor
10(1)(a) The volume and sensitivity of personal data processed
10(1)(b) Risk to the rights of the Data Principal
10(1)(c) Potential impact on the sovereignty and integrity of India
10(1)(d) Risk to electoral democracy
10(1)(e) Security of the State
10(1)(f) Public order

Three features of that provision shape how an organisation should read it. The factors are stated in permissive terms: the Central Government “may” consider them. The provision prescribes no quantitative thresholds for any factor, so it does not say that a Data Fiduciary processing the personal data of more than a given number of individuals shall be deemed Significant, nor does it define “sensitivity” by reference to categories of data. And the assessment is therefore a matter of discretion, guided by the enumerated factors but not mechanically determined by them (para 10.1).

The book is even about the consequences of that design. It gives the Central Government considerable flexibility to tailor the designation to evolving circumstances, including the emergence of new technology platforms, changes in the threat environment and the identification of specific processing activities that present elevated risks. It also creates a degree of uncertainty for Data Fiduciaries that cannot definitively determine their status until a notification is issued (para 10.1).

There is a procedural mechanism that precedes a notification, and it is worth knowing about because it may be the first signal an organisation receives. Rule 23 and the Seventh Schedule provide a mechanism for the Central Government to gather the information necessary for the assessment. The Seventh Schedule, at entry 3, specifies that information may be called for from Data Fiduciaries for the purpose of carrying out an assessment for notifying any Data Fiduciary or class of Data Fiduciaries as a Significant Data Fiduciary, through such officer of the Central Government in the Ministry of Electronics and Information Technology as the Secretary in charge of the Ministry may designate. The Data Fiduciary is required to furnish the information called for within the specified period (para 10.1).

In other words, a request for information under Rule 23 may be the assessment in progress.

3. What additional obligations follow from the designation?

Those set out in section 10(2) and Rule 13 (para 10, opening):

Obligation Source Periodicity
Appoint a Data Protection Officer based in India Section 10(2)(a) Continuous
Appoint an independent data auditor to carry out a data audit Section 10(2)(b), Rule 13(1) Once every twelve months
Undertake a Data Protection Impact Assessment Section 10(2)(c)(i), Rule 13(1) Once every twelve months
Furnish a report of significant observations to the Board Rule 13(2) Each cycle
Verify that algorithmic software does not pose a risk to Data Principal rights Rule 13(3) Continuous, on deployment and material modification
Ensure specified personal data and its traffic data are not transferred outside India Rule 13(4) and (5) On notification of specified categories

The penalty for breach of these additional obligations is set by the Schedule to the Act at up to Rs. 150 crore (para 14.4).

4. What does the Data Protection Officer requirement actually demand?

Section 10(2)(a) requires the Significant Data Fiduciary to appoint a Data Protection Officer who shall satisfy four conditions (para 10.2):

Condition What it means in practice
The individual shall represent the Significant Data Fiduciary under the provisions of the Act The DPO is the organisation’s face in proceedings under the Act
The individual shall be based in India A residency condition, examined below
The individual shall be responsible to the Board of Directors or similar governing body A direct reporting line to the highest level of corporate governance
The individual shall be the point of contact for the grievance redressal mechanism under the Act The DPO receives and owns Data Principal grievances

Section 2(l) defines the Data Protection Officer simply as an individual appointed by the Significant Data Fiduciary under section 10(2)(a) (Glossary).

Two of the four conditions are frequently misread.

On reporting, the book draws the contrast with the GDPR carefully. The GDPR’s DPO under Article 38 must be involved in all issues relating to the protection of personal data, must not receive instructions regarding the exercise of tasks, and must report to the highest management level. The DPDP Act does not prescribe independence from management instruction, but it does require the DPO to be responsible to the Board of Directors or similar governing body, which establishes a direct reporting line to the highest level of corporate governance. The DPO is not positioned as a middle-management compliance officer who reports through a chain of functional managers; the statute requires accountability to the board or its equivalent (para 10.2).

On residency, the condition has teeth. The requirement that the DPO be based in India ensures the individual responsible for the organisation’s compliance is physically present within the jurisdiction, accessible to the Board in proceedings, and able to engage with the regulatory machinery directly. The book’s illustration is pointed: a multinational corporation that designates its global Chief Privacy Officer, resident in a foreign jurisdiction, as the DPO for its Indian operations does not satisfy this condition. The individual must be based in India, which ordinarily means that India is the person’s primary work location and that they are available for in-person engagement with the Board, the Central Government and Data Principals, as required (para 10.2).

What the Act does not prescribe is qualifications. There are no required professional certifications or minimum experience, which is a departure from several data protection statutes that require the DPO to possess expert knowledge of data protection law and practices. The book’s view is that the absence of a statutory qualification requirement does not diminish the practical need. A DPO who represents the Significant Data Fiduciary under the Act, serves as the point of contact for grievance redressal and is responsible to the Board must have a working understanding of the Act and Rules, the organisation’s processing activities, the security safeguard architecture, the breach notification process and the rights fulfilment mechanisms. Appointing an individual who lacks this understanding, even where the appointment satisfies the formal conditions of section 10(2)(a), will produce an ineffective DPO function that exposes the organisation to both operational risk and regulatory censure (para 10.2).

On how to make the appointment work, the book treats it as a senior governance appointment, not a human resources decision delegated to a functional department. The appointment should be formalised through a board resolution or equivalent governing body action, and the DPO’s terms of reference should specify the reporting line to the board, the scope of responsibilities, the authority to access information across all functions that process personal data, and the resources, including budget, staff and technology, allocated to the role (para 10.7.1).

The integration matters as much as the appointment. The DPO should be informed of and consulted on any material change to processing activities: a new product launch involving new categories of personal data, a new vendor engagement involving cross-border data transfer, a system change affecting the security safeguard architecture, or a policy change altering the basis on which personal data is retained or shared. The DPO should have standing agenda time at board meetings, or at a minimum at the meetings of a board-level committee responsible for risk, compliance or technology oversight, and should provide periodic reports on the state of compliance (para 10.7.1).

Taxmann.com | Research | Subscribe Now!

5. What does the independent data audit involve?

Section 10(2)(b) requires the Significant Data Fiduciary to appoint an independent data auditor to carry out a data audit, who shall evaluate the compliance of the Significant Data Fiduciary in accordance with the provisions of the Act. Rule 13(1) supplies the periodicity: 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, the Significant Data Fiduciary shall undertake a Data Protection Impact Assessment and an audit to ensure effective observance of the provisions of the Act and the rules made thereunder (para 10.3).

The independence requirement is stated without elaboration and the Act does not define the criteria. Drawing on established audit standards, including those under the Companies Act, 2013 for statutory auditors, the ICAI’s standards on auditing for independence and the ISACA framework for information systems audit, the book sets out what independence would ordinarily require (para 10.3):

Requirement The question it answers
No financial interest in the Significant Data Fiduciary other than the audit engagement Does the auditor have anything to gain beyond the fee?
No consulting or implementation services to the same entity in respect of the same subject matter being audited Is the auditor auditing its own work?
Not a current or recent employee of the entity Is this an internal review presented as an independent audit?
Professional judgment exercised without direction or influence from the entity’s management Who decided the scope?

The book’s caution is specific: an auditor that has designed the very controls it is now auditing, or that receives a material portion of its revenue from the entity being audited, would face legitimate questions about independence in a Board proceeding (para 10.3).

On reporting, Rule 13(2) requires the Significant Data Fiduciary to cause the person carrying out the Data Protection Impact Assessment and audit to furnish to the Board a report containing significant observations. Two points follow. The obligation to furnish the report rests on the Significant Data Fiduciary, not on the auditor directly, so the organisation must ensure that the auditor produces the report and that it is transmitted. And the content is limited to significant observations, not the entirety of the audit findings, which means the determination of what is significant requires professional judgement informed by the materiality of the finding, the number of Data Principals affected, the severity of the risk to Data Principal rights, and whether the finding indicates a systemic rather than isolated compliance gap (para 10.3).

The engagement should be structured accordingly: define the audit scope, identify and evaluate potential auditors against independence and competence criteria, and conclude with a formal engagement letter specifying the scope, the applicable standards and methodology, the deliverables including the Rule 13(2) report, the timeline, and the terms of access to systems, records and personnel. The independence assessment should itself be documented and retained, because the Board may scrutinise the auditor’s independence when reviewing the report, and a finding that the auditor lacked independence could undermine the credibility of the entire audit and the organisation’s compliance position (para 10.7.2).

6. What must the DPIA contain, and how often is it due?

Section 10(2)(c)(i) requires the Significant Data Fiduciary to undertake a periodic Data Protection Impact Assessment, which shall be a process comprising a description of the rights of Data Principals and the purpose of processing of their personal data, assessment and management of the risk to the rights of the Data Principals, and such other matters regarding the process as may be prescribed. Rule 13(1) specifies the periodicity as once every twelve months, measured from the date of notification as a Significant Data Fiduciary (para 10.4).

The difference from the GDPR DPIA is one of trigger, and it changes the operating model. The GDPR DPIA is triggered by specific categories of high-risk processing, such as systematic and extensive profiling with legal effects, large-scale processing of special categories, or systematic monitoring of a publicly accessible area, and is required only for processing likely to result in a high risk. The DPDP Act’s DPIA is a periodic obligation that applies to the Significant Data Fiduciary’s processing as a whole, conducted annually regardless of whether any specific processing activity has changed. As the book puts it, the DPIA is not event-driven; it is calendar-driven, which means a fresh assessment is required every twelve months even if processing activities have remained unchanged since the previous assessment (para 10.4).

The statutory content requirements establish a minimum, not a ceiling. A well-structured DPIA would additionally include a description of the processing activities under assessment, the categories and volumes of personal data involved, the data flows including transfers to Data Processors and cross-border transfers, the technical and organisational measures in place, the identification of specific risks to Data Principal rights such as those arising from data inaccuracy, excessive retention, inadequate security or lack of transparency, the assessment of the likelihood and severity of each identified risk, and the measures adopted or proposed to mitigate each risk. The DPIA should produce a documented risk register and a remediation plan, both of which feed into the report to the Board under Rule 13(2) (para 10.4).

Figure 10.1 in the book sets out the structure in seven parts (para 10.7.4):

Part Contents
1. Scope and context Assessment period; assessor name, designation and independence declaration; processing activities in scope; status of open items from the prior cycle
2. Description of processing [section 10(2)(c)(i)] Categories of personal data processed; categories and estimated volume of Data Principals; specified purposes for each processing activity; data flow maps covering internal systems, Data Processors and cross-border transfers; technical and organisational measures currently in place
3. Rights of Data Principals [section 10(2)(c)(i)] Notice compliance assessment under section 5 and Rule 3; consent mechanism assessment under section 6; rights fulfilment mechanism assessment under sections 11 to 14 and Rule 14; grievance mechanism assessment under section 13 and Rule 14(3)
4. Risk assessment [section 10(2)(c)(i)] Risk identification; risk analysis by likelihood against severity; risk register with risk owner, current controls and residual risk rating
5. Risk treatment Mitigation measures for high and medium risks; implementation timeline and responsible owner; accepted risks with documented justification
6. Algorithmic risk assessment [Rule 13(3)] Inventory of algorithmic and automated processing systems; assessment of each system against Data Principal rights risk; testing methodology and results
7. Significant observations for the Board report [Rule 13(2)] Material findings; systemic risks identified; remediation status and timeline

The template closes with a DPO signature, a board or governing body acknowledgement and a date (para 10.7.4).

The methodology itself should be documented as a standard operating procedure that can be applied consistently across annual cycles, defining the scope of the assessment, the risk assessment framework with its criteria and scales, the data gathering process of interviews, document reviews, system inspections and data flow mapping, the risk treatment process, and the documentation and reporting requirements (para 10.7.3).

The first cycle is the expensive one. It requires the organisation to build the methodology, gather baseline data on all processing activities and conduct the initial risk assessment from a standing start. Subsequent cycles can build on the baseline, focusing on changes in processing activities, new risks identified through incidents or audit findings, and the effectiveness of previously implemented mitigation measures. The organisation should plan for the first DPIA cycle to begin well in advance of the twelve-month deadline following its notification, so that the assessment is complete, the report prepared and the significant observations furnished to the Board within the prescribed period (para 10.7.3). Where the methodology and the first cycle have to be built rather than refreshed, Taxmann Advisory provides implementation support, including compliance SOPs and automation of compliances.

7. What does the algorithmic risk assessment under Rule 13(3) require?

This is the obligation most often missed, and the book flags it as distinctive to the DPDP Rules with no direct statutory equivalent in the Act’s text beyond the general DPIA requirement (para 10.5).

Rule 13(3) requires a Significant Data Fiduciary 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 processed by it are not likely to pose a risk to the rights of Data Principals (para 10.5).

Two words in that provision carry most of the weight. “Verify” means the obligation is not satisfied by assumption. And the enumerated operations, nine of them, mean the verification must extend to every technical measure used across the full spectrum of data processing operations: hosting, display, uploading, modification, publishing, transmission, storage, updating and sharing (para 10.5).

The provision is directed at the automated decision-making systems, recommendation engines, content moderation algorithms, fraud detection models, credit scoring algorithms and other software systems that process personal data and produce outcomes affecting Data Principals (para 10.5).

The practical difficulty the book identifies is that the risks may not be apparent from an examination of the algorithm’s design specification alone. A recommendation algorithm designed to maximise user engagement may, in practice, produce outcomes that disproportionately expose certain categories of users to harmful content, or create filter bubbles that restrict the diversity of information available to the Data Principal. A credit scoring model designed to assess creditworthiness on the basis of financial data may, in practice, produce discriminatory outcomes if the training data reflects historical biases. Rule 13(3) therefore requires the Significant Data Fiduciary to look beyond design intent and assess actual or likely outcomes, which in turn requires testing, monitoring and periodic review of algorithmic systems in production (para 10.5).

The book sets this alongside the European Union’s Artificial Intelligence Act, which entered into force in 2024 and establishes a risk-based classification framework for AI systems operating independently of the GDPR. High-risk AI systems there, including those used for credit scoring, employment decisions, access to essential services and law enforcement, are subject to mandatory conformity assessments, risk management systems and human oversight requirements. Rule 13(3) does not establish a comparable classification framework, but its requirement that Significant Data Fiduciaries verify that algorithmic software does not pose a risk to Data Principal rights addresses the same underlying concern: that automated processing systems can produce outcomes that harm individuals in ways the Data Fiduciary may not anticipate unless it conducts a systematic assessment (para 10.5).

The common failure is one of recognition rather than effort. The book records it among its findings: the algorithmic risk assessment is not conducted because the organisation did not recognise its recommendation engine or fraud scoring model as falling within Rule 13(3) (para 10.8).

8. Is data localisation in force?

The framework is in force. The obligation is not yet activated in respect of any specific data category.

Rule 13(4) requires the Significant Data Fiduciary 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 the territory of India (para 10.6).

Rule 13(5) defines the committee as one constituted by the Central Government for the purpose of this rule, which shall include officials from the Ministry of Electronics and Information Technology and may include officials from other Ministries or Departments of the Central Government. The book reads the committee mechanism as ensuring that the specification of data categories for localisation is informed by inter-ministerial consultation rather than determined by a single Ministry, reflecting the cross-cutting nature of decisions that may affect financial services, healthcare, telecommunications, defence and other sectors simultaneously (para 10.6).

As of the date of the Timelines Notification G.S.R. 843(E), dated 13 November 2025, the Central Government has not specified any categories of personal data for mandatory localisation under Rule 13(4), nor has the constitution of the committee under Rule 13(5) been publicly announced (para 10.6).

The book’s recommendation is to prepare rather than wait. Significant Data Fiduciaries should conduct a data residency assessment identifying where each category of personal data currently resides, which categories are processed or stored outside India, and what architectural changes would be required to bring specific categories within Indian territory if a notification is issued. The cost and complexity of data repatriation increase with delay; an organisation that begins the assessment only after a notification is issued will face a compressed implementation timeline under enforcement pressure (para 10.6).

This localisation power is specific to Significant Data Fiduciaries. The general position on sending personal data outside India, the section 16 framework and the sector rules that keep data in India are covered in the post on data localisation and cross-border transfers under the DPDP Act.

9. How should the annual cycle be run?

As a compliance calendar managed with the same rigour as the financial reporting calendar. Several of the obligations, the DPIA, the audit and the Board reporting under Rule 13(1) and (2), are annual, and the book sets milestones measured backwards from the cycle deadline (para 10.7.5):

Milestone Timing before the cycle deadline
Initiate the DPIA and the audit engagement At least three months
Complete fieldwork and analysis At least six weeks
Draft the DPIA and audit reports At least four weeks
Management review of findings and development of remediation plans At least two weeks
Finalise and submit the report of significant observations to the Board By the deadline

The twelve-month cycle should be defined from the date of notification. Alongside it, the calendar should incorporate the obligations that are continuous rather than annual: the algorithmic risk assessment under Rule 13(3), which should be conducted whenever new algorithmic systems are deployed or existing systems are materially modified; the data localisation monitoring under Rule 13(4), which requires awareness of any Central Government notification specifying data categories; and the DPO’s reporting to the board at regular intervals through the year (para 10.7.5).

The book’s warning on this point is the one most worth carrying into a steering committee. An organisation that treats its Significant Data Fiduciary obligations as an annual compliance exercise rather than a continuous governance function will find that compliance gaps accumulate between cycles and that the annual assessment becomes a remediation exercise rather than a verification exercise (para 10.7.5).

10. Should an organisation assess its status before being notified?

Yes, and the book makes the case on lead time rather than on legal obligation.

Organisations that process personal data at scale, or that process data of a nature engaging the criteria under section 10(1), should proactively assess whether they are likely to fall within a notification. Until the Central Government issues specific notifications there is no definitive threshold. But an organisation processing the personal data of millions of individuals, or processing health data, financial data or biometric data at scale, should treat the Significant Data Fiduciary obligations as a planning scenario rather than as a contingency (para 2.14.3).

The practical consequence of proactive assessment is lead time. If an organisation waits for a notification and then discovers it is a Significant Data Fiduciary, it must immediately appoint a Data Protection Officer, engage an independent data auditor, conduct its first Data Protection Impact Assessment and establish the governance structures required under section 10(2) and Rule 13. Doing so under time pressure, with an enforcement deadline already in effect, is materially more difficult and more expensive than building these capabilities in advance. The book’s conclusion is unsentimental: the cost of early preparation, even if the notification never comes, is modest; the cost of late preparation, if it does, is high (para 2.14.3).

There is a penalty dimension too. An incorrect assessment, whether an organisation wrongly concludes it is not a Significant Data Fiduciary or fails to assess the question at all, carries a penalty exposure of up to Rs. 150 crore under the Schedule (para 1.9.3).

Appendix A records the evidence this assessment should leave behind: a copy of the Central Government notification if applicable, a self-assessment against the notification criteria covering volume and sensitivity of data, risk to Data Principal rights, impact on sovereignty, electoral democracy, security and public order, a board or management resolution acknowledging Significant Data Fiduciary status or non-applicability, and a compliance plan for the additional obligations (Appendix A, section 1).

11. What does an auditor test, and what goes wrong?

The test programme the book sets out for this chapter runs as follows (para 10.8): whether the DPO is appointed, based in India and reports to the Board of Directors or equivalent governing body; whether the DPO’s terms of reference are documented; whether the DPIA has been conducted within the twelve-month cycle prescribed by Rule 13(1); whether the DPIA covers the statutory content requirements of section 10(2)(c)(i); whether the independent data auditor satisfies the independence requirements; whether the audit report containing significant observations has been furnished to the Board under Rule 13(2); whether the algorithmic risk assessment under Rule 13(3) has been conducted for all automated processing systems; and whether data localisation requirements under Rule 13(4) are being monitored and, if applicable, implemented.

The evidence to have ready: the DPO appointment letter or board resolution; the DPO’s terms of reference; DPO reporting records to the board, including meeting minutes and reports; the DPIA report for the current cycle; the prior cycle DPIA with remediation tracking; the auditor engagement letter with independence declaration; the audit report with significant observations; evidence of Board submission such as a transmission receipt or acknowledgement; the algorithmic systems inventory; algorithmic risk assessment reports with testing evidence; and the data residency assessment for Rule 13(4) preparedness (para 10.8).

The five findings the book reports as recurring (para 10.8):

Finding What it looks like
DPO appointed without terms of reference No documented terms of reference and no regular board reporting cadence
DPIA limited to a policy review The DPIA was conducted, but with no data flow mapping, no risk register and no algorithmic assessment
Auditor independence compromised A concurrent consulting engagement with the same entity
Board report not submitted The DPIA was completed but the Rule 13(2) Board reporting step was omitted
Algorithmic risk assessment not conducted The organisation did not recognise its recommendation engine or fraud scoring model as falling within Rule 13(3)

Two of those five are failures of completion rather than of capability. The DPIA was done and the Board report was not sent. The DPO was appointed and the terms of reference were never written. Both are inexpensive to fix and expensive to leave.

12. Quick answers

What is a Significant Data Fiduciary under the DPDP Act?

A Data Fiduciary, or class of Data Fiduciaries, notified as such by the Central Government under section 10(1) of the Digital Personal Data Protection Act, 2023. The designation is not self-assessed and is not triggered by a statutory threshold: it is a discretionary act of the Central Government, exercised by notification on the basis of an assessment of six enumerated factors. Once notified, the organisation carries additional obligations under section 10(2) and Rule 13.

What is the difference between a Data Fiduciary and a Significant Data Fiduciary?

Every Data Fiduciary bears the general obligations under sections 4 through 9: notice, consent, security safeguards, breach notification, retention, erasure and children’s data protections. A Significant Data Fiduciary bears those obligations and more under section 10(2) and Rule 13: a Data Protection Officer based in India and responsible to the governing body, an independent data auditor, an annual Data Protection Impact Assessment and audit with a report of significant observations to the Board, verification that its algorithmic software does not pose a risk to Data Principal rights, and data localisation for categories the Central Government may specify.

Under Rule 13, when is a Significant Data Fiduciary required to conduct a DPIA?

Once in every period of twelve months from the date on which it is notified as a Significant Data Fiduciary, or is included in the class of Data Fiduciaries notified as such. Rule 13(1) requires both a Data Protection Impact Assessment and an audit in that cycle. The obligation is calendar-driven, not event-driven, so a fresh assessment is required every twelve months even if processing activities have not changed.

Who must appoint a Data Protection Officer in India?

Only a Significant Data Fiduciary, under section 10(2)(a). The DPO must represent the organisation under the Act, be based in India, be responsible to the Board of Directors or similar governing body, and be the point of contact for the grievance redressal mechanism. The Act prescribes no professional qualifications. A global Chief Privacy Officer resident outside India does not satisfy the residency condition. Other Data Fiduciaries publish the contact details of a designated person under section 8(9) and Rule 9 instead.

What are the criteria for being notified as a Significant Data Fiduciary?

Section 10(1) enumerates six factors the Central Government may consider: the volume and sensitivity of personal data processed, risk to the rights of the Data Principal, potential impact on the sovereignty and integrity of India, risk to electoral democracy, security of the State, and public order. The factors are permissive and carry no quantitative thresholds, so the assessment is a matter of discretion guided by them rather than mechanically determined by them.

What does Rule 13(3) require about algorithms?

A Significant Data Fiduciary must observe due diligence to verify that technical measures including algorithmic software it adopts 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 obligation is to verify rather than to assume, which requires testing, monitoring and periodic review of algorithmic systems in production, and it covers recommendation engines, fraud detection models, credit scoring algorithms and content moderation systems.

Is data localisation mandatory for Significant Data Fiduciaries?

The framework is in force but not yet activated. Rule 13(4) requires a Significant Data Fiduciary to ensure that personal data specified by the Central Government, on the recommendations of a committee constituted under Rule 13(5), together with the traffic data pertaining to its flow, is not transferred outside India. As of the Timelines Notification G.S.R. 843(E), dated 13 November 2025, no categories have been specified and the committee’s constitution has not been publicly announced.

What is the penalty for breach of Significant Data Fiduciary obligations?

Up to Rs. 150 crore under the Schedule to the Act. Section 33(1) applies the penalty power only where the Board determines the breach to be significant, and section 33(2) requires the amount to be calibrated against seven factors, including the nature, gravity and duration of the breach, the mitigation action taken and its timeliness, and the likely impact of the penalty on the person.


This article draws on Chapter 10 of Taxmann’s Digital Personal Data Protection – An Essential Guide to India’s DPDP Law by CA Narasimhan Elangovan (2026 Edition), which examines the notification criteria, the four conditions governing the Data Protection Officer, the independent data audit and the independence standard, the annual DPIA with the structure set out in Figure 10.1, the Rule 13(3) algorithmic risk assessment, the localisation power, the annual compliance calendar and the audit considerations for this chapter. It also draws on Chapter 2 on assessing Significant Data Fiduciary status in advance of a notification, and on Chapter 14 and Appendix A on the penalty framework and the evidence a notification assessment should leave behind. Law stated as updated till 15 September 2026.

The DPDP Act, 2023, the DPDP Rules, 2025 and the notifications of 13 November 2025 are available on Taxmann.com | Research under Indian Acts and Rules.

Related reading: obligations of Data Fiduciaries under the DPDP Act · scope and key definitions · cross-border data transfers · the DPDP Act compared with the EU GDPR.

More in this series: the Data Protection Board of India · how a DPDP compliance audit is conducted · Consent Managers under the DPDP framework · personal data breach intimation under Rule 7 · handling Data Principal rights requests · Data Fiduciary, Data Processor or both · children’s data and verifiable parental consent · the SPDI Rules and the DPDP Act · the Record of Processing Activities (ROPA) · the incident response plan · data retention and erasure · the privacy notice under Rule 3 · the data processing agreement · data localisation and cross-border transfers · employee data and workplace monitoring · exemptions under the DPDP Act · legitimate uses under section 7.

Disclaimer: The content/information published on the website is only for general information of the user and shall not be construed as legal advice. While the Taxmann has exercised reasonable efforts to ensure the veracity of information/content published, Taxmann shall be under no liability in any manner whatsoever for incorrect information, if any.

Leave a Reply

Your email address will not be published. Required fields are marked *

Everything on Tax and Corporate Laws of India

To subscribe to our weekly newsletter please log in/register on Taxmann.com

Author: Taxmann

Taxmann Publications has a dedicated in-house Research & Editorial Team. This team consists of a team of Chartered Accountants, Company Secretaries, and Lawyers. This team works under the guidance and supervision of editor-in-chief Mr Rakesh Bhargava.

The Research and Editorial Team is responsible for developing reliable and accurate content for the readers. The team follows the six-sigma approach to achieve the benchmark of zero error in its publications and research platforms. The team ensures that the following publication guidelines are thoroughly followed while developing the content:

  • The statutory material is obtained only from the authorized and reliable sources
  • All the latest developments in the judicial and legislative fields are covered
  • Prepare the analytical write-ups on current, controversial, and important issues to help the readers to understand the concept and its implications
  • Every content published by Taxmann is complete, accurate and lucid
  • All evidence-based statements are supported with proper reference to Section, Circular No., Notification No. or citations
  • The golden rules of grammar, style and consistency are thoroughly followed
  • Font and size that's easy to read and remain consistent across all imprint and digital publications are applied