Redacting documents for Freedom of Information requests: third parties' personal data

A journalist asks a council for all correspondence about a disputed planning enforcement case. The search turns up 140 emails, two officer reports, a spreadsheet of site visits and a scanned letter from a neighbour. The information officer has 20 working days, and almost every page mixes material the public is entitled to see with personal data about residents, complainants and junior staff. Release everything and you breach data protection law; withhold everything and you breach the Freedom of Information Act.
This guide explains how the law treats third parties' personal data in an FOI or EIR response in the UK, how to decide what comes out, and how to redact so that what you remove is really gone. It complements our articles on subject access requests and on publishing council minutes.
The legal framework: section 40 and regulation 13
The Freedom of Information Act 2000 gives anyone a right to information held by public authorities, subject to exemptions. Personal data is dealt with in section 40, which works in two halves. If the requester asks for their own personal data, section 40(1) exempts it from FOI altogether: the request should be handled as a subject access request under the UK GDPR instead. If the information is about someone else, section 40(2) applies, and it is exempt when one of three conditions is met.
- First condition: disclosure to a member of the public would contravene the data protection principles in Article 5(1) of the UK GDPR. This is the condition used in most cases, and it is absolute: there is no public interest test.
- Second condition: disclosure would contravene an objection the individual has made under Article 21 of the UK GDPR.
- Third condition: the individual could not get the information themselves through a subject access request, because a Data Protection Act 2018 exemption would apply.
- The second and third conditions are qualified: you must also weigh the public interest. Section 40 also allows you to neither confirm nor deny that information is held where confirming would itself reveal something about a person.
For environmental information, such as planning, pollution, land use or waste, the request falls under the Environmental Information Regulations 2004. Regulation 13 mirrors section 40 with the same three conditions, and the first one is again applied without a public interest test. In Scotland, devolved authorities answer under the Freedom of Information (Scotland) Act 2002, where personal information is covered by section 38, and under the Scottish EIR; the reasoning is similar, but follow the Scottish Information Commissioner's guidance rather than assuming the two regimes are identical.
Disclosure is to the world, not to the requester
The ICO stresses that an FOI or EIR disclosure is treated as a disclosure to the world at large. Who is asking, and why, is generally irrelevant, and the requester is under no duty of confidence afterwards. A useful test for every name on the page is: would we be comfortable publishing this on our website?
The lawfulness test in three steps
According to the ICO, the principle most likely to be breached is lawfulness, fairness and transparency (Article 5(1)(a)). The lawful basis normally examined in an FOI context is legitimate interests, which the ICO breaks down into three questions asked in order. If one fails, you stop there.
1. Legitimate interest
Is the requester, or the public, pursuing a legitimate interest in this personal data? Accountability for public spending or decisions usually qualifies; idle curiosity carries little weight.
2. Necessity
Is disclosing this person's data the least intrusive way to meet that interest? Often a job title, a team or an aggregate figure serves the purpose just as well as a name.
3. Balancing
Do the legitimate interests outweigh the individual's rights? Consider possible harm, what is already public, any objection and what the person would reasonably expect.
Special category data (health, ethnicity, sexual life and so on) and criminal offence data need an extra condition on top. The ICO notes that, in practice, only explicit consent or information the person has manifestly made public are likely to be relevant, so this kind of data is very rarely disclosable under FOI.
Who usually stays visible and who is redacted
There is no fixed list, but the ICO's guidance points to the factors that matter most for staff: seniority, whether the role is public-facing, responsibility for spending public money and whether the information is about their work or their private life. The table summarises common outcomes; each request still needs its own judgement.
| Who or what | Example (fictitious) | Usual treatment |
|---|---|---|
| Senior officials acting in role | Director of Place approves enforcement action | Name and role usually disclosed |
| Elected members in their public capacity | Ward councillor emails the planning team | Usually disclosed; private matters redacted |
| Junior or non-public-facing staff | Planning support officer, direct line | Name and contact details often redacted; job title or team kept |
| Members of the public | Neighbour who complained, home address | Usually redacted, including details that point to them |
| Health or allegations of offences | “Mr B. has been unwell since…” | Almost always withheld |
| Signatures, mobiles, personal emails | Handwritten signature on a scanned letter | Redacted, even for senior staff |
Remember that section 40 applies to information, not documents. If a report contains one paragraph about a resident's circumstances, you redact that paragraph and release the rest. Withholding a whole document because it mentions people is rarely defensible. Redactions are a partial refusal, so the response letter should cite the exemption relied on (section 40(2) or regulation 13) and explain it, as a refusal notice requires.
A practical workflow for the 20 working days
1. Log, locate and scope
Record the date of receipt and the deadline: 20 working days under section 10 of FOIA, and the same under regulation 5 of the EIR, where regulation 7 allows an extension to 40 working days for complex and voluminous requests. Decide early whether the request is FOI or EIR, and whether part of it is really the requester's own data.
2. Map the personal data
Before anyone redacts, list the categories of people in the bundle: officials, members, residents, contractors. Do not forget email headers, signatures, attachments, comments and spreadsheet tabs. A neighbour can be identified by a house number or a description of their car as easily as by a name.
3. Decide per category and write it down
Apply the three-step test once per category of person rather than per page, and record the outcome in a short decision note. That note drives consistent redaction across 140 emails and is what you will rely on if the requester asks for an internal review or complains to the ICO.
4. Redact for real
Use a method that deletes the underlying content, not one that draws a shape on top. Then remove the PDF metadata, flatten the file and, for scans, make sure the OCR text layer has been redacted too. Our article on PDF redaction mistakes covers the technical traps in detail.
5. Second-person check and release
A colleague who did not do the redaction opens the final files, searches for the names in the decision note, copies a few redacted areas into a text editor and checks every worksheet. Only then is the response sent, ideally in the same format you would use for publication in your disclosure log.
The redaction failures that make the headlines
The best-known UK example is the Police Service of Northern Ireland. In August 2023, a spreadsheet published in response to an FOI request contained a hidden worksheet with the surname, initials, rank and role of every officer and member of staff. The ICO fined the force, and in 2025 it published new guidance on disclosing documents to the public securely. The recurring failures are well documented:
- Hidden worksheets, rows, columns and filters in spreadsheets, and source data behind pivot tables.
- Overlay boxes or black highlighting in PDFs, with the text still there to copy and paste.
- Metadata, comments and tracked changes in Word files, and author names in document properties.
- The OCR text layer of scanned letters, which keeps the words even when the image is covered.
- Inconsistent redaction: a name removed in the body but left in a quoted reply further down the thread.
- Re-identification by context: small numbers, unusual job titles or a street name that point to one person.
Before an FOI or EIR response goes out
- Exemption cited (section 40(2) or regulation 13) and explained in the response letter.
- Decision note completed for each category of person in the bundle.
- Every worksheet, hidden row, column and filter checked; spreadsheets converted to a simpler format where possible.
- Redactions remove the content; nothing comes back with copy and paste or a text search.
- Metadata, comments, tracked changes and file names cleaned.
- Scanned pages checked for a hidden text layer.
- Second-person check done and the unredacted set kept separately with restricted access.
How Anonimatum helps with FOI redaction
Anonimatum detects names, addresses, phone numbers, email addresses and identifiers with its own AI running on EU servers, and you can add patterns for your own formats, such as case or staff reference numbers. A whitelist keeps senior officials and members visible while everyone else is hidden, and a saved template applies the same decision note to the whole bundle, in batches. OCR runs only on the pages that are scanned, signatures and stamps can be covered with zones or shapes through visual anonymisation, and every match is shown in a preview for human review before anything is applied. The redacted text is genuinely removed from the output rather than covered, metadata can be stripped, and Word, Excel and PowerPoint files are processed in their own format. It does not replace your judgement on what the law requires, nor the final check of hidden worksheets and context: it makes the mechanical part faster and consistent.
See how GDPR redaction works on your own documents, from detection to a clean file.
Explore document redactionFrequently asked questions
Can we refuse a whole document because it contains names?
Rarely. Section 40 and regulation 13 apply to the personal data, not to the document. The usual approach is to redact the exempt personal data and release the rest, citing the exemption in the response.
Should we disclose the names of our staff?
It depends on seniority, whether the role is public-facing and what the information is about. Senior officials acting in their role are often named; junior staff are often replaced with a job title or team. Record the reasoning for each category.
What if the requester asks for information about themselves?
Their own personal data is exempt under section 40(1) of FOIA (regulation 5(3) of the EIR excludes it in the same way). Handle that part as a subject access request under the UK GDPR, with its own deadline and exemptions.
Is there a public interest test for third-party personal data?
Not under the first condition, which is the one used most often: if disclosure would breach the data protection principles, the exemption is absolute. The second and third conditions do involve a public interest test.
Does the same apply in Scotland?
Scottish public authorities apply the Freedom of Information (Scotland) Act 2002, where section 38 covers personal information, and the Scottish EIR. The logic is similar, but follow the Scottish Information Commissioner's guidance.
Sources and legislation
- Freedom of Information Act 2000, section 40
- Environmental Information Regulations 2004, regulation 13
- ICO: Section 40 and regulation 13 – personal information
- ICO: Disclosing documents to the public securely
- ICO: PSNI facing a £750k fine following spreadsheet error (May 2024)
- Freedom of Information (Scotland) Act 2002, section 38
