Alex Morgan’s data subject access request was received by email on 3 November 2026. The appraisal (Lesson 1), the witness statement (Lesson 2) and the Microsoft 365 export (Lesson 3) have all been through review. What remains is the response: the letter that goes to Alex with the files. This lesson is about what that letter has to contain, and what the organisation keeps afterwards.
The law sets the deadline. The applicable time period is one month from the day the request was received, so the response is due by 3 December. Alex is a current employee who wrote from a work address, so identity was never in doubt and the clock started on day one. Because the request arrived electronically, the response goes back electronically, in a commonly used format, unless Alex asks for something else.
What the letter is for
Article 15 gives Alex three things: confirmation that personal data is being processed, a copy of that data, and a set of supplementary information about the processing. The enclosures carry the data. The letter carries everything else. It confirms the request and the date it was received, states what was searched and that the search was reasonable and proportionate, lists what is enclosed, explains what was redacted or withheld and on what basis, sets out the supplementary information, and tells Alex what to do if they disagree. Article 12 adds the manner: concise, transparent, intelligible, in clear and plain language. A letter that says in ordinary words what was done, and why, passes that test.
The enclosure index
The letter lists what is enclosed, so that Alex can see the response is complete and the organisation can later show what was sent. In this example there are three sets: the appraisal, A-014, with the manager’s private mobile number redacted; the investigation note, I-022, with the witness’s name and the role and shift details that would identify them redacted; and the Microsoft 365 export, the emails from Alex’s own mailbox and others, the files from OneDrive and the HR site, and the Teams transcripts, redacted for other people’s personal data. Each file is named, the count in each set is stated, and the redacted versions are the ones attached. The index is short, and it is the first thing a requester checks against what they expected to receive.
Redactions and withheld items
The letter explains redactions in plain terms without revealing what was removed. Where other people’s personal data has been redacted, the ground is paragraph 16 of Schedule 2 to the Data Protection Act 2018, read with Article 15(4): the right to a copy must not adversely affect the rights and freedoms of others. The letter says that information relating to other individuals has been redacted where it was not reasonable to disclose it without their consent, and that the redaction was limited to that information. It does not name the witness or describe what was removed in a way that identifies them.
If any document had been withheld in full, the letter would say so and name the exemption, for instance legal professional privilege under paragraph 19, or a confidential reference under paragraph 24. Nothing in Alex’s bundle was withheld in full, and the letter says that too. Two documents found in the search were not Alex’s personal data at all, and they are simply not included.
The supplementary information
Article 15(1) lists the information that goes with the data, and the list changed this year. The purposes of the processing. The categories of personal data. The recipients, or categories of recipient, including any outside the UK. The retention period, or the criteria used to decide it. Alex’s rights to rectification, erasure, restriction and objection. Since 19 June 2026, the right to complain to the organisation itself, under section 164A of the 2018 Act. The right to complain to the regulator, which since 30 September 2026 is the Information Commission. Where data was not collected from Alex, the source. And whether any automated decision-making applies, with meaningful information about the logic and the consequences if it does.
For an employee this is usually a page: HR administration, payroll and performance management as purposes; the HR system, payroll provider and pension administrator as recipients; the retention schedule for employment records. The privacy notice can be attached, as long as the answer is specific to Alex.
Timing, format and tone
Three rules on time, all in Article 12A as inserted by the Data (Use and Access) Act 2025. The applicable time period is one month from the relevant time: the day the request was received, or the later day on which identity information was received or a fee was paid. It can be extended by two further months where the complexity or the number of requests requires it, by a notice sent before the first month ends that gives the reasons; the regulator counts the extension as three months from the original start date. And if the organisation needs clarification of what is being asked for, the time between asking and receiving the answer does not count.
None of those applied to Alex. The response is free; a fee or a refusal is available only for a request that is manifestly unfounded or excessive, and the organisation has to be able to show that. On tone, the letter is written to Alex. It says what was found, what was done, and where to go next.
| Request | Alex Morgan, data subject access request, received by email 3 November 2026 |
|---|---|
| Due | 3 December 2026; identity known on receipt; no extension, no clarification |
| Format | Electronic, commonly used format, secure link to the address Alex used |
| Enclosed | Three sets: A-014, I-022, the Microsoft 365 export; index attached; redacted versions only |
| Redactions | Other individuals’ information, Schedule 2 paragraph 16 with Article 15(4); schedule kept internally |
| Withheld | None in full; two documents out of scope and not included |
| Supplementary information | Article 15(1)(a) to (h), one page, including the section 164A and Information Commission routes |
| Record kept | Letter, index, redaction schedule, IT search note, audit trail, review decision log, delivery confirmation |
Checking before sending
Before the letter goes, four checks by a second person. The attachments are the redacted exports, with metadata stripped, and every file in the index is present. The redactions in the files match the redaction schedule, document by document. The letter’s supplementary information is specific to Alex. And the delivery route is secure: an encrypted email or a secure download, sent to the address Alex used.
Then the record. The organisation keeps the letter, the enclosure index, the redaction schedule with the ground for each decision, the search note from IT, the audit trail and the review decision log from the redaction tool, and the delivery confirmation. If Alex complains to the organisation, section 164A gives it 30 days to acknowledge and a duty to investigate, and the answer is written from that record. If Alex goes to the Information Commission, the same record is what it will ask for.
The outcome and next step
The response to Alex is the letter, the index, the redacted files and the supplementary information, sent within the month, with a record behind every line of it. The next lesson goes back into the bundle, to the manager’s email thread: messages about Alex, messages copied to Alex, and messages where Alex is one name among many, and how the review decides what each one is. A fill-in version of the letter is on the DSAR response letter template page.
Watch the lesson by chapter
- 00:00 The last step
- 01:13 What the letter is for
- 02:21 The enclosure index
- 03:26 Redactions and withheld items
- 04:56 The supplementary information
- 06:35 Timing, format and tone
- 07:54 Checking before sending
- 09:05 The outcome and next step
Frequently asked questions
What must a DSAR response letter contain?
Article 15 gives the requester three things: confirmation that their personal data is being processed, a copy of that data, and the supplementary information in Article 15(1)(a) to (h). The enclosures carry the data; the letter confirms the request and its date, states what was searched and that the search was reasonable and proportionate, lists what is enclosed, explains what was redacted or withheld and on what basis, sets out the supplementary information, and tells the requester how to complain. Article 12 requires it to be concise, transparent, intelligible and in clear and plain language.
How do we explain redactions without revealing what was removed?
State the ground and the limit. Where other people’s personal data was redacted, the ground is paragraph 16 of Schedule 2 to the Data Protection Act 2018, read with Article 15(4): the right to a copy must not adversely affect the rights and freedoms of others. Say that information relating to other individuals has been redacted where it was not reasonable to disclose it without their consent, and that the redaction was limited to that information. Do not name the person or describe the redacted content in a way that identifies them. If a document was withheld in full, say so and name the exemption.
What changed in the supplementary information in 2026?
Two items. Since 19 June 2026, Article 15(1)(ea) requires the response to tell the requester about their right to complain to the organisation itself under section 164A of the Data Protection Act 2018, which obliges the organisation to acknowledge a complaint within 30 days and investigate it. Since 30 September 2026 the regulator named in the letter is the Information Commission, which replaced the Information Commissioner’s Office under the Data (Use and Access) Act 2025. The rest of the list is unchanged: purposes, categories, recipients, retention, the rights of rectification, erasure, restriction and objection, the source, and automated decision-making.
How long do we have to respond to a DSAR?
One month from the relevant time, which is the latest of the day the request was received, the day any identity information the organisation reasonably asked for was received, and the day any permitted fee was paid (Article 12A). The period can be extended by two further months where the complexity or the number of requests requires it, by a notice sent before the first month ends that states the reasons; the regulator counts the extension as three months from the original start date. Where the organisation asks for clarification of what is being requested, the days between asking and receiving the answer do not count. The response is free unless the request is manifestly unfounded or excessive, which the organisation has to be able to show.
In what format should the response be sent?
If the request was made electronically, the information is provided in a commonly used electronic form unless the requester asks otherwise (Article 15(3)). Send it by a secure route: an encrypted email or a secure download, to the address the requester used. Attach the redacted exports with metadata stripped, never the working copies.
What should the organisation keep after the response has gone?
The letter, the enclosure index, the redaction schedule with the ground for each decision, the search note from IT, the audit trail and review decision log from the redaction tool, and the delivery confirmation. If the requester complains to the organisation under section 164A, the answer is written from that record; if they complain to the Information Commission, it is the same record the regulator asks for.
Transcript
00:00 The last step
Alex Morgan's data subject access request, a D-S-A-R under UK GDPR, was received by email on 3 November 2026. The appraisal, the witness statement and the Microsoft 365 export have all been through review. What remains is the response: the letter that goes to Alex with the files. The law sets the deadline. The applicable time period is one month from the day the request was received, so the response is due by 3 December. Alex is a current employee who wrote from a work address, so identity was never in doubt and the clock started on day one. Because the request arrived electronically, the response goes back electronically, in a commonly used format, unless Alex asks for something else. This lesson is about what that letter has to contain, and what the organisation keeps afterwards.
01:13 What the letter is for
Article 15 gives Alex three things: confirmation that personal data is being processed, a copy of that data, and a set of supplementary information about the processing. The enclosures carry the data. The letter carries everything else. It confirms the request and the date it was received, states what was searched and that the search was reasonable and proportionate, lists what is enclosed, explains what was redacted or withheld and on what basis, sets out the supplementary information, and tells Alex what to do if they disagree. Article 12 adds the manner: concise, transparent, intelligible, in clear and plain language. A letter that says in ordinary words what was done, and why, passes that test.
02:21 The enclosure index
The letter lists what is enclosed, so that Alex can see the response is complete and the organisation can later show what was sent. In this example there are three sets. The appraisal, A-014, with the manager's private mobile number redacted. The investigation note, I-022, with the witness's name and the role and shift details that would identify them redacted. And the Microsoft 365 export: the emails from Alex's own mailbox and others, the files from OneDrive and the HR site, and the Teams transcripts, redacted for other people's personal data. Each file is named, the count in each set is stated, and the redacted versions are the ones attached. The index is short, and it is the first thing a requester checks against what they expected to receive.
03:26 Redactions and withheld items
The letter explains redactions in plain terms without revealing what was removed. Where other people's personal data has been redacted, the ground is paragraph 16 of Schedule 2 to the Data Protection Act 2018, read with Article 15(4): the right to a copy must not adversely affect the rights and freedoms of others. The letter says that information relating to other individuals has been redacted where it was not reasonable to disclose it without their consent, and that the redaction was limited to that information. It does not name the witness or describe what was removed in a way that identifies them. If any document had been withheld in full, the letter would say so and name the exemption, for instance legal professional privilege under paragraph 19, or a confidential reference under paragraph 24. Nothing in Alex's bundle was withheld in full, and the letter says that too. Two documents found in the search were not Alex's personal data at all, and they are simply not included.
04:56 The supplementary information
Article 15(1) lists the information that goes with the data, and the list changed this year. The purposes of the processing. The categories of personal data. The recipients, or categories of recipient, including any outside the UK. The retention period, or the criteria used to decide it. Alex's rights to rectification, erasure, restriction and objection. Since 19 June 2026, the right to complain to the organisation itself, under section 164A of the 2018 Act. The right to complain to the regulator, which since 30 September 2026 is the Information Commission. Where data was not collected from Alex, the source. And whether any automated decision-making applies, with meaningful information about the logic and the consequences if it does. For an employee this is usually a page: HR administration, payroll and performance management as purposes; the HR system, payroll provider and pension administrator as recipients; the retention schedule for employment records. The privacy notice can be attached, as long as the answer is specific to Alex.
06:35 Timing, format and tone
Three rules on time. The applicable time period is one month from the relevant time: the day the request was received, or the later day on which identity information was received or a fee was paid. It can be extended by two further months where the complexity or the number of requests requires it, by a notice sent before the first month ends that gives the reasons; the regulator counts the extension as three months from the original start date. And if the organisation needs clarification of what is being asked for, the time between asking and receiving the answer does not count. None of those applied to Alex. The response is free; a fee or a refusal is available only for a request that is manifestly unfounded or excessive, and the organisation has to be able to show that. On tone, the letter is written to Alex. It says what was found, what was done, and where to go next.
07:54 Checking before sending
Before the letter goes, four checks by a second person. The attachments are the redacted exports, with metadata stripped, and every file in the index is present. The redactions in the files match the redaction schedule, document by document. The letter's supplementary information is specific to Alex. And the delivery route is secure: an encrypted email or a secure download, sent to the address Alex used. Then the record. The organisation keeps the letter, the enclosure index, the redaction schedule with the ground for each decision, the search note from IT, the audit trail and the review decision log from the redaction tool, and the delivery confirmation. If Alex complains to the organisation, section 164A gives it 30 days to acknowledge and a duty to investigate, and the answer is written from that record. If Alex goes to the Information Commission, the same record is what it will ask for.
09:05 The outcome and next step
The response to Alex is the letter, the index, the redacted files and the supplementary information, sent within the month, with a record behind every line of it. The next lesson goes back into the bundle, to the manager's email thread: messages about Alex, messages copied to Alex, and messages where Alex is one name among many, and how the review decides what each one is. 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 (as amended; paragraphs 1(ea), 1A, 3 and 4)
- UK GDPR Article 12, transparent information and modalities (manner, time, fees, identity)
- Data (Use and Access) Act 2025, section 76, inserting Article 12A (applicable time period, extension, stop the clock)
- Data (Use and Access) Act 2025, section 103, inserting section 164A DPA 2018 (complaints to controllers), in force 19 June 2026
- Data Protection Act 2018, Schedule 2 (paragraphs 16, 19 and 24)
- Information Commission, right of access: what should we consider when responding to a request? (updated 8 December 2025)
- SafeRedact, DSAR response letter template (written guide)
Legislation quoted or summarised is UK GDPR and the Data Protection Act 2018 as amended by the Data (Use and Access) Act 2025, as in force in November 2026. The Information Commission replaced the Information Commissioner’s Office on 30 September 2026; its guidance remains published at ico.org.uk. Regulator guidance is reproduced under the Open Government Licence v3.0. This page is informational, not legal advice; the legislation, the regulator’s 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.