LawFuzeICO registered
For SolicitorsMethodologyTrustPricing
Sign inGet started→

Methodology · Public disclosure

How LawFuze works.

An AI research assistant for qualified UK legal professionals. This page explains where our data comes from, how we process it, which models we use, what we don't do, and how we're held accountable. Part of our UK legal-AI transparency commitments.

Last updated 17 May 2026·Next review 17 August 2026

Processing pipeline

Five stages, live at public launch

Today, case-law search runs at query time over the official public sources, with every citation verified before a draft can leave. At public launch, every judgment on Find Case Law will move through this same fixed pipeline, logged and versioned, with daily reconciliation to pick up revisions and withdrawals.

01

Fetch

Daily Atom feed from Find Case Law + LegalDocML per judgment.

02

Parse

Metadata, parties, citations and paragraph structure.

03

Embed

Section-level search index, stored in isolation per firm.

04

Graph

Citation network — 'cites' and 'cited-by' edges.

05

Reconcile

Daily sweep — withdrawn records suppressed within 24h.

01

Fetch

Daily Atom feed from Find Case Law + LegalDocML per judgment.

02

Parse

Metadata, parties, citations and paragraph structure.

03

Embed

Section-level search index, stored in isolation per firm.

04

Graph

Citation network — 'cites' and 'cited-by' edges.

05

Reconcile

Daily sweep — withdrawn records suppressed within 24h.

Data residency & security

UK primary · EU inference · documented transfers

UK-only primary hosting

Microsoft Azure UK (London) — compute, Postgres, Blob Storage and Key Vault. No AWS.

Encrypted end-to-end

TLS 1.3 in transit, AES-256 at rest via Azure Key Vault-managed keys.

EU AI inference

Anthropic EU (Frankfurt) for generation. OpenAI text-embedding-3-large for retrieval today; moves to Azure OpenAI UK at public launch (1 Sep 2026) so the entire path becomes UK-resident. US transfers operate under ICO IDTAs until then.

Tenant isolation

Per-firm namespace in the search index and row-level scoping in Postgres.

Retrieval & ranking

What we use — and what we refuse to

What we do

  • Semantic search over the search index
  • Citation-graph expansion for foundational authorities
  • Re-ranking by recency, jurisdiction and citation weight
  • Every query runs inside a single tenant boundary

What we refuse to do

  • No ranking on personal-name fields
  • Query parser blocks free-text person lookups
  • No merging with external personal-data sources
  • No judge-identity input to outcome-prediction features

Language models

Inference only. Never training.

We call large language models at inference time via vendor APIs. We do not train, fine-tune or otherwise update any model on customer, judgment or query data.

Claude

Vendor: Anthropic PBC

Role
Primary model — grounded answer generation from retrieved judgment extracts.
Data retention
No-training default on paid API. Zero-retention endpoint used for customer-matter queries where available.
Known limits
Can hallucinate citations when retrieval returns ambiguous context — mitigated by citation-verification before render.

text-embedding-3-large

Vendor: OpenAI, L.L.C.

Role
Retrieval only — embeds document chunks (3072-dim vectors) for the RAG pipeline. Not used for generation.
Data retention
No-training default on paid API. The search index is stored in our Weaviate database, not retained by OpenAI.
Known limits
Provider-side data path is US today; moves to Azure OpenAI Service UK at public launch (1 Sep 2026) so the entire retrieval path becomes UK-resident.

Every model change goes through a change-management process with before/after evaluation before merge.

Known limitations

Six things the product can't do

Part of the product, not a disclaimer to hide from. Each appears as an in-product notice on every AI response.

The corpus is incomplete.

Find Case Law does not cover every court or tribunal. Coverage skews to higher courts and recent years.

Records change.

Judgments can be revised or withdrawn. Every cited authority is checked against the official source at the point it is used; an authority that no longer resolves is blocked, and every output is version-stamped.

AI can hallucinate.

LLMs can invent citations. We ground in retrieved extracts, verify citations, but a qualified legal professional must verify.

Bias is a constant risk.

Both the data and the AI can exhibit bias along protected characteristics. Weekly eval probes + user reports.

Not legal advice.

LawFuze produces research, not advice. Every decision must be made by a qualified legal professional exercising independent judgement.

Snapshot-dated answers.

Every output is stamped with the corpus snapshot date. Law changes. Older snapshots may not reflect the current state of the law.

Governance · MoJ nine principles

Nine principles — all accepted

Ministry of Justice principles for computational analysis of court records. Every principle is part of our UK legal-AI transparency commitments and an engineering invariant in the product.

P1

Dignity of the court

Verbatim citations, prohibited interpretive language, 24h review on flagged outputs.

P2

Independence of the court

No judge-level analytics, no prediction of pending cases, no marketing to courts.

P3

Appropriate scrutiny

Preserve court redactions; block person-name retrieval; no external data merging.

P4

Anti-discriminatory harm

Weekly protected-characteristic bias probes; user-reporting channel with 24h SLA.

P5

Anti-bias

Stable benchmark with regression alerts; external legal-ethics advisor before first paying customer.

P6

Personal privacy

UK-only data residency; DPIA under UK GDPR Art 35; no training on customer data.

P7

Discoverability

Auth wall, noindex meta + X-Robots-Tag headers on authenticated routes, robots.txt disallow.

P8

Algorithmic transparency

This page, model cards, visible AI badge on every output with a link back here.

P9

Accurate data representation

Every cited authority verified against the official source at the point of use; authorities that no longer resolve are blocked; version-stamped outputs.

Attribution

We link back to the source, always.

Every judgment we surface links back to the authoritative source on caselaw.nationalarchives.gov.uk. We do not operate an alternative case-law viewer. Our use of UK judgments is governed by the Computational Analysis Licence granted by The National Archives. Open Government Licence v3.0 applies to legislation we reference from legislation.gov.uk.

noindex on authenticated routes·Auth wall on judgment content·No sitemap entries

See an output that looks wrong?

Tell us. We respond within 24 hours and publish anonymised incident summaries in our annual transparency report. Customers, regulators, academics — anyone can reach the compliance team directly.

legal@lawfuze.com

Data-protection enquiries: same address with "DPA" in the subject line. Founder escalation: arjun@lawfuze.com.

Privacy·Terms·Compliance·Licence programme
LawFuze

An AI co-worker for UK solicitors — research and drafting support, supervised by the solicitor on the file. Hosted in UK data centres.

Product

  • Chat AI
  • Document Intelligence
  • Matter Management
  • Time & Billing
  • Compliance & Audit
  • Security
  • Legal Research (Phase 2)
  • Judge Intelligence (Phase 2)
  • War Room (Phase 2)
  • Methodology

Company

  • About
  • For Solicitors
  • Get started
  • Contact

Trust & Legal

  • Trust Center
  • Privacy Policy
  • Sub-processors
  • Terms of Service
  • Acceptable Use
  • DPA Template
  • Beta Agreement
  • Complaints
  • Cookies
  • Accessibility
  • DPO
  • Disclaimers
AI Disclaimer

LawFuze provides AI tools that support qualified legal professionals with research and drafting. AI outputs are not legal advice. Every AI output carries a confidence indicator and source citations, and must be reviewed by a qualified solicitor before reliance. The supervising solicitor — not the AI — remains responsible to the client under the SRA Code of Conduct.

Regulatory Notice

LawFuze is a technology platform and is not a law firm. We do not provide legal advice or legal services. Solicitors using LawFuze remain individually responsible for compliance with the SRA Standards and Regulations and the SRA Code of Conduct. Use of AI tools does not diminish a solicitor's duty to their clients or professional obligations.

Data Protection

LawFuze processes personal data in accordance with the UK General Data Protection Regulation (UK GDPR) and the Data Protection Act 2018. Customer data is stored in the UK on UK data centres. AI inference uses named sub-processors in the EU and US; where data flows outside the UK/EEA we rely on ICO International Data Transfer Agreements (IDTAs) supported by published Transfer Risk Assessments — treat IDTA execution as an in-progress control until each is signed and filed. The current sub-processor list and IDTA status of each is published on our sub-processor register. For data subject rights including access, rectification, erasure, and portability, contact legal@lawfuze.com.

Security & Compliance Roadmap
ICO controller registration· LiveUK GDPR aligned· LiveDPIA + ROPA published· Livelegislation.gov.uk + TNA Find Case Law (OGL v3.0, read use)· LiveCyber Essentials Plus· In progressDeeper case-law search index (public UK judgments)· In progressPII / Cyber / D&O insurance· In progressISO 27001· On roadmapSOC 2 Type II· On roadmap

Certifications in progress or on the roadmap are not current attestations. We publish certificate references only once an accredited body has issued them.

© 2026 LawFuze Ltd. All rights reserved.

Registered in England & Wales • Company No. 16800372

Support: support@lawfuze.com

ICO controller registration ZC147676 (14 May 2026 — 13 May 2027) — listed on the Trust Center. VAT registration in progress; reference will be added on receipt.

Data Protection Officer: dpo@lawfuze.com · Security: security@lawfuze.com · Complaints: /complaints