← All articlesDPDP Act

DPDP and your vendors: what the processor contract needs

Under the DPDP Act the organisation that decides why and how personal data is processed — the Data Fiduciary — is responsible for complying with the Act, whatever any agreement says, including for processing done on its behalf by a Data Processor. Put plainly: if your payroll vendor, your cloud host or your outsourced support desk mishandles the data, the Board looks to you.

Who is a Data Processor

Anyone who processes personal data on your behalf. In practice: hosting and cloud providers, SaaS tools that hold customer or employee records, payroll and HR bureaus, email and SMS gateways, outsourced support and collections, analytics providers, and consultants with access to live systems.

If you are an IT services company, you are probably both: a fiduciary for your own employees’ and customers’ data, and a processor for your clients’. Expect your clients to send you the contract described below.

What the law requires

  • A valid contract. A Data Fiduciary may engage a Data Processor only under one.
  • Safeguards in the contract. The Rules list appropriate contractual provision for security safeguards among the minimum measures a fiduciary must take.
  • Erasure that reaches the processor. When data must be erased, the fiduciary must cause its processors to erase it too.

The Act places almost no direct duties on processors. That is exactly why the contract matters: it is the only lever you have.

What a workable contract covers

ClauseWhat it should say
Purpose and instructionsThe processor handles the data only for the stated purpose and on your written instructions.
SecurityThe specific safeguards expected: encryption, access control, logging, backups.
Breach noticeThe processor tells you immediately on becoming aware, with the facts you need for your own notices.
Sub-processorsNone without your approval, and on the same terms.
Logs and retentionLogs kept for at least a year; data kept only as long as you instruct.
Return and erasureData returned or erased at the end, and on request, with confirmation.
AssistanceHelp with requests from individuals and with enquiries from the Board.
AuditYour right to review, or to receive independent assurance such as an ISO 27001 certificate.
LocationWhere the data is stored and processed, and notice of any change.

The breach clock is the reason to be strict

Your duty to notify runs from when you become aware of a breach. A vendor who takes a week to tell you has used your week. The contract should require notice within hours, not “without undue delay”, and name the address it goes to.

Keeping vendors under review

  • Keep one register of every vendor that touches personal data, with what they hold and why.
  • Check them before you sign: who they are, what security they have, what assurance they can show.
  • Do not let work start before the contract is signed.
  • Review each one periodically. A check done once at onboarding says nothing about year three.
  • Record the review. An auditor, a client or the Board will ask to see it.
Who is liable if a vendor causes a data breach?
The Data Fiduciary remains responsible under the Act for processing done on its behalf, whatever the contract says. The contract determines what you can recover from the vendor afterwards.
Is a data processing agreement mandatory under the DPDP Act?
A Data Fiduciary may engage a Data Processor only under a valid contract, and the Rules expect that contract to provide for security safeguards.
Does the DPDP Act apply directly to Data Processors?
Almost all obligations fall on the Data Fiduciary. Processors are bound mainly through their contracts.
Do existing vendor contracts need to be changed?
Most will need an addendum covering security, breach notice, erasure and sub-processors before May 2027.

This is a working summary for people who have to act on the law, not legal advice. Read the Act and the Rules, and take advice on your own facts.

See SimDesk Remote Support in action

Attended & unattended, recorded and ticket-native. Free — no per-operator fees.