Skip to main content

Free guides to the law for parish, town and community councils

Guides for: Wales

We remember this choice with one cookie on this device, and use it for nothing else. Forget my choice

The council has lost or wrongly shared personal information. Whom do we have to tell, and how quickly?

England and Wales. Last checked against the source on .

The council must report the breach to the Information Commission, the data protection regulator, without undue delay and, where feasible, within 72 hours of becoming aware of it, unless the breach is unlikely to result in a risk to people's rights and freedoms. If the breach is likely to result in a high risk to people's rights and freedoms, the council must also tell the people whose information it is, without undue delay, unless one of the exceptions below applies. Whether or not it reports the breach, it must keep a record of it.

  • The 72 hours run through weekends and bank and public holidays. To be safe, count them from the moment the council became aware of the breach.
  • A report made after 72 hours must give the reasons for the delay.
  • A person or organisation that handles personal information on the council's behalf must tell the council without undue delay after becoming aware of a breach.

Applies to: Every parish and town council in England and every community and town council in Wales, for the personal information it is the "controller" of: the body that decides why and how the information is used, or that the law requires to use it.

What counts as a breach

The law defines a personal data breach 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". Personal data is any information about a person who can be identified from it, directly or indirectly, for example by their name.

So a breach can be an accident or something unlawful. It can be information lost, destroyed or changed, as well as information passed to, or got at by, someone who should not have it. Read plainly, the definition takes in, for example, residents' details emailed to the wrong address, a lost laptop or paper file, or someone getting into a council email account without permission.

Paper records count as well as computer records. That includes papers kept in a filing system and, because a parish or community council is a public authority under the Freedom of Information Act 2000, papers that are not filed in any order.

There is one narrow exception. The duties on this page do not apply to papers that are not on a computer and are not kept, or meant to be kept, in a structured filing system, if they are about the appointment, removal, pay, discipline, pension or other personnel matters of people who hold an office in, work for or work under contract for a public body, such as the council's own staff and contractors. The exact terms are in section 24 of the Data Protection Act 2018.

Telling the Information Commission

When. The report must be made "without undue delay and, where feasible, not later than 72 hours after having become aware of it". The rules on reporting do not say when meeting the 72 hours is not feasible, so treat them as the limit, not a target. A report made after 72 hours must give the reasons for the delay, and must still be made without undue delay.

These rules do not say at what point a council counts as having become aware of a breach. The safe course is to start counting as soon as the council knows that personal information has been lost or wrongly shared, and not to wait until it has finished finding out what happened: the details can follow in stages, as below.

Counting the 72 hours. The UK GDPR, the set of rules these duties come from, counts time by rules made in 1971. Under them:

For example, a council that becomes aware of a breach at 4.20pm on a Friday should treat 4.20pm on the Monday as the limit. Strictly, the clock hour in which the council became aware is not counted, so the 72 hours start when that hour ends and run until 5pm on the Monday, but there is no need to rely on that. If the clocks go back that weekend, take an hour off each of these times, so treat 3.20pm on the Monday as the limit. The same rules say that a period of two days or more must include at least two working days. They do not make clear whether that applies to a period counted in hours, like this one, so do not rely on it to give you more time.

When no report is needed. Only where the breach is unlikely to result in a risk to people's rights and freedoms. The question is whether a risk is unlikely, not whether harm has already been done. The rules on reporting do not define a risk or a high risk. The UK GDPR opens with numbered paragraphs, called recitals, that explain its rules. On this point they say:

What the report must contain. At least:

A council with no data protection officer gives another contact point. See Does a parish council need a data protection officer? and Can the clerk be the council's data protection officer?

If not everything is known yet. If the council cannot give all of this at once, it may give what it can now and the rest in stages "without undue further delay".

How to report. The rules on reporting do not say how a report is made, or who in the council makes it. The regulator's page on reporting a breach says that a report can be made online, and points to a self-assessment tool to help decide whether to report.

The regulator's name. The Information Commission replaced the Information Commissioner on 30 September 2026 and took over its work. Anything done with the Commissioner before then, such as a report already made, carries on with the Commission. The regulator's website still uses the name ICO.

Telling the people affected

When. Where the breach is likely to result in a high risk to people's rights and freedoms, the council must tell the people whose information it is, without undue delay. A high risk is a higher test than the one for reporting to the Commission, so a breach can need reporting without anyone needing to be told. No number of hours is set. The recitals say the purpose is to let people "take the necessary precautions", and that they should be told "as soon as reasonably feasible". They add that this should be done in close cooperation with the Commission, and that an immediate risk calls for a prompt warning, while the need to stop a breach that is still going on may justify more time.

What to tell them. In "clear and plain language", tell them:

The council must take appropriate steps to make the message concise, clear, easy to understand and easy to get at. It can be given in writing or in other ways, including electronically where appropriate, and it is free of charge. The recitals add that it should advise people how to limit the harm the breach may do them.

When people need not be told. The council does not have to tell them if any one of these applies:

If the council has not told the people affected, the Commission may consider how likely a high risk is. It may then require the council to tell them, or decide that one of these three exceptions applies.

Other exemptions. The Data Protection Act 2018 also removes the duty to tell people, and the Commission's power to require it, in a few other cases. One is information used to prevent, investigate or detect crime, to catch or prosecute offenders, or to assess or collect a tax or duty, so far as telling people would be likely to prejudice any of those. Two others, in Schedule 2 to the Act, are for Parliament's privileges and for journalism and academic, artistic or literary work, on conditions set out there. None of these three removes the duty to report the breach to the Commission or to keep a record of it. A separate exemption for national security and defence, in section 26 of the Act, can remove the duties to report the breach and to keep a record of it as well.

The record of every breach

The council must record every personal data breach: the facts of it, its effects and what was done to put it right. The record must be enough for the Commission to check that the council kept to the rules on reporting.

The record covers every breach, including one the council decided it did not have to report. The rule does not say in so many words that the record should give the reason a breach was not reported. But the record must let the Commission check the council's decisions, so it is the place to note that reason. The rule sets no form for the record and no time for keeping it.

If someone else handles the information for the council

A "processor" is a person or body that handles personal information on the council's behalf: depending on the arrangement, a firm, or another council, that runs the council's payroll, for example.

What this page does not cover

Source

Everything else was read as revised. The official website lists no outstanding changes for the UK GDPR articles and recitals, the 1971 Regulation, the 2025 Act's sections or the 2000 Act's provisions. For the Data Protection Act 2018 it lists one change not yet applied, to a paragraph of Schedule 3 that this page does not rely on. It holds the two 2026 instruments only as made.

Last checked against the source on 14 November 2026.