Quick answer
A Data Fiduciary is any person who, alone or with others, determines the purpose and means of processing personal data; a Data Processor processes personal data on behalf of a Data Fiduciary. Under section 8(1) of the DPDP Act, the fiduciary stays responsible for its processors, and may engage them only under a valid contract. Rules 6 and 8(3) add contract and retention duties from 13 May 2027.
- The Data Fiduciary decides purpose and means; the Data Processor only acts on its instructions.
- Section 8(1) makes the fiduciary responsible for compliance even for processing carried out by its processors.
- A processor may be engaged only under a valid contract (section 8(2)), which must include security safeguards (Rule 6(1)(f)).
- Rule 8(3) requires the fiduciary to ensure processors also retain data and logs for at least one year.
- A vendor that uses your customer data for its own purposes, such as training its models, starts to look like a fiduciary for that use.
Who this is for: SaaS and cloud vendors, Indian IT services and BPO firms, Procurement and vendor-risk teams, CTOs and platform engineers, Legal counsel drafting DPAs
What is the difference between a Data Fiduciary and a Data Processor?
The DPDP Act uses two roles for organisations that handle personal data:
- Data Fiduciary (section 2(i)): any person who, alone or in conjunction with other persons, determines the purpose and means of processing personal data.
- Data Processor (section 2(k)): any person who processes personal data on behalf of a Data Fiduciary.
"Person" is broad and includes individuals, companies, firms, associations and the State. The labels describe what you do in a particular processing activity, not what kind of company you are. The same business can be a fiduciary for its own HR and marketing data and a processor for the customer data it hosts for clients.
The word "fiduciary" is deliberate. It signals a relationship of trust towards the Data Principal, not just a technical role. That is why the Act loads almost all obligations onto the fiduciary: notice, consent, security, breach intimation, erasure, grievance redressal and responding to rights requests.
The DPDP Act is close to GDPR here: fiduciary maps to "controller" and processor to "processor". The main difference is that the DPDP Act puts very few direct statutory duties on processors; their obligations flow mostly through the contract the fiduciary must sign with them.
How to tell which role you play
Ask these questions for each processing activity, not for the company as a whole:
| Question | Points to Fiduciary | Points to Processor |
|---|---|---|
| Who decided to collect the data and why? | You did | Your customer did |
| Who chooses which data fields, retention and recipients? | You | The customer, via contract and configuration |
| Do you use the data for your own product analytics, model training or marketing? | Yes, for that use | No |
| Does the Data Principal have a relationship with you? | Usually | Usually with your customer |
| Can you act on the data without instructions? | Yes | No, beyond what the contract allows |
Typical examples
- Cloud hosting provider storing a retailer's customer records: processor (Rule 8(3) Case 2 uses exactly this example).
- Payroll bureau running salaries for a client: processor.
- Email delivery platform sending a brand's campaigns: processor, unless it builds its own cross-customer profiles.
- LLM API vendor answering prompts for your support bot: processor for inference; if it trains its own models on your prompts, it is deciding a purpose of its own.
- Two companies co-running a loyalty programme and jointly deciding purposes: both fiduciaries, since the definition covers determining purpose "in conjunction with other persons".
What the Data Fiduciary is responsible for
Section 8(1) is the core: a 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. You cannot contract out of liability by blaming a vendor.
Fiduciary duties that touch processors directly:
- Valid contract (section 8(2)) before engaging or involving a processor, and only for offering goods or services to Data Principals.
- Security safeguards covering processing "undertaken by it or on its behalf by a Data Processor" (Rule 6(1)), including access control over the processor's computer resources where applicable (Rule 6(1)(b)) and contract clauses for safeguards (Rule 6(1)(f)).
- Breach intimation to the Board and each affected Data Principal (Rule 7), even if the breach happened at the processor. Your contract must make the processor tell you quickly.
- Erasure when consent is withdrawn or the purpose is served, and causing the processor to erase too (section 8(7)).
- Ceasing processing on withdrawal of consent, and causing processors to cease (section 6(6)).
- Minimum one-year retention of personal data, traffic data and processing logs, including processing by the processor (Rule 8(3)). Case 2 says the fiduciary must ensure its cloud provider also retains data and logs for at least one year before erasure.
- Access requests: section 11 lets a Data Principal ask for the identities of other fiduciaries and processors with whom data was shared.
What obligations does a Data Processor have?
The DPDP Act names few direct duties for processors. In practice their obligations arrive through three routes:
- The contract. Section 8(2) and Rule 6(1)(f) mean every serious customer will impose security, breach-notification, sub-processing, retention, erasure and audit clauses.
- Instructions. A processor acts "on behalf of" the fiduciary. Going beyond instructions — reusing data, combining customers' data, selling insights — risks making you a fiduciary for that activity, with all the duties that brings.
- Other laws. CERT-In Directions of 28 April 2022 apply to service providers, data centres and body corporates directly, including reporting specified incidents within 6 hours and keeping ICT logs for 180 days in India. See CERT-In rules for AI systems.
Indian vendors serving foreign clients
Section 17(1)(d) disapplies most of Chapter II (except sections 8(1) and 8(5)), Chapter III and section 16 where a person in India processes personal data of Data Principals outside India under a contract with a person outside India. Security safeguards under section 8(5) still apply. Foreign clients will also impose GDPR Article 28 terms; see GDPR for Indian IT services firms.
What a DPDP-ready processor contract should contain
There is no prescribed template, but the Act and Rules point to a minimum set of clauses:
- Scope and instructions: purposes, data categories, Data Principal categories, and a ban on processing for the processor's own purposes.
- Security safeguards mapped to Rule 6(1)(a)–(g): encryption, masking or tokenisation; access control; logging and monitoring; backups; technical and organisational measures.
- Breach notice to the fiduciary within a short window (many contracts use hours, not days) with enough detail for the fiduciary's Rule 7(2)(b) report to the Board within 72 hours.
- Retention: keep personal data, traffic data and processing logs for at least one year from processing (Rule 8(3)), then erase on instruction, unless another law needs longer.
- Erasure and cessation on withdrawal of consent or end of purpose, with written confirmation (sections 6(6) and 8(7)).
- Sub-processors: prior approval, flow-down of the same terms, and a current list (needed for section 11 access responses).
- Assistance with rights requests, grievances within the published period (not more than 90 days under Rule 14(3)), and Board inquiries.
- Audit rights and evidence such as certifications.
- Location and transfer terms, especially for regulated sectors with localisation rules.
A worked template is at DPDP data processing agreement template.
Engineering controls that prove the relationship
Contracts are evidence; systems are proof. Build these so the role split holds up under inquiry:
- Processor register. A machine-readable list of every processor and sub-processor, the processing activity, data categories, region and contract reference. Generate the section 11 "who did you share with" answer from it.
- Tenant isolation. If you are a processor, keep each customer's data logically separated and never join across tenants for your own analytics.
- Scoped credentials. Give vendors least-privilege, time-bound access. Rule 6(1)(b) covers access control to the processor's computer resources.
- Shared log pipeline. Pull processor access logs into your SIEM or require exports, so you have Rule 6(1)(c) visibility and the one-year retention in Rule 8(3).
- Erasure propagation. Expose an API or batch job that sends erasure events to each processor and records the acknowledgement.
- Breach hooks. Agree a webhook or ticketing integration so a processor incident lands in your incident queue immediately.
If you are adopting AI vendors, the same split applies to model APIs and vector databases. See AI vendor due diligence.
Further reading on suhasbhairav.com
- BlogAgent-based vendor risk auditing for sub-processors
- BlogProduction-grade legal risk instructions for contract review agents
- AI AutomationAI Automation for Vendor Risk: How It Works, With an Example
- AI SkillsAGENTS.md Template for Privacy and Data Governance Agents
- AI Use CasesAI Agent Use Case: Law Firms Using Contracts to Extract Obligations, Renewal Dates, and Risk Clauses
Key dates
DPDP Rules notified
Section 8 duties and Rules 6 to 8 apply to fiduciaries and their processor contracts
Answers
Frequently asked questions
What is a Data Fiduciary under the DPDP Act?
What is a Data Fiduciary under the DPDP Act?
A Data Fiduciary is any person who, alone or in conjunction with others, determines the purpose and means of processing personal data, as defined in section 2(i) of the DPDP Act, 2023. It is the equivalent of a GDPR controller and carries most obligations, including notice, security, breach intimation, erasure and handling rights requests.
What is a Data Processor under the DPDP Act?
What is a Data Processor under the DPDP Act?
A Data Processor is any person who processes personal data on behalf of a Data Fiduciary, under section 2(k) of the DPDP Act. Cloud hosts, payroll bureaus and email delivery platforms are typical processors. Their obligations arrive mainly through the contract the fiduciary must put in place under section 8(2).
Is the Data Fiduciary liable for a processor's data breach?
Is the Data Fiduciary liable for a processor's data breach?
Yes. Section 8(1) makes the Data Fiduciary responsible for compliance in respect of processing done on its behalf by a Data Processor, irrespective of any agreement to the contrary. The fiduciary must intimate the Board and affected Data Principals under Rule 7, so contracts should require the processor to report incidents quickly.
Can a company be both a Data Fiduciary and a Data Processor?
Can a company be both a Data Fiduciary and a Data Processor?
Yes. Roles are assessed per processing activity. A SaaS company is a fiduciary for its own employee and marketing data and a processor for the customer data it handles for clients. If it reuses client data for its own product purposes, it becomes a fiduciary for that use.
Is a contract with a Data Processor mandatory in India?
Is a contract with a Data Processor mandatory in India?
Yes. Section 8(2) of the DPDP Act allows a Data Fiduciary to engage a Data Processor only under a valid contract, and Rule 6(1)(f) requires the contract to include appropriate provision for reasonable security safeguards. These apply from 13 May 2027, but contracts are best updated at the next renewal.
Do processors need to keep logs for one year?
Do processors need to keep logs for one year?
Rule 8(3) requires the Data Fiduciary to retain personal data, traffic data and processing logs, including processing by its Data Processor, for at least one year from the date of processing. Illustration Case 2 says the fiduciary must ensure its cloud provider also keeps data and logs for at least one year before erasure.
Legal references and sources
- Digital Personal Data Protection Act, 2023 — Sections 2(i), 2(k), 8(1), 8(2) (official text)
- Digital Personal Data Protection Rules, 2025 — Rule 6(1)(f) (official text)
- Digital Personal Data Protection Rules, 2025 — Rule 8(3) (official text)
- Digital Personal Data Protection Act, 2023 — Section 17(1)(d) (official text)
- DPDP Rules, 2025 (G.S.R. 846(E)) ↗
- MeitY — Data protection framework ↗
- GDPR (for Article 28 comparison) ↗
This guide explains the law for engineering and business teams. It is not legal advice; confirm how it applies to your organisation with qualified counsel, and check the Gazette for later notifications or amendments.
About the author

Suhas Bhairav
Systems architect and applied AI practitioner who designs production AI systems for Indian and global companies, with a focus on privacy-by-design under the DPDP Act and the EU AI Act.
Related guides
- Templates & playbooksDPDP Data Processing Agreement Clauses TemplateCopy-ready data processing agreement clauses for India, mapped to DPDP section 8(2), Rule 6(1)(f), Rule 7 breach timelines and Rule 8(3) one-year retention.
- AI & personal dataAI Vendor Due Diligence Checklist Under the DPDP ActA practical due diligence checklist for LLM APIs, vector databases, observability tools and AI SaaS vendors, mapped to DPDP section 8 and Rules 6, 7 and 8(3).
- DPDP Rules 2025DPDP Reasonable Security Safeguards Under Rule 6Rule 6 lists the minimum security safeguards every Data Fiduciary must take from 13 May 2027. Failure can attract a penalty of up to ₹250 crore, the highest in the DPDP Act.
- DPDP Rules 2025DPDP One-Year Log Retention: What to Keep and for How LongTwo DPDP rules require one year of retention: Rule 6(1)(e) for security logs and Rule 8(3) for personal data, traffic data and processing logs. What to keep, where, and how to protect it.
- Sector guidesDPDP for IT Services, BPO and Outsourcing FirmsWhat the DPDP Act's section 17(1)(d) outsourcing exemption covers, what still applies to Indian IT services and BPO firms, and how to treat domestic and employee data.
- EU & cross-borderDPA & SCCs Explained for Indian Vendors Selling to EU ClientsWhat a DPA and Standard Contractual Clauses are, which SCC module an Indian vendor signs, how the annexes and transfer impact assessment work, and how they fit with DPDP processor contracts.