Templates & playbooksUpdated 22 November 202610 min read

DPDP Data Processing Agreement Clauses Template

Copy-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.

By Suhas Bhairav · Reviewed against the DPDP Rules, 2025 (G.S.R. 846(E), 13 Nov 2025)

Contract requirement
Section 8(2), DPDP Act
Security clause requirement
Rule 6(1)(f)
Board detailed report
Within 72 hours of awareness (Rule 7(2)(b))
Processor log retention
Minimum 1 year (Rule 8(3))
Fiduciary accountability
Section 8(1)
In force from
13 May 2027

Quick answer

Under section 8(2) of the DPDP Act, a Data Fiduciary may engage a Data Processor only under a valid contract, and Rule 6(1)(f) requires that contract to include appropriate provisions for reasonable security safeguards. A DPDP data processing agreement should also cover instructions, breach reporting fast enough for the 72-hour Rule 7 report, one-year log retention under Rule 8(3), erasure, sub-processors and audit.

  • Section 8(2) permits processor engagement only under a valid contract; Rule 6(1)(f) requires security clauses in it.
  • The fiduciary stays responsible under section 8(1), so the contract is its main control over processors.
  • Processor breach notice must be fast enough for the fiduciary to report to the Board within 72 hours.
  • Rule 8(3) requires processors to retain data and logs for at least one year, then erase.
  • Erasure on withdrawal or end of purpose must flow down to processors under section 8(7).
  • The DPDP Act does not prescribe a DPA template; GDPR Article 28 terms can be adapted but not copied blindly.

Who this is for: In-house counsel and contract managers, Procurement and vendor risk teams, SaaS vendors selling to Indian enterprises, IT services firms acting as processors, CISOs reviewing vendor security terms

Why does DPDP require a data processing agreement?

Three provisions combine to make a written contract with every Data Processor non-negotiable.

  • Section 8(1): the Data Fiduciary is responsible for compliance in respect of processing undertaken by it or on its behalf by a processor, irrespective of any agreement to the contrary.
  • Section 8(2): a Data Fiduciary may engage, appoint, use or otherwise involve a Data Processor to process personal data on its behalf for any activity related to offering goods or services only under a valid contract.
  • Rule 6(1)(f): reasonable security safeguards must include appropriate provisions in the contract between the Data Fiduciary and the Data Processor for taking reasonable security safeguards.

Other rules depend on the processor's cooperation: Rule 7 breach intimation, Rule 8(3) retention of processor-held logs, section 8(7) erasure, and rights handling under sections 11 to 14.

Neither the Act nor the Rules prescribe a standard DPA. That gives freedom of drafting, and responsibility for getting it right. The clauses below are a starting point, numbered for insertion into a master services agreement as a schedule.

Clauses 1–4: scope, instructions, confidentiality and personnel

1. DEFINITIONS AND ROLES
1.1 Terms used in this Schedule have the meanings given in
    the Digital Personal Data Protection Act, 2023 ("Act")
    and the DPDP Rules, 2025 ("Rules").
1.2 Customer is the Data Fiduciary and Vendor is the Data
    Processor for the Personal Data described in Annex A.

2. PROCESSING ON INSTRUCTIONS  (s.8(1), s.8(2))
2.1 Vendor shall process Personal Data only on Customer's
    documented instructions and only for the purposes,
    categories of data and Data Principals in Annex A.
2.2 Vendor shall not process Personal Data for its own
    purposes, including product improvement, analytics or
    training of models, without Customer's prior written
    approval.
2.3 Vendor shall promptly inform Customer if an instruction
    appears to infringe the Act or Rules.

3. CONFIDENTIALITY
3.1 Vendor shall ensure persons authorised to process
    Personal Data are bound by confidentiality obligations.

4. ACCURACY SUPPORT  (s.8(3))
4.1 Where Personal Data is used for a decision affecting a
    Data Principal or disclosed to another Data Fiduciary,
    Vendor shall implement Customer's instructions to keep
    it complete, accurate and consistent.

Annex A should list purposes, data categories, Data Principal categories, processing locations and retention periods. Generate it from your data inventory so it stays accurate.

Clause 5: security safeguards mapped to Rule 6

5. SECURITY SAFEGUARDS  (Rule 6(1)(f))
5.1 Vendor shall implement reasonable security safeguards
    to prevent Personal Data breach, including at minimum:
  (a) encryption, obfuscation, masking or virtual tokens
      mapped to Personal Data            [Rule 6(1)(a)]
  (b) access control over computer resources used for the
      Services                           [Rule 6(1)(b)]
  (c) logging, monitoring and review of access to Personal
      Data sufficient to detect, investigate and remediate
      unauthorised access               [Rule 6(1)(c)]
  (d) measures for continued processing, including backups,
      if confidentiality, integrity or availability is
      compromised                       [Rule 6(1)(d)]
  (e) retention of such logs and Personal Data for one year
      for detection, investigation and remediation, unless
      law requires otherwise            [Rule 6(1)(e)]
  (f) technical and organisational measures to ensure
      effective observance of the above [Rule 6(1)(g)]
5.2 Vendor shall maintain the controls in Annex B and shall
    not materially reduce them during the Term.
5.3 Vendor shall impose obligations no less protective than
    this clause 5 on each Sub-processor.

Annex B should name concrete controls: encryption standards, MFA, privileged access management, log sources, backup frequency and restore testing. Vague promises such as "industry standard security" are hard to enforce and harder to evidence before the Board.

Clause 6: breach notification timed for Rule 7

Under Rule 7(2)(b), the fiduciary must give the Board detailed information within 72 hours of becoming aware of a breach, and give a description without delay before that. Each affected Data Principal must be told without delay. The Rules do not say whether a processor's awareness counts as the fiduciary's. Do not build a plan that depends on that gap: keep the processor's notice window short.

6. PERSONAL DATA BREACH  (Rule 7; s.8(6))
6.1 Vendor shall notify Customer without undue delay and in
    any event within [__] hours of becoming aware of any
    Personal Data breach affecting Customer Personal Data.
6.2 The notice shall include, to the extent known: nature,
    extent, timing and location of the breach; categories
    and approximate number of Data Principals and records;
    likely impact; measures taken or proposed; and a contact
    for further information.
6.3 Vendor shall provide updates as information becomes
    available, including the facts and circumstances,
    findings on the person who caused the breach, and
    remedial measures, to enable Customer to report to the
    Board within 72 hours.
6.4 Vendor shall not notify Data Principals or the Board on
    Customer's behalf without Customer's written approval,
    unless required by law.
6.5 Vendor shall preserve evidence and logs relating to
    the breach.

Pick a figure that leaves the fiduciary real working time inside 72 hours. Also check CERT-In reporting duties, which require specified cyber incidents to be reported within 6 hours of noticing.

Clauses 7–9: retention, erasure and rights assistance

7. RETENTION  (Rule 8(3))
7.1 Vendor shall retain Personal Data, associated traffic
    data and logs of processing for a minimum of one year
    from the date of processing, for the purposes in the
    Seventh Schedule to the Rules, and shall then erase
    them unless Customer instructs a longer period required
    by law.

8. ERASURE  (s.8(7))
8.1 On Customer's instruction, including following
    withdrawal of consent or a Data Principal's erasure
    request, Vendor shall erase the specified Personal Data
    within [__] days, subject to clause 7.
8.2 On termination, Vendor shall return or erase Customer
    Personal Data, subject to clause 7, and certify erasure
    in writing.

9. DATA PRINCIPAL RIGHTS  (ss.11-14; Rule 14)
9.1 Vendor shall promptly forward to Customer any request
    from a Data Principal and shall not respond directly
    unless instructed.
9.2 Vendor shall provide assistance, including data
    exports and corrections, within [__] days so that
    Customer can respond within its published grievance
    period, which shall not exceed 90 days.

Clause 7 reflects the Rules' own illustration: a company using a cloud service provider must ensure the provider retains data and associated logs for at least one year before erasure. Erasure in clause 8 therefore needs to separate live data from the restricted retention archive.

Clauses 10–12: sub-processors, audit and cross-border transfer

10. SUB-PROCESSORS
10.1 Vendor shall not engage a Sub-processor without
     Customer's prior [specific / general] written
     authorisation and shall maintain a current list.
10.2 Vendor shall notify Customer [30] days before adding or
     replacing a Sub-processor; Customer may object.
10.3 Vendor remains liable to Customer for each
     Sub-processor's performance.

11. AUDIT AND INFORMATION
11.1 Vendor shall make available information necessary to
     demonstrate compliance with this Schedule, including
     independent audit reports, and allow audits on
     reasonable notice.
11.2 Vendor shall cooperate with Customer in responding to
     any inquiry by the Data Protection Board or request
     for information by the Central Government.

12. LOCATION AND TRANSFER  (s.16; Rule 15)
12.1 Vendor shall process Personal Data only in the
     locations listed in Annex A.
12.2 Vendor shall not transfer Personal Data to any country
     or territory restricted by the Central Government under
     section 16 of the Act, and shall comply with any
     requirement specified under Rule 15.
12.3 Where Customer is notified as a Significant Data
     Fiduciary, Vendor shall comply with any restriction
     on transfer outside India applicable under Rule 13(4).

For European data handled by Indian vendors, pair this schedule with Article 28 GDPR terms and SCCs. See DPAs and SCCs explained for Indian vendors.

Negotiation tips and common pitfalls

  • Liability caps that swallow the DPA. Penalties for security failures can reach ₹250 crore per instance against the fiduciary. Fiduciaries will push for data protection breaches to sit outside or above the general cap; processors will resist. Agree a specific super-cap rather than leaving it ambiguous.
  • "Industry standard" security. Replace with Annex B controls mapped to Rule 6.
  • No breach timeline. "Promptly" is not enough when the fiduciary's Board report is due within 72 hours.
  • Silent model training. Many SaaS terms allow use of customer data to improve services. Clause 2.2 should switch that off or define it narrowly.
  • Ignoring Rule 8(3). Immediate deletion on termination can conflict with the one-year retention duty. Clause 7 resolves it.
  • Forgetting AI vendors. LLM APIs, transcription and vector database providers are processors too. See AI vendor due diligence.
  • One DPA for every vendor. Keep the core clauses fixed and tailor Annex A and Annex B per vendor.

Further reading on suhasbhairav.com

Before 13 May 2027

Compliance checklist

  1. Put a written DPA in place with every processor

    Do not let any vendor process personal data without a valid contract.

    Section 8(2)

  2. Map security obligations to Rule 6

    List concrete controls for each Rule 6(1) item in a security annex.

    Rule 6(1)(f)

  3. Set a short processor breach window

    Choose hours, not days, so the 72-hour Board report is achievable.

    Rule 7(2)(b)

  4. Require one-year retention then erasure

    Oblige processors to keep data and logs for a year and erase afterwards.

    Rule 8(3)

  5. Flow down erasure instructions

    Require processors to erase on withdrawal or purpose completion within a fixed time.

    Section 8(7)

  6. Control sub-processors

    Require authorisation, a current list, notice of changes and flow-down terms.

    Section 8(1)

  7. Prohibit own-purpose use

    Bar use of personal data for vendor analytics or model training without approval.

    Section 8(2)

  8. Restrict processing locations

    List approved locations and bind the vendor to any section 16 restrictions.

    Section 16; Rule 15

Answers

Frequently asked questions

Is a data processing agreement mandatory under DPDP?

Yes, in substance. Section 8(2) allows a Data Fiduciary to use a Data Processor only under a valid contract, and Rule 6(1)(f) requires that contract to contain appropriate provisions for reasonable security safeguards. The Act does not prescribe a format, so the agreement can be a schedule to the main services contract.

Can I reuse my GDPR Article 28 DPA for India?

You can adapt it, but check three gaps. Add Rule 6 security items, a breach notice window that supports the fiduciary's 72-hour Board report under Rule 7, and the one-year retention of data and logs required by Rule 8(3). Replace GDPR terms like controller with DPDP terms.

How fast must a processor report a breach under DPDP?

The Rules do not set a processor deadline. They require the fiduciary to inform the Board without delay and give detailed information within 72 hours of becoming aware. The contract should therefore require the processor to notify within a short, fixed number of hours, leaving the fiduciary time to investigate and report.

Who pays a DPDP penalty if the processor causes a breach?

The Board's penalties apply to the Data Fiduciary, which under section 8(1) remains responsible for processing done on its behalf. The fiduciary may seek to recover losses from the processor through indemnity and liability clauses, which is why data protection liability caps are heavily negotiated.

Must a processor delete data immediately when the contract ends?

Not entirely. Rule 8(3) requires personal data, traffic data and processing logs to be retained for at least one year from processing, and the Rules' illustration applies this to a cloud provider. The DPA should require return or erasure of live data at exit, with a restricted archive kept until the year ends.

Should the DPA mention cross-border transfers?

Yes. Section 16 lets the Government restrict transfers to notified countries, and Rule 15 allows it to specify requirements about making data available to foreign States. The DPA should list approved processing locations and bind the processor to any restrictions, including Rule 13(4) limits if the fiduciary is a Significant Data Fiduciary.

Legal references and sources

  • Digital Personal Data Protection Act, 2023 — Sections 8(1), 8(2) and 8(7) (official text)
  • Digital Personal Data Protection Rules, 2025 — Rule 6(1)(f) (official text)
  • Digital Personal Data Protection Rules, 2025 — Rule 7 (official text)
  • Digital Personal Data Protection Rules, 2025 — Rule 8(3) (official text)

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

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.