How to redact emails for a subject access request

General information, not legal advice. What you disclose or redact in a particular request is your organisation's decision. Last checked against ICO guidance on 16 November 2026.

Email is usually the largest and most awkward part of a subject access request (SAR or DSAR). A single thread can contain the requester's personal information, colleagues' and clients' details, attachments and hidden data in the message itself. This guide walks through the decisions and the mechanics, based on the ICO's guidance on subject access and on disclosing documents securely.

Step 1: decide what in each email is in scope

The ICO's guidance on emails sets the starting point (ICO: information contained in emails):

  • The right of access only applies to the personal information in the email that relates to the requester, so you may need to disclose only part of an email.
  • Being the recipient does not make the whole email the requester's personal information.
  • A business email may still contain their personal information, depending on what it says.
  • An email moved to "Deleted items" has not been deleted.

Where the requester is only named or copied in and the content is not about them, the ICO's example suggests you could tell them how many emails their name and address appear on and disclose those details, or send one redacted email as a sample.

Step 2: decide what to redact from the in-scope emails

Most email redactions fall into two groups:

  • Other people's personal information. Names, email addresses, signatures, phone numbers and anything else that identifies someone else, unless they consent or disclosure is reasonable without consent (ICO: information about other people). Remember that redacting a name may not hide someone if the context identifies them.
  • Information covered by an exemption. For example, privileged advice from your solicitors or a confidential reference (ICO: What exemptions are relevant for SARs?). See our guide to DSAR exemptions.

Keep the response intelligible. The ICO says you should give enough context for the requester to understand the information, and that it may often be better to leave information in unless an exemption covers it (ICO: How can we supply information to the requester?).

Step 3: deal with threads and duplicates

Long threads repeat the same text many times. Each copy needs the same redaction decision, or the redacted text in one message will appear in clear in the quoted reply below it. A consistent approach across the whole set, with the same code for the same reason, also makes the response easier to explain. The ICO's audit framework expects organisations to take a consistent approach to removing third-party information and to keep records of redactions (ICO: Exemptions and redactions).

Step 4: check attachments and hidden information

Attachments are separate documents and need their own review. Emails and documents can also carry information you cannot see on screen. The ICO's guidance on hidden personal information mentions metadata such as email routing information and document properties, and markup such as comments and tracked changes (ICO: personal information hidden in documents). It suggests, for example, removing email metadata by saving the email as plain text, or printing and scanning it to PDF.

Step 5: redact so it cannot be undone

This is where many accidental breaches happen. The ICO's guidance on redaction makes several clear points (ICO: avoiding an accidental breach when redacting):

  • Black boxes are not enough on their own. Text covered by a black rectangle may still be in the file and can be revealed, for example by copying and pasting.
  • Changing the text or background colour does not redact it.
  • Converting to PDF is not, on its own, a completely secure redaction method.
  • Use redaction software, or a technique such as "roundtrip" conversion (for example, PDF to a simple image format and back) so the information is permanently removed.
  • Redact a copy, never the original, and keep clearly labelled redacted and unredacted versions for as long as needed.
  • Check before you send, and keep a record of who redacted what, when and why.

The ICO also suggests reviewing redactions, or a sample of them, to check they are effective.

Step 6: label and explain the redactions

The requester should be able to see where something has been removed and, where possible, why. The ICO suggests you could replace removed text with a marker such as "[redacted]" so it is clear where information has been taken out. Short codes that match a key in your cover letter or schedule (for example, TP for third-party personal data) do the same job more precisely. Unless explaining would itself prejudice an exemption, the ICO says you should be transparent about your reasons for withholding information (ICO: What do we need to do if we refuse?).

Where Fairleaf fits

Fairleaf Disclosure prepares redacted disclosure packs for UK organisations. Our software proposes redactions for other people's personal data in the emails and documents you send us, flags passages that may fall under an exemption, and builds a pack in which each redaction carries a code matching the schedule. You review every proposed redaction and make the final call before anything is released. See what goes in a disclosure pack.

Frequently asked questions

Is it safe to redact a DSAR by drawing black boxes in a PDF?

Not on its own. The ICO warns that text under a black rectangle can remain in the file. It recommends redaction software or roundtrip conversion so the information is permanently removed.

Do we have to disclose every email the requester is copied into?

No. The ICO says the right of access only covers the requester's personal information in the email. If the content is not about them, you may only need to disclose their name and email address.

Do we need to redact email addresses as well as names?

Usually, if they identify someone other than the requester and the third-party test does not support disclosure. An email address can identify a person as clearly as a name.

See a full example pack

We will email you a complete disclosure pack built from a synthetic mailbox: the redacted documents, the schedule, the exemption log and the search record. It is free and there is no obligation.

Request the example packGet the pack (opens your email app)

hello@fairleaf.co.uk

Please do not send us any real personal data or request material by email. We will arrange a secure route if you go ahead.

Example redacted email from a Fairleaf disclosure pack. Third-party names are covered by black boxes marked TP; the requester's own details stay visible. Synthetic data. Example pack, synthetic data

Fairleaf does not give legal advice. Our clients remain responsible for their disclosure decisions.