In-house legal · Data protection

DPA when you are the controller: what to require from vendors

The vendor sends its standard DPA. It covers Article 28 in outline and leaves the timing, the audit and the transfers to the vendor. Here is what to require, and where vendors usually move.

Data processing addendum — Vendor template § 8 Personal data breach

8.1 Processor shall notify Controller of a Personal Data Breach within a reasonable timewithout undue delay and in any event within forty-eight (48) hours of becoming aware of it.

Redline · round 1 Returned in 22h
In short
  • Article 28(3) is the floor. A vendor DPA that does not cover every item on it is not a negotiation point; it is a defect.
  • The negotiation is about mechanics: notice periods, audit form, breach timing, deletion proof and transfers.
  • Add the AI clause now. It is the term most vendor templates still leave out.

The Article 28 minimum

As controller, you may use only processors that give sufficient guarantees, and the contract must set out the subject matter, duration, nature and purpose of the processing, the types of personal data and the categories of data subjects. Article 28(3) then lists what the processor must commit to:

  • process only on your documented instructions, including on transfers outside the EEA;
  • ensure that people authorised to process the data are bound to confidentiality;
  • take the security measures required by Article 32;
  • engage sub-processors only with your authorisation and on the same obligations;
  • help you respond to data-subject requests;
  • help you with security, breach notification and impact assessments;
  • delete or return the data at the end of the services, at your choice;
  • make available the information needed to demonstrate compliance, and allow and contribute to audits.

Check the vendor template against the list before anything else. The common gaps are the choice between deletion and return, which templates often reserve to the vendor, and the description of the processing, which is left as a blank annex.

Sub-processors

General authorisation is workable for both sides, provided three things are in the text. First, a current list, with the service each sub-processor provides and the country where it processes. Second, notice before a new sub-processor starts: long enough for your privacy team to assess it. Fourteen days is the floor; thirty is where many negotiated DPAs land. Third, a right to object on reasonable data-protection grounds, with termination of the affected service without penalty as the remedy if the objection cannot be resolved.

Article 28(4) already requires the vendor to impose the same obligations on its sub-processors and keeps it fully liable for them. Make sure the template does not water that down, for example by limiting the vendor’s responsibility to “reasonable efforts” to enforce its sub-processor contracts.

Audit

Vendors will resist open-ended on-site audits, and you rarely need them. Require documentation first — independent audit reports, completed questionnaires, written answers within a fixed period — and an on-site or remote audit where the documentation is not enough, on reasonable notice, at your cost. Keep two exceptions: after a breach affecting your data, and where a supervisory authority requires it. In those cases the audit is not limited to once a year, and the vendor carries its own cost.

Breach notice timing

Under Article 33, you must notify the supervisory authority within 72 hours of becoming aware of a breach, where notification is required. Article 33(2) obliges the processor to notify you “without undue delay”, which in practice is negotiated into a number. Require a fixed outer limit — 24 to 48 hours is common — and a minimum content: what happened, which data and data subjects, likely consequences, measures taken, and a contact. Allow information to follow in phases, but do not let the first notice wait for the vendor’s investigation to finish.

Deletion and return

At the end of the services, you choose between deletion and return. Fix a period — thirty days is usual — and require written confirmation that deletion has been done. Two points the vendor will raise, and which are fair: data it must keep by law stays protected by the DPA until deleted, and backups are deleted on the normal backup cycle, which the vendor should state.

International transfers

If the vendor or any sub-processor processes outside the EEA, Chapter V of the GDPR applies. Ask for three things. The transfer mechanism for each destination: an adequacy decision where one exists (for the US, only for recipients certified under the EU–US Data Privacy Framework), otherwise the Standard Contractual Clauses — Module 2 between you and the vendor, Module 3 between the vendor and its sub-processors. A transfer impact assessment where the SCCs are used. And the countries named on the sub-processor list, so that a change of hosting region is a change you hear about.

AI clauses

Most vendor templates still say nothing about artificial intelligence, and most vendors now use it somewhere in the service. Require three commitments: your personal data is not used to train or improve models; it is not submitted to third-party AI services unless those services are listed as sub-processors; and AI use in the service is disclosed on request. The training prohibition is the one vendors accept most easily. The listing requirement is the one that does the work. For how these clauses read from the vendor’s side, see AI clauses are now standard in enterprise DPAs.

Liability

A DPA with no liability clause of its own falls under the cap in the main agreement, which may be low for a data incident. Ask for a separate, higher cap for breaches of the data-protection obligations. Vendors usually accept one, and it is a better result than a fight about unlimited liability.

On the desk

Your DPA requirements go into the playbook as one table, like any other contract type. Each vendor DPA is then checked against it, and only the gaps come back to your privacy lead.

General information, not legal advice. This page describes how EU and cross-border commercial contracts commonly work; it is not advice on your situation, and no engagement arises until a service agreement with Icon.Partners is signed. For advice on a specific contract, speak to a lawyer qualified in the relevant jurisdiction.

Next step

Have a vendor DPA waiting for review?

Send it over on per-document terms. We will check it against Article 28 and your requirements, and tell you what to ask for.

Book a contract call