Key takeaways
- Article 13 sets the minimum content: who you are, why and on what basis you use data, who receives it, transfers, retention, rights and complaints[1].
- Since 19 June 2026 notices must also tell people they can complain to the firm itself, and firms must acknowledge complaints within 30 days[1][2].
- Visitors already struggle to find regulatory information: only 56% found PII and ombudsman details easy to locate[3].
- Layer it: a short notice at each form and on calls, linked to a full notice in the footer of every page.
- Write for the actual audiences, prospective clients, opponents, job applicants and referrers, in plain English.
Who reads a law firm's privacy notice
A firm's privacy notice is read by more people than most partners assume, and for more pointed reasons. Prospective clients check it before typing sensitive details into an enquiry form. Opponents and their solicitors read it when deciding whether to make a subject access request. Job applicants, referrers, experts and corporate clients doing supplier due diligence all look at it. A notice copied from a template, naming the wrong entity or describing systems you no longer use, undermines the trust the rest of your site is trying to build.
It also sits alongside other information the SRA requires on your website. Authorised firms must display their SRA number and digital badge prominently[4] and publish their complaints procedure, including how and when to complain to the Legal Ombudsman and the SRA[5]. Consumers do not always find that information easily. In the 2026 tracker survey, 74% of people who shopped around found cost information easy to find[6], but only 56% found information about professional indemnity insurance and the right to complain to an ombudsman easy to locate[3].
What the law requires you to say
Article 13 of UK GDPR lists what you must tell people when you collect data from them, at the time you collect it[1]. In summary:
- Your identity and contact details, and your DPO's contact details if you have one.
- The purposes of each use of data and the lawful basis for it, including the legitimate interests you rely on.
- The recipients or categories of recipients.
- Any transfer outside the UK and the safeguard relied on.
- How long you keep data, or the criteria used to decide.
- The rights people have, including access, rectification, erasure, restriction, objection and portability, and the right to withdraw consent.
- The right to complain to you directly and the right to complain to the regulator.
- Whether providing the data is required and what happens if they do not provide it.
- Any automated decision-making with significant effects, and how it works.
The complaint right is new. Since 19 June 2026, notices must tell people they can complain to the controller[1], and controllers must make complaining easy, for example with an electronic complaint form, acknowledge complaints within 30 days and tell the complainant the outcome[2][7]. If your notice only mentions the regulator, it is out of date.
Where you collect data from someone other than the individual, an opponent's details from your client for example, Article 14 applies instead, with similar content. For legal work, the exemptions for privileged and confidential information often mean you do not have to notify the opponent directly, but your website notice should still describe that processing in general terms.
A section-by-section checklist
Who we are
The full legal name of the controller, registered office, SRA number and a role mailbox for data protection questions.
Information we collect
Separate headings for website visitors, enquirers, clients, other parties to matters, job applicants and referrers. Mention calls, recordings, forms, identity checks and cookies.
Why we use it and our lawful basis
A short table of purpose against basis: providing legal services under contract, anti-money laundering checks under legal obligation, marketing under consent or legitimate interests.
Sensitive information
Explain that matters can involve health, criminal and other special category data, and the conditions you rely on.
Who we share it with
Counsel, experts, courts and tribunals, HM Land Registry, banks and lenders, identity verification providers, IT and telephony suppliers, insurers and regulators.
International transfers
Which suppliers store or access data outside the UK and the safeguard relied on, in plain terms.
How long we keep it
A summary of your retention schedule by type of record, with a link or offer to provide the full schedule.
Your rights and how to complain
Each right in one line, how to exercise it, the complaint route to the firm and the route to the regulator.
Changes
The date of the current version and how you will tell people about material changes.
Layering and placement
Nobody reads a long legal notice before submitting an enquiry. A layered approach gives people the essentials when they need them and the full detail when they want it.
| Touchpoint | Short notice | Link to |
|---|---|---|
| Enquiry form | We use these details to respond to your enquiry and check for conflicts. Please give only an outline; do not include sensitive details yet. | Enquirers section of full notice |
| Telephone line | Calls may be recorded for quality and training. Our privacy notice explains how we use call information. | Website address read out or sent by text on request |
| Client care letter | A paragraph summarising use, sharing and retention for this matter | Full notice and retention schedule |
| Careers page | How applications are used, shared and kept | Job applicants section |
| Newsletter sign-up | What you will receive and how to unsubscribe | Marketing section |
Put a footer link on every page, labelled Privacy notice, not Legal. Keep cookie information in a separate cookie notice so the privacy notice stays readable. If calls to the firm are answered by an AI Employee such as Ava, say so in the telephone section and explain what is recorded, who sees the notes and how long they are kept.
Plain English, not boilerplate
Law firms have an advantage here: they employ people who write clearly for a living. Use it. Replace we may process your personal data for the purposes of our legitimate interests with we use your details to check for conflicts of interest before we agree to act, because we have a legitimate interest in meeting our professional duties. Short sentences, active voice and concrete examples do more for transparency than any number of defined terms.
- Name real categories of supplier rather than saying selected third parties.
- Give retention periods or criteria rather than as long as necessary.
- Say which data you need and why, for example identity documents for anti-money laundering checks.
- Avoid we may when you do. If you record calls, say so.
Keeping the notice true over time
Privacy notices go stale quietly. The website is rebuilt, a new identity verification provider is added, the firm starts recording calls, and the notice still describes the systems of three years ago. Regulators and claimants compare what you say with what you do, so a notice that overstates or understates your processing is a liability either way.
Tie the notice to the changes that should trigger a review. Put a line in your supplier onboarding checklist and your project template: does this change what our privacy notice says? Typical triggers are:
- A new or replacement case management, document, telephony or email system.
- A new supplier that receives client data, such as an identity check service, an outsourced typing team or an answering service.
- Any new use of artificial intelligence on client or enquiry data, including call summaries or document review.
- A new practice area that brings a different kind of sensitive data, such as crime or Court of Protection work.
- A change of legal entity, office address or data protection contact.
- A change to your retention schedule or marketing practices.
Keep the previous versions with their dates. If someone complains about how their data was used two years ago, you need to show what the notice said at that time, not only what it says now.
Common mistakes
- Naming a trading name or a defunct partnership as controller after converting to an LLP.
- Missing the complaint route to the firm itself.
- Describing cookies in detail but saying nothing about calls, recordings or enquiry forms.
- Listing rights without explaining how to use them or who to contact.
- No version date, so nobody can tell whether it reflects current systems.
- Templates that mention processing you do not do, such as profiling, or omit processing you do, such as identity verification through a third-party provider.
Example: a fictional firm reviews its notice after moving to a cloud case management system and adding an online identity check for conveyancing clients. The review adds the identity provider to the recipients list, explains the transfer safeguard for the case management supplier's support team abroad, updates the retention section to match the new schedule and adds the complaint route to the firm, with a link to an online complaint form.
For the cookie side of the website, see cookie consent on solicitors websites, and for the reform behind the new complaint right, our overview of the Data (Use and Access) Act 2025.
Frequently asked questions
Is a privacy policy the same as a privacy notice?
In practice the public-facing document is the notice. A privacy policy is often the internal document setting out how staff must handle data. Many firms call the public document a policy; what matters is that it contains the Article 13 information.
Do we need separate notices for clients and website visitors?
One notice with clear sections usually works, provided each audience can quickly find the part that applies to them. Some firms add a short client-specific summary in the client care letter.
How often should we review the notice?
At least annually and whenever you introduce a new system, supplier, service or type of processing, such as call recording, online identity checks or a new practice area.
Do we have to tell opponents we hold their data?
Article 14 normally requires notice where data is collected from someone else, but exemptions for privileged and confidential legal information usually apply. Describe the processing in your website notice in general terms.
References
legislation.gov.uk (The National Archives) (2026). UK GDPR Article 13: Information to be provided where personal data are collected from the data subject (opens in a new tab) ↑
legislation.gov.uk (The National Archives) (2025). Data (Use and Access) Act 2025, section 103: Complaints by data subjects (opens in a new tab) ↑
Legal Services Consumer Panel (2026). How consumers are choosing legal services (Tracker Survey 2026): regulatory information (opens in a new tab) ↑
Solicitors Regulation Authority (2025). SRA Transparency Rules (SRA number and digital badge) (opens in a new tab) ↑
Solicitors Regulation Authority (2025). SRA Transparency Rules (complaints procedure) (opens in a new tab) ↑
Legal Services Consumer Panel (2026). How consumers are choosing legal services (Tracker Survey 2026) (opens in a new tab) ↑
GOV.UK (DSIT) (2025). Data (Use and Access) Act 2025: data protection and privacy changes (opens in a new tab) ↑