Article
7 mins read
Updated on 23 November 2021
Our subject expert
Lillian Tsang MBA
Senior Solicitor - Data Protection & Privacy
If your supplier suffers a data protection breach, you may still be liable – even if your own systems are secure.
Under UK data protection laws, the liability for a personal data breach doesn’t end with the party directly responsible for the breach. You must understand your obligations as either a data controller or data processor in any supplier relationship, especially as cyber attacks and insider threats become more sophisticated.
Our experienced data protection solicitors can help you assess your exposure, structure robust data processing agreements, and ensure that, contractually and operationally, your business is protected when things go wrong.
Under GDPR, a personal data breach is described as ‘a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, personal data transmitted, stored, or otherwise processed.’
A personal data breach is probably the worst thing that could happen to a supplier (processor) as well as a controller. A processor has many responsibilities towards their controller client, one of which is to ensure that technical and organisational measures are in place to process personal data and inform the controller without undue delay of any personal data breach.
Whilst a processor would do their best to look after the personal data that they process on behalf of the controller, we all know that data can never be 100% secure, especially in the virtual world. It is known that cyber identity fraud is the fastest-growing risk through which hackers gain access to our personal data.
A personal data breach by a processor can have many consequences. A data processor has numerous responsibilities and duties towards controllers, one of which is to ensure that personal data is kept secure and safe.
There are many consequences for businesses when a personal data breach occurs; however, we list what we believe as our top 3:
The party that determines what personal data is to be processed is the controller, and the party that follows the controller's instructions is the service provider, also known as the processor. The ICO provides a simple example to illustrate this point:
‘A private company provides software to process the daily pupil attendance records of a state-maintained school. Using the software, the company gives attendance reports to the school. The company’s sole purpose in processing the attendance data is to provide this service to the school. The school sets the purpose – to assess attendance. The company has no need to retain the data after it has produced the report. It does not determine the purposes of the processing; it merely provides the processing service. This company is likely to be a processor.‘
The school would be the controller, as it determines what personal data to process. Whereas the company is acting on the controller's instructions and carries out the said processing activities.
Whilst a party can be both controller and processor for different purposes, they cannot be both roles for the same processing activity. It may be the case that the processor wishes to engage another sub-processor to assist with the processing activity for which they have been instructed. Any processors would be regarded as sub-processors, and the same obligations would follow down the chain. So, in the above example, if the company engages another sub-processor to perform some of the processing activities, it will always be considered a processor.
Your GDPR obligations would also depend on whether you are a controller or a processor. Essentially, a controller would have more obligations and exercise ultimate control. In contrast, the processor would have fewer obligations and would be restricted in what they could do with the personal data.
The services that a processor would provide would be limited to the controller’s instructions. The processor would not exercise any control over the purpose for which the personal data is processed. Article 28(3) of the GDPR requires a contract to specify the nature and purpose of the processing. This is the reason the controller wishes to instruct the processor. The clauses would apply to the delivery of the services specified in the body of any substantive agreement.
Should there be any ambiguity in role determination, the data processing agreement would be the first place to look. The contract would include precedent clauses which would include, but are not limited to:
If a breach occurs, the supplier must notify the relevant parties immediately, following their contractual obligations. The supplier contracted with the controller would notify the controller immediately of any personal data breach in accordance with Article 33 GDPR. So, despite the original supplier using sub-processors, that original supplier would be directly liable to the controller for the sub-processor's obligations. The requirements for reporting a personal data breach should be contained within the data processing agreement.
A controller has a duty to notify the ICO of a 'serious personal data breach' without undue delay and within 72 hours of becoming aware. The processor will provide as much information as possible to the controller, enabling the controller to determine where the breach is reportable to the ICO.
The controller would also determine whether the breach is likely to result in a high risk of adversely affecting individuals’ rights and freedoms. If their rights and freedoms are affected, then the controller must also inform those individuals without undue delay.
GDPR gives individuals the right to claim compensation against a controller if they have suffered damage due to a personal data breach. This includes both ‘material and non-material damage’. The ICO does not have the power to award compensation, so an individual would need to make an application to the court. An individual can also bring a claim directly against a processor in court. A processor can be held liable under Article 82 to pay compensation for any damage caused by processing, including non-material damage such as distress. A processor will only be liable for the damage if:
A processor will not be liable if it can prove it is not responsible for the cause giving rise to the damage.
The landmark judgment in Lloyd v Google LLC [2021] is the leading authority on damages for breaches of data protection laws (despite the lawsuit being brought under the Data Protection Act 1998, it will apply equally to the Data Protection Act 2018). The decision would mean it’s highly unlikely for private claims for damages to be brought en masse against controllers.
Data processing agreements are carefully drafted documents, and it's important to get them right. The case of Schrems II states that transfer impact assessments need to be conducted before any transfer of personal data cross-border to non-adequate countries. It’s not always the case that processors are based in the EEA or the UK; many service providers are based across the globe, such as in the US. It is necessary to ensure you have adequate safeguards in place to be able to transfer personal data to your processor cross-border. If in the EU, you must ensure that your transfers comply with UK international data transfer laws or if you are transferring personal data out of the UK to the US, via the ‘UK-US Data Bridge.
A well-drafted data processing agreement is your first line of defence, but it’s only part of the picture. The way you assess risk, manage cross-border data transfers, allocate liability, and respond to breaches must all align with your business’s operational model and legal obligations. Whether you're renegotiating supplier contracts, navigating international data flows, or reviewing your data breach insurance, our data protection solicitors can work with you to build a resilient, compliant framework that protects both your customers’ data and your commercial interests.
About our expert
Senior Solicitor - Data Protection & Privacy
Lillian is an experienced data protection, privacy and AI lawyer, who qualified in England and Wales in 2008. She helps businesses navigate complex and fast-changing data laws with confidence, combining technical expertise with practical, commercially focused advice.
Cyber security Data Breaches & Incident Management Data Governance Data Processing Agreements Data Protection & Privacy Law Data Protection Health Check Data Protection Impact Assessments and 5 more...
25 September
What information shouldn’t I put into an AI tool...
10 October
Preparing your Record of Processing Activities for...
26 September
Legitimate interest: What the Data Use and Access ...
16 June
Do I need a privacy policy?...
21 May