What belongs in a DSAR disclosure pack?
General information, not legal advice. Last checked against ICO guidance on 16 November 2026.
"Disclosure pack" is not a legal term. It is the practical name for everything you send a requester in response to a subject access request (SAR or DSAR), plus the working records you keep to show how you reached your decisions. This guide sets out what the law requires you to provide, and what a well-organised pack usually adds so the response can be checked, explained and defended later.
What the law requires you to provide
The ICO says a person is entitled to three things (ICO: What is the right of access?):
- Confirmation that you are processing their personal information.
- A copy of their personal information.
- Supplementary information, including your purposes, the categories of data, recipients (or categories of recipients), how long you will keep it, their rights to rectification, erasure, restriction and objection, their right to complain to you and to the ICO, the source of the data if not from them, and information about automated decision-making and international transfers.
The supplementary information largely matches your privacy notice. The ICO says you could include a link to it in your response.
If the request was made electronically, the ICO says you must provide the information in a commonly used electronic format unless the person asks otherwise, and you must take all reasonable steps to provide it securely (ICO: How can we supply information to the requester?).
What a well-organised pack usually contains
None of the items below is a legal form. They are a common, practical way to meet the requirements above and keep the record the ICO expects.
A cover letter
The letter confirms processing, sets out or links to the supplementary information, explains how the pack is organised and explains any redactions. If you are withholding anything, the ICO says you must tell the person why, their right to complain to you and to the ICO, and their ability to go to court, unless explaining would itself prejudice an exemption (ICO: What do we need to do if we refuse?).
The redacted documents, in one bundle
One PDF with a cover page, contents and bookmarks is easier for a requester to use than a folder of loose files. The ICO says the information you provide must be clear and accessible (ICO: A guide to subject access), and that you should give enough context for the requester to understand it.
A redaction key
A short list of codes, such as TP for third-party personal data or LPP for legal professional privilege, each tied to the provision relied on. Each redaction in the bundle carries its code, so the requester can see why something was removed.
A schedule of documents
One row per document: reference, date, type, sender and recipient, page count, number of redactions and codes used. It lets a reviewer, a complaints handler or the ICO find any document quickly.
An exemption log
A record of what was withheld or redacted and on what basis. The ICO says you should document your reasons for relying on an exemption and record why you decided to disclose or withhold third-party information (ICO: information about other people). Its audit framework also expects records of redactions showing who did them, when and why (ICO: Exemptions and redactions). The log is usually kept internally rather than sent to the requester.
A search record
The sources, search terms and date range used. You must make a reasonable and proportionate search, and the ICO says you must be able to show why any search would be unreasonable or disproportionate (ICO: How do we find and retrieve the relevant information?). A search record is how you show it.
Redacted and unredacted versions, kept on file
The ICO says you should keep a clearly labelled copy of the redacted and unredacted versions for as long as needed (ICO: avoiding an accidental breach when redacting). If the requester complains, you can show exactly what was released.
What goes to the requester and what stays with you
| Item | Usually sent to the requester | Usually kept on file |
|---|---|---|
| Cover letter and supplementary information | Yes | Copy |
| Redacted document bundle | Yes | Copy |
| Redaction key | Yes | Copy |
| Schedule of documents | Often, in a redacted form | Yes |
| Exemption log | Rarely | Yes |
| Search record | Sometimes, as a summary | Yes |
| Unredacted versions | No | Yes |
These are common practice, not rules. Decide case by case, and remember that a log or schedule can itself contain third-party information.
Where Fairleaf fits
This is what Fairleaf Disclosure prepares. You receive one bookmarked disclosure pack with redacted documents, a redaction key, a schedule of every document, an exemption log and a search record, plus a draft cover letter in your organisation's name for your DPO or solicitor to amend and sign. Our software proposes the redactions and builds the pack. You review every proposed redaction and make the final call before anything is released. For the decisions behind the codes, see what can be redacted and DSAR exemptions explained.
Frequently asked questions
Do we have to send copies of whole documents?
Not necessarily. The ICO says a SAR gives a right to a copy of personal information, not necessarily to documents (ICO: manifestly unfounded or excessive). But you must give enough context for the information to make sense, and sending a redacted document is often the clearest way to do that.
Do we have to give the requester our exemption log?
There is no requirement to send an internal log. You must tell the requester the reasons for withholding information where you can, and the ICO says you should document your reasons internally.
Can we just send a link to our privacy notice for the supplementary information?
The ICO says you could include a link to this information in your response, as long as it covers what the requester is entitled to.