Confidentiality is in the code
The SRA Code of Conduct requires solicitors to keep client affairs confidential. Matter material stays in the firm's environment.
Private AI / law firms / the UK
Private AI for UK law firms: precedent search, obligations, and first drafts from approved firm material. Solicitors owe confidentiality to clients under the SRA Code of Conduct, and legal professional privilege attaches to communications — the system is built so both hold.
Example material only / no client matter
Why it matters here
Confidentiality and privilege are duties the deployment is designed around, not marketing terms.
The SRA Code of Conduct requires solicitors to keep client affairs confidential. Matter material stays in the firm's environment.
Legal professional privilege attaches to communications with clients. The system's access rules and data path are documented so that protection is not undermined.
The setup is designed for review against the UK GDPR and the Data Protection Act 2018, with named processors and a London-region default.
What teams use it for
The assistant supports the firm. It does not replace legal advice, review, or sign-off.
Precedents, policies, engagement letters, and matter material.
Separate users, teams, matters, and sources where the workflow requires it.
Runbook, training, credentials, source map, tests, and known limitations.
First project
A small, approved archive — not the entire matter history on day one.
One person responsible for feedback and access.
Precedents, policies, and matter material that the practice group actually searches.
Source references and a clear “not found” boundary.
Other teams, sources, languages, or actions after the first workflow works.
Why trust Pristine3D?
Pristine3D Ltd builds and operates live digital products, and we run private AI workflows internally as part of our own operations. We scope around your real workflow: the documents you own, the questions your team asks, and the access boundary you approve. Based in Lagos, Nigeria, we work remotely with clients worldwide.
Based in Lagos, Nigeria, Pristine3D currently builds and operates smartcards.ng, venu.ng, photoshoot.ng, and ugc.ng in production.
One input, one output, one test set, and one person who owns the result. We scope a real workflow instead of a transformation programme.
Cloud, model, storage, and messaging accounts stay in your name. The chosen data path, access rules, test record, documentation, and training are part of the agreed scope.
Pricing / fixed scope
The final quote follows the workflow. Infrastructure and model bills stay on your accounts.
One workflow for a small team, with training and handover.
See the one-workflow packageMultiple sources, roles, integrations, and admin handover.
See the deploymentStandard care for one delivered workflow. Optional. Larger deployments and active monitoring are separately scoped.
See supportArchitecture review from $500. Standard annual support is $3,000 / ₦1.5m per year for one delivered workflow. New workflows, integrations, active monitoring, and infrastructure are separately scoped; infrastructure, model, storage, and messaging bills stay on client accounts. Full pricing and what changes the quote
Straight answers
Yes. Hosting in eu-west-2 (London) is the default, with on-prem as the strict option. The data path is documented either way.
Privilege belongs to the firm and its client. The system supports it by keeping communications inside the firm's environment under controlled access.
It prepares first drafts from the firm's own material for a lawyer to review and settle. It does not give legal advice.
Yes, from £2,900 for a first workflow, with USD and naira floors unchanged.
Own your knowledge base
Documents, the retrieval index, access rules, and the workflows built around them are the asset, and they compound. We deploy so the knowledge base stays yours: on your accounts, in the environment you choose, under access rules your team defines. The model behind the answers is a connector, so the knowledge base moves with you, not with a vendor.
The document store, metadata, and retrieval setup live on accounts you own. No vendor holds the corpus.
Change the model provider, move regions, or go local without rebuilding the knowledge base or the workflow.
Every improvement to the corpus improves the answers, and the improvement stays with you, not with a vendor.
Keep exploring
Start with the search problem
Describe the documents and the questions your team keeps asking. We will recommend a focused first step.