Alex is Sprintlaw’s co-founder and principal lawyer. Alex previously worked at a top-tier firm as a lawyer specialising in technology and media contracts, and founded a digital agency which he sold in 2015.
Yes, you usually need a Data Processing Agreement if your business shares personal data with a supplier who handles that data for you.
The slightly trickier part is working out whether your supplier is really acting for you, or whether they make their own decisions about the data. That controller and processor distinction is what decides whether a formal UK GDPR data processing contract is required.
This can sound more technical than it needs to be. If you use payroll software, a CRM, a marketing agency, cloud storage, an IT support provider, an outsourced bookkeeper or other supplier agreement, you may already be sharing customer or employee data in ways that need a proper written agreement.
Do I Need A Data Processing Agreement?
Yes, you need a Data Processing Agreement when another organisation processes personal data on your behalf as your processor.
Under the UK GDPR, a controller must only use processors that give enough guarantees that they can protect personal data properly. Article 28 of the UK GDPR also says the processing must be governed by a written contract or other legal act.
In plain English, if your business decides why personal data is collected and how it will be used, and your supplier simply uses it to provide their service to you, you'll usually need a DPA with that supplier.
For example, you may need a DPA if you send or give access to:
- Customer names, email addresses, phone numbers or order histories
- Employee payroll details, bank details, National Insurance numbers or sickness records
- Website enquiry data, analytics data or marketing lists
- Client files, user profiles or account information stored in cloud software
A DPA isn't just a nice-to-have privacy document. If the Information Commissioner's Office asks how you manage processors, or if something goes wrong with a supplier, your written agreement is one of the first documents you'll want to have ready.
What Is A Data Processing Agreement Under UK GDPR?
A Data Processing Agreement is a contract that sets out how a processor must handle personal data for your business, usually alongside your privacy policy.
You might also hear it called a data processing contract, processor agreement, controller processor agreement, Article 28 agreement or DPA. Try not to confuse it with the Data Protection Act 2018, which is also often shortened to DPA.
The purpose of the agreement is to make the rules clear between you and your supplier. It should say what data the supplier can use, what they can use it for, how they must protect it, and what happens when the work ends.
For example, say Nina runs a small dental supplies business in Manchester with 18 employees. She uses an external payroll provider. Each month, she uploads employee names, addresses, salary details, National Insurance numbers, bank account details and pension contribution information.
Nina decides why that information is processed: to pay staff and meet payroll obligations. The payroll provider uses the data only to run payroll for Nina's business. That means Nina is likely the controller and the payroll provider is likely the processor, so a DPA should be in place.
If the payroll provider suffers a security incident involving Nina's employee records, Nina may need to assess whether there's a personal data breach. If the breach is notifiable, the controller usually has 72 hours from becoming aware of it to report it to the ICO. A good DPA helps because it should require the processor to tell Nina quickly and give her the details she needs.
When Is A Supplier A Processor Rather Than A Controller?
A supplier is usually a processor when they handle personal data only to provide services to you and they don't decide their own separate purpose for using it.
This is the part that causes the most confusion. You don't work it out from the supplier's job title. You work it out from who decides the purpose and main means of the processing.
Signs Your Supplier Is A Processor
Your supplier is more likely to be a processor if they:
- Only use the personal data to deliver the service you requested
- Follow your instructions about what to do with the data
- Don't use the data for their own marketing, profiling or analytics beyond what you've authorised
- Return or delete the data when the service ends
- Need your permission before appointing another processor, such as a hosting provider or subcontractor
Signs Your Supplier May Be A Controller
Your supplier may be an independent controller if they decide their own purposes for using the data.
For example, your accountant may be a controller for some client due diligence, regulatory record-keeping and data sharing arrangements. A payment provider may be a controller for fraud prevention and transaction monitoring. A professional adviser may need to keep records for their own legal, regulatory or insurance reasons.
In those cases, you may still need privacy clauses in your contract, but you may not need a processor-style DPA for that part of the relationship.
Some relationships are mixed. A marketing agency might be your processor when sending your email campaign to your customer list, but a controller if it uses its own contact database for separate lead generation. If the line isn't clear, it's worth getting tailored advice before you sign.
Which Small Business Suppliers Usually Need A DPA?
Many everyday business tools and suppliers need a DPA because they handle personal data for your business.
You don't need to panic and treat every supplier the same way. Start with suppliers that can access customer, employee, subscriber, user or client information. Then ask what they do with it.
Common Examples Where A DPA Is Usually Needed
- Payroll providers: They process employee pay, bank, tax and pension information for you.
- HR software: They store staff records, leave data, performance notes and sometimes sensitive information.
- CRM platforms: They host customer and lead details so your team can manage sales and support.
- Email marketing platforms: They send campaigns to your mailing list based on your instructions.
- Marketing agencies: They may upload, segment or manage your customer lists for campaigns.
- Cloud storage providers: They store files that may include contracts, invoices, employee records or customer data.
- IT support providers: They may have admin access to systems containing personal data.
- Bookkeepers: They may process customer invoices, employee payments and supplier contact details.
Worked Example: CRM Plus Marketing Agency
Amira runs a fitness studio in Leeds with 1,200 customers on her mailing list. She uses a CRM to store names, email addresses, phone numbers, membership start dates and attendance tags. She also hires a marketing agency to send a 6-week reactivation campaign to 350 former members.
The CRM provider stores Amira's customer data so her studio can manage bookings and communications. The marketing agency receives a segment of 350 contacts and sends emails using Amira's wording and campaign plan.
Both suppliers are likely processors for those activities. Amira should have a DPA with the CRM provider and a DPA or processor clauses with the agency. She should also check whether either supplier transfers data outside the UK, uses subcontractors, or keeps the data after the campaign ends.
What Should A UK GDPR Data Processing Contract Include?
A UK GDPR data processing contract must include the Article 28 processor terms, plus practical clauses that match the way your supplier actually works.
A strong DPA shouldn't sit in a drawer looking impressive but saying very little. It should answer the questions you would ask if there was a data breach, a customer complaint, an ICO enquiry, or a messy supplier exit.
At a minimum, the agreement should cover:
- Subject matter and duration: What processing the supplier will carry out and how long it will last.
- Nature and purpose: What the supplier is doing with the data and why.
- Types of personal data: For example, names, contact details, payment information, staff records or usage data.
- Categories of data subjects: For example, customers, employees, contractors, subscribers or website users.
- Your documented instructions: The processor should only process the data on your instructions.
- Confidentiality: People who handle the data must be under suitable confidentiality duties.
- Security measures: The processor must use appropriate technical and organisational measures.
- Sub-processors: The agreement should control when the supplier can use subcontractors.
- Help with rights requests: The processor should help you respond to data subject access requests and other rights.
- Breach support: The processor should notify you without undue delay and give you useful information.
- Deletion or return: The supplier should delete or return personal data when services end, unless the law requires retention.
- Audits and information: You should have a way to check the processor is meeting its obligations.
If personal data may leave the UK, the contract also needs to deal with international transfers. Depending on the destination and setup, this may involve UK-approved transfer safeguards, such as the International Data Transfer Agreement or the UK Addendum to the EU Standard Contractual Clauses.
Can I Use A DPA Template?
Yes, you can use a DPA template as a starting point, but it should be tailored before you rely on it.
Templates can be helpful because they remind you of the main UK GDPR clauses. The risk is that a generic template may not match your actual data flows, your supplier's subcontractors, the type of data involved or any international transfers.
For example, a template that says no personal data leaves the UK won't help if your CRM stores backups in the United States. A template that gives blanket permission for all sub-processors may not be right if you're handling sensitive employee health information. A template that doesn't say when the supplier must tell you about a breach can leave you scrambling to meet the ICO's 72-hour reporting expectation.
DPA Template Outline: What To Fill In
This outline isn't a finished legal document, but it can help you gather the details a tailored DPA should cover.
- Parties: Name your business as controller and the supplier as processor, unless the roles are different.
- Services: Describe the services the supplier provides, such as payroll, CRM hosting or email campaign management.
- Processing Details: State the duration, purpose, nature of processing, data types and people affected.
- Instructions: Explain that the supplier can only process personal data on your documented instructions.
- Security Measures: List the practical controls expected, such as access controls, encryption, backups and staff training.
- Sub-Processors: Set out whether the supplier needs specific or general permission before using subcontractors.
- International Transfers: Record where data is stored or accessed from and what transfer safeguards apply.
- Data Subject Requests: Say how quickly the supplier must help you respond to access, deletion or correction requests.
- Personal Data Breaches: Require prompt notice, details of what happened, affected data and remedial steps.
- End Of Services: Say whether data must be returned, deleted or retained for a lawful reason.
- Audit And Evidence: Explain what reports, certifications or information the supplier must provide to show compliance.
- Liability And Contract Priority: Make clear how the DPA works with your main services agreement.
If you're comparing options, a free template may be fine for an early draft, but you'll need to do more of the legal and practical checking yourself. An online fixed-fee legal service can be useful if you want a lawyer to tailor the document and explain the key risks. A traditional firm billing by the hour may suit complex, high-risk processing or larger procurement projects.
How Do I Put DPAs In Place Without Making It A Huge Project?
You can keep this manageable by mapping your main data-sharing relationships first, then prioritising the higher-risk suppliers.
You don't need to solve every privacy issue in one afternoon. Start with the suppliers that hold the most sensitive, valuable or high-volume personal data.
A Practical Step-By-Step Process
- List your suppliers: Include software platforms, agencies, contractors, outsourced admin providers and cloud tools.
- Identify the data they access: Note whether they see customer details, staff records, payment data, health information or login credentials.
- Decide the role: Ask whether they act only on your instructions, or whether they use the data for their own purposes.
- Check existing terms: Many software providers already include a processor agreement, data processing schedule or data processing addendum in their online terms.
- Review key gaps: Look for breach notice, sub-processors, international transfers, deletion at the end, security and audit rights.
- Put the DPA in writing: Sign a standalone DPA or add suitable clauses to your main services agreement.
- Keep a record: Save the agreement with your supplier contract and note it in your records of processing activities.
- Review when things change: Revisit the DPA if you add new data, new countries, new services or new subcontractors.
For many small businesses, the biggest win is simply knowing which suppliers touch personal data and having clear processor terms for the key ones. That gives you a much better position if a customer asks a privacy question, a staff member makes a data request, or a supplier has a security incident.
Key Takeaways
- You usually need a Data Processing Agreement when a supplier processes personal data on your behalf.
- The main question is whether the supplier is your processor, an independent controller, or both for different activities.
- Payroll providers, CRMs, marketing agencies, cloud tools, IT support providers and HR platforms often need processor terms.
- A UK GDPR data processing contract should cover instructions, security, sub-processors, breaches, data subject requests, deletion and international transfers.
- A DPA template can help you get started, but it should be tailored to your real data flows and supplier setup.
- Start with your higher-risk suppliers, then keep your agreements under review as your business grows.
If you'd like help with reviewing your supplier data arrangements, preparing a tailored Data Processing Agreement, checking your controller and processor roles, or updating your privacy contracts, you can reach us at 08081347754 or team@sprintlaw.co.uk for a free, no-obligations chat.
Get your customer-facing terms right
What should your privacy and online terms cover?
If you collect customer data, sell online or run marketing campaigns, your public terms and privacy documents should match the real customer journey.






