Obligations of Data Fiduciaries under DPDP Act 2023
- Blog|Company Law|
- 16 Min Read
The meaning of Data Fiduciary under section 2(i) of the DPDP Act, the control test, and the obligations that follow: notice and consent, the section 8 duties, security and breach intimation, retention, grievance redressal, children’s data and penalties.
- By Taxmann
- |
- Last Updated on 16 November, 2026

Table of Contents
- What is the meaning of Data Fiduciary under the DPDP Act?
- Who counts as a Data Fiduciary in practice?
- What must be in place before personal data is processed?
- What does section 8 require of every Data Fiduciary?
- What security safeguards and breach steps are required?
- How long may personal data be kept?
- What must be published, and how are grievances handled?
- What more applies to children’s personal data?
- When do the obligations apply, and what does a failure cost?
- Quick answers
1. What is the meaning of Data Fiduciary under the DPDP Act?
Section 2(i) defines a Data Fiduciary as any person who alone or in conjunction with other persons determines the purpose and means of processing of personal data. The book notes that the definition is functionally equivalent to that of a “controller” under Article 4(7) of the GDPR: the natural or legal person, public authority, agency or other body which, alone or jointly with others, determines the purposes and means of the processing of personal data (para 2.3).
The determinative test is one of control. The question is not who physically handles the data; it is who decides why the data is processed and how (para 2.3). The book’s illustration is a payroll arrangement. An organisation that engages an external payroll provider to process employee salary data remains the Data Fiduciary for that processing, because it determines the purpose, which is salary payment, and the means: the categories of data processed, the frequency of processing and the retention period. The payroll provider, acting on the organisation’s instructions, is the Data Processor (para 2.3).
The counterpart role is defined in section 2(k): a Data Processor is any person who processes personal data on behalf of a Data Fiduciary. It does not determine the purpose and means of processing; it executes instructions received from the Data Fiduciary (para 2.4). The individual to whom the personal data relates is the Data Principal under section 2(j) (para 2.5), whose rights are set out in rights of Data Principals under the DPDP Act.
2. Who counts as a Data Fiduciary in practice?
The answer is less obvious than the definition suggests. Three points from the book settle most cases.
First, the role attaches to the processing activity, not to the organisation. The same entity may be a Data Fiduciary for its employee data, a Data Processor for client data it hosts under a service agreement, and a joint Data Fiduciary with a partner for co-branded marketing. The classification must be assessed for each processing activity on its facts and purpose, not at the entity level (paras 2.4 and 2.14.1).
Second, there can be more than one Data Fiduciary for the same processing. The DPDP Act does not use the term “joint controller” or “co-fiduciary”, but where two or more entities jointly determine the purpose and means of processing, each is a Data Fiduciary for that processing and bears the full set of obligations under the Act (para 2.3).
Third, the role reaches entities that may not recognise themselves in it. The book reads the decision of the Court of Justice of the European Union in Google Spain (2014) as applying to the DPDP Act: search engines, platforms and marketplaces that process personal data in the course of their operations will ordinarily qualify as Data Fiduciaries, even where they host or index content generated by third parties (para 2.3).
A wrong classification cuts both ways. It means either assuming obligations that do not apply, which creates unnecessary compliance overhead, or failing to discharge obligations that do apply, which creates enforcement risk. The book’s advice is to record each determination in a role classification register, reviewed annually at a minimum and immediately on any material change in processing activities (para 2.14.1). How to make and document that determination, activity by activity, is covered in Data Fiduciary, Data Processor or both. To test a particular arrangement against section 2(i), the question can be put to Taxmann AI, which answers questions against the law and drafts from it.
3. What must be in place before personal data is processed?
A lawful basis, a notice and, where consent is the basis, a valid consent that can be proved.
The lawful basis comes from section 4: personal data may be processed only in accordance with the Act and for a lawful purpose, either with the consent of the Data Principal or for one of the legitimate uses enumerated in section 7 (Appendix A, section 2). Those legitimate uses are explained in legitimate uses under section 7.
The notice comes from section 5(1) and Rule 3. Before or at the time of requesting consent, the Data Fiduciary must give a notice that is presented as a standalone document understandable independently of any other information; that gives, in clear and plain language, an itemised description of the personal data and the specified purpose, including a specific description of the goods or services to be provided or uses to be enabled; and that provides the means for withdrawing consent, exercising rights and making a complaint to the Board (Appendix A, section 2). The book’s reading is that these requirements favour short, purpose-specific notices over long, multi-purpose documents (para 4.8.1). The notice is covered in the privacy notice under Rule 3.
The consent must meet section 6(1): free, specific, informed, unconditional and unambiguous, given through a clear affirmative action, and limited to such personal data as is necessary for the specified purpose (Appendix A, section 2). And it must be provable. Under section 6(10), where consent is the basis of processing and a question arises in a proceeding, the Data Fiduciary must prove that a notice was given and consent was obtained in accordance with the Act and the Rules; the Data Principal does not need to prove that she did not consent (para 4.6). That reversal drives system design. The consent record must be immutable, and it must carry the notice version in effect at the time, because a consent record that cannot be linked to the notice under which it was obtained is incomplete evidence (para 4.6). Consent and its withdrawal are discussed further in lawful processing and consent.
4. What does section 8 require of every Data Fiduciary?
The general obligations under sections 4 to 9 apply to every Data Fiduciary, regardless of size, sector or the volume of personal data it processes. Section 10 adds a second tier that applies only to a Data Fiduciary, or a class of Data Fiduciaries, notified by the Central Government as a Significant Data Fiduciary: the appointment of a Data Protection Officer based in India, the engagement of an independent data auditor, an annual Data Protection Impact Assessment and audit with reporting to the Board, algorithmic risk assessment, and data localisation for categories of personal data specified by the Central Government (Chapter 10, opening; para 10.1). Those obligations do not apply to a Data Fiduciary that has not been notified. For other Data Fiduciaries, the book’s counterpart to the Data Protection Officer is the designated contact person under Rule 9 (para 12.2.5). The designation and the second-tier obligations are covered in Significant Data Fiduciary obligations.
Within the first tier, section 8 sets the general obligations. The first four are below; security, breach intimation, retention, contact information and grievance redressal follow in sections 5 to 7.
Accountability, under section 8(1). The Data Fiduciary is responsible for complying with the Act and the Rules in respect of any processing undertaken by it or on its behalf by a Data Processor, irrespective of any agreement to the contrary or any failure of the Data Principal to carry out her duties (Appendix A, section 8). The Data Principal’s duties are set out in section 15 (para 9.5), but a failure to perform them does not shift the Data Fiduciary’s responsibility. Nor does a contract: a clause that purports to transfer the Data Fiduciary’s compliance obligations to the Data Processor does not relieve the Data Fiduciary of liability (para 2.4).
Data Processors only under a valid contract, under section 8(2). A Data Fiduciary may engage a Data Processor to process personal data on its behalf, for any activity related to the offering of goods or services to Data Principals, only under a valid contract. Permitting a vendor to process personal data without a written agreement, whether through an informal arrangement, a verbal understanding or a series of emails that do not constitute a contract, is a breach of section 8(2). Rule 6(1)(f) adds that the contract must contain an appropriate provision for taking reasonable security safeguards; a contract silent on security does not satisfy it, even if it is otherwise valid (para 5.2). The book’s advice is to treat every Data Processor engagement involving personal data this way, including internal administrative ones such as a payroll vendor for the Data Fiduciary’s own employees (para 5.2). The clauses are covered in the data processing agreement.
Data quality, under section 8(3). Where personal data is likely to be used to make a decision that affects the Data Principal, or is likely to be disclosed to another Data Fiduciary, the Data Fiduciary must ensure its completeness, accuracy and consistency. The book gives each attribute an operational meaning: a credit decision made on an incomplete income record fails completeness; an address not updated after the Data Principal moves fails accuracy; a date of birth recorded one way in the human resources system and another in the insurance records fails consistency. Because data degrades over time, the obligation implicitly requires periodic data quality reviews (para 5.3).
Technical and organisational measures, under section 8(4). This is the umbrella obligation: the Data Fiduciary must implement appropriate technical and organisational measures to ensure effective observance of the Act and the Rules. “Appropriate” introduces a standard of reasonableness sensitive to the Data Fiduciary’s circumstances, so what a large bank needs differs from what a small accounting firm needs. And “organisational” matters as much as “technical”: a consent management platform without trained staff, or access control systems without defined and enforced role-based access policies, does not meet the standard (para 5.4).
5. What security safeguards and breach steps are required?
Section 8(5) requires the Data Fiduciary to protect personal data in its possession or under its control by taking reasonable security safeguards to prevent a personal data breach, and the duty extends to personal data processed by Data Processors on its behalf (paras 1.7 and 6.1). Rule 6(1) turns that duty into seven minimum requirements (para 6.1):
- Encryption, obfuscation, masking or the use of virtual tokens, under Rule 6(1)(a).
- Access controls, under Rule 6(1)(b).
- Logging, monitoring and review, under Rule 6(1)(c).
- Business continuity and data backups, under Rule 6(1)(d).
- Retention of logs and personal data for one year, under Rule 6(1)(e), which Rule 8(3) reinforces.
- Contractual provisions with Data Processors, under Rule 6(1)(f).
- Technical and organisational measures for effective observance of the safeguards, under Rule 6(1)(g).
The book stresses two features. The seven are a floor, not a ceiling: a Data Fiduciary that implements all seven inadequately, with encryption that relies on deprecated algorithms or access control lists unreviewed for years, may still fail the reasonableness standard. And they are individually mandatory: a Data Fiduciary that adds safeguards beyond the seven but omits one of them is in breach of Rule 6(1), however strong its overall security posture (para 6.1).
When a breach happens, section 8(6) and Rule 7 govern the response. A personal data breach is any unauthorised processing of personal data, or accidental disclosure, acquisition, sharing, use, alteration, destruction or loss of access to personal data, that compromises its confidentiality, integrity or availability (para 6.2). Each affected Data Principal must be told without delay, through her user account or a mode of communication she has registered, with five prescribed elements: a description of the breach, the consequences likely to arise for her, the measures taken or being taken to mitigate risk, the safety measures she may take, and the business contact information of a person able to respond on the Data Fiduciary’s behalf (para 6.2.1). Unlike Article 34 of the GDPR, which requires notice to the data subject only where a breach is likely to result in a high risk, the DPDP Act requires notice to every affected Data Principal, without a risk threshold (para 6.2.1). The Board must be told without delay and then given detailed information within seventy-two hours of the Data Fiduciary becoming aware of the breach, or such longer period as the Board may allow on a written request (Appendix A, section 6). The operational side is in the incident response plan, and the contents and timing of each intimation in personal data breach intimation under Rule 7.
6. How long may personal data be kept?
Only as long as the purpose requires, subject to two fixed periods in the Rules.
The erasure obligation under section 8(7) requires the Data Fiduciary to erase personal data when the specified purpose is no longer being served (para 6.1.5), and the erasure must reach its Data Processors too: the book places the Data Processor’s duty to erase personal data when directed by the Data Fiduciary in section 8(7)(b) (para 2.4).
The first fixed period is a floor. Under Rule 8(3), personal data, associated traffic data and other logs of processing undertaken by or on behalf of the Data Fiduciary must be retained for a minimum of one year from the date of processing, for the purposes specified in the Seventh Schedule, and then erased unless further retention is required by any other law or as notified by the Government (Appendix A, section 7). The book’s illustration is an e-commerce platform that fulfils an order within three days: it cannot erase the associated personal data and processing logs on fulfilment, and must keep them for at least one year (para 6.1.5).
The second is a notice period. Where section 8(8) and the Third Schedule deem the purpose to have ceased after a period of inactivity, the Data Fiduciary must, at least forty-eight hours before that period ends, inform the Data Principal that the data will be erased unless she logs into her user account, initiates contact for the specified purpose or exercises her rights (paras 1.7, 8.2 and 8.10; Appendix A, section 7).
In audit terms, the test is whether the retention schedule is real: whether data that has reached its retention expiry has actually been erased, and whether Data Processor erasure is evidenced by erasure instructions and confirmations (para 8.10). The evidence an auditor will ask for, obligation by obligation, is set out in how a DPDP compliance audit is conducted. Retention periods and deletion are covered in data retention and erasure.
7. What must be published, and how are grievances handled?
Three things must be visible to the Data Principal. Under section 8(9) and Rule 9, the details of the Data Protection Officer or a designated contact person must be prominently published on the website or application and included in every response to a request to exercise rights (paras 5.5 and 5.8). Under section 8(10), section 13 and Rule 14(3), the Data Fiduciary must provide a readily available grievance mechanism and prominently publish a reasonable response period not exceeding ninety days; the period is a ceiling, not a target, and publishing it is itself a mandatory requirement (para 9.3). And under Rule 14(1), it must prominently publish the means by which a Data Principal may make a request to exercise her rights, and the particulars needed to identify her (para 9.6).
The grievance mechanism matters more than its customer-service appearance suggests. Under section 13(3), a Data Principal must exhaust it before approaching the Board, which makes it the organisation’s primary point of regulatory exposure: a grievance properly investigated and resolved within the prescribed period will ordinarily not reach the Board, while one ignored, inadequately investigated or answered late gives the Data Principal both the cause and the procedural standing to escalate (para 9.3). The book recommends designing it as a structured workflow, with graduated internal timelines that treat the ninety-day ceiling as the absolute outer boundary rather than the default, and auditable records of each grievance, because those records will be the primary evidence of compliance with section 13(2) in a Board inquiry (para 5.7.4).
8. What more applies to children’s personal data?
Three additional obligations under section 9, each stricter than the general regime. A child is an individual who has not completed eighteen years of age (section 2(f); para 2.5).
Before processing any personal data of a child, the Data Fiduciary must, subject to any applicable exemption, obtain the verifiable consent of a parent. The book calls this a precondition and a stricter standard than section 6(1), which prescribes the attributes of valid consent but does not require verification of the identity or status of the person giving it (para 7.1). Rule 10(1) requires appropriate technical and organisational measures and due diligence to check that the individual identifying herself as the parent is an identifiable adult, by reference to reliable identity and age details already held, or to details provided voluntarily or through a virtual token issued by an authorised entity (para 7.1; Appendix A, section 3).
The other two obligations are prohibitions that parental consent cannot lift. Under section 9(2), a Data Fiduciary must not undertake processing likely to cause any detrimental effect on the well-being of a child; the provision is stated in absolute terms and the standard is objective (para 7.2). Under section 9(3), it must not undertake tracking or behavioural monitoring of children or targeted advertising directed at children, a categorical prohibition that applies even where a parent has given verifiable consent (para 7.3). Breach of the children’s obligations carries a maximum penalty of Rs. 200 crore (para 14.4). Verification methods, the Fourth Schedule exemptions and age-gating design are covered in children’s data and verifiable parental consent.
9. When do the obligations apply, and what does a failure cost?
From 13 May 2027. Under Notification G.S.R. 843(E), dated 13 November 2025, sections 3 to 5, section 6(1) to (8) and (10), and sections 7 to 10 come into force on that date as part of the third phase, together with Rules 3 and 5 to 16; the same phase brings in the rights of Data Principals, the Board’s procedure and the penalties (para 1.6). The work of getting ready, from the first ninety days to testing and validation, is set out in the DPDP Act compliance checklist for businesses, and where the mechanisms have to be built rather than described, including compliance SOPs and automation of compliances, Taxmann Advisory provides implementation support.
The Schedule attaches maximum penalties to the Data Fiduciary’s principal obligations: up to Rs. 250 crore for breach of the obligation to take reasonable security safeguards under section 8(5), up to Rs. 200 crore for failing to give notice of a personal data breach under section 8(6), up to Rs. 200 crore for breach of the children’s obligations under section 9, up to Rs. 150 crore for breach of the Significant Data Fiduciary obligations under section 10, and up to Rs. 50 crore for breach of any other provision (para 14.4). The Board may impose a penalty only if it determines that the breach is significant, and must have regard to seven factors in setting the amount, including the nature, gravity and duration of the breach, any gain realised or loss avoided, and the action taken to mitigate its effects (para 14.4). The enforcement process is covered in breach, enforcement and penalties under the DPDP Act.
10. Quick answers
What is a Data Fiduciary under the DPDP Act?
Under section 2(i), any person who alone or in conjunction with other persons determines the purpose and means of processing of personal data. The test is control: the Data Fiduciary is whoever decides why and how the personal data is processed, not whoever physically handles it. An employer that engages a payroll provider to process salary data is the Data Fiduciary, because it decides the purpose and means; the payroll provider, acting on its instructions, is the Data Processor.
Is a Data Fiduciary the same as a data controller?
Functionally, yes. Taxmann’s Digital Personal Data Protection notes that the definition in section 2(i) of the DPDP Act is functionally equivalent to the definition of controller in Article 4(7) of the GDPR, which refers to the natural or legal person, public authority, agency or other body which, alone or jointly with others, determines the purposes and means of the processing of personal data. Under both, the question is who decides why and how personal data is processed.
What are the obligations of a Data Fiduciary under the DPDP Act?
To process personal data only on consent or a legitimate use under sections 4 and 7; to give notice under section 5 and Rule 3; to obtain valid consent under section 6 and be able to prove it; and, under section 8, to remain accountable for processing by Data Processors, engage them only under valid contracts, ensure data quality, implement technical and organisational measures and reasonable security safeguards, notify personal data breaches, erase personal data when the specified purpose is no longer served, publish contact details and provide grievance redressal. Section 9 adds obligations for children’s data, and section 10 adds obligations for Significant Data Fiduciaries.
Under the DPDP Act, which of the following is not an obligation of a Data Fiduciary?
It depends on the options offered, but two groups of items are not obligations of every Data Fiduciary. The first is the second tier under section 10, which applies only to a Data Fiduciary notified by the Central Government as a Significant Data Fiduciary: appointing a Data Protection Officer based in India, engaging an independent data auditor, an annual Data Protection Impact Assessment and audit, algorithmic risk assessment and data localisation. The second is the duties in section 15, which fall on the Data Principal, not the Data Fiduciary. Every Data Fiduciary, by contrast, must give notice, rely on valid consent or a legitimate use, take reasonable security safeguards, notify personal data breaches, erase personal data when the purpose is no longer served, publish contact details and provide grievance redressal.
Who has to prove that consent was obtained?
The Data Fiduciary. Under section 6(10) of the DPDP Act, where consent is the basis of processing and a question arises in a proceeding, the Data Fiduciary must prove that a notice was given and consent was obtained in accordance with the Act and the Rules. The Data Principal does not have to prove that she did not consent.
Does a Data Fiduciary have to publish contact details?
Yes. Under section 8(9) and Rule 9, the details of the Data Protection Officer or a designated contact person must be prominently published on the website or application and included in every response to a request to exercise rights. The Data Fiduciary must also publish its grievance response period, which cannot exceed ninety days under Rule 14(3).
When do the obligations of Data Fiduciaries apply?
From 13 May 2027. Notification G.S.R. 843(E) brings sections 3 to 5, section 6(1) to (8) and (10), and sections 7 to 10 of the DPDP Act into force on that date, together with Rules 3 and 5 to 16 of the DPDP Rules, 2025. Section 6(9), on the registration of Consent Managers, came into force earlier, on 13 November 2026, with Rule 4.
This article draws on Chapters 2 and 5 of Taxmann’s Digital Personal Data Protection – An Essential Guide to India’s DPDP Law by CA Narasimhan Elangovan (2026 Edition), which examine the definitions of Data Fiduciary, Data Processor and Data Principal, the role classification exercise, and the general obligations of a Data Fiduciary under section 8: accountability, Data Processor contracts, data quality, technical and organisational measures, publication of contact information and grievance redressal. It also draws on Chapter 1 on commencement, Chapter 4 on notice and consent, Chapter 6 on security safeguards and breach intimation, Chapter 7 on children’s data, Chapter 8 on retention, Chapter 9 on the grievance framework, Chapter 10 on Significant Data Fiduciaries, Chapter 12 on the compliance programme, Chapter 14 on penalties, and Appendix A, the Consolidated Requirements Register. 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: overview of the DPDP Act · scope and key definitions · rights of Data Principals · lawful processing and consent · cross-border data transfers · breach, enforcement and penalties · the DPDP Act compliance checklist for businesses · the DPDP Act and the IT Act · the DPDP Act and the EU GDPR · startups and SMEs · FinTech and BFSI · healthcare and HealthTech.
More in this series: 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 · the Data Protection Board of India · how a DPDP compliance audit is conducted · Significant Data Fiduciary obligations · 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.
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.

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



CA | CS | CMA