Data processing agreement: what it is and when you need one

If you work as a freelancer or small organisation with software that processes client data — an EHR system, accounting software, email marketing, or CRM — you are legally required to have a data processing agreement (DPA) in place with that vendor. This follows from GDPR Article 28.

Data processing agreement: what it is and when you need one

Data processing agreement: what it is and when you need one

If you work as a freelancer or small organisation with software that processes client data — an EHR system, accounting software, email marketing, or CRM — you are legally required to have a data processing agreement (DPA) in place with that vendor. This follows from GDPR Article 28.


Who this guide is for

This guide is mainly for:

  • freelancers, small organisations, and independent professionals who use software vendors to handle client or patient data
  • readers in business, legal, or healthcare contexts where GDPR obligations are part of normal operations
  • people who need to know whether a vendor is merely convenient or actually usable in a defensible way

For mainstream readers with no client-data responsibility, this is usually not a priority page. This guide matters once you are responsible for other people’s personal data, not only your own.


What you gain, and what it costs

If you handle this properly, you usually gain:

  • less legal and operational ambiguity about what your vendors are allowed to do with client data
  • a clearer paper trail for audits, incidents, or regulator questions
  • a better filter for excluding vendors that are not suitable for professional data handling

But it costs something:

  • some administrative work
  • a little friction when choosing or onboarding vendors
  • less freedom to use quick, free, or poorly documented tools

For professional contexts that is usually a reasonable trade. It becomes overkill only if you turn this into a legal paperwork exercise before identifying which vendors actually process client data on your behalf.


What is a data processing agreement?

A data processing agreement is a written contract (electronic counts, such as accepting it online) between you (the data controller) and a vendor (the data processor) who processes personal data on your behalf.

The agreement establishes:

  • Which data the processor may process, and for what purpose
  • How the processor secures the data
  • That the processor may not use the data for their own purposes
  • How data breaches are reported
  • That data is deleted or returned when the agreement ends

Working with a processor without this agreement is an infringement in itself, by you and by the vendor: the regulator can fine both (this tier of GDPR fines goes up to €10 million or, for a company, 2% of worldwide annual turnover if that is higher). You also remain responsible for choosing a vendor that protects the data properly.


When do you need one?

You need a data processing agreement whenever an external party processes personal data on your behalf. Examples:

Situation DPA required?
Accounting software (QuickBooks, Xero) with client invoices Yes
EHR or case management system Yes
Email marketing tool (Mailchimp, Brevo) with client list Yes
CRM system (HubSpot, Pipedrive) Yes
Cloud storage (Proton Drive, Tresorit) for client files Yes
Bookkeeper who keeps your records on your instructions Yes
Auditing accountant Usually not: an auditor decides how to process for the audit, so is a controller in their own right
Tools you use purely for yourself, without client data No

How to arrange it

Step 1 — Inventory your processors

Make a list of all software vendors and service providers who can see client data. Don’t forget: IT management, hosting, payroll administration.

Step 2 — Check whether a DPA already exists

Many large vendors have the data processing agreement already built into their terms of service or available as a separate document. Check:

  • The vendor’s privacy or legal page
  • Search for “[vendor name] data processing agreement” or “DPA”

Examples where this is handled by default:

  • Proton Drive / Proton Mail — Data Processing Agreement at proton.me/legal/dpa, part of the terms
  • Google Workspace — Cloud Data Processing Addendum (formerly the Data Processing Amendment)
  • Mailchimp — Data Processing Addendum, part of its standard terms
  • Microsoft 365 — Products and Services Data Protection Addendum

Step 3 — Sign or accept

Sometimes clicking “agree” in account settings is sufficient. Sometimes you need to sign a document. Keep the confirmation.

Step 4 — Store the agreement

Keep the signed DPA or confirmation of acceptance. In the event of a supervisory authority audit you need to be able to demonstrate that the agreement exists.


What if a vendor doesn’t have one?

Small or unknown vendors sometimes have no standard DPA. In that case you can:

  • Send your own DPA: the European Commission publishes free standard contractual clauses for exactly this (2021); the Dutch regulator points to these and to sector associations’ models
  • Ask the vendor to draw one up
  • Reconsider whether this vendor is suitable for processing client data

If a vendor refuses to enter into a DPA but does process client data, you legally cannot use that vendor for that purpose.


EU servers and transfers outside the EU

A data processing agreement says the vendor may only move data abroad on your instructions, but it doesn’t make such a transfer lawful by itself. The GDPR doesn’t require data to stay in the EU; a transfer outside the EEA needs a legal ground, such as an adequacy decision (e.g. Switzerland, the UK, Canada for commercial organisations, US companies certified under the Data Privacy Framework) or safeguards such as Standard Contractual Clauses.

Check with your processors:

  • Where are the servers located?
  • Is there an adequacy decision or Standard Contractual Clauses (SCCs) for transfers outside the EU?

Proton (Switzerland, adequacy decision; its DPA keeps transfers to Switzerland, the EU and adequacy countries where possible) and Tresorit (Ireland by default) need no extra steps. For US providers, check which mechanism they use: Mailchimp, for example, relies on the DPF with SCCs as a fallback. Unknown or free services: always check.

A note on US providers relying on the EU-US Data Privacy Framework (DPF) instead of SCCs: the DPF is in force (November 2026). The EU General Court dismissed a challenge to it in September 2025; an appeal is pending at the EU Court of Justice (C-703/25 P). On 29 June 2026 the US Supreme Court struck down the legal protection of FTC commissioners against removal by the President (Trump v. Slaughter); the FTC is one of the two US agencies that enforce companies’ DPF commitments. Whether that matters for the appeal is open. For providers that mainly rely on the DPF: treat SCCs as a genuine fallback, not a formality.


Records of processing activities

In addition to data processing agreements, as a data controller you almost always need a record of processing activities: an overview of what personal data you process, for what purpose, and for how long. Organisations under 250 staff are exempt only if their processing is occasional, low-risk and involves no sensitive data; the Dutch regulator notes that processing client or staff data is rarely occasional.

A simple spreadsheet is fine: the format is free, but the GDPR lists what goes in it: your name and contact details, purposes, categories of people and data, recipients (including processors), transfers outside the EEA, retention periods and, where possible, a general description of your security measures. A legal-basis column isn’t required but is recommended. The Dutch regulator has a free template for small businesses (in Dutch).


Next step

Go further

Profiles

Reviews