Mortgage Data Privacy: A UK Broker's Guide to Client Documents

Mortgage data privacy, for a UK broker, means handling every bank statement, payslip, tax form and ID document in line with the UK GDPR and the Data Protection Act 2018: a lawful basis for each use, clear privacy information, restricted access, defined retention periods and a tested breach process. This guide sets out what that looks like in daily practice, from the first document request to disposal.
TL;DR
- Brokers process large volumes of personal and financial data, so the UK GDPR and Data Protection Act 2018 apply to every stage of a case, from fact-find to completion.
- Identify a lawful basis for each purpose, tell clients plainly what you do with their data, and keep records that show you can demonstrate compliance.
- Share only what lenders and service providers need, with the roles of each party clear, and restrict internal access to the people working the case.
- Set retention periods, dispose of data securely, and be ready to answer client rights requests within one month.
- A notifiable breach must be reported to the ICO within 72 hours of becoming aware of it, where feasible, so the process must exist before it is needed.
Table of Contents
- What personal data a mortgage case involves
- Which UK rules apply
- Lawful basis and privacy notices
- Collect less, and collect it once
- Store and control access
- Sharing documents with lenders and providers
- Retention and disposal
- Client rights and how to answer them
- If something goes wrong: breach response
- Handling client documents with Casefile
- A practical checklist for your brokerage
- FAQ
- Sources
What personal data a mortgage case involves
A mortgage application is one of the most data-heavy consumer transactions. A typical file holds names, addresses, dates of birth, identity documents, employment details, bank details, credit history, bank statements, payslips and tax forms. Mortgage providers' own privacy policies also list health and family-history information where it is relevant to advice, which brings special-category data into scope.
Three features make this data sensitive in practice:
- It is financial and identifying at once. A bank statement shows income, spending, commitments and the names of third parties.
- It often covers more than one person. Joint applicants, guarantors and dependants appear in the same documents.
- It travels. Documents move between client, adviser, administrator, lender and sometimes a verification or case-management provider.
Each handover is a point where privacy can fail, so the controls below follow the document through its life.
Which UK rules apply
The UK GDPR and the Data Protection Act 2018 govern how brokers handle personal data. The core requirement is that processing is lawful, fair and transparent, with security and accountability built in, as summarised for brokers. The ICO's guidance on the first data protection principle adds that fair processing means not using data in ways that are unduly detrimental, unexpected or misleading for the person.
Two practical consequences follow:
- Accountability. Brokers must be able to demonstrate compliance and keep records that evidence it if the ICO or the FCA challenges them. Our guide to FCA record keeping for mortgage brokers covers what a file should hold.
- Special-category data. Health information needs an additional condition under the Data Protection Act 2018, on top of the ordinary lawful basis. The Act itself provides for processing for substantial public interest purposes while balancing individuals' rights, so confirm the condition you rely on before recording such data.
Data privacy and regulatory conduct also meet in the file. The FSA's final notice against a mortgage intermediary found that it failed to verify income information that was inconsistent with what the customer had said earlier. Collecting documents is not enough: checking them, and keeping the evidence, is part of doing the job properly.
Lawful basis and privacy notices
Every purpose needs a valid lawful basis. For brokers the usual candidates are contract performance for arranging a mortgage, legal obligation for anti-money-laundering checks, and legitimate interests, as set out for brokers. Consent is available, but it suits optional uses such as marketing better than the core advice process, because it can be withdrawn.
A working approach is to map each purpose to a basis and write it down:
| Purpose | Typical lawful basis | Note |
|---|---|---|
| Assessing affordability and arranging the mortgage | Contract performance | Pre-contract steps requested by the client count |
| Identity and AML checks | Legal obligation | See our AML document checks guide |
| Fraud prevention and internal quality checks | Legitimate interests | Record the balancing test |
| Health or vulnerability information | Ordinary basis plus a special-category condition | Collect only what advice needs |
| Marketing | Consent or another basis you can justify | Keep separate from case data |
Your privacy notice must then tell clients why data is collected and processed and what rights they hold. Write it for a first-time buyer, not a lawyer. State who you are, what you collect, which lenders and providers receive it, how long you keep it and how to complain. Give it to clients at the start, before the first document request, not after the documents arrive.
Collect less, and collect it once
Data minimisation starts with the document request. A generic checklist sent to every client invites over-collection: the self-employed applicant receives a payslip request, the salaried applicant a tax-return request, and each uploads extra material you then have to protect.
Tailor the request to the client:
- Match the list to the income type. Employed, self-employed, contractor and retired applicants need different evidence.
- Ask for the period you need. If the lender's criteria call for three months of statements, do not accept a year by default.
- Keep it in one place. Documents sent by personal email, messaging apps and photographs on advisers' phones create copies nobody tracks.
- Allow redaction where it is appropriate. Clients can often hide unrelated transactions or third-party details that you do not need.
Our platform builds document lists automatically from the client's payment type, so each applicant is asked only for what that profile requires. Our guide to income verification in the UK explains which documents belong to which income type.
Store and control access
Security is a legal requirement, not a preference. Brokers should document the data they hold and share, restrict access, secure it and set retention processes, as intermediary GDPR guidance puts it. In practice, five controls do most of the work:
- A single secure repository instead of inboxes and shared drives.
- Role-based access. The adviser and administrator on the case see it; others do not.
- A UK data-residency requirement for any provider that stores client documents, with no manual or offshore handling.
- An audit trail showing who uploaded, viewed, approved or changed each document.
- Authenticity checks at intake, so altered or fabricated documents are caught before they enter a lender submission. See our guide to document tampering detection and the mortgage fraud red flags checklist.
Identity documents deserve particular care, because they combine biometric-grade detail with name, address and date of birth. Our identity document verification guide covers the checks, and a guide to keeping UK identity verification private looks at the same issue from the ICO's standpoint.
Sharing documents with lenders and providers
Brokers share documents with lenders every day, and that is lawful when it is necessary for the application. The principle is that the recipient needs its own lawful basis, and the parties' roles should be clarified, ideally in a data-sharing agreement, as described for brokers. The same source notes that where possible, anonymised or aggregated information should be shared about groups of vulnerable customers, with individual-level data reserved for cases where it is genuinely necessary.
Use this short test before each disclosure:
- Does the recipient need this document to decide or service the application?
- Is the client's privacy notice clear that this type of recipient receives data?
- Is the transfer made through a secure channel, not an email attachment?
- Is the recipient's role (separate controller or processor acting on your instructions) clear and recorded?
For the wider principle of limiting what leaves your hands, a secure document sharing guide lays out how brokers in another lending sector think about transparency and limiting disclosure.
Suppliers you use to collect or check documents are processors. Before onboarding one, run a privacy impact assessment; our guide to privacy impact assessments for UK mortgage brokers walks through the questions.
Retention and disposal

Keeping documents indefinitely is a privacy risk and a breach of the storage-limitation principle. Keeping them too briefly can leave you unable to evidence your advice. The answer is a written schedule: define how long each category is held, why, and what triggers disposal. Practical retention guidance, including the periods that apply to mortgage files, is in our article on data retention for mortgage brokers.
A workable disposal routine has four parts:
- Set the clock from a clear event, such as completion or case closure.
- Review quarterly for files that have passed their date.
- Delete securely, including copies in backups, exports and email.
- Log the deletion so you can show the schedule is followed.
Where a document must be retained for regulatory purposes, keep it and restrict access to it rather than leaving it in the live case queue.
Client rights and how to answer them
Clients can request access to their data, rectification of inaccurate or incomplete information, erasure, restriction and portability, and can object to certain processing, as one mortgage lender's privacy policy sets out. Not every right applies to every purpose. Erasure, for example, will not override a legal obligation to retain records.
Subject access requests are the most common. The ICO states that you must respond without undue delay and within one month, that requests can be made verbally or in writing, that in most circumstances you cannot charge a fee, and that the period can be extended by up to two further months where a request is complex.
To answer quickly:
- Log the date of receipt the moment a request arrives, whoever receives it.
- Verify the requester's identity without collecting more data than needed.
- Search every place data is held: the case system, email, call recordings and processors.
- Correct inaccurate data in every location, and tell recipients where appropriate.
A single repository makes this far faster. If documents live in one place with an audit trail, the search is a query and not a hunt.
If something goes wrong: breach response
A personal data breach covers loss, unauthorised disclosure or access, not only cyber attacks. Sending a client's payslips to the wrong email address counts. The ICO's guidance says certain breaches must be reported to it within 72 hours of becoming aware, even if you do not yet have all the details. Where a breach is likely to result in a high risk to individuals, they must be told as well.
Prepare before you need it:
- Name a responsible person and a deputy.
- Write a one-page procedure: contain, assess, record, decide whether to notify the ICO, decide whether to tell clients.
- Keep a breach log, including incidents you decide not to report, with your reasoning.
- Rehearse once a year with a realistic scenario such as a misdirected email with identity documents.
If the incident involves a lender or processor, your data-sharing terms should say who notifies whom and how fast.
Our perspective on mortgage data privacy
Most privacy failures in brokerages are not dramatic. They are small habits: documents arriving by email, copies saved to desktops, requests sent in a generic list, and no clear record of who looked at what. Each habit is understandable when an adviser is chasing a case, and each is hard to defend later.
We built Casefile around the idea that the process should make the compliant route the easy one. Document lists build themselves from the client's payment type, so clients upload what is needed and no more. Data stays in the UK, with no manual or offshore handling. Every action sits in an audit trail. Discrepancies, such as undeclared commitments or mismatched wage deposits, are flagged before the file reaches a lender, which reduces queries and keeps fewer copies of documents in circulation.
Smaller brokerages feel this most, because there is no compliance team to absorb the workload. The platform carries the brokerage's own branding, so clients see a familiar firm throughout, and the interface is designed to need little technical learning.
Darren
Handling client documents with Casefile
Casefile is a cloud-based platform for UK mortgage brokers that collects client documents, cross-checks bank statements, payslips, tax forms, ID and utility bills, flags discrepancies, and manages approval queues under your own branding, with UK-only data residency. To see how documents are handled, read how Casefile handles your documents, or visit Casefile to start a conversation about setting it up for your brokerage.

Support for multiple applicant types and applicant privacy is built in, so joint cases do not mean one person's documents are exposed to the other more than the process requires.
A practical checklist for your brokerage
Use this list as a quarterly review:
- Is there a written record of the lawful basis for each purpose?
- Does the privacy notice reach clients before the first document request?
- Are document requests tailored to income type?
- Do all documents sit in one controlled repository with an audit trail?
- Is access limited by role?
- Are lenders and processors covered by clear roles and, where needed, data-sharing terms?
- Is there a retention schedule, and was it applied this quarter?
- Can you answer a subject access request inside one month?
- Is the breach procedure written, with named owners, and was it rehearsed this year?
More guidance on adjacent topics is collected on the Casefile blog, including payslip verification.
FAQ
Do mortgage brokers need client consent to process documents?
Not usually for the core advice process. Brokers more often rely on contract performance, legal obligation for anti-money-laundering checks or legitimate interests, as described for brokers. Consent suits optional uses such as marketing. Whichever basis you choose, record it and explain it in your privacy notice.
How long does a broker have to answer a data access request?
The ICO says you must respond without undue delay and within one month of receiving the request. You can extend by up to two further months where the request is complex or the person has made several. Start the clock on the day any member of staff receives it.
When must a mortgage broker report a data breach?
A breach that must be notified goes to the ICO within 72 hours of becoming aware of it, where feasible, even if details are incomplete. Record every breach internally, including those you decide not to report, and note your reasoning.
Can brokers send client documents to lenders?
Yes, where it is necessary for the application and the recipient has a lawful basis. Clarify each party's role, use a secure channel, and make sure your privacy notice tells clients that lenders receive their data.
Sources
- Privacy policy, mortgage provider
- FCA and GDPR: What Brokers Need to Know
- ICO: Lawfulness, fairness and transparency
- Data Protection Act 2018
- FSA final notice, PMSG Insurance Services Limited
- UK GDPR intermediary guidance
- Privacy Policy, LiveMore Mortgages
- ICO: A guide to subject access
- ICO: Personal data breaches, a guide
Recommended
- Privacy Impact Assessments for UK Mortgage Brokers
- Document Intake Forms for UK Mortgage Brokers: A Practical Guide
- Data Retention for Mortgage Brokers: UK Rules and Periods
- Document Version Control for UK Mortgage Brokers
This article was generated with AI, and whilst it is our expectation that the article is accurate, it should not be taken as advice.