Key takeaways
- Decide the device model first (firm-owned only, managed apps, browser-only or full enrolment); the policy follows from that choice.
- Personal phones are where client email, messaging apps and consumer AI tools meet, so the policy must cover apps as well as hardware.
- Minimum controls: screen lock, multi-factor sign-in, managed work apps, remote wipe of work data and a fast route to report a lost device.
- A lost phone holding client data can start the UK GDPR 72-hour notification clock, so staff must report within the hour, not the next morning.
Why personal devices deserve their own policy
Most solicitors already read client email on a personal phone, take a call from a client on a mobile while away from the office, or log in to the case management system from a home laptop. The question is not whether personal devices touch client data but whether the firm has decided, in writing, how they may.
The wider picture is not reassuring. Just over four in ten UK businesses (43%) reported a cyber breach or attack in the last 12 months, and phishing featured for 85% of those affected[1]. Only 61% restrict access to organisation-owned devices, and only 40% require two-factor authentication for networks or applications[1].
Law firms have been studied directly. When the SRA visited 40 firms for its cyber security review, 18 allowed staff to reach firm systems through an online portal on a personal device, and nine did not monitor who had accessed their systems at all[2]. In 23 of the 30 cases where firms were directly targeted, more than £4m of client money was stolen in total[2].
There is also a newer reason. 55% of UK employees say they use AI for work or education, against around 35% of businesses reporting AI use[3]. On a personal phone, a consumer AI app is one paste away from a client email. Your device policy and your rules on AI tools need to agree with each other.
Choose your device model before you write a word
The National Cyber Security Centre sets out five actions for BYOD: determine your objectives, user needs and risks; develop the policy; understand the extra costs and implications; choose a deployment approach; and put technical controls in place[4]. Most small firms skip straight to the policy. Pick the model first, because every clause depends on it.
| Model | What staff can do | Controls the firm needs | Usually suits |
|---|---|---|---|
| Firm-owned devices only | No client data on personal kit at all | Issue phones and laptops; block sign-in from unknown devices | Firms handling high-value conveyancing funds or sensitive crime and family files |
| Managed work apps on personal phones | Email, calendar and case apps inside a managed container | App protection policies, PIN on the work apps, selective wipe | Most small and mid-sized practices |
| Browser or virtual desktop only | Work in a browser session; nothing saved locally | Conditional access, session timeouts, no downloads | Occasional home working, consultants, locums |
| Full enrolment of a personal device | Device treated like a firm device | Device management profile, full wipe rights | Rarely popular with staff; use only with clear consent |
Whichever model you choose, write down who is in scope: partners, fee earners, secretaries, reception, cashiers, trainees, consultants and contractors. Partners are often the heaviest personal-device users and the least likely to accept controls, so the policy needs their sign-off first.
Questions to settle with the partners first
Drafting goes faster once the people who will be asked for exceptions have agreed the answers. Put these to the partners in one meeting and record the decisions.
- Will the firm pay towards personal phone contracts, or issue phones to anyone who refuses controls on their own device?
- Which roles may work from a personal laptop, and which must use a firm machine or a browser session only?
- Is client contact by text or messaging app allowed, and if so, from which numbers and accounts?
- Who may approve an exception, how long does an exception last, and where is it recorded?
- What happens when someone refuses to install the work app: no mobile access, or a firm-issued phone?
- How will the firm handle a device shared with family members, such as a home tablet?
Write the answers into the policy as decisions, not aspirations. 'Client contact by personal WhatsApp is not permitted' is easier to follow and to enforce than 'staff should avoid using personal messaging where possible'.
Clauses a law firm BYOD policy should contain
Keep the policy short enough to read in five minutes. Two or three pages is plenty for most firms; put technical settings in a separate checklist for whoever runs IT.
- Purpose and scope: which devices, which people and which systems the policy covers.
- Approved access routes: the work apps or browser portal staff must use, and a plain statement that client documents are never saved to personal storage, photo galleries or personal cloud accounts.
- Device standards: supported operating system versions, automatic updates on, screen lock of six digits or biometrics, encryption enabled, no jailbroken or rooted devices.
- Messaging: whether client contact on personal WhatsApp or text is allowed at all, and if so how messages are saved to the matter file.
- Calls: recording, voicemail greetings and caller ID on personal numbers, and what to do when a client keeps calling a personal mobile.
- AI and other apps: no client information in consumer AI tools, transcription apps or keyboard apps that send text to a third party.
- Monitoring and privacy: exactly what the firm can see (work apps, sign-in logs) and what it cannot (personal photos, messages, browsing).
- Loss, theft and leaving: the reporting deadline, the remote wipe the employee agrees to, and the exit checklist.
- Confidentiality: a reminder that the duty under the SRA Code of Conduct to keep the affairs of current and former clients confidential applies on every device[5].
- Acknowledgement: a signed or recorded acceptance, renewed when the policy changes.
Minimum technical controls
A policy without controls relies on memory. These are the controls that turn it into something enforced, in the order most small firms can put them in place.
Require multi-factor sign-in
Turn it on for email, case management and remote access. It is the single control that most often stops a stolen password becoming a stolen inbox.
Allow only approved apps
Use conditional access so firm email can only be opened in the managed app or a browser session, not in the phone's default mail app.
Protect the work container
Set a separate PIN, block copy and paste from work apps into personal apps, and block saving attachments to personal storage.
Set timeouts
Short session timeouts for browser access and automatic sign-out after inactivity in case management.
Enable selective wipe
Test that you can remove work data from a device without touching personal photos, and record that you tested it.
Review sign-in logs monthly
Look for unknown devices, sign-ins from unusual countries and accounts of people who have left.
Lost phones, leavers and breaches
Under UK GDPR Article 33, a controller must notify a personal data breach to the ICO without undue delay and, where feasible, within 72 hours of becoming aware of it[6]. A phone left on a train on Friday evening and reported on Monday morning has already eaten most of that window.
- Staff report a lost or stolen device to a named person within one hour, by phone, at any time of day.
- The named person triggers a selective wipe and revokes active sessions immediately.
- They record what data the device could reach, whether it was encrypted and locked, and when the wipe was confirmed.
- The data protection lead decides whether the loss is a notifiable breach and documents the reasoning either way.
- For leavers, access is removed on the last working day, the work container is wiped, and the exit checklist is signed.
Write the out-of-hours reporting number into the policy and onto a card in every phone case. The reporting deadline only works if people know who to call at 10pm.
Example: a six-person private client practice
Example: a fictional practice with two partners, two fee earners, a secretary and a receptionist. Everyone reads email on a personal phone; one partner also signs off wills on a home laptop.
The firm chooses managed work apps for phones and browser-only access for the home laptop. It turns on multi-factor sign-in, blocks the default phone mail apps, and bans client contact on personal messaging apps, routing all client messages through the firm's phone system and email instead.
In the first month, sign-in logs show an old tablet belonging to a former trainee still connected. It is removed the same day. The policy, signed by all six, runs to two pages. The setup took one afternoon with the firm's IT provider and a short team meeting to explain why.
Rolling it out without resistance
Explain the trade: staff keep the convenience of their own phone, and the firm can only see and remove work data. People accept controls more readily when they know what is not monitored.
Run the change alongside your data protection training, check that your cyber insurance wording does not exclude losses from personal devices, and review the policy at least once a year or whenever you change phone systems, case management or remote access.
Keep an exceptions register. Each entry records who asked, what was allowed, why, and the date it ends. Review it at the same time as the policy, and close any exception whose reason has gone. A register with no end dates is a sign the policy is being quietly ignored.
Frequently asked questions
Can a law firm insist on wiping an employee's personal phone?
Only with clear, recorded agreement, and most firms avoid it. Managed work apps let you remove firm data without touching personal content, which is easier to justify and to explain.
Is WhatsApp acceptable for talking to clients?
Only if the firm decides it is, sets rules for saving messages to the matter file and controls the account. Many firms ban personal messaging for client contact and offer a firm channel instead.
Does a lost phone always need reporting to the ICO?
No. If the device was encrypted, locked and wiped quickly, the risk may be low. The firm must still assess it promptly and record its decision, because the 72-hour clock runs from awareness.
Who should own the BYOD policy?
A named partner or the COLP, supported by whoever runs IT. Ownership matters most when someone senior asks for an exception.
References
Department for Science, Innovation and Technology (GOV.UK) (2025). Cyber security breaches survey 2025 (opens in a new tab) ↑
Solicitors Regulation Authority (2020). Cyber Security - A thematic review (opens in a new tab) ↑
Office for National Statistics (2026). Artificial intelligence in UK businesses: 2023 to 2026 (opens in a new tab) ↑
National Cyber Security Centre (2025). Device security guidance: Bring your own device (BYOD) (opens in a new tab) ↑
Solicitors Regulation Authority (2025). SRA Code of Conduct for Solicitors, RELs, RFLs and RSLs (opens in a new tab) ↑
legislation.gov.uk (The National Archives) (2016). UK GDPR Article 33: Notification of a personal data breach to the supervisory authority (opens in a new tab) ↑