
The GDPR data processing agreement with your IT supplier: what belongs in it
A GDPR data processing agreement with your IT supplier is usually signed in an afternoon, often on the supplier’s own template. What it is worth sits in the schedules: which data they can see, through which systems, with which sub-processors, and what happens to the backups when you leave. This is what the IT side has to supply for it.
An IT supplier with admin rights is almost always a processor, even if they never look at your data: being able to is enough.
The GDPR sets out what a data processing agreement must contain at minimum. The real work is in the schedules (systems, sub-processors, security measures), and the IT side fills those in, not a template.
Agree how quickly a breach reaches you and what happens to backups and returned devices. Then have the agreement reviewed by a lawyer; we do not do that.
When your IT supplier is a processor
A processor handles personal data on behalf of someone else: the controller, which is your organisation. With managed IT that is almost always the case, even if the supplier is never meant to look at your data. Whoever holds admin rights on your Microsoft 365 tenant, your file server or your backup can reach the mailboxes, the HR folder and the customer list. That ability is enough.
- Managed IT and service desk: processor. Admin rights, password resets and remote sessions on a user’s screen all give access to personal data.
- Backup and cloud storage: processor. The supplier holds a copy of everything on your systems.
- Hardware supply: usually not, because a new laptop in a box holds no data. It changes once the supplier builds devices with user profiles, or takes old devices back and wipes them: those drives hold whatever was on your desks.
- An engineer pulling cable or fitting an access point: generally not, as long as they cannot log in to anything.
If in doubt, do not ask what the supplier does; ask what they can reach. “We never read your email” is a promise. An admin account with access to every mailbox is a fact.
What a GDPR data processing agreement must contain
Article 28 of the GDPR, which in the UK carries over into the UK GDPR, lists the minimum content of a data processing agreement. There are fewer points than most templates suggest, and almost every one has a technical answer:
- Subject matter, duration, nature and purpose of the processing, the types of personal data and the categories of data subjects.
- Documented instructions only: the supplier does not use the data for its own purposes.
- Confidentiality for everyone at the supplier who can access the data.
- Appropriate security measures, as Article 32 requires.
- Rules on sub-processors: whom the supplier may engage and on what terms.
- Assistance with data subject requests, such as access or erasure, and with security, breaches and a DPIA.
- Return or deletion at the end of the service.
- Information and audits to demonstrate compliance.
The agreement must be in writing, and electronic form counts. The supplier’s template, the guidance from the ICO on controller and processor contracts, or the standard clauses the European Commission has adopted for EU organisations are all reasonable starting points. Without an agreement at all, neither you nor your supplier complies.
What no template can fill in is your environment. That is why the work is in the schedules, and that is what the rest of this article is about.
The schedule that does the work: which data, through which systems
Almost every data processing agreement has a schedule listing the data and the data subjects. It usually reads “name, address, email address; employees and customers”. That is accurate, and it helps nobody. Ask the supplier to state, system by system, what they can reach:
- The workplace environment: mailboxes, OneDrive, Teams and SharePoint, and with which permissions.
- File servers and shared drives, including those of HR and finance.
- Backups: of which systems, where they are held and how long they are kept.
- Remote management: the software the supplier uses to view screens and files on devices.
- Their own ticketing system: tickets hold names, phone numbers and sometimes a screenshot full of customer data.
Two kinds of data deserve their own line: health data in absence records and National Insurance numbers in payroll. If either sits on a system the supplier can reach, it belongs in the schedule, and the bar for security goes up.
This overview also feeds your own record of processing. A supplier who cannot draw it up does not know what they can reach, and that is an answer in itself.
Sub-processors: the list your supplier should be able to give you
An IT supplier rarely works alone. The workplace runs on Microsoft, the backup sits with a storage provider, remote management goes through a third-party tool and tickets live in a cloud service desk. Each of them is a sub-processor as soon as your personal data passes through it.
- A current list with, for each sub-processor, the name, the service and the country where the data is held or accessed from.
- Authorisation: specific to each sub-processor, or general with advance notice of every change and a window to object. General authorisation is common; without advance notice it is a blank cheque.
- Obligations passed down: the sub-processor is bound by the same terms, and your supplier remains responsible to you.
- International transfers: if a sub-processor stores data outside the UK or the EEA, or someone can reach it from there, that is a restricted transfer and needs a basis, such as adequacy regulations, the International Data Transfer Agreement or the UK Addendum to the EU clauses. Remote access counts, even when the data itself stays put.
The question that yields the most is a plain one: “Who, apart from your own staff, can reach our data, and from which country?”
Security measures and audits: what a certificate proves
The GDPR requires “appropriate technical and organisational measures”, and most agreements point to a schedule for them. A schedule that only repeats that phrase is not a schedule. What belongs in it:
- Multi-factor authentication on every admin account.
- Named admin rights rather than shared ones, revoked on the day someone leaves.
- Logging of admin actions, and how long those logs are kept.
- Encryption of backups and of laptops.
- Confidentiality undertakings for staff, and how they are vetted.
- A backup restore test at a fixed interval.
The right to audit is in the law, but auditing your supplier yourself is out of reach for most SMEs. That is why many agreements accept a certificate or an independent report as first evidence. An ISO/IEC 27001 certificate shows that the supplier runs a working information security management system. It does not by itself show that the service you buy is in scope: ask for the scope of the certificate and the Statement of Applicability. What to look for there is in our ISO 27001 checklist.
Breaches, backups and the end of the relationship
In a breach, the processor reports to you, not to the ICO. The GDPR says without undue delay. You then have 72 hours to report where the breach is reportable, and you can only manage that if the facts arrive quickly and complete. So agree a deadline in hours rather than “promptly”, and what the notice must contain: which systems, which accounts, which period, which data, and what has already been done. Why those questions in particular is explained in what is a data breach.
At the end, the supplier must return or delete the data. That sounds simple until you think of the backups: they have a retention period, and your data is still in them after the service has stopped. Agree whether those backups are deleted early or kept to the end of their retention, and that they stay just as protected until then. Ask for written confirmation once everything is gone.
Returned devices belong here too. If the supplier takes back laptops or servers, agree the wiping method and a certificate per serial number. A drive that has been “reformatted” has not been wiped.
Where our work stops
What we do. We supply the technical side of a data processing agreement: a system-by-system overview of the data we can reach, the list of sub-processors with their countries, a description of the measures we actually take, incident notices with the facts attached, and deletion with a certificate per device. We are ISO/IEC 27001 certified; that describes how we work and is not a judgement on your agreement.
What we do not do. We are not lawyers and not a data protection officer. We do not review a data processing agreement legally, including one from another supplier, and we do not decide whether processing has a lawful basis or which party is the controller. Have the agreement reviewed by a lawyer before you sign.
Questions we get about this
The five that come up most often.
What is a GDPR data processing agreement?
It is the contract between an organisation and a party that processes personal data on its behalf, such as an IT supplier. Article 28 of the GDPR, and of the UK GDPR, sets out what it must contain: which data, for what purpose, which security, which sub-processors and what happens to the data at the end. It may be concluded electronically.
Is a data processing agreement mandatory?
Yes, whenever a party processes personal data on your behalf. With managed IT that is nearly always the case, because admin rights give access to mailboxes, files and backups even if the supplier never looks at them. Without an agreement, neither party complies.
Who drafts the data processing agreement?
Either party can. Suppliers often use their own template, and the ICO publishes guidance on what controller and processor contracts should say. More important than whose template it is are the schedules: which systems, which sub-processors and which measures, and the supplier has to fill those in for your environment.
Is a hardware supplier a processor too?
Usually not when delivering new devices, because they hold no data. That changes once the supplier builds devices with user profiles or takes old ones back and wipes them. Then they handle personal data and an agreement is needed, covering the wiping method and a certificate per device.
Can you review our data processing agreement legally?
No. We are not lawyers and not a data protection officer, and we do not review contracts legally, including those of other suppliers. What we do is complete or explain the technical schedules: which systems, which sub-processors and which measures. Have the agreement itself reviewed by a lawyer before you sign.
Further reading
What this touches: the breach itself, the standard and the management.
Shall we go through the technical schedules with you?
Send us the data processing agreement you have now. We will show you which systems, sub-processors and measures belong in it for your environment; the legal review we leave to your lawyer.
Practical IT knowledge in your inbox
New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.