“Cyberattack” has been a rising search in the United Kingdom over the past two days. This guide does not describe any particular incident. No official document read for this article establishes the facts of a specific attack, and none is assumed here. It starts instead from the situation many readers face after a message from a shop, an employer, a school, a landlord or an online service explaining that an attacker has accessed systems holding their details. Two separate questions follow. The first concerns the attacker, whose conduct may be a criminal offence. The second concerns the organisation that held the data, and whether its handling of that data complied with data protection law. Only the second question gives the reader a direct route to complain to that organisation and, where the legal conditions are met, to claim compensation from it.
The Data Protection Act 2018 applies across the United Kingdom, in England and Wales, Scotland and Northern Ireland, alongside the UK GDPR. Two recent changes matter here. Since 19 June 2026, a person can complain directly to the organisation responsible for the data, which must acknowledge the complaint within 30 days. Since 30 September 2026, complaints to the regulator go to the Information Commission. The method set out below is of general scope and reflects the revised legislation as read on 18 November 2026. It is general information on foreign law, prepared in Paris, and it does not assess any individual file.
I. Separate the Attack From the Organisation’s Data Protection Duties
A. Identify the offence, the organisation responsible and the data actually exposed
The person who breaks into a computer system and the organisation that held your data are in very different legal positions. For the attacker, the starting point is section 1 of the Computer Misuse Act 1990. It makes it an offence for a person to cause a computer to perform any function with intent to secure access to any program or data held in any computer, where that access is unauthorised and the person knows this at the time. The intent does not need to be directed at any particular program, data or computer. On conviction on indictment, the section provides for imprisonment of up to two years, a fine or both. Lower maximum penalties apply on summary conviction, with separate figures for England and Wales and for Scotland.
That criminal offence concerns the attacker. A police investigation, a prosecution, or the absence of either, does not answer the question that matters most to a person whose data has been exposed: did the organisation that held the data meet its own legal obligations, and if not, what remedy follows? The two tracks can run at the same time. Reporting suspected fraud or a suspicious message to the police or to your bank is one step. Asking the organisation to explain what happened to your data is another. Keeping these steps apart avoids a common mistake, which is to wait for the outcome of a criminal inquiry that may never identify anyone before raising questions with the organisation itself.
Next, check whether the exposed information is personal data. Under section 3 of the 2018 Act, personal data means any information relating to an identified or identifiable living individual. An individual is identifiable when he or she can be identified directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data or an online identifier, or by reference to factors specific to the person’s physical, physiological, genetic, mental, economic, cultural or social identity. A customer number linked to a name, an email address used as a login, a delivery address or a scanned identity document will usually fall within that wording. The person to whom the data relates is the “data subject”.
The same section gives “processing” a broad meaning. It covers operations such as collection, recording, organisation, storage, retrieval, consultation, use, disclosure, combination, restriction, erasure and destruction. Holding customer records on a server is therefore a form of processing, and so is sending them to a service provider. This matters because the obligations under data protection law attach to processing, and an organisation that stores your data remains within the scope of those rules while the data sits on its systems.
You also need to identify who is responsible. Section 3(6) of the Act explains that “controller” and “processor” take the meaning given in the Part of the Act that applies to the processing in question. In everyday terms, the controller is the organisation that decides why and how your data is used, while a processor handles data on its behalf, for example a hosting provider or a payroll service. A notice about an incident may come from either. If the message refers to a supplier, ask which organisation holds your account or employed you, because the complaint route described below is directed to the controller.
Then build a short, dated record. Keep the notice exactly as you received it, with the sender address, the date and any reference number. Note which categories of information the notice says were affected: contact details, dates of birth, account numbers, passwords, identity documents, health information or something else. Record any later event that may be connected, such as a message quoting details that only the organisation held, an unexpected password reset or an unfamiliar transaction. Note what you did and when: changing a password, cancelling a card, buying a replacement document or taking time off work to deal with the consequences. Keep receipts. If you are unsure whether the notice itself is genuine, check it through the organisation’s usual website or app rather than through links in the message, since a real incident is sometimes followed by imitation messages.
This record serves three purposes. It allows you to write a precise complaint. It helps the organisation and later the regulator understand which data relating to you was involved. And it creates the evidence you may need if you later claim compensation, where you will have to show what you lost or suffered and why it is connected to the exposure of your data.
B. Use the complaint routes: the controller first, then the Information Commission
The first formal step is now a complaint to the controller. Section 164A of the 2018 Act allows a data subject to complain to the controller if he or she considers that, in connection with personal data relating to him or her, there is an infringement of the UK GDPR or of Part 3 of the Act. The section was inserted by section 103 of the Data (Use and Access) Act 2025, and the revised text shows it fully in force since 19 June 2026. The same section 103 extended the regulator complaint provision to the UK GDPR and omitted Article 77 of the UK GDPR, which had previously contained the right to complain to the regulator.
Section 164A places four concrete duties on the controller. It must facilitate complaints, for example by providing a complaint form that can be completed electronically and by other means. It must acknowledge receipt of a complaint within the period of 30 days beginning when the complaint is received. It must, without undue delay, take appropriate steps to respond to the complaint. And it must inform the complainant of the outcome. The Act adds that appropriate steps include making enquiries into the subject matter of the complaint, to the extent appropriate, and informing the complainant about progress. A controller that receives a complaint is therefore expected to investigate it, keep the complainant informed and say how the matter ended.
A complaint after a cyberattack works best when it asks questions the controller can answer from its own records. Identify yourself and your account or customer relationship. Attach or quote the notice you received. Ask which categories of your personal data were affected, over what period, and whether the organisation knows that any of it has been copied or published. Ask what the organisation has done in response and what it recommends you do. State briefly why you consider that there may be an infringement, for instance because sensitive identity documents were kept longer than you expected or were accessible in a way you did not anticipate, and avoid assertions you cannot support. Ask the controller to acknowledge the complaint and to inform you of the outcome. Use the complaint form if the organisation provides one, keep a copy of what you sent and note the date. That date starts the 30-day period for acknowledgement.
If the response is incomplete or slow, the next route is the regulator. Section 165 allows a data subject to complain to the Commission if he or she considers that there is an infringement of the UK GDPR or of Part 3 or 4 of the Act in connection with personal data relating to him or her. Since 30 September 2026, the revised text refers to the Commission rather than the Commissioner. Section 3(8A) defines the Commission as the Information Commission, a body corporate established by section 114A of the Act.
Section 165 sets out what the Commission must do. It must facilitate complaints, including by providing a form that can be completed electronically and by other means. When it receives a complaint, it must take appropriate steps to respond, inform the complainant of the outcome, inform the complainant of the rights under section 166 and, if asked, give further information about how to pursue the complaint. Appropriate steps include investigating the subject matter of the complaint to the extent appropriate and informing the complainant about progress. The text read for this article does not make a prior complaint to the controller a condition of a complaint to the Commission. Even so, a complaint that already shows what the controller was asked and how it replied gives the Commission a clearer file to work on.
Section 166 deals with delay. It applies where the Commission fails to take appropriate steps to respond to a complaint, or fails to tell the complainant about progress or the outcome before the end of the period of three months beginning when it received the complaint. It also applies where the consideration of the complaint continues beyond that period and the Commission fails to provide such information during a subsequent period of three months. On an application by the data subject, the Tribunal may then order the Commission to take appropriate steps to respond, or to inform the complainant of progress or of the outcome within a specified period. The order may specify steps, or require an investigation or a specified step to be concluded within a set period. Under section 205, “the Tribunal” means the Upper Tribunal where Tribunal Procedure Rules determine that it should hear the application, and the First-tier Tribunal in any other case.
Section 166 is about the handling of the complaint. It allows a complainant to push a stalled complaint forward. It does not, in the text read, provide for compensation. Compensation is a separate question, dealt with by the courts under other provisions examined in Part II.
Collective action is also possible at the complaint stage. Under section 187, a data subject can authorise a body or organisation that meets two conditions to exercise, on his or her behalf, the rights under sections 164A and 165 and certain remedies under the UK GDPR, including the right to compensation in Article 82. The first condition is that the body must, by its constitution or an enactment, apply its income and any capital it expends for charitable or public purposes, must not distribute its assets among its members otherwise than for such purposes, and must have objectives in the public interest. The second is that it must be active in protecting data subjects’ rights and freedoms with regard to their personal data. After a large incident, joining a complaint run by such a body can be more practical than acting alone, provided you check that the body meets these conditions.
II. Turn the Complaint Into a Remedy When the Answer Falls Short
A. Show a contravention and the damage it caused
For processing covered by the UK GDPR, which in most cases includes the customer and staff records of shops, employers and online services, the right to compensation is found in Article 82 of the UK GDPR. Section 168 of the 2018 Act, headed “Compensation for contravention of the UK GDPR”, refers to that Article as the right to compensation for material or non-material damage. It then adds a clarification that is central for people affected by a data breach: in Article 82, “non-material damage” includes distress. In practice, a claim is not limited to money taken from a bank account. Worry, anxiety or upset caused by the exposure of your data can form part of the claim, provided the other conditions are met.
The heading of section 168 also shows the structure of the claim. Compensation is linked to a contravention. A cyberattack is a crime committed by someone else, and the fact that an attacker succeeded does not on its own establish that the organisation broke the law. The question is whether the organisation’s processing of your data contravened the UK GDPR, and whether that contravention caused you damage. The answer often depends on facts that only the organisation can explain at first: what data it held about you, why it still held it, who could access it, how the attacker got in and what the organisation did once it learned of the intrusion. This is one reason why the complaint under section 164A matters. A specific question asked early, and the controller’s written answer, can later show what the organisation knew and said about the incident.
Other sources of evidence may follow. The outcome of a complaint to the Commission may record its view of the organisation’s handling of the matter. Documents produced in later proceedings, or a technical report, may explain how the intrusion happened. None of these is guaranteed, and each depends on the facts. What a reader can control is the quality of his or her own record: the notice, the complaint, the replies, the dates and the evidence of consequences.
Damage then needs to be shown and connected to the exposure of the data. Material damage covers financial consequences. Examples might include a sum lost to a fraud that can be traced to the exposed details, the cost of replacing an identity document, or charges incurred in securing an account. Non-material damage covers distress, and its weight depends on the circumstances. The exposure of an email address is not the same as the exposure of a scanned passport, a medical record or full card details, and the risk that follows differs accordingly. A contemporaneous note of how the incident affected you, and any later evidence showing actual misuse of your data, usually carry more weight than a general statement made months later.
Causation must be addressed with care. If you were already receiving similar fraudulent messages before the incident, or if the same details were exposed in another way, the link between the attack on this organisation and your loss will be harder to establish. If, on the other hand, a fraudulent message quotes an order number, a membership reference or another detail that only the organisation held, that may support the connection. Keep these messages with their full headers or screenshots and the date of receipt.
A different provision applies to processing that falls outside the UK GDPR. Section 169 gives a person who suffers damage by reason of a contravention of a requirement of the data protection legislation, other than the UK GDPR, a right to compensation from the controller or the processor. It covers, for example, processing under Part 3 of the Act, which section 29 applies to the processing of personal data by a competent authority, a term defined in section 30. For claims under section 169, the section states that damage includes financial loss and damage not involving financial loss, such as distress. It provides that a controller involved in processing is liable for any damage caused by the processing, while a processor is liable only if it failed to comply with obligations specifically directed at processors or acted outside or contrary to the controller’s lawful instructions. A controller or processor escapes liability if it proves that it is not in any way responsible for the event giving rise to the damage. Readers should first identify which regime applies to the records concerned, because a claim against a retailer and a claim concerning data held by a competent authority under Part 3 do not rest on the same provision.
Several questions remain outside the scope of this guide. It does not set out the rules on refunds of unauthorised bank payments, which belong to separate payment rules, nor the time limits for bringing a civil claim. Both points should be checked early, because they may determine what can still be recovered and how quickly a claim must be started.
B. Choose the court route, compliance orders and collective representation
When the complaint routes do not resolve the matter, the courts decide claims for compensation and for compliance orders. Section 180 determines which courts have jurisdiction. The jurisdiction conferred by sections 167, 168 and 169, and by Articles 79 and 82 of the UK GDPR, is exercisable in England and Wales by the county court or by the superior civil court named in that section. In Northern Ireland, it is exercisable by a county court or by the superior court named in the section. In Scotland, it is exercisable by the sheriff or by the senior civil court named in the section. Where the processing falls under Part 4 of the Act, which section 82 applies to processing by an intelligence service and, where a designation notice is in force, to certain processing by a qualifying competent authority, only the superior courts named in section 180 may hear the case. For a claim arising from a breach at a retailer, an employer or an online service, both levels of court have jurisdiction under the section. Which one is appropriate, the procedure to follow and the costs exposure depend on the rules of court of the relevant part of the United Kingdom, which should be checked before any claim is issued.
Compensation is not the only remedy a court can grant. Under section 167, if a court is satisfied, on an application by a data subject, that there has been an infringement of the data subject’s rights under the data protection legislation, it may make a compliance order. The order may require the controller, or a processor acting on its behalf, to take steps specified in the order or to refrain from taking specified steps, and it may set the time or period within which each step must be taken. The section states that an application by a data subject includes one made in exercise of the right in Article 79(1) of the UK GDPR, described in the Act as the right to an effective remedy against a controller or processor. For this power, the data protection legislation does not include Part 4 of the Act or regulations made under that Part.
A compliance order can be useful where the problem is ongoing rather than purely historical. Examples might include a refusal to give clear information to the person affected, or the continued retention of data that should no longer be held. The order addresses future conduct. A claim for compensation addresses the damage already suffered. Both can be considered together, and the exchanges under section 164A will often show which of the two, or both, the facts justify.
Large incidents raise the question of collective claims. Section 168 deals with proceedings under Article 82 brought by a representative body on behalf of a person in accordance with rules of court. Where a court orders the payment of compensation in such proceedings, it may order that the compensation be paid on behalf of the person to the representative body or to such other person as it thinks fit. Section 187 defines a representative body as a body or organisation authorised to exercise the data subject’s right on his or her behalf, and it sets the conditions described in Part I: a not-for-profit structure, public interest objectives and activity in the protection of personal data. Before authorising a body, read its terms carefully. Check what it will do on your behalf, whether it pursues a complaint, a compensation claim or both, and how any compensation would reach you.
A hypothetical timeline shows how these steps fit together. A customer of an online shop receives a notice saying that names, addresses and order histories were accessed. Two weeks later, the customer receives a convincing message quoting a real order number and asking for card details. The customer reports the message, keeps a screenshot and complains to the shop through its complaint form, asking which data relating to the customer was affected and what the shop has done. The shop must acknowledge the complaint within 30 days and then, without undue delay, respond and inform the customer of the outcome. If the reply is vague, the customer complains to the Commission, attaching the exchange. If three months pass without information on progress or outcome, the customer may apply to the Tribunal for an order under section 166. If the customer suffered a loss, such as money taken through the fraudulent message, or significant distress, the customer can consider a compensation claim before the county court or, in Scotland, the sheriff. That claim will rest on showing a contravention by the shop and the damage it caused. The criminal investigation into the attacker, if any, continues separately.
Readers in France or elsewhere in Europe sometimes compare this sequence with the rules they know. The UK system now rests on its own revised texts, with a direct complaint to the controller and a regulator constituted as a body corporate. This overview of UK data protection remedies is written from the perspective of a law firm in Paris as general information on foreign law. It does not replace advice from a lawyer qualified in the relevant part of the United Kingdom on a specific file.
Two practical points close this part. First, keep the exchanges in writing and in order. A clear sequence of notice, complaint, acknowledgement, answer, regulator complaint and response is easier to evaluate than a series of telephone calls. Second, separate the claims. A dispute with your bank about an unauthorised payment, a complaint to the organisation that held your data and a report to the police follow different rules and involve different parties. Mixing them in a single letter usually delays all three.
Conclusion
After a cyberattack, the law treats the attacker and the organisation that held your data separately. The attacker may have committed the offence of unauthorised access under the Computer Misuse Act 1990. The organisation is assessed under the UK GDPR and the Data Protection Act 2018, and that is where a person whose data was exposed has direct rights.
Since 19 June 2026, the first step is a written complaint to the controller, which must acknowledge it within 30 days, look into it, keep you informed and tell you the outcome. If that route fails, a complaint can go to the Information Commission, and the Tribunal can order the Commission to act or to report on progress when it has not done so within the three-month periods set by section 166. Compensation is a separate route before the courts. It requires a contravention by the organisation and damage caused by it, and distress counts as damage. Courts can also order an organisation to take, or to refrain from taking, specified steps, and qualifying not-for-profit bodies can act on behalf of affected people who authorise them.
The strongest position comes from a precise and dated record: the notice, the data affected, the complaint, the replies and the consequences. That record allows each route to be used at the right time and keeps the question of the organisation’s responsibility separate from the criminal case against the attacker.