How data processors can get you fined: vetting vendors and transfers under UK GDPR
TL;DR
Difficulty: Intermediate
- A vendor that handles customer data for you is your processor. Article 28 says choose one with sufficient guarantees and sign a contract with eight set terms.
- Processors can be fined directly, but you stay responsible for your choice. A dated record of your checks is your evidence.
- Data leaving the UK, including to the EU, needs adequacy, a safeguard (IDTA or Addendum) plus a transfer risk assessment, or an exception. Since 5 February 2026 the test is protection not materially lower than in the UK.
- A US vendor is covered by the data bridge only if it is active on the Data Privacy Framework List for the UK Extension. Check, screenshot, move on.
- Rank vendors by probability times cost and spend the time on the top two.
Your email platform, chat widget and reviews tool all handle your customers' data, and under UK GDPR each one is a relationship you answer for. I go through what Article 28 asks of you, how the transfer rules rewritten in February 2026 work, and how to check a US vendor in two minutes, with an invented Leeds candle shop worked through from start to finish.
The point: your vendors are part of your compliance
A small online shop in Leeds runs on perhaps a dozen outside services. An email platform, a chat widget, a reviews tool, analytics, accounting, a courier app. Each of them touches customer data, and each of them is a legal relationship under the UK General Data Protection Regulation (UK GDPR). If one of them handles that data badly, the regulator does not stop at the vendor's door. It knocks on yours as well.
The law asks two things of you. First, before you hand personal data to a service provider, you choose one that can be trusted with it and you put a contract in place that says what it may do.1 Second, if the data leaves the UK, you make sure the transfer has a legal route out and that the protection does not drop on the way.2 Both rules changed shape on 5 February 2026, when the Data (Use and Access) Act 2025 rewrote the UK's transfer rules.34
I go through both halves with the statute and the regulator's guidance, then show how I rank vendors so the review time goes where the risk is. The shop and its numbers are made up. The law is not.
Controller and processor: who decides and who does the work
Two words carry the whole subject. The controller is the business that decides why and how personal data is processed. The processor is the business that processes personal data on the controller's behalf.5 You are the controller of your customer list. The email platform that sends your newsletter to that list is your processor.
The test is who decides, not size or who owns the servers. A global software company is still your processor if it only does what you told it to do. The moment it uses the data for its own purposes, such as training its products or selling advertising, it acts as a controller for that part, and you need to know before you sign.
An example: Kirkstall Candle Company, an invented shop in Leeds at kirkstallcandles.example, run by Amira. She decides to send a monthly newsletter to customers who opted in, so she is the controller. The email platform stores the list and sends on her instruction, so it is her processor. Her chat widget stores transcripts for her staff, a processor too. But if its terms let it analyse those transcripts to improve its own models, it is deciding a purpose of its own. That is the sentence I look for first in any vendor's terms.
What Article 28 asks of you before you sign
Article 28 of the UK GDPR says you may use only processors that provide sufficient guarantees to implement appropriate technical and organisational measures.1 The regulator, the Information Commission, judges those guarantees by the processor's expert knowledge, resources and reliability, and says the controller stays primarily responsible for its own compliance and its processors'.6 Until 30 September 2026 that was the Information Commissioner's Office (ICO), and its website and guidance still use the name ICO, so I do too.7
Then the contract. It must set out the subject matter, duration, nature and purpose of the processing, the types of data and people, and your rights and obligations, and it must oblige the processor to do eight things:18
- Process the data only on your documented instructions, including on transfers abroad.
- Make sure everyone handling the data is bound by confidentiality.
- Take the security measures Article 32 requires.
- Use another processor only with your authorisation, on the same terms.
- Help you answer people who exercise their rights, such as access or erasure.
- Help you with security, breach notification and impact assessments.
- Delete or return all the data when the service ends, at your choice.
- Give you the information needed to show compliance, and allow audits.
Most software vendors publish a data processing agreement meant to cover this list. Your job is not to write one. It is to check that it exists, applies to your plan, and says these eight things.
Worked example: checking the chat widget's agreement
Amira's chat widget sends her a link to its data processing agreement. I read it against the list with her, one point at a time.
Instructions: the agreement says the provider processes data "to provide and improve the services". Improve is the provider's own purpose, so point one is only half met.
Confidentiality, security, help with rights and with breaches: a clause each, plus a security annex naming encryption and access controls. Points two, three, five and six pass.
Subprocessors: general authorisation, a public list, 30 days' notice of changes. Point four passes if Amira subscribes to the notices.
Deletion within 90 days of the end of the contract, and a yearly audit summary on request. Points seven and eight pass.
Result: seven of eight met, one to fix. Amira asks the vendor in writing how to opt out of "improvement" use. That one email is the due diligence for this point, and it is the one most shops never send.
Subprocessors: the vendors of your vendors
Your processor will almost always use processors of its own: hosting, email delivery, support tools. The law calls them other processors, and the industry says subprocessors. Article 28 says your processor must not engage one without your prior specific or general written authorisation, must tell you about changes so you can object, and must pass the same data protection obligations down to them by contract.1 If a subprocessor fails, your processor stays fully liable to you.1
An example: Amira's accounting software lists four subprocessors on its website. Hosting in Ireland, email delivery in the United States, a support desk tool in the United States, and a payment provider in the UK. Two of the four send her customers' names and addresses to the United States. The sales page never mentions it. The subprocessor list does. Five minutes of reading changes which transfer questions she needs to ask.
Who pays when a processor gets it wrong
The old version of this article said that if your processor fails, you are the one on the hook. That is too simple.
On compensation to the people affected, Article 82 says any controller involved in processing is liable for the damage caused by processing that breaks the law. A processor is liable only where it did not meet the obligations aimed at processors, or acted outside or against your lawful instructions.9 Where both are responsible for the same damage, each can be held liable for the whole of it, so the person gets paid, and the one who paid can then claim back the other's share.9 A controller escapes only by proving it was not in any way responsible.9
On fines, the regulator can fine processors directly. In March 2025 the ICO fined Advanced Computer Software Group £3.07 million after a ransomware attack in 2022 that disrupted NHS and social care services. Advanced processes personal information on behalf of those organisations, and the attackers got in through a customer account without multi factor authentication. Personal data of 79,404 people was taken.10
The fine levels are set in Article 83 and in section 157 of the Data Protection Act 2018. Breaking the controller and processor obligations, Article 28 among them, carries a maximum of £8.7 million or 2% of worldwide annual turnover, whichever is higher. Breaking the transfer rules carries the higher maximum, £17.5 million or 4%.1112
The old article also said the law does not distinguish deliberate from accidental failures. It does. When setting a fine, the regulator weighs the intentional or negligent character of the infringement, and the degree of responsibility, taking into account the measures put in place.11 That is the reason to keep a written record of your vendor checks.
An example: suppose Amira's chat provider is breached and chat transcripts with delivery addresses leak. If Amira read the agreement and fixed the one gap, her file shows it. If she pasted a script into her site and never looked, her file is empty. Same breach, very different position.
When data leaves the UK: the three step test
Chapter V of the UK GDPR now opens with Article 44A, in force since 5 February 2026: personal data may go to a third country only if adequacy regulations approve the transfer, it is subject to appropriate safeguards, or it relies on an exception for specific situations.23
For a UK business a third country is anywhere outside the UK, the European Union included. The old article asked whether data stayed "within the EEA". That is the European question. A Leeds shop asks about the UK.
The ICO's updated guidance of January 2026 gives a three step test. You are making a restricted transfer, and the transfer rules apply, if you answer yes to all three questions:13
- Does the UK GDPR apply to your processing of the personal information being transferred?
- Are you initiating the transfer to an organisation located outside the UK?
- Is that organisation a separate legal entity from your own?
Two details from the same guidance catch most shops out. A transfer includes making data accessible, so a support team abroad that logs into your UK system is receiving a transfer, even though the servers never move. And when your UK processor passes data to its own subprocessor abroad, it is your processor that initiates that transfer and has to comply with the rules.13 Your own employee working from a holiday flat in Spain is not a restricted transfer, because they belong to your own legal entity.13
Worked example: which of Amira's vendors make a restricted transfer
I take each vendor through the three questions.
The analytics tool is a German company hosting in Frankfurt. The UK GDPR applies, Amira sends it page view data, and it is a separate company. Three yeses: restricted transfer. The email platform is a US company: three yeses again.
The chat widget is a UK company, but its support agents work for a contractor in India and log into the transcripts. For Amira, question two is a no, because the chat company is in the UK. For the chat company, all three are yes. The transfer exists, and it is the processor's to cover. Amira checks that its agreement says how.
The courier app is UK based, with UK hosting and nothing abroad. Question two is a no. Four vendors, three restricted transfers, one made by her processor on her behalf.
The routes out: adequacy, safeguards, exceptions
Every restricted transfer needs one of three routes.2
Adequacy regulations come first. The government approves countries by regulations, and the ICO keeps the list. All of the European Economic Area (EEA) has full adequacy, as do Switzerland, New Zealand, South Korea and a handful of others. The United States has partial adequacy, covering only transfers under the UK Extension to the EU US Data Privacy Framework.14 With adequacy, no transfer risk assessment is needed, although the ICO still expects reasonable and proportionate checks that the recipient will meet its obligations.15
Appropriate safeguards come second, under Article 46. For a small business the relevant ones are the standard data protection clauses: the ICO's International Data Transfer Agreement, and its Addendum to the European Commission's standard contractual clauses.1617 Binding corporate rules, codes of conduct and certification exist too, but there are no approved UK certification schemes for restricted transfers yet.18
Exceptions come last, under Article 49. They include the person's explicit consent after being told the risks, and transfers necessary for a contract with the person, such as delivering an order abroad.19 They are for specific situations, not a way to run a software stack.
An example: Amira's analytics tool in Frankfurt is covered by adequacy for the EEA, so no safeguard and no risk assessment are needed. Her email platform in the United States needs either the data bridge or a safeguard. A customer in Bristol who asks for a gift to be shipped to her sister in Canada triggers a transfer of name and address to a courier abroad, which is necessary for the contract with that customer. That one fits the contract exception. Three transfers, three different routes.
The data protection test, new since February 2026
Article 46 says a transfer is made subject to appropriate safeguards only if a safeguard is in place and the controller or processor, acting reasonably and proportionately, considers that the data protection test is met.16 The test is met if, after the transfer, the protection for the people concerned would not be materially lower than under the UK GDPR and the Data Protection Act 2018.16 What counts as reasonable and proportionate is judged by all the circumstances of the transfer, including the nature and volume of the personal data.16 The government applies the same standard to adequacy regulations under Article 45B.20
The ICO calls the practical exercise a transfer risk assessment, or TRA. It says that if you completed a TRA under its earlier guidance and concluded the protection was sufficient, you have met the data protection test.21 You only need a TRA when you rely on a safeguard, not when adequacy or an exception covers the transfer.15 And if the assessment shows the protection would be materially lower and you cannot add protections, you must not make that transfer on that safeguard.21
"Reasonable and proportionate" is the useful phrase for a small business: the effort scales with the data.
Worked example: a proportionate test for the reviews tool
Amira uses a reviews widget run by a small US company that is not on the Data Privacy Framework list. It receives each customer's first name, email address and order number, so it can send a review request after delivery. About 400 a month.
Step one, the safeguard: the European standard contractual clauses with the ICO's UK Addendum, an Article 46 safeguard (more on that paper below).
Step two, the data: names, email addresses and order numbers. Nothing that reveals more than that someone bought a candle.
Step three, the destination: the usual question for the United States is access by public authorities. This data is low in sensitivity and of little interest to anyone but the vendor.
Step four, extra protections: encryption at rest and in transit, deletion 12 months after the request.
Step five, the conclusion: acting reasonably and proportionately, the protection is not materially lower than in the UK. Amira writes this on one page, dates it, and sets a review for next year. That page is the TRA. It took 20 minutes, about right for this data. Health data would take far longer.
The US data bridge, and how to check it in two minutes
Since 12 October 2023 the UK has had adequacy regulations for the United States, known as the UK US data bridge.22 They cover a transfer only if the recipient is indicated on the Data Privacy Framework List as participating in the UK Extension, and the data will be subject to the framework's principles once it arrives.22 The list is kept by the US Department of Commerce.22
The government's factsheet and the ICO give the checks.2324 Find the company on the Data Privacy Framework List and confirm its status is active. Confirm that it has signed up to the UK Extension, not only to the European framework. If you are sending staff data, confirm its certification covers human resources data. Read the privacy policy linked from its entry. If you send genetic data, biometric data used to identify someone, data about sexual orientation, or criminal offence data, tell the recipient it is sensitive.2324 And check again from time to time, because the status can lapse.23
If the company is not on the list, or not for the UK Extension, you fall back on a safeguard such as the IDTA or the Addendum, with a TRA.24 The ICO also notes that the UK Extension would not automatically fall if European courts struck down the European framework, though the government would then need to review it.23
An example: Amira's email platform is a US company. I search its name on the list at dataprivacyframework.gov. The entry shows an active status, participation in the EU US framework and in the UK Extension, and covers non human resources data. She sends no staff data and nothing sensitive. The data bridge covers the transfer, no TRA is needed, and the check is a screenshot dated today in her vendor file. If the entry had shown the European framework alone, the bridge would not apply, and she would need the vendor's Addendum and a TRA instead.
IDTA or Addendum: which paper for which vendor
The ICO's two sets of standard clauses do the same job in different shapes. The International Data Transfer Agreement is a standalone UK contract. The Addendum is a short document that amends the European Commission's standard contractual clauses of 4 June 2021 so they work under the UK GDPR, because the European clauses alone are not valid for UK restricted transfers.17 Both were laid before Parliament under section 119A of the Data Protection Act 2018 on 2 February 2022.1725
In practice the vendor chooses. One that already signs the European clauses attaches the Addendum. Either is a valid safeguard. The rules on changing them are strict: only minor changes, and nothing that lowers the protection.17
Two current points. The ICO plans to update both documents during 2026 to reflect the Data (Use and Access) Act, and says to keep using the current versions until then.17 And the clauses do not replace the TRA. You need both: the paper, and the one page that says the protection is not materially lower.17
An example: when Amira first asked, the reviews tool sent the European clauses on their own. That is not enough for a UK transfer. She asks for the UK Addendum, the vendor sends the completed tables and the mandatory clauses, and she files them with her one page TRA. The old version of this article also suggested an EU based proxy as a fix. It is not a transfer route: it adds a transfer to the EEA and does nothing for where the data goes next.
Ranking vendors by expected loss
A shop with a dozen vendors cannot give each a day's review, so I rank them by expected loss. For each vendor I estimate the probability of a data incident in the next year and its cost to the business, multiply, and add up.
Here is the expected loss for a year across all vendors, is the number of vendors, counts through them one by one, is the probability of an incident at vendor in that year, a number between 0 and 1, and is the cost to the business if that incident happens, in pounds. The formula is the ordinary expected value, explained from scratch in Foundations: expected value.
The probabilities are judgement, not statistics. I set them from what I see: whether the agreement meets Article 28, whether the transfer route is in place, the sensitivity of the data, whether support staff abroad have access, and how the vendor handles security. The cost includes the hours to respond, notifying the ICO and customers where needed, lost orders and the customers who do not come back. The point is the ranking, not precision.
Worked example: the candle shop's five vendors
These are my own illustrative estimates for the invented shop, not industry figures. One line per vendor, probability times cost:
- Chat widget (addresses in transcripts, the "improvement" clause open, support abroad):
- Email platform (9,000 customers, active on the data bridge, good agreement):
- Reviews tool (no safeguard signed yet):
- Accounting (hosted in Ireland, US subprocessors on the bridge):
- Analytics in Frankfurt (page views, little personal data):
Adding the five lines gives the total:
So , the expected yearly loss across the five vendors, is £2,740. The chat widget alone is more than half of it. That is where the first hour goes.
Each bar is one vendor, along the horizontal axis. The height is the expected yearly loss in pounds, probability times cost, before any fixes. The takeaway is the shape: two vendors carry most of the risk, and two short pieces of work, the chat clause and the reviews safeguard with its TRA, cut the total from £2,740 to £1,370. After the fixes the chat widget drops to a probability of 0.03, so , and the reviews tool to 0.02, so . The email platform did not need anything and got nothing beyond its screenshot.
My review, step by step
I run this before a tool goes live, and again yearly or when the vendor sends a change notice.
The flow runs from the data to the paperwork. It starts with what the tool touches, because a tool that never sees personal data needs none of the rest. Every path ends in the same place: a dated record in the vendor file, the evidence of the measures you took.
An example: Amira adds a postcode lookup at checkout. It receives a postcode and returns addresses, and never sees a name or an email address. I note that in one line, check the vendor is in the UK, and stop. Two minutes. The review is only long where the data is.
When a vendor fails the review
Sometimes a vendor will not sign an agreement, has no transfer route, or keeps a clause that lets it use your customers' data for its own purposes. In my experience there are three sensible responses.
Ask. Most vendors have the documents and simply do not advertise them. A short email asking for the data processing agreement, the subprocessor list and the transfer mechanism resolves more than half of the gaps I find.
Reduce what the tool sees. If a tool only needs an order number to do its job, do not send it the name and address. Less data lowers the probability and the cost in the formula at the same time, and it can turn a transfer that needs a long assessment into one that needs a short one.
Replace it. If the answers stay wrong, choose a vendor that gets them right. That is a decision, not a failure.
In my experience the tools most likely to fail are the ones added in a hurry by pasting a script into the site: chat widgets, session recording tools that can capture what people type into forms unless they are configured not to, and marketing tools that pass behaviour back to advertising platforms. The cookie side of those tools is a separate rule with its own consent requirements, which I cover in cookies, consent and tracking.
An example: the chat widget's vendor confirms by email that the "improvement" use can be switched off in the account settings for business customers. Amira switches it off, saves the email and the screenshot, and asks the vendor to name the mechanism for its support contractor abroad. The answer is the IDTA, signed between the vendor and its contractor. Two emails, one setting. The highest bar on the chart drops to a third.
Why this belongs in growth, not only in legal
The customer data in these tools is what a shop grows on: the email list, the order history, the reviews. A vendor that cannot delete a customer on request, or holds data somewhere you cannot account for, makes that data harder to use with confidence. When I design a shop's data flows, as in data warehousing for marketing automation, the vendor file is part of the design.
The work is small. A list of vendors, a few questions each, a screenshot or a page of reasoning where a transfer needs it, and a date to look again. Done properly, it is an afternoon. Left undone, it is an empty file on the day someone asks.