Other people
Third party names in a disclosure
Before removing a named individual, put three questions to yourself in sequence, and note the answer even when you decide to release the name.
Last reviewed against Information Commissioner's Office, GOV.UK and DLA Piper. Sources
Three questions
In this order
-
1
Can you comply without identifying them? Look at what the requester already holds or could reach, and whether names can simply be removed [1]. -
2
Have they consented? If so, release the data. Asking is optional, and the ICO lists situations where it would be wrong to ask [1]. -
3
Is release reasonable without consent? Weigh the circumstances, among them the type of information, any duty of confidence and any refusal [1].
Factors
What pushes towards disclosure
Already known
If the requester has seen the material before, or it can be found in public, release is easier to justify [1].
Staff in their role
A staff member acting in their duties, and well known to the requester, is a likelier candidate for disclosure than an anonymous individual [1].
Importance to the requester
The other person's confidentiality is balanced against the requester's right of access [1].
Confidentiality
A label is not enough
A "Confidential" stamp does not by itself create a duty of confidence, and widely available information may not have the necessary quality of confidence [1]. Where a genuine duty exists, withholding without consent is usually reasonable [1].
Always respond
A reply is owed whether or not you release third party data, and it should include as much of the requested material as you can give without revealing the other person [1].

Keep reading
Read next
Undoing redaction
Why a blacked-out file can still reveal text, what the ICO advises on saving new files and checking paper, and how to test before release.
Read the guide
Failures
Two UK disclosure failures the ICO reprimanded, Birmingham Children's Trust and Southend-on-Sea council, and what each teaches.
Read the guide
Deadlines
How redaction fits inside the one month response deadline: extensions, stopping the clock, searches and how to plan review time.
Read the guideHow CyPro can help
Need a hand getting ready?
Reading the rules is one job. Mapping them to your organisation, closing the gaps and showing the evidence are several more. CyPro's consultants can take any of them off your plate.
Fractional CISO for the board
A senior security lead who advises the board on what to fix first, what to accept and what to tell customers, and owns the decision record.
More on cypro.co.uk
Penetration testing
A focused test of your systems and the controls around them, so you know they hold before an attacker finds out for you.
More on cypro.co.uk
Hardening and segmentation
Our consultants put the controls in place that limit the damage when something is missed: firewall rules, network isolation and tighter admin access.
More on cypro.co.uk
24/7 security monitoring
Our SOC analysts watch your systems day and night for the signs of an attack in progress: unexpected processes, new outbound connections, logins that do not fit.
More on cypro.co.uk
Incident response
If you may already be compromised, our responders contain it, preserve the evidence, find out what was touched and get you running again safely.
More on cypro.co.uk
Vulnerability scanning
Find every internet-facing system you run, including the forgotten ones, and see which are still on a vulnerable build.
See the scanning service
Get ready
Need to know what this means for you?
A disclosure that leaks, or a redaction you cannot explain, becomes a complaint to the ICO. A GDPR consultant can review your disclosure workflow, exemption log and release checks before a request tests them.