Key takeaways
- Every use of personal data needs a lawful basis; for agencies the workhorses are contract, legal obligation and legitimate interests[1].
- The principles of minimisation, accuracy and storage limitation cause more agency problems than consent ever does[2].
- Security is the weak point: 43% of UK businesses reported a breach or attack in the latest survey, and phishing was the most common[3][4].
- Most agencies must also pay the annual data protection fee; it is £52 or £78 for most organisations[5].
Why an agency is a data business
An estate or letting agency handles more personal data than most small firms. A single sale can involve the seller's identity documents and bank details, the buyer's mortgage position and proof of funds, notes from viewings and offers, and calls with solicitors. A let adds referencing, right to rent copies, deposit records, repair reports from inside people's homes and years of landlord statements.
Regulators treat the everyday parts of this work as regulated activity too. HMRC counts arranging viewings and answering questions from potential sellers, buyers, landlords or tenants as estate agency activity for money laundering registration[6], which tells you how wide the net of client data is. UK GDPR applies to all of it, from the negotiator's mobile to the archive boxes in the loft.
The principles in agency language
UK GDPR's principles are short. Read in agency terms, each one maps to a habit you can check[2].
- Lawful, fair and transparent: people know who you are, what you collect and why, usually through a privacy notice given at registration.
- Purpose limitation: data collected to reference a tenant is not quietly reused to sell them mortgage products.
- Data minimisation: you collect what the task needs; a viewing booking does not need a date of birth.
- Accuracy: buyer positions, phone numbers and landlord bank details are corrected when they change.
- Storage limitation: records are kept no longer than necessary, which needs a retention schedule rather than an open-ended archive.
- Integrity and confidentiality: devices, inboxes and paper files are secured against loss and misuse.
- Accountability: you can show how you comply, not just say that you do.
Choosing a lawful basis for each client type
Processing is lawful only where at least one basis in Article 6 applies[1]. Consent is one, but it is rarely the best fit for core agency work because people can withdraw it and it must be freely given. Most processing sits on contract, legal obligation or legitimate interests.
| Who | Typical processing | Usual lawful basis |
|---|---|---|
| Sellers and landlords | Agency agreement, marketing the property, statements and payments | Contract |
| Sellers, landlords and buyers in a sale | Identity and money laundering checks | Legal obligation |
| Applicant buyers | Registering requirements, matching and arranging viewings | Legitimate interests, or steps before a contract at their request |
| Prospective tenants | Referencing and affordability checks before a tenancy | Steps before entering a contract at the applicant's request |
| Prospective tenants | Right to rent checks and keeping copies | Legal obligation |
| Past clients and applicants | Marketing emails and texts | Consent, or the soft opt-in where it applies under PECR |
The Data (Use and Access) Act 2025 added a new basis, processing necessary for a recognised legitimate interest[1]. It covers a short list of purposes such as crime prevention and safeguarding. For most agency work it changes little, but it can help when sharing information to prevent fraud or protect a vulnerable person.
Write the basis down. A one-page record that says, for each activity, what you collect, why, on which basis and for how long is the core of accountability and the first thing an investigator asks for.
The mistakes agencies make most
- Keeping everything forever because the CRM never deletes, including rejected tenant applications and buyers who stopped searching years ago.
- Using personal mobiles and messaging apps for client conversations without any record or control over the data.
- Sending landlords the whole referencing file when they only need the outcome and the facts that support it.
- Forwarding identity documents by ordinary email and leaving them in sent folders indefinitely.
- Treating every applicant as a marketing contact the moment they register, without checking PECR rules.
- Having no plan for a breach, so a misdirected email becomes a scramble rather than a routine decision.
Sharing data with landlords, solicitors and suppliers
Agencies pass data along a chain: to landlords and sellers, to solicitors and conveyancers, to referencing firms, contractors, deposit schemes, inventory clerks and CRM providers. Each link needs a reason that fits the purpose you collected the data for, and a decision about whether the recipient is a separate controller or your processor.
- Processors, such as your CRM, telephony or referencing platform, act on your instructions and need a written contract that sets out what they may do with the data.
- Separate controllers, such as a buyer's solicitor or a deposit scheme, decide their own purposes; share only what the task needs and record why.
- Contractors visiting a property need the tenant's name, phone number and access details, not their referencing history or rent arrears.
- Overseas suppliers, including software hosted abroad, need a check that the transfer has proper safeguards.
A short sharing register, listing each regular recipient, what they receive and on what basis, answers most of the questions a tenant, landlord or regulator will ask.
Security: where the risk really sits
Most data protection failures in small firms are security failures. In the government's 2025/26 survey, 43% of UK businesses, about 612,000, reported a cyber security breach or attack in the previous 12 months[3]. Phishing was the most common type, experienced by 38% of businesses[4], and 12% reported impersonation attacks[3].
For an agency, phishing and impersonation are not abstract. A fake email from a landlord asking to change bank details, or a spoofed message from a conveyancer, targets exactly the money and data that agencies hold. Strong passwords, two-step login on email and the CRM, and a call-back rule for any change of payment details do more for compliance than another policy document. Our guide to bank detail change fraud sets out the call-back routine in detail.
Sensitive information you did not ask for
Agencies often receive sensitive information without asking: a tenant explains a disability when requesting an adjustment, a seller mentions a divorce or a bereavement, a buyer discloses a health condition affecting their move. Data about health and some other categories carries extra conditions under UK GDPR. Record only what you need to act, keep it out of general notes that the whole office can read, and never pass it to a landlord or seller unless it is necessary and the person understands why.
People are uneasy about automated judgements too: 91% of UK adults say they are concerned about important decisions being made by computers without human input[7]. If your referencing or lead scoring relies on automated tools, make sure a person reviews any decision that refuses an applicant.
Example: a lettings branch tidies up
Example (fictional): a single-branch letting agency reviews its data after a tenant asks what it holds. It finds rejected applications going back six years, copies of passports in three places, and a shared inbox where referencing reports are forwarded to landlords in full.
Over a month it sets a retention schedule, moves identity documents into the CRM's restricted area and deletes the email copies, and changes the landlord template to send a summary outcome instead of the full report. It adds a privacy notice link to every registration form and books a quarterly check of what has been deleted. None of this needed new software, only decisions written down and applied.
Fees, notices and the rest of the framework
Most businesses that process personal data must pay the annual data protection fee to the data protection regulator unless they are exempt; it is £52 or £78 for most organisations[5]. Alongside the fee, you need a privacy notice that matches what you actually do, a way to handle access requests within the time limit, a breach procedure, and contracts with processors such as referencing firms and CRM providers.
Each of these has its own guide in this series: the data protection fee, privacy notices and subject access requests.
A one-page compliance checklist
Map your data
List each activity, the data it uses, where it is stored and who can see it, including mobiles and messaging apps.
Record the lawful basis
Attach a basis to each activity and note any legitimate interests assessment[1].
Set retention periods
Agree how long each record is kept and switch on deletion or archiving to match[2].
Secure the basics
Turn on two-step login, restrict access by role, encrypt laptops and train staff to spot phishing.
Tell people
Publish privacy notices for each audience and link them from every form and email footer.
Rehearse a breach
Agree who decides whether to report, and practise once a year with a realistic scenario.
Frequently asked questions
Do we need consent to keep a buyer's details on file?
Usually not. Registering a buyer's requirements and contacting them about matching properties can normally rest on legitimate interests, provided they know about it and can object. Marketing emails and texts have separate PECR rules[1].
Is a negotiator's personal mobile covered by UK GDPR?
Yes, if it holds client data for work. That includes contacts, call logs and messaging apps. Either provide work phones or set clear rules and controls for personal devices.
Can we send the full referencing report to the landlord?
Only what is necessary. Many agencies send the outcome and the key facts behind it. Sharing more needs a clear reason and should be explained in the applicant's privacy notice[2].
What is the biggest data risk for a small agency?
Security. Phishing was the most common attack on UK businesses in 2025/26, experienced by 38%[4], and agencies hold exactly the bank and identity details fraudsters want.
References
legislation.gov.uk (The National Archives) (2016). UK GDPR Article 6: Lawfulness of processing (opens in a new tab) ↑
legislation.gov.uk (The National Archives) (2016). UK GDPR Article 5: Principles relating to processing of personal data (opens in a new tab) ↑
Department for Science, Innovation and Technology (GOV.UK) (2026). Cyber security breaches survey 2025/2026 (opens in a new tab) ↑
Department for Science, Innovation and Technology (GOV.UK) (2026). Cyber security breaches survey 2025/2026 (opens in a new tab) ↑
GOV.UK (2026). Pay the data protection fee (opens in a new tab) ↑
HM Revenue & Customs (GOV.UK) (2021). Money laundering supervision for estate agency businesses (opens in a new tab) ↑
Department for Science, Innovation and Technology (GOV.UK) (2024). Public attitudes to data and AI: Tracker survey (Wave 4) report (opens in a new tab) ↑