In February 2026, the SRA authorised LawFairy as a technology-led law firm operating in UK immigration law. The firm uses deterministic, rule-based AI rather than traditional practitioners to deliver eligibility assessments and application preparation. AI-driven legal services are no longer a fringe proposition. The regulator is authorising firms built around technology.
That should concentrate minds. Few firms need to become LawFairy, but the firms still debating whether to adopt AI now compete with firms that have regulatory approval to deliver legal services through AI systems. The live question is how to use AI without compromising professional obligations.
For most law firms, the answer depends on three things: what the SRA actually requires, what happens to privilege when client data leaves the firm’s infrastructure, and what architecture satisfies both.
What the SRA actually requires
The SRA regulates on outcomes, not on technology choices. The SRA Standards and Regulations do not mention AI explicitly. They do not need to. The obligations that govern AI adoption already exist in the Principles and the Code of Conduct.
Principle 2 requires solicitors to act in a way that upholds public trust and confidence in the profession. Principle 7 requires them to act in the best interests of each client. Paragraph 3.5 of the Code of Conduct keeps supervisors accountable for work carried out through others. Paragraph 6.3 requires solicitors to keep the affairs of current and former clients confidential unless disclosure is required or permitted by law or the client consents.
The SRA’s own Risk Outlook report on AI in the legal market makes the position explicit: “you will remain responsible and accountable for the outputs from AI you are using.” The report adds that firms cannot delegate accountability to an IT team or external provider.
It identifies three confidentiality threats from AI:
- Direct exposure from staff uploading client data to online AI systems
- Training data leakage where confidential data is transferred to a provider for model training
- Cross-case contamination where an AI system replicates confidential details from one matter in its response to another
The SRA says firms will need “clear rules covering” AI use, and that supervision and guidance should cover the difference between casual use of tools like ChatGPT and systems the firm has formally adopted. It also expects clients to be suitably informed of how AI is involved in their cases.
The framework is outcomes-focused, so there is no prescriptive checklist to follow and no safe harbour from ticking boxes. A firm must be able to demonstrate, at any point, that its use of AI satisfies the Principles. If the regulator asks how client confidentiality is maintained when data is processed by a third-party AI system, the answer needs to be specific, documented, and defensible.
The privilege problem
Legal professional privilege is the foundation of the solicitor-client relationship and a substantive right. It is also easy to compromise through technology choices that nobody in the firm’s management thought to scrutinise.
When a law firm sends client data to a SaaS AI provider, that data typically leaves the firm’s infrastructure and is processed on servers controlled by a third party. If that provider is incorporated in the United States or processes data on US-hosted infrastructure, the data falls within the reach of FISA Section 702.
FISA Section 702 authorises US intelligence agencies to compel US-based service providers to disclose communications of non-US persons located abroad, without an individual warrant. Providers are bound to secrecy, so neither the data subject nor the customer is told. A UK law firm using a US-hosted AI tool would have no way of knowing whether privileged client material had been accessed under a FISA order.
The risk follows from processing data on infrastructure subject to US jurisdiction. The Court of Justice of the European Union reached precisely this conclusion in Schrems II (Case C-311/18), which invalidated the EU-US Privacy Shield on the grounds that US surveillance law does not provide adequate protection for personal data transferred from the EU. The court found that Standard Contractual Clauses alone cannot compensate for a legal framework that permits mass surveillance of foreign communications.
Since 2023, the EU-US Data Privacy Framework and its UK extension have given firms a lawful route for transfers to certified US companies. They do not change what US surveillance law permits, which is why many firms still want privileged material kept out of US-hosted systems. Separately, Article 28 of the UK GDPR requires a contract with any processor of personal data that specifies the subject matter, duration, nature, purpose and type of data processed. Many SaaS AI agreements cover this only in general terms.
For privileged material, the exposure is worse than a data protection violation. Privilege depends on confidentiality. If a firm transmits privileged material to a third-party system without adequate safeguards, and that material is accessed or disclosed, the privilege may be lost. The firm bears the burden of maintaining confidentiality through its technology choices, and a passive assumption that a vendor will protect it is not enough.
A firm that processes privileged client material through a US-hosted AI service is accepting a risk that the SRA’s confidentiality obligations, the Data Protection Act 2018 and the common law of privilege all require it to mitigate. A better contract with the vendor helps. The stronger mitigation is keeping the data in an environment the firm controls, in a region it has chosen.
The supervision gap
The SRA’s accountability framework creates a second problem with hosted AI services: supervision.
Paragraph 3.5 requires that solicitors who supervise or manage others remain accountable for the work carried out through them. The SRA’s Risk Outlook tells firms to supervise AI systems and staff use of them. A partner who relies on an AI tool to draft a contract clause, review a disclosure bundle, or summarise case law is accountable for the output. That accountability requires the ability to inspect, verify, and audit the system’s reasoning.
Most SaaS AI tools are opaque. The user submits a prompt and receives an output. There is no audit trail showing what the model considered, what context it retrieved, what confidence level it assigned, or what alternative outputs it discarded. The firm receives a result but cannot reconstruct the reasoning path. When the SRA asks how a piece of work was supervised, “the AI produced it and a solicitor reviewed the output” may not satisfy a regulator that expects documented oversight of the decision-making process.
The SRA’s Risk Outlook report advises firms: “Do not trust an AI system to judge its own accuracy.” That recommendation presupposes the firm has the ability to independently verify accuracy. With a hosted tool that provides no transparency into its reasoning, independent verification is limited to checking whether the output looks right. That is pattern matching rather than supervision.
Architecture that satisfies both obligations
A private deployment architecture addresses the privilege and supervision problems together. The design principles are simple, but they must be built in rather than bolted on.
Data boundary enforcement
The AI platform runs in a dedicated environment, either as a managed service in the firm’s preferred region (UK, EU or US) or inside the firm’s own cloud tenancy. Models are reached through private endpoints under terms that exclude training on client data, with zero data retention available. Client data is not sent to consumer AI services or shared multi-tenant tools.
This narrows the exposure considerably. Data stays in a region the firm chose, the model provider keeps no copy, and there is no routine cross-border transfer to assess under Schrems II. It does not remove every question: a US-incorporated cloud provider remains subject to US law wherever its data centres are, so the firm’s risk assessment should still cover it. Privilege is easier to defend because the data sits behind the same kind of boundary as the firm’s other confidential systems.
For most UK firms, this means a UK or EU cloud region, with encryption keys held in a key vault the firm controls. The firm controls access, retention and deletion.
Confidence scoring and human review gates
AI agent outputs should carry a confidence score derived from the quality and relevance of retrieved context, the consistency of the model’s reasoning, and the degree of alignment with known precedent or firm knowledge. The score decides what happens next.
High-confidence outputs on routine tasks (document classification, metadata extraction, standard clause identification) can proceed to a review queue. Low-confidence outputs, or outputs on matters involving judgement, are routed to mandatory human review before any action is taken. Every citation is checked against the source document, and the workflow runs as fixed, versioned steps, so the same task follows the same path each time.
This maps directly to the SRA’s supervision requirements. The firm can demonstrate that every AI-assisted output was subject to a governance process calibrated to risk. The audit trail records the confidence score, the routing decision, the reviewer’s identity, and the reviewer’s determination. When a regulator asks how supervision was maintained, the firm produces the log.
Immutable audit trails
Every interaction with an AI agent is recorded: the input, the retrieved context, the model version, the reasoning steps, the output, and any human review decision. The log is append-only and tamper-evident. Records cannot be modified or deleted.
The log supports the SRA’s expectation of accountability and provides the evidence base for responding to complaints, regulatory inquiries, or professional negligence claims. It also gives the firm’s management visibility into how AI tools are actually being used, which effective supervision under paragraph 3.5 depends on.
Role-based access controls
Access to AI agents and the data they process is governed by the same permission model as the firm’s other systems. A trainee working on a corporate transaction cannot query an agent loaded with family law matter data. A paralegal can run document extraction but cannot approve a client-facing output. The controls mirror the firm’s existing information barriers and supervision hierarchies.
What this means in practice
A mid-sized law firm deploying AI agents on private infrastructure can:
- Process privileged client material through AI systems while keeping it in a region and environment the firm controls
- Demonstrate to the SRA that every AI-assisted output was subject to documented supervision proportionate to the risk
- Produce a complete audit trail for any matter, any agent interaction, any output, at any time
- Maintain professional indemnity insurance coverage without the uncertainty of explaining US-hosted data processing to underwriters
- Train staff with clear, enforceable rules about AI use backed by technical controls rather than policy documents alone
The SRA’s approach to technology is collaborative. The regulator has stated it wants to support innovation and has operated an innovation space for firms testing new approaches. But that support operates within the existing Principles. A firm that cannot demonstrate how its AI deployment meets the Principles and its confidentiality duties will find the collaborative tone sharpens.
The competitive reality
The SRA’s authorisation of LawFairy reflects a regulatory position that AI in legal services is acceptable, provided the outcomes for clients are protected. Firms that delay AI adoption on the grounds that the regulatory position is unclear are misreading the situation. The position is clear. The Principles apply. The firm is accountable. The question is whether the firm’s architecture supports that accountability.
Private deployment is not the only way to use AI in a law firm. For work involving privileged material, confidential client data or outputs that need documented supervision, it is the architecture that fits the SRA’s outcomes-based framework without asking the firm to accept risks its professional obligations do not permit. See how CompleteFlow works for law firms and the controls on the security page.