Alex Morgan’s data subject access request is still open. Lesson 1 took the appraisal to a proposed disclosure and left one record unresolved: a witness account from an internal investigation. This lesson takes that record to a proposed disclosure and a decision record, applying the third-party test line by line.
The worked example
The account is paragraph 1 of investigation note I-022, written up by the HR investigator after an interview. It reads: “I was the only supervisor on the night shift. At 21:10 on 3 October I saw Alex Morgan leave the server room carrying a laptop bag. Please keep my name out of this. I am worried Alex will find out I reported it.” The witness’s name appears above the paragraph. The example states three facts: Alex knows an investigation took place; the rota for that night shift is posted on the team noticeboard and shows one supervisor and four other staff; and the investigator told the witness that their name would not be passed to Alex unless the law required it. Change those facts and the result changes.
Whose information it is
The sighting is about Alex: where Alex was, when, and what Alex was carrying. It is an allegation Alex may need to answer, so Alex’s interest in receiving it is strong. What a colleague says about the requester is generally the requester’s personal data, even when the colleague’s identity is not. The witness’s name is information about the witness, and so are the request for confidentiality and the worry about retaliation. The statute adds a point that matters in every investigation file: identifying the witness as the source of the account is itself information relating to the witness (Data Protection Act 2018, Schedule 2, paragraph 16). The paragraph is mixed data. The answer to mixed data is not to withhold the paragraph; it is to apply the third-party test line by line and write down how it was applied.
The identification problem
Removing the name is the obvious first step, and on its own it may protect nobody. The statute asks whether the other individual can be identified from the information together with other information the requester is likely to possess or obtain. Alex has the rota, and the rota names one supervisor for that night. A redacted name next to the words “only supervisor on the night shift” identifies the witness as surely as the name did. The redaction has to reach the context, or the passage has to be withheld.
Once the name and the role descriptor are gone, what remains is the sighting: “At 21:10 on 3 October I saw Alex Morgan leave the server room carrying a laptop bag.” Alex can infer that one of five people on that shift said it. The reviewer records that five possible people is not identification on these facts, and records the reasoning, because another reviewer may weigh it differently.
The balance
Under paragraph 16 the controller is not obliged to disclose information relating to another identifiable individual unless that person consents or disclosure without consent is reasonable. The reviewer works through the factors the statute lists and records an answer to each. The type of information is an allegation about the requester, which weighs toward Alex receiving the substance. The investigator’s assurance brings confidentiality into the balance; it weighs, it does not decide, and the ICO’s guidance notes that a confidential label does not by itself create a duty. Consent was sought on 10 November and the witness, who is capable of giving it, declined in writing on 12 November, an express refusal.
The factors point in two directions. They support giving Alex the substance of the account and protecting the identity of the person who gave it. They do not support releasing the name, the role descriptor, or the witness’s own words about confidentiality and retaliation.
Redact, summarise or withhold
Three treatments are available for the paragraph: disclose it as written, redact the identifying words and disclose the rest, or withhold the passage. Lesson 1 floated a fourth, a summary in the reviewer’s words. A summary changes the form of the source and needs its own checks for accuracy and meaning, and a later reviewer cannot easily compare it with the original. Where redacting the original gives the same protection, redaction keeps the witness’s words intact for Alex, which matters when the words are an allegation.
The proposed output is R-022. It carries the sighting with the date, the time and the laptop bag retained. The name and the role descriptor are redacted. The two sentences about confidentiality and retaliation are withheld as the witness’s own information. The original note stays intact in the case record.
The decision record
| Source → output | I-022 paragraph 1 → R-022 paragraph 1, version 1 |
|---|---|
| Treatment | Name and role descriptor redacted. The two confidentiality sentences withheld as the witness’s own information. The sighting retained with date, time and the laptop bag. |
| Reason | Schedule 2 paragraph 16 balance: an allegation about the requester; an assurance given at interview; consent sought; capable of consent; express refusal. |
| Consent history | Asked 10 November 2026; declined in writing 12 November 2026. |
| Identification check | Rota for 3 October shows one supervisor and four other staff. Five possible people is not identification on these facts; reasoning recorded. |
| Reviewer · date · version | RV-02 · 18 November 2026 · R-022 v1 (example values) |
The open item from Lesson 1 closes with an outcome, and the case record shows the path from the unresolved question to the decision.
Checking the package
A redaction that works in one file can fail in the bundle. This case also holds the interview schedule, which lists who was interviewed and when, and an email from HR thanking the witness for coming forward. Either file, released as written, identifies the witness that R-022 protects. The proposed files are read together, as Alex would receive them. Every record that names the witness as a source needs a treatment consistent with R-022, and the decision record points to each of them. Where the review protects an identity, the inference created by the whole package is the test.
The response to Alex still has to account for the information that was withheld, in terms the organisation can justify. That is the response letter, and it is a later lesson.
Watch the lesson by chapter
- 00:00 The witness record
- 01:39 Whose information it is
- 02:42 The identification problem
- 03:57 The balance
- 05:19 Redact, summarise or withhold
- 06:32 Recording the decision
- 07:35 Checking the package
- 08:49 The outcome and next step
Frequently asked questions
Does an employee receive what a witness said about them in a DSAR?
Generally yes, as to the substance. What a colleague or witness says about the requester is the requester’s personal data. The witness’s identity is a separate question: paragraph 16 of Schedule 2 to the Data Protection Act 2018 says the controller is not obliged to disclose information relating to another identifiable individual unless that person consents or it is reasonable to disclose without consent, and the statute treats identifying the witness as the source of the information as information relating to the witness. In the worked example the substance of the sighting goes to the requester and the identity is protected.
Is redacting the witness’s name enough?
Often not. The statute asks whether the other individual can be identified from the information together with other information the requester is likely to possess or obtain. A unique role descriptor next to a redacted name, read against a rota the requester can see, identifies the witness as surely as the name did. The redaction has to reach the identifying context, or the passage has to be withheld. The lesson records the residual identification check and its basis, in this case the rota count of five people on the shift.
Does a promise of confidentiality to the witness decide the question?
No. An assurance given to a witness weighs in the paragraph 16 balance as a duty of confidentiality, together with the type of information, the steps taken to seek consent, whether the witness can consent, and any express refusal. It does not decide the question on its own, and the ICO’s guidance adds that marking a document confidential does not by itself create a duty of confidence.
Should we summarise the statement instead of redacting it?
Redaction of the original is usually the better route where it gives the same protection. A summary changes the form of the source, needs its own checks for accuracy and meaning, and is harder for a later reviewer to compare against the original. When the words are an allegation the requester may need to answer, keeping the witness’s words intact matters.
What goes in the decision record for a witness statement?
The source and output references, the treatment of each part of the statement, the reason tied to the paragraph 16 factors, the consent history with dates, the residual identification check with its basis, and the reviewer identifier, date and output version. The record also points to every other file in the bundle that names the witness as a source, so the treatment stays consistent across the response.
Which other files can give the witness away?
Any record that lists who was interviewed, such as an interview schedule, and any correspondence with the witness about the investigation, such as an email thanking them for coming forward. A redaction that works in one file fails if another file in the same response identifies the person. The proposed files are read together, as the requester would receive them, and the inference created by the whole package is the test.
Transcript
00:00 The witness record
Alex Morgan's data subject access request, a D-S-A-R under UK GDPR, is still open. The first lesson left one record unresolved. This lesson takes that record, a witness account from an internal investigation, to a proposed disclosure and a decision record. The account is paragraph one of investigation note I-022, written up by the HR investigator after an interview. It reads: "I was the only supervisor on the night shift. At 21:10 on 3 October I saw Alex Morgan leave the server room carrying a laptop bag. Please keep my name out of this. I am worried Alex will find out I reported it." The witness's name appears above the paragraph. The example states three facts. Alex knows an investigation took place. The rota for that night shift is posted on the team noticeboard and shows one supervisor and four other staff. The investigator told the witness that their name would not be passed to Alex unless the law required it. Change those facts and the result changes.
01:39 Whose information it is
Begin by identifying the information about Alex. The sighting is about Alex. It is an allegation Alex may need to answer, so Alex's interest in receiving it is strong. What a colleague says about the requester is generally the requester's personal data, even when the colleague's identity is not. The witness's name is information about the witness. So are the request for confidentiality and the worry about retaliation. The statute adds a point that matters in every investigation file: identifying the witness as the source of the account is itself information relating to the witness. The paragraph is mixed data. The answer to mixed data is not to withhold the paragraph. It is to apply the third-party test line by line and write down how it was applied.
02:42 The identification problem
Removing the name is the obvious first step, and on its own it may protect nobody. The statute asks whether the other individual can be identified from the information together with other information the requester is likely to possess or obtain. Alex has the rota, and the rota names one supervisor for that night. A redacted name next to the words "only supervisor on the night shift" identifies the witness as surely as the name did. The redaction has to reach the context, or the passage has to be withheld. Now test what remains once the name and the role descriptor are gone: "At 21:10 on 3 October I saw Alex Morgan leave the server room carrying a laptop bag." Alex can infer that one of five people on that shift said it. The reviewer records that five possible people is not identification on these facts, and records the reasoning.
03:57 The balance
Under paragraph 16 of Schedule 2 to the Data Protection Act 2018, the controller is not obliged to disclose information relating to another identifiable individual unless that person consents or disclosure without consent is reasonable. The reviewer works through the factors the statute lists and records an answer to each. The type of information is an allegation about the requester, which weighs toward Alex receiving the substance. The investigator's assurance brings confidentiality into the balance; it weighs, it does not decide, and a confidential label does not by itself create a duty. Consent was sought on 10 November and the witness declined in writing on 12 November, an express refusal. The factors point in two directions. They support giving Alex the substance of the account and protecting the identity of the person who gave it. They do not support releasing the name, the role descriptor, or the witness's own words about confidentiality and retaliation.
05:19 Redact, summarise or withhold
Three treatments are available. Disclose the paragraph as written. Redact the identifying words and disclose the rest. Withhold the passage. The first lesson floated a fourth, a summary in the reviewer's words: an account reports seeing Alex leave the room at 21:10. A summary changes the form of the source and needs its own checks for accuracy and meaning. Where redacting the original gives the same protection, redaction keeps the witness's words intact for Alex, which matters when the words are an allegation. The proposed output is R-022. It carries the sighting with the date, the time and the laptop bag retained. The name and the role descriptor are redacted. The two sentences about confidentiality and retaliation are withheld as the witness's own information. The original note stays intact in the case record.
06:32 Recording the decision
The decision record follows the appraisal's pattern. It names source I-022, paragraph one, and output R-022, version one. It states the treatment and the reason: the paragraph 16 balance, with the type of information, the assurance, the consent request and the refusal. Two entries get their own lines. One is the residual identification check with its basis, the rota count of five. The other is the consent history, asked on 10 November and declined in writing on 12 November. Add the reviewer identifier, the date and the output version: RV-02, 18 November 2026, version one. The open item from the first lesson closes with an outcome.
07:35 Checking the package
A redaction that works in one file can fail in the bundle. This case also holds the interview schedule, which lists who was interviewed and when, and an email from HR thanking the witness for coming forward. Either file, released as written, identifies the witness that R-022 protects. Read the proposed files together, as Alex would receive them. Every record that names the witness as a source needs a treatment consistent with R-022. The inference created by the whole package is the test. In SafeRedact, DSAR mode lets the reviewer name Alex as the data subject whose information should be preserved while other individuals' personal information is flagged for redaction across every file in the case. Each flag is reviewed by a person before anything is exported, and the review decision log records what was decided and why.
08:49 The outcome and next step
The witness record now has a proposed disclosure and an explanation another reviewer can follow. Alex receives the substance of what was said about them. The person who said it is protected on the stated facts. The response to Alex still has to account for the information that was withheld. That is the response letter, and it is a later lesson. The sources for this lesson and information about SafeRedact are in the description.
How SafeRedact Fits
SafeRedact is browser-based redaction software for data subject access requests. Files never leave your browser: documents are processed client-side, only extracted text and the case's data subject details are sent for AI detection, and no documents are stored on servers. Detection text is never used for training and is deleted within 30 days. You name the data subject whose information should be preserved, and other individuals' personal information is flagged for redaction across every file in the case, including ZIP and Purview PST exports. Every detection is reviewed by a human before anything is exported, and the export package includes the redacted files, a processing summary, an audit trail and a review decision log. Supported formats: PST, PDF, DOCX, XLSX, EML, MSG, HTML, TXT, CSV, JSON, ZIP. A Data Processing Agreement is available and enterprise cases are priced per case, with the price set with you and shown before you download.
Make Every Redaction Decision Once
AI detection flags every identifier in the case. You decide whose it is, with the requester's data preserved and every decision recorded in the exported audit trail. Cases are priced per case, with a Data Processing Agreement available.
Set up your organisationDSAR: The Complete Guide
DSAR Redaction Guide (Pillar) What Is a DSAR? Employee DSAR Redaction ICO DSAR Guidance DSAR Redaction Mistakes DSAR Response Template DSAR Compliance Checklist Automate DSAR Redaction DSAR Redaction Cost DSAR Software Comparison CCPA DSAR Guide US State Privacy Laws DSAR Cost CalculatorSources
- UK GDPR, Article 15 (right of access)
- Data Protection Act 2018, Schedule 2, paragraph 16 (information about other individuals)
- ICO, Information about other people in a SAR (right of access guidance, 8 December 2025)
- ICO, Supplying information to the requester (31 July 2025)
- ICO guidance is reproduced in summary under the Open Government Licence v3.0
This page is informational, not legal advice; the legislation, ICO guidance, and your counsel govern. The people, organisation and references in the worked example are invented. Miriam is SafeRedact’s virtual narrator; her voice and likeness are generated with AI. The lessons are written and checked by SafeRedact.