1. Home
  2. Tools
  3. Processor addendum template

Template

Processor addendum template

A clause outline for contracts with Data Processors under s.8(2): security, breach notice, erasure, sub-processors, audit and exit. Not legal advice; adapt it with counsel.

Updated 4 Nov 2026

Short answer

Under s.8(2) a Data Fiduciary may engage a Data Processor only under a valid contract, and it stays responsible for processing done on its behalf (s.8(1)). Rule 6 asks for security terms in contracts with processors, and s.8(7) requires the fiduciary to make processors erase personal data when consent is withdrawn or the purpose is no longer served. This template outlines those clauses plus breach notice, sub-processors, audit and return or deletion; it is not legal advice, so adapt it with counsel.

A clause outline for a data processing addendum under the DPDP Act. Fields ending in a colon are for you to fill in. Not legal advice; adapt it with counsel.

Data processing addendum (DPDP): clause outline

1. Parties and scope

Data Fiduciary (legal name):

Data Processor (legal name):

Main agreement this addendum supplements (name and date):

Services the Processor provides:

Personal data covered (itemise):

Data Principals covered (for example customers or employees):

Purpose of processing:

Duration of processing:

2. Instructions (s.8(2))

This addendum is the contract under which the Fiduciary engages the Processor to process personal data on its behalf.

The Processor processes personal data only on the Fiduciary's documented instructions and only for the purpose stated above.

The Processor does not use the personal data for its own purposes.

3. Security safeguards (s.8(5), Rule 6)

The Processor maintains reasonable security safeguards, including at least the measures in Rule 6.

Encryption, obfuscation, masking or virtual tokens for personal data.

Access control, with access logs that are monitored and reviewed.

Backups and measures for continuity.

Retention of logs and personal data for one year to detect and investigate unauthorised access, unless another law requires otherwise.

Description of the Processor's measures (attach as an annex):

4. Personal data breach

The Processor notifies the Fiduciary without delay on becoming aware of a personal data breach affecting the Fiduciary's personal data.

The notice includes what the Processor knows of the nature, extent and timing of the breach, its likely consequences and the steps taken.

The Processor helps the Fiduciary prepare its intimations and the detailed report Rule 7 requires.

Processor's breach contact (name, email, phone):

Fiduciary's breach contact (name, email, phone):

5. Withdrawal of consent and erasure (s.6(6), s.8(7))

When the Fiduciary tells the Processor that consent has been withdrawn, the Processor stops processing within a reasonable time.

On the Fiduciary's instruction, the Processor erases the personal data, including when consent is withdrawn or the purpose is no longer served, unless a law requires it to be retained.

Time to complete erasure after an instruction:

6. Sub-processors

The Processor engages a sub-processor only with the Fiduciary's prior written approval.

The Processor places the same obligations on each sub-processor and remains responsible to the Fiduciary for its work.

Approved sub-processors (name, service, location):

Notice period before adding or changing a sub-processor:

7. Transfers outside India (s.16)

The Processor tells the Fiduciary before processing or storing the personal data in a new country, so the Fiduciary can check any restriction notified under s.16.

Countries where the personal data is processed or stored:

8. Audit and information

The Processor gives the Fiduciary the information it needs to show compliance with the Act and the Rules.

The Processor allows audits by the Fiduciary or an auditor it appoints, on reasonable notice.

Audit notice period:

9. End of services

At the end of the services, the Processor returns or deletes the personal data, as the Fiduciary chooses, unless a law requires it to be retained, and confirms this in writing.

Deadline for return or deletion:

Confirmation of deletion signed by (name and designation):

10. Signatures

For the Data Fiduciary (name, designation, date):

For the Data Processor (name, designation, date):

Why the contract matters

The fiduciary remains responsible for what its processors do (s.8(1)). Rule 7 asks the fiduciary to act without delay once it is aware of a breach, so a processor that reports late costs you time.

The contract is where you set those expectations. The processor contracts guide covers negotiation and review.

Clauses in the template

ClauseWhy it is thereSource
Processing only on documented instructionsKeeps the processor within your specified purposes.8(1), s.8(2)
Security safeguardsAt least the Rule 6 measuress.8(5), Rule 6
Breach notice to the fiduciary without delaySo you can intimate the Board and Data Principalss.8(6), Rule 7
Stop processing after withdrawalWithin a reasonable times.6(6)
Erasure on instructionWhen consent is withdrawn or the purpose is no longer serveds.8(7)
Sub-processorsApproval and the same terms passed downContract term
Transfers outside IndiaSo you can check any restriction notified under s.16s.16
Audit and informationEvidence you can showContract term
Return or deletion at the endNo personal data left behind after the service endss.8(7)

What this template is not

Not legal advice; adapt with counsel

This is a clause outline, not legal advice and not a certification. Adapt it with counsel to your main agreement, the processing involved and your sector regulator's directions.

How TruePrivacy helps

Vendors and processors keeps vendor records with risk levels, sends assessments through a vendor portal link, offers question templates including one asking processors to report breaches without delay, and tracks contracts (DPAs).

Cross-border transfers warns you when a vendor or transfer destination matches a country on the restriction list you maintain.

Sources

  • Digital Personal Data Protection Act, 2023 (Act No. 22 of 2023)
  • Digital Personal Data Protection Rules, 2025, G.S.R. 846(E), 13 November 2025

Updated 4 Nov 2026. Educational information, not legal advice.

Questions, answered

Educational, not legal advice.

All DPDP FAQs
Is a contract with a data processor mandatory under DPDP?

Yes. Section 8(2) lets a Data Fiduciary engage a Data Processor only under a valid contract.

Who is responsible if a processor mishandles personal data?

The Data Fiduciary remains responsible for processing done by its processors on its behalf (s.8(1)).

Must processors erase personal data?

Yes, when you instruct them. Section 8(7) requires the fiduciary to erase personal data when consent is withdrawn or the purpose is no longer served, unless a law requires retention, and to make its processors erase it too.

Does the template cover sub-processors?

Yes. It covers approval of sub-processors, passing down the same terms, and notice before changes.

Your DPDP plan, starting today

Core obligations for data fiduciaries begin on 13 May 2027.

13 May 2027

Core obligations begin