Byteet
Book a call
Back to articles

Cybersecurity / Guide

Data Processing Agreement: When You Need One and What It Must Cover

Nov 13, 20268 min read

Cloud accounting, a hosted CRM, outsourced payroll — the moment a supplier processes personal data on your behalf, GDPR Article 28 requires a written data processing agreement, and both sides can be found in breach if it's missing. This guide covers when you need one, who drafts it, the eight things it must cover, and what changes once sub-processors or overseas servers get involved.

Data Processing Agreement: When You Need One and What It Must Cover

Every Dutch SME now runs part of its business on someone else's servers: email through Microsoft 365, bookkeeping in a SaaS package, a CRM hosted by a vendor, payroll handled by an external provider. The moment one of those suppliers processes personal data on your behalf — customer names, employee records, email addresses — the GDPR requires a written data processing agreement between you and that supplier. Plenty of SMEs assume the standard terms a vendor hands over at sign-up are good enough, or skip the agreement altogether because the relationship feels informal. Neither is safe: the duty applies regardless of company size, and both sides of the relationship can be found in breach if the agreement is missing or incomplete. This guide covers when you actually need one, who is responsible for arranging it, what it must contain, and what changes once a supplier's own sub-processors or overseas servers get involved.

What a data processing agreement actually requires

Article 28(3) of the GDPR requires a written agreement whenever one organisation — the controller — has another organisation — the processor — handle personal data on its behalf. The controller decides why and how the data is processed; the processor carries that out, under instruction. A cloud accounting package, an email marketing tool, a hosted CRM and an IT provider with access to your systems are typically processors in this sense. This isn't a courtesy or a formality: without the agreement in place, the controller cannot demonstrate it has adequate safeguards for how the processor handles the data, and Dutch supervisory guidance treats that gap itself as a breach — by the controller, and separately by the processor, since the same duty to have a written agreement applies to it directly.

When you actually need one

Not every supplier needs this agreement — only a supplier that genuinely acts as a processor. The test is factual, not contractual: whoever actually determines the purpose and means of a given processing activity is the controller for it, whatever a contract happens to say. Dutch supervisory guidance gives a concrete example of where the line falls the other way: a logistics company delivering your packages is not a processor of your customers' data, even though it handles names, addresses and phone numbers for track-and-trace. It is itself a controller for that handling, because the data is necessary for its own delivery service, not processed purely under your instruction. Cloud and SaaS suppliers sit on the other side of that line far more often: an accounting platform, an email host, a backup provider or a hosted CRM processes your customers' or staff's data strictly to deliver the service you asked for, for your purposes — that is a processor relationship, and it needs a written agreement.

Who arranges it, and why you stay responsible either way

In practice, the controller usually takes the initiative, since outsourcing the processing was the controller's decision in the first place — but the agreement can just as easily start from the processor's side, for instance when a SaaS vendor hands new customers a standard data processing addendum at sign-up. Either way, accepting a supplier's own template does not shift responsibility: as the controller, you remain accountable for the processing itself, even when the processor drafted the agreement you both signed.

The eight things the agreement must cover

Article 28(3) sets out the topics a processing agreement needs to address. A template that skips one of these, or restates it too vaguely to mean anything, has not actually met the requirement:

  • A description of the processing — its subject, duration, nature and purpose, the categories of personal data and data subjects involved, and your rights and duties as controller.
  • Processing only on your written instructions — the processor may not use the personal data for its own purposes.
  • A confidentiality duty covering everyone at the processor who handles the data.
  • Appropriate technical and organisational security measures, for example pseudonymisation and encryption, the ability to restore availability after an incident, and regular testing of those measures.
  • Written consent from you before engaging a sub-processor, with the same obligations passed down in a sub-processing agreement — the processor stays fully liable to you if a sub-processor fails to meet them.
  • Assistance so you can honour the rights of the people whose data you hold: access, correction, erasure and data portability requests.
  • Assistance with your other duties, including reporting a data breach, running a data protection impact assessment, and any required prior consultation with the supervisory authority.
  • Deletion or return of all personal data, including copies, once the service ends — unless the processor is legally required to retain it.

A ninth item, cooperation with audits and making relevant information available to verify compliance, usually sits alongside these eight in practice.

Sub-processors and data leaving the EU

Most cloud and SaaS suppliers rely on their own sub-processors — a hosting provider, a support tool, a payment processor. The agreement needs your written approval before the processor can bring in a sub-processor, and the same obligations need to pass down to each one. If a sub-processor stores or processes data outside the European Economic Area, that transfer needs its own legal basis on top of the processing agreement itself. The European Commission has adopted standard contractual clauses for exactly this purpose, and a supplier operating outside the EEA should be able to point to the specific clauses it relies on rather than a general assurance that "it's handled."

What happens without one

There is no size exemption and no grace period tied to how informal the relationship feels. If you are working with a processor and have not put a written agreement in place, Dutch supervisory guidance is explicit that both you and the supplier are in breach — you because you cannot demonstrate adequate safeguards, and the supplier because the same duty applies to it directly. You cannot force a supplier to sign; if you cannot agree on terms, the alternative is not working with that supplier, not working together informally without paper.

Keeping it more than a signature

A data processing agreement that just restates the wording of the GDPR without making it concrete for your situation does not do its job — the clauses are supposed to spell out how you and the supplier will actually meet those obligations, not merely confirm that you will. The same applies over time: an agreement signed when you first bought a tool can go stale once you start sending it more data, more sensitive data, or once the supplier changes what it does with sub-processors. Review the agreements with the suppliers that handle your most sensitive data at least once, and again whenever the relationship changes materially, rather than treating the signature as the end of the work.

Where this fits with the rest of your security work

A data processing agreement with every genuine processor is only one part of being able to show you handle personal data responsibly — it sits alongside the technical measures you control directly, such as who can actually reach that data and how well it's backed up. Our Cybersecurity & Identity team can review your current supplier agreements against these requirements as part of a broader security assessment, and if you're moving systems to new cloud or SaaS suppliers in the first place, our Cloud Infrastructure team can help make sure the right agreement is in place before data moves, not after. If a supplier incident ever does expose personal data, what counts as a reportable data breach and how the 72-hour duty works is worth reading alongside this guide — the two duties often apply to the same incident.

FAQ

Is a data processing agreement a legal requirement, or just best practice? It's a legal requirement. Article 28(3) of the GDPR obliges both the controller and the processor to have one in writing; it is not optional guidance.

Our supplier already has a standard agreement we signed when we bought the software. Is that enough? Only if it actually covers all the required topics and nothing in it conflicts with the GDPR. A standard template is a starting point to check against those requirements, not something to accept without reading it.

Does our courier or delivery company need a processing agreement with us? Not as a processor relationship in most cases. Dutch supervisory guidance specifically notes that a logistics company handling names and addresses for delivery is itself a controller for that data, not your processor, because it needs the data for its own service rather than processing it purely on your instructions.

What if our supplier stores data outside the EU? That transfer needs its own legal basis, on top of the processing agreement itself. The European Commission's standard contractual clauses are the usual mechanism suppliers rely on for this.

Who is liable if we never put an agreement in place? Both sides. Dutch supervisory guidance treats the missing agreement as a breach by the controller, who cannot show adequate safeguards are in place, and separately by the processor, who has the same written-agreement duty directly.

  • AVG
  • Privacy
  • Cybersecurity
  • SME

Related Articles