[Analysis] Data Processing Agreement under the DPDP Act – Section 8(2) Valid Contract | Essential Clauses | Sub-Processors | Template

  • Blog|Company Law|
  • 13 Min Read

The data processing agreement under the DPDP Act: why section 8(2) needs a valid contract, how it compares with GDPR Article 28, the clauses to include, sub-processors and vendor terms.

  • By Taxmann
  • |
  • Last Updated on 15 November, 2026
A data processing agreement is the contract under which a Data Processor handles personal data on behalf of a Data Fiduciary. Section 8(2) of the Digital Personal Data Protection Act, 2023 (DPDP Act) lets a Data Fiduciary engage a Data Processor only under a valid contract, and Rule 6(1)(f) of the Digital Personal Data Protection Rules, 2025 (DPDP Rules) requires that contract to provide for reasonable security safeguards. Both apply from 13 May 2027. The Act itself asks only for a valid contract, so the agreement has to carry the detail.

Table of Contents

  1. What is a data processing agreement under the DPDP Act?
  2. Who is responsible if there is no agreement?
  3. How does the DPDP Act compare with Article 28 of the GDPR?
  4. What clauses should a data processing agreement contain?
  5. How should sub-processors be handled?
  6. What should a Data Fiduciary check in a vendor’s standard terms?
  7. What do enforcement cases show?
  8. Quick answers

1. What is a data processing agreement under the DPDP Act?

A data processing agreement, or DPA, is the contract that governs personal data processed by one organisation on behalf of another. Section 2(k) of the DPDP Act defines a Data Processor as any person who processes personal data on behalf of a Data Fiduciary. Section 8(2) allows a Data Fiduciary to engage, appoint, use or otherwise involve a Data Processor, for any activity related to offering goods or services to Data Principals, only under a valid contract.

Abha Tiwari and Aditya Singhania describe the agreement as both a compliance instrument and a risk allocation mechanism. It records the subject-matter, duration, nature and purpose of the processing, the categories of personal data involved and the rights and obligations of each party. It makes the processor apply appropriate safeguards, submit to audit, help the controller meet its duties to individuals and seek authorisation before engaging sub-processors, and it governs the return or destruction of the data when the engagement ends.

Where the terms should sit is a matter of choice. No statute says whether they belong in the body of the principal agreement, in an annexure to it or in a standalone instrument. The DPDP Act requires only a valid contract, and the EU General Data Protection Regulation (GDPR) requires only that the contract be in writing, including in electronic form. The choice turns on commercial and structural factors: the nature of the transaction, whether processing is central or incidental to the services, and whether the same processor works across several work orders.

A standalone agreement can be negotiated by the people who understand it, reused across engagements with the same counterparty and amended as the law develops without reopening the commercial bargain. Terms inside the principal agreement stay in one document and share its duration and termination. Where the two are separate, each should refer to the other.

Section 8 of the DPDP Act and Rule 6 of the DPDP Rules apply from 13 May 2027. Until then, the enforcement risk for an ordinary Data Fiduciary arises under section 43A of the Information Technology Act, 2000, the Information Technology (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules, 2011 (SPDI Rules) and the CERT-In Directions, not under the DPDP Act.

2. Who is responsible if there is no agreement?

The Data Fiduciary. Section 8(2) directs the obligation at the fiduciary, and section 8(1) makes the fiduciary responsible for compliance irrespective of any agreement to the contrary. Engaging a processor without a contract is a breach of section 8(2) in itself, and the fiduciary remains answerable for the processing regardless.

That does not leave the processor safe. Without a contract, a processor loses its principal evidence that it was acting on another’s behalf. Roles are decided by who in fact determines the purposes and means of processing, so the missing contract is not conclusive, but it removes the documents the processor would rely on to resist being treated as a controller in its own right. Article 28(10) of the GDPR deems a processor that determines purposes and means to be a controller for that processing. The DPDP Act has no equivalent deeming provision and imposes few direct obligations on processors, so the exposure in India is presently narrower. How the role is determined and documented for each processing activity is covered in Data Fiduciary, Data Processor or both.

Other laws put the duty on both sides. Under the GDPR, Article 28(3) binds both parties and Article 83(4)(a) exposes both to fines. Article 37(2) of Vietnam’s Law on Personal Data Protection lets a processor receive personal data only after an agreement with the controller has been concluded.

Sector regulators have required these agreements for years. RBI’s outsourcing rules for banks, NBFCs and payment companies, SEBI’s outsourcing framework, IRDAI’s regulations and the CERT-In Directions of April 2022 all impose contracting, audit and incident-reporting obligations, some of them stricter than the DPDP baseline. A regulated business without a vendor agreement will usually hear from its sector regulator long before the Data Protection Board of India is involved.

The agreement should therefore be signed before processing starts, not completed afterwards. In a case decided by the Belgian data protection authority on 29 September 2023, a municipality and its service provider had no agreement when the complainant’s data was processed. An agreement signed on 27 July 2020, with a clause backdated to 25 May 2018, did not cure the breach, and both controller and processor were found in breach.

Taxmann.com | Research | Indian Acts & Rules

3. How does the DPDP Act compare with Article 28 of the GDPR?

Article 28 of the GDPR lists what a processor contract must contain. The DPDP Act and the DPDP Rules prescribe very little of it, so most of the clauses a GDPR contract must carry are, in India, a matter of drafting. The comparison below follows the clause-by-clause table in the book, which also covers Singapore and the Middle East.

Clause GDPR DPDP Act and DPDP Rules
Contract in place before processing Article 28(3); Article 28(9): in writing, including electronic form Section 8(2): a processor may be engaged only under a valid contract
Processing only on documented instructions Article 28(3)(a); Article 29; Article 28(10): a processor exceeding instructions is deemed a controller Not expressly prescribed; implicit in “on its behalf” under section 8(2)
Confidentiality of personnel Article 28(3)(b) Not prescribed
Security measures Article 28(3)(c) with Article 32(1)(a) to (d); Article 28(1) Section 8(5); Rule 6(1)(f): the contract must contain appropriate provision for reasonable security safeguards
Sub-processors Article 28(2) and Article 28(4) Not prescribed
Help with individuals’ rights Article 28(3)(e) Not prescribed; the Data Fiduciary bears its duties under sections 11 to 13 regardless
Breach notice to the controller Article 28(3)(f) with Article 33(2) Section 8(6): the Data Fiduciary notifies the Board and affected Data Principals; the contract must carry the flow-down
Help with impact assessments Article 28(3)(f) with Articles 32 to 36 No impact assessment duty except for Significant Data Fiduciaries under section 10
Deletion or return at the end Article 28(3)(g) Section 8(7)(b): the Data Fiduciary must cause the processor to erase the data
Audit rights Article 28(3)(h) No statutory audit right; it has to be written into the contract, and Rule 6(1)(f) is the nearest anchor
Cross-border transfers Article 28(3)(a); Chapter V Section 16: a restricted-country model
Liability Article 82: joint and several liability to individuals Section 8(1): the Data Fiduciary is responsible irrespective of any agreement to the contrary

4. What clauses should a data processing agreement contain?

Annexure B of the book is a template data processing agreement drafted to work under the GDPR, the UK GDPR and the DPDP Act at the same time. Where the GDPR and the DPDP Act both apply to the same processing, the parties follow the higher standard of protection. Square brackets in the template mark commercial or fact-specific terms for the parties to settle, so the periods below are the template’s suggestions.

Its recitals state the statutory purpose, because section 8(2) permits a processor only under a valid contract and Rule 6 requires the Data Fiduciary to impose security obligations on its processors by contract. Reciting that purpose makes the agreement easier to defend and easier to construe. The clauses that matter most in India are these.

Clause What the template provides
Roles (clause 4) The processor may not process the data for its own purposes. It may not sell the data, use it for marketing, use it to develop other products or use it to train, fine-tune or evaluate an artificial intelligence model without the controller’s prior written instruction. Where it decides purposes and means itself, it is a controller for that processing.
Instructions (clause 6) Processing only on documented instructions. The processor must say without undue delay if an instruction appears to infringe the law, and may suspend it until the controller confirms or withdraws it.
Personnel (clause 7) Confidentiality that survives the end of each person’s engagement, access on a need basis reviewed at least every three months, and revocation of access on the same working day it is no longer needed.
Security (clause 8) Encryption, masking and virtual tokens, multi-factor authentication for privileged accounts, and access logs kept for at least one year. Rule 6 requires logs and processing records to be kept for a minimum of one year, so a template without that floor needs amending before 13 May 2027.
Rights requests (clause 9) The processor tells the controller within two business days of any request or complaint and does not reply to the individual directly without written authorisation.
Significant Data Fiduciaries (clause 10.3) Where the controller is a Significant Data Fiduciary, the processor cooperates with its periodic impact assessments and independent data audits.
Breach (clause 11) Notice to the controller within six hours, and enough detail within twenty-four hours for the Data Fiduciary to meet Rule 7, which requires it to inform each affected Data Principal and the Board without delay and to give the Board detailed particulars within seventy-two hours. Each party keeps its own reporting duty under the CERT-In Directions.
Government access (clause 12) The processor notifies the controller of a legally binding disclosure request, challenges one that appears unlawful or disproportionate, discloses the minimum and records each request.
Transfers (clause 14) Data originating from India leaves India only in accordance with section 16 of the DPDP Act and Rule 15 of the DPDP Rules, and never to a country the Central Government has restricted.
Children (clause 18) Where children’s data is in scope, no tracking, behavioural monitoring or targeted advertising, and help with verifying parental consent under section 9 and Rule 10. Section 9 carries a penalty of up to two hundred crore rupees.
Liability (clause 19) Indemnities in both directions. The cap in clause 19.4 is the most heavily negotiated provision, and if it is left open the processor’s indemnity reads as uncapped.
Return and deletion (clause 20) Return in a machine-readable format or deletion of all copies, including those held by sub-processors and in backups, certified within thirty days. A deletion certificate given while the data persists in immutable backups is a false certificate.

Three other clauses tie the agreement to the rest of a compliance programme. Clause 10.4 makes the processor help the controller with data retention and erasure, erasing data where the specified purpose is no longer served or consent is withdrawn and confirming completion in writing. Clause 15 makes the processor keep its own record of processing activities and produce it on request. Clause 14.5 binds the processor to any sector rule that requires specified categories of data to be stored or processed only within India, the subject of data localisation and cross-border transfers.

5. How should sub-processors be handled?

The DPDP Act has no rule on sub-processors, so the agreement has to supply one. The GDPR model is the usual reference. Under Article 28(2), a processor may not engage another processor without the controller’s prior specific or general written authorisation, and under a general authorisation it must tell the controller of any intended addition or replacement, giving the controller the chance to object. Article 28(4) requires the same data protection obligations to be imposed on the sub-processor by contract, and leaves the original processor fully liable to the controller for the sub-processor’s performance.

Clause 13 of the template turns this into a procedure:

  1. No sub-processor without the controller’s prior specific or general written authorisation, with the approved sub-processors listed in Schedule 5.
  2. At least thirty days’ written notice of a new or replacement sub-processor, naming it, the processing it will do and where.
  3. An objection on reasonable grounds within fifteen days, after which the proposed sub-processor is not engaged and the parties discuss an alternative for fifteen days.
  4. If no workable alternative emerges, a right to end the affected services on thirty days’ notice, without penalty or termination charge.
  5. The same obligations passed down to every sub-processor by binding written contract, with the processor fully liable for each sub-processor’s acts and omissions.

The harder problem is visibility. Platforms run on other platforms: a CRM sits on a large cloud provider and uses a separate email service, support tool and analytics vendor, and now probably an AI provider. Standard terms usually let the platform appoint sub-contractors freely, and some processors do not declare the large technology companies behind their platforms as sub-processors at all. When a platform adds an AI feature, the data starts moving differently but the paperwork usually stays the same. The authors suggest asking each time whether content is used for training and whether that is on by default, whether the AI provider is a sub-contractor or acting for itself, where the processing physically happens, whether prompts and answers are stored and who can read them, and what happens to a deletion request after the data has been used in training.

Self-certification does not close the gap. On 28 December 2021 the CNIL, the French regulator, fined SLIMPAY €180,000 after some of its contracts with its own service providers omitted several of the required clauses and others contained none of them. Questionnaires asking those providers to confirm compliance were held not to be enough to show that sub-processors offered sufficient guarantees.

6. What should a Data Fiduciary check in a vendor’s standard terms?

Most of the risk sits in clauses that let the vendor use the data for itself. When a platform stores records or sends emails for a client, it acts on the client’s instructions. When it counts how customers use the product, improves the service, spots security threats across all its customers, builds benchmark reports or trains AI models, it decides its own purposes and is a controller for those activities, not a processor.

Watch for wording that lets the provider use “aggregated”, “de-identified” or “anonymised” data for its own purposes. If the data is truly anonymous, data protection law no longer applies, but making data anonymous is itself a processing activity that needs its own legal basis, and true anonymity is a high bar that most de-identified data does not clear. Other phrases to flag are rights to use data to “improve the Services”, “develop new features” or “train and improve machine learning models”, and carve-outs for “Service Data”, “Usage Data” or “Telemetry”.

A related request is a supplier asking its customer to collect consent from the customer’s users so that the supplier can use the data for its own purposes. This has two problems. The supplier is then deciding what it wants the data for, so it is a controller for that activity and the processor agreement does not cover it. The consent is also probably invalid, because the customer usually cannot describe the supplier’s plans accurately and often does not know how long the supplier keeps the data, who else receives it or whether it leaves the country, and consent buried in the terms of service or made a condition of using the product usually is not valid at all.

Click-through terms add a further risk. They sit behind a link, are accepted with a click and often let the provider change them unilaterally, so they may not contain everything the law requires and may change without the customer ever agreeing. As the authors put it, “an unread click-through is a weak thing to put in front of a regulator.”

The controller stays accountable throughout, and it makes no difference that a large, reputable vendor drafted the terms. The authors’ practical steps are:

  1. read the actual processing terms rather than the marketing page;
  2. list which activities the vendor does on your instructions and which it does for itself;
  3. make the vendor state its role for each one;
  4. treat secondary-use clauses as something to negotiate, not boilerplate;
  5. get the sub-contractor list and a change-notification process with an objection right that means something; and
  6. write the analysis down, because you must be able to show your reasoning, not just the answer.

7. What do enforcement cases show?

European regulators have fined controllers and processors alike over these clauses. The decisions below, all discussed by the authors, show where agreements fail in practice.

Case Regulator and penalty What it shows
UniCredit, NTT Data Italia and Truel IT Garante (Italy), €800,000 A sub-processor engaged without the controller’s prior authorisation, and a data breach reported late to the controller
Vodafone Italia Garante (Italy), 2020, €12.25 million Unlawful marketing calls by third-party processors, arising from inadequate contractual controls and insufficient oversight
Dedalus Biologie CNIL (France), 15 April 2022, €1.5 million The processor itself was fined because its contracts lacked the particulars Article 28(3) requires, and it exceeded its instructions by migrating substantially more data than the migration required
Advanced Computer Software Group ICO (United Kingdom), 27 March 2025, £3.07 million The ICO’s first monetary penalty against a processor under the UK GDPR, after a ransomware attack through a customer account without multi-factor authentication exposed the data of 79,404 people
SEUR AEPD (Spain), €200,000 The real roles outweighed how the contract described them; SEUR was given three months to put a proper agreement in place
Criteo CNIL (France), 15 June 2023, €40 million Requiring partners by contract to obtain consent, with no check that they had, did not discharge the obligation

8. Quick answers

What is a data processing agreement?

It is the contract under which a Data Processor processes personal data on behalf of a Data Fiduciary. It sets out the subject-matter, duration, nature and purpose of the processing, the categories of data and each party’s obligations, including security, audit, sub-processors and what happens to the data at the end.

Is a data processing agreement mandatory under the DPDP Act?

Yes, in substance. Section 8(2) of the DPDP Act lets a Data Fiduciary engage a Data Processor only under a valid contract, and section 8 applies from 13 May 2027. The Act does not prescribe the clauses.

Who is liable for a processor’s mistakes under the DPDP Act?

The Data Fiduciary. Section 8(1) makes it responsible for processing done on its behalf by a Data Processor, irrespective of any agreement to the contrary. The Act imposes few direct obligations on processors, so their liability to the fiduciary rests on the contract.

What does Rule 6 of the DPDP Rules require in the contract?

Rule 6(1)(f) requires the contract with a Data Processor to contain appropriate provision for reasonable security safeguards. Rule 6 also requires logs and processing records to be kept for a minimum of one year.

Does the DPDP Act regulate sub-processors?

No. The agreement has to supply the rule, usually on the GDPR model: prior written authorisation, notice of changes with a right to object, the same obligations passed down by contract and full liability of the processor for its sub-processors.

Can a vendor use client data to train its AI models?

Not as a processor. A vendor that uses the data for its own purposes, such as training a model, is a controller for that use. The template agreement bars such use without the controller’s prior written instruction.

What happens to the data when the agreement ends?

The processor returns or deletes it at the controller’s choice, including copies held by sub-processors and in backups, and certifies deletion. Under section 8(7)(b) the Data Fiduciary must cause its processor to erase personal data when erasure is due.

Is there a template data processing agreement for India?

Annexure B of Digital Personal Data Protection Law Practice and Compliance by Abha Tiwari and Aditya Singhania is a template drafted to work under the GDPR and the DPDP Act together, with notes for the drafter.


Paragraph 7.4 of Digital Personal Data Protection Law Practice and Compliance by Abha Tiwari and Aditya Singhania explains the Data Processor’s position under section 8(2), compares the processor contract under the DPDP Act with the GDPR, Singapore and the Middle East clause by clause, keys the leading enforcement decisions to each clause and lists the questions to put to vendors. Annexure B is a template Data Processing Agreement with drafting notes.
Taxmann.com | Research carries the Digital Personal Data Protection Rules, 2025, including Rules 6, 7 and 15, under Indian Acts & Rules, and Taxmann.com | Store has the Digital Personal Data Protection Act 2023 with Rules – Bare Act with Section Notes.
Related reading: obligations of Data Fiduciaries · the DPDP Act and the GDPR compared · breach, enforcement and penalties under the DPDP Act · the DPDP Act compliance checklist.
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 · 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.
Law stated as updated till October 2026.

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