Subject Access Requests and Mortgages: A Broker's Guide

Subject Access Requests and Mortgages: A Broker's Guide

A subject access request (SAR) from a mortgage client is a legal request for a copy of the personal data your brokerage holds about them, and you must answer it within one month. Brokers who keep every client document in one tracked, UK-hosted place can answer a SAR in hours rather than days. Brokers who store files across inboxes, shared drives and paper folders spend that month searching.

This guide covers the process for an adviser or brokerage owner: what a SAR is, how to recognise one, the deadline, identity checks, what you can withhold and how to set up your file handling before the first request arrives.

TL;DR

  • A SAR is a client's right under UK GDPR Article 15 to a copy of their personal data and information about how you use it. No form, no reason and no fee is needed in most cases.
  • You must respond without undue delay and within one month, extendable by up to two further months for complex requests. Under the Data (Use and Access) Act 2025 you can pause the clock while you wait for genuinely needed clarification.
  • A SAR can arrive verbally, by email, through social media or via a third party, and can reach any member of staff. Staff need to know how to recognise one.
  • Verify identity in a proportionate way, search reasonably, redact third-party data and record your decisions.
  • The fastest SAR is the one where documents are already collected, labelled and logged in a single system.

Table of Contents

What a subject access request means for a mortgage broker

Under Article 15 of the UK GDPR, individuals have the right to access and obtain a copy of their personal information, plus supplementary information about how it is used. The ICO, the UK data protection regulator, sets this out in its guide to subject access. The ICO describes the right as a fundamental one that helps people understand how and why their information is used and check that the processing is lawful (ICO, right of access).

For a broker, the personal data in scope is wider than a client's name and address. A typical mortgage file holds:

  • identity documents and proof of address
  • bank statements and payslips
  • tax documents such as SA302s and tax year overviews
  • fact-find notes, affordability assessments and emails
  • call notes and recordings
  • lender correspondence and application data

The client can ask for all of it. They are also entitled to the supplementary information: why you process the data, which categories you hold, who receives it, how long you keep it, where it came from if not supplied by the client, their rights to correction, deletion and complaint, and any safeguards for transfers outside the UK (ICO, what is the right of access).

The supplementary information is why your privacy notice and your data retention schedule matter. If your answers to "how long do you keep this" and "who do you share it with" are vague, the SAR exposes that. Our guides to mortgage data privacy and data retention for mortgage brokers cover those foundations.

Recognising a SAR when it arrives

Many SARs are missed because they do not look like one. The ICO states there are no formal requirements: a person can make a SAR verbally or in writing, including through social media, to any part of the organisation. They do not need to use the phrase "subject access request" or cite Article 15, and they do not have to give a reason (ICO, how do we recognise a SAR).

In a brokerage, that means these all count:

  • A client emails their adviser: "Can you send me everything you hold on me?"
  • A client phones the admin team and asks for a copy of their file.
  • A client writes after a declined application asking what you told the lender.
  • A claims or data-request company submits a request on the client's behalf.

The ICO suggests that clients ideally include a subject line, their name and contact details, what they want and any dates that help you find it, but you cannot insist on a template. You can invite people to use one, provided you still act on requests made another way.

Requests through third parties and portals

The ICO's guidance, updated on 8 December 2025 and amended on 7 April 2026, says that for requests via online portals you should consider whether you can verify the person's identity, whether you are satisfied the portal acts with the person's authority, and whether you can view the request without paying a fee or signing up (ICO). Written authority or power of attorney should be checked before you disclose anything to a third party.

The deadline: one month, with limited extensions

The ICO's guide says you must comply without undue delay and at the latest within one month of receiving the request, or of receiving the identity confirmation, third-party authorisation or fee information you asked for. You can extend by up to two further months if the request is complex or you have received a number of requests from the same person. You must tell the client and explain why within the first month (ICO guide to subject access).

What the Data (Use and Access) Act 2025 changed

The Data (Use and Access) Act 2025 brought in a "stop the clock" provision. According to the ICO, you can pause the deadline while you reasonably wait for information you need, such as identity confirmation or clarification of a vague request (ICO guide to subject access). The relevant commencement regulations, SI 2026/82, brought provisions into force on 5 February and 19 June 2026. The ICO's December 2025 guidance clarifies that searches must be reasonable and proportionate, that the clock can be stopped only where clarification is genuinely necessary, not as a blanket practice, and that the threshold for "manifestly unfounded" or "excessive" is high (Employers Federation, February 2026 update).

In practice, log the date every request lands, whichever channel it used, and log every date you stop and restart the clock, with the reason.

What the Data (Use and Access) Act 2025 changed

A five-step process for handling a SAR

1. Log the request and confirm receipt

Record the date, the channel, who received it and who owns the response. The ICO's audit guidance expects systems to record SARs and trained staff who know what to do (ICO, how can we supply information). A simple register is enough for a small firm: request date, due date, identity check status, clock pauses, disclosure date.

Where it goes wrong: the request sits in an adviser's inbox for three weeks because it was treated as a routine query.

2. Verify identity proportionately

You must be satisfied you know who is asking and that the data relates to them. The ICO says checks should be reasonable and proportionate, should use existing verification measures where possible, and should ask for formal ID only if necessary (ICO, responding to a request). A current client emailing from the address on file, whom you have advised in recent months, rarely needs a passport copy. A request from an unknown address or a third party does.

The ICO's audit toolkit adds that you should verify the address you send the data to, keep records of verification checks and check third-party authority. It warns that failing to verify can breach UK GDPR Articles 5(1)(f), 12, 15 and 32 (ICO toolkit). Sending a client's bank statements to the wrong person is a personal data breach, not only a SAR failure. For the identity documents you already collect at onboarding, see our guide to identity document verification.

3. Search every place the data lives

The search must be reasonable and proportionate, but it must cover the places where client data realistically sits. For a brokerage that usually means:

  • your CRM or case management system
  • the document collection platform
  • email accounts, including individual advisers' mailboxes
  • call recordings and notes
  • paper files and scanned copies on shared drives
  • data held by processors acting for you

This is where document sprawl costs time. If bank statements arrived by email, were saved to a desktop and forwarded to a lender, you have three or four copies to find. Collecting documents through one branded client portal creates one location, one log and one audit trail. Casefile is built for this: it automates document collection from clients, keeps UK-only data residency and maintains clear audit trails. Our piece on automated document collection explains the mechanics.

4. Decide what to disclose, redact or withhold

You must give the client their own personal data, not entire documents that happen to contain it, although in practice handing over the whole document is often simplest. Check each item for:

  • Information about other people. A joint application file contains the second applicant's data. A payslip or bank statement may name an employer contact or a payee. Consider whether to redact or whether the other person consents.
  • Exemptions. The ICO's guide lists legal professional privilege, crime and taxation, regulatory functions, management information, negotiations, confidential references and information about other people. Consider each case by case and document your reasons (ICO guide to subject access).
  • Fraud-related information. If you have flagged suspected document tampering and are required to handle that information in a particular way, take advice from your compliance lead or a data protection professional before disclosing it. Do not guess.

You may refuse wholly or partly, or charge a reasonable fee, only where the request is manifestly unfounded or excessive. The ICO says the threshold is high and each request should be considered in context. If you refuse, you must explain why and tell the person they can complain to the ICO and ask the courts to enforce their right (ICO guide to subject access). A large mortgage file is not, by itself, excessive.

5. Send it securely and record what you did

For an electronic request, provide the copy in a commonly used electronic format unless the client reasonably asks for something else. Sensitive data must travel by an appropriately secure method, and you should check the email or postal address before sending (ICO, supplying information). A mortgage file contains financial and identity data, so an unencrypted attachment to a plain email is the wrong choice. Use a secure link or encrypted file with the password sent separately.

Include the supplementary information with the copy: purposes, recipients or categories of recipients, retention periods, the source of the data, the client's rights and the right to complain to the ICO (ICO, getting a response). Keep a record of what was disclosed, what was withheld and why.

Worked example: a SAR after a declined application

A client's remortgage application is declined by the lender. Three weeks later the client emails the adviser asking for "all the information you passed to the lender and everything on my file".

  • Day 0: the request is logged and the one-month due date is set.
  • Day 1: the adviser's record shows the client has been in regular contact from the same email address. The firm decides no further ID is needed and records why.
  • Days 2 to 5: the search covers the case management system, the document platform, the adviser's mailbox and call notes.
  • Days 6 to 8: the file includes the client's partner's payslip from the joint application. The partner's data is redacted unless they consent.
  • Day 9: the copy goes out via an encrypted link, with a cover note setting out purposes, recipients, retention and complaint rights.

The search took days because the work was scoped and logged from day one. The same request in a firm with documents scattered across inboxes can consume most of the month.

How document handling affects SAR workload

SAR effort is mostly search effort. Three habits reduce it.

Collect once, in one place. Documents requested by email chain end up in several mailboxes. A single collection platform means the file you disclose is the file you hold. See mortgage data privacy for how to structure client documents.

Keep to your retention schedule. Data you no longer need and should have deleted still falls in scope if it exists. Deleting on schedule shrinks every future SAR. Our data retention guide sets out periods for mortgage files.

Keep an audit trail. A log of who uploaded, viewed and approved each document lets you answer "who is this shared with" accurately. It also supports your answer to the client's question about recipients, which the ICO lists as part of the supplementary information.

Promo

Casefile is a cloud-based platform for UK mortgage brokers that automates document collection from clients and cross-checks bank statements, payslips, tax forms, ID and utility bills. It flags discrepancies, manages document approval queues, carries your brokerage's branding and keeps data in the UK only, with clear audit trails. For a brokerage, that means client documents sit in one controlled place rather than across inboxes and drives. See how it works at Casefile, or read how Casefile handles your documents.

Gocasefile

Perspective

Most brokers meet the SAR as an interruption: a request lands, an adviser stops work and the search begins. We see it differently. A SAR is a test of how well a firm knows where its client data is, and the answer is decided long before the request arrives.

Our approach to document handling is designed around that idea. Documents are collected through a branded client portal, stored with UK-only data residency, with no manual or offshore data handling and a clear audit trail of what was received and by whom. When the document file is already ordered and logged, finding it is the easy part of a SAR.

For small brokerages without a dedicated compliance team, that matters most. The time saved on document checking and chasing is the same time you need when a client asks for their file.

Darren

FAQ

Can a mortgage broker charge for a subject access request?

Generally no. The request is free, and a fee is allowed only where the request is manifestly unfounded or excessive, and the ICO says that threshold is high (ICO guide to subject access). Record your reasoning if you consider it.

Does the client have to give a reason or use a form?

No. The ICO says a SAR can be made verbally or in writing, to any part of the organisation, without specific wording, and the client does not have to explain why they want the data (ICO). You can ask for clarification only where it is genuinely needed to locate the information.

Can we pause the one-month deadline?

Yes, in limited cases. Under the Data (Use and Access) Act 2025, you can stop the clock while you reasonably wait for identity confirmation or clarification of a vague request (ICO guide to subject access). The ICO's guidance says this must be genuinely necessary, not applied as a blanket practice (Employers Federation).

Do we have to disclose a joint applicant's data?

Not without considering their rights. The ICO lists information about other people as a ground to withhold or redact, to be assessed case by case with your reasons documented (ICO guide to subject access). Redact the other applicant's data or seek their consent.

Is a client's request to a claims company the same as a SAR?

It can be, if the company acts with the client's authority. Check the authority and your ability to verify identity before you disclose anything (ICO). If you are unsure how to answer a complex or contested request, speak to your compliance lead or a data protection professional.

Sources

This article was generated with AI, and whilst it is our expectation that the article is accurate, it should not be taken as advice.