How to outsource a DSAR: what stays with you and what a provider can do

General information, not legal advice. Last checked against ICO guidance on 16 November 2026.

Many UK organisations bring in outside help for a subject access request (SAR or DSAR), especially when a request covers years of email. Outsourcing can take the heavy lifting off your team, but it does not move the legal responsibility. This guide explains how the roles work, what you can hand over, what you should keep, and what to put in place before any real data changes hands.

You stay the controller

The organisation that receives the request and decides why and how the personal data is used is the controller. The ICO says controllers are responsible for complying with SARs, and that you are responsible for deciding how to deal with them (ICO: Who is responsible for responding to a request?).

A provider that handles the data only on your instructions, with no purpose of its own, is likely to be a processor (ICO: Controllers and processors). The ICO notes that controllers carry the highest level of compliance responsibility, including for the compliance of their processors.

In practice that means:

  • the deadline is still yours;
  • every decision to disclose, redact or withhold is still yours; and
  • the response still goes out in your organisation's name.

A written contract comes first

The ICO says that whenever a controller uses a processor, there must be a written contract (or other legal act) in place (ICO: Contracts). The requirements come from Article 28 of the UK GDPR.

According to the ICO, the contract must set out the subject matter, duration, nature and purpose of the processing, the types of personal data and categories of people, and the controller's obligations and rights. It must also include terms about acting only on documented instructions, confidentiality, security, sub-processors, helping with individuals' rights, end-of-contract deletion or return, and audits.

The ICO also says controllers must only use processors that can give sufficient guarantees about the technical and organisational measures they will put in place.

What you can hand over

There is no fixed list, but these are the stages organisations most often outsource:

  • Redaction. Going through documents to remove other people's personal data and anything covered by an exemption, so that your reviewer starts from a proposed set of redactions rather than a blank page.
  • Exemption flagging. Marking passages that may be covered by legal professional privilege, confidential references or other exemptions, for your reviewer to decide on.
  • Building the disclosure pack. Assembling the redacted documents into a single, bookmarked bundle with a schedule, an exemption log and a record of the search.
  • Drafting. Preparing a cover letter for your DPO or solicitor to amend and sign.

What you should keep

  • Logging the request and the deadline. Including any ID checks, extensions or clarification. The ICO says a request is not complex just because you rely on a processor to provide the information you need (ICO: When is a request complex?), so outsourcing does not by itself justify an extension.
  • Collecting the data. You know your systems. The search must be reasonable and proportionate (ICO: How do we find and retrieve the relevant information?).
  • Decisions. Reviewing every proposed redaction and exemption, and making the final call.
  • The response. Sending it securely, with the supplementary information, and handling any complaint.

Questions to ask any provider

Before you share any real data, ask a provider to answer these in writing:

  1. Will you act as our processor, only on our documented instructions?
  2. What contract will we sign, and does it cover the points the ICO lists for Article 28?
  3. Which sub-processors would handle our data, and how will you tell us about changes?
  4. Where will the data be held, for how long, and how is it deleted at the end?
  5. What will we actually receive? Ask to see an example.
  6. How will we review proposed redactions, and how is each decision recorded?
  7. How should we send you the documents, and how will you send the pack back?

How Fairleaf works

Fairleaf Disclosure is a DSAR redaction service for UK organisations. You gather the relevant emails, files and records from your own systems and send them to us. Our software proposes redactions for other people's personal data, flags passages that may fall under an exemption and builds the disclosure pack. It proposes; it does not decide. You review every proposed redaction and make the final call before anything is released.

You stay the controller and we act as your processor, handling the data only on your instructions. We'll agree a data processing agreement with each client before any real data is shared. If you have questions about hosting, retention and security, email us and we will answer in writing.

We work by email. See what goes in a disclosure pack, or, if you are a law firm or DPO provider, our page for partners.

Frequently asked questions

Can we outsource a subject access request?

Yes. You can ask an outside provider to handle all or part of the work, such as the redaction and the disclosure pack. Your organisation stays the controller and remains responsible for the response. The provider acts as your processor and works only on your instructions.

Does outsourcing give us more time to respond?

No. The ICO says a request is not complex just because you rely on a processor. The one-month limit, and any justified extension, still applies. See our DSAR deadline guide.

Do we need a contract with a DSAR provider?

Yes, if they act as your processor. The ICO says there must be a written contract or other legal act whenever a controller uses a processor, and the UK GDPR sets out what it must include.

Can a provider decide what to redact for us?

A provider can propose redactions, but the disclosure decisions remain yours as controller. The ICO says you are responsible for deciding how to deal with SARs.

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.