Quick answerNov 16, 20265 min read

Data protection clauses a vendor contract must contain

A compliance analyst reads a printed contract marked with coloured sticky tabs at a tidy desk.
CR

CyberRank Research

A vendor contract needs clauses that make the supplier a processor bound to your instructions: the permitted purposes, the security measures, the sub-processor rules, the assistance duties, the deletion terms and the audit rights. GDPR Article 28(3) requires them in writing, and UU PDP places equivalent duties on processors. CyberRank reports whether a vendor publishes these clauses at all, so the gap is visible before you sign.

TL;DR

  • GDPR Article 28(3) requires a written contract between controller and processor that sets out the processor's obligations.
  • The core clauses cover permitted purposes, security measures, sub-processors, assistance with data subject rights, deletion and audit.
  • UU PDP places comparable duties on processors, so an Indonesian vendor needs the same clauses.
  • A published data processing addendum is evidence the clauses exist; a security page is not.
  • To confirm the clauses exist before you sign, read the published data processing addendum: CyberRank reports whether a vendor's terms contain data protection clauses, as one lens in every assessment.

What data protection clauses should a vendor contract contain?

A vendor contract should bind the supplier as a processor: permitted purposes only, defined security measures, sub-processor rules, assistance with data subject rights, deletion on exit, and audit or evidence rights.

These clauses do the work that a privacy policy cannot. A policy describes what a vendor does; a contract clause makes it an obligation you can enforce. GDPR Article 28(3) lists the minimum content, and the list is short enough to check against any vendor's published addendum.

The table below maps each clause to the obligation it creates and to what CyberRank can report from a vendor's public terms. This is the clause list that vendor contract clause detection checks against.

How CyberRank helps: CyberRank reads a vendor's published legal terms and reports whether data protection clauses appear, as part of the same assessment that rates its security.

Data protection clauses and the obligation each creates
Permitted purposesWhat it should sayProcess only on documented instructions, for the stated purposesReferenceGDPR Art. 28(3)How CyberRank helpsReports whether processor terms are published
Security measuresWhat it should sayAppropriate technical and organisational measures, describedReferenceGDPR Art. 32How CyberRank helpsRates the technical measures it can observe
Sub-processorsWhat it should sayAuthorisation, notice of changes, flow-down of obligationsReferenceGDPR Art. 28(2) and 28(4)How CyberRank helpsRates the sub-vendors it can discover
AssistanceWhat it should sayHelp with data subject requests and breach notificationReferenceGDPR Art. 28(3)(e) and (f)How CyberRank helpsReports whether assistance and notification clauses appear
Deletion or returnWhat it should sayDelete or return data at the end of the serviceReferenceGDPR Art. 28(3)(g)How CyberRank helpsReports whether exit terms appear
Audit and evidenceWhat it should sayAllow audits or provide equivalent evidenceReferenceGDPR Art. 28(3)(h)How CyberRank helpsChecks certifications and evidence as their own lens

Example: a payroll provider with a short addendum (fictional)

A payroll provider publishes a two-page addendum that names the sub-processors and the security measures but says nothing about breach notification or deletion.

The addendum looks complete because it is titled correctly and signed by both parties. Reading it against the clause list shows two gaps: no notification deadline, and no deletion commitment at the end of the service. Both are clauses the controller needs, and neither is unusual to request.

The finding is not that the vendor is careless. It is that the published terms do not cover the situation, which is exactly the kind of gap a clause check is meant to surface before the contract is signed rather than after an incident. The notification element is covered separately in whether the terms require breach notification.

How CyberRank helps: CyberRank would report the addendum as present, the sub-processor and security clauses as found, and the notification and deletion clauses as not found.

Where CyberRank does not help

CyberRank reports whether clauses appear in published terms; it does not draft them, negotiate them, or judge whether they are legally sufficient for your processing.

It cannot read a private agreement, so a clause that exists only in your signed contract will not be found. It does not interpret the wording, and it does not tell you whether a specific clause satisfies Article 28(3) for your facts. Under UU PDP the same duties fall on Indonesian processors, so the clause list does not change with the jurisdiction.

How CyberRank helps: it tells you which vendors need a lawyer's reading, which is a much shorter list than the whole vendor portfolio.

References

  1. European Union, Regulation (EU) 2016/679 (General Data Protection Regulation), Articles 28 and 32 (27 April 2016)
  2. Republic of Indonesia, Undang-Undang No. 27 Tahun 2022 tentang Pelindungan Data Pribadi, Article 51 (17 October 2022)

Frequently asked questions

Check a vendor's data protection terms

See whether a supplier publishes the data protection clauses your contract needs, alongside its security rating.

Check a vendor's data protection terms