Security

Where your firm’s data lives

A law firm holds other people’s secrets for a living, so the answers here are specific and the unfinished parts are marked as unfinished. If your questionnaire asks something this page does not cover, send it to us and a person will answer it.

Current posture

What is live, and what is not yet

Ghana Data Protection Act, Act 843

Aligned

AES-256 and TLS 1.3

Active

Row-level tenant isolation

Active

EU data residency, Frankfurt

Active

SOC 2 Type I

Planned

ISO 27001

Planned

Aligned means we have mapped our handling to the requirements and can walk you through it. Planned means work has not started or is not finished, and we will not describe it any other way until an auditor says otherwise.

Authorities

What the assistant is allowed to rely on

Confidentiality is one half of trust. The other half is knowing what an answer was built from. Lexqura answers only from a fixed corpus of primary law, and every claim in an answer names the source it came from, so you can open the section and read it yourself.

Jurisdictions live: 2
Primary sources: 55
Indexed passages: 14,063

Ghana: The 1992 Constitution, 38 Acts of Parliament, and the two principal sets of procedural rules. Sourced from GhanaLII, the Parliament of Ghana, and the Judicial Service.
United States: The Constitution, five titles of the United States Code, and all five sets of Federal Rules. Sourced from the Office of the Law Revision Counsel USLM releases and Cornell LII.
No case law: the corpus contains statutes, constitutions and procedural rules. It contains no reported decisions, and the assistant will not cite one. Where a question turns on authority we do not hold, the answer says so rather than filling the gap.

Isolation

One firm cannot see another firm

Every record carries the firm it belongs to, and the database refuses to return a row whose firm does not match the person asking for it. Isolation is enforced in the database itself with row-level security, not in the screens on top of it.

That distinction matters. If isolation lived in application code, a single mistake in one view could expose another firm’s matter. Here, the query simply returns nothing.

Encryption

Encrypted in transit and at rest

Traffic between your browser and Lexqura travels over TLS 1.3. Matter records, client details, documents in firm storage and backups are encrypted at rest with AES-256.

Passwords are never stored in a readable form, and sessions are scoped to your firm’s workspace.

AI and confidentiality

Your matters are not training data

We never train models on your matters, and your client data never leaves your firm’s workspace.

When you ask a research question or draft from a matter, the text needed to answer it is sent to our model provider, used to produce the answer in front of you, and nothing more. It is not retained to improve a model, and it is not pooled with any other firm’s work.

This is a negative promise, which is the only kind worth making about confidentiality. It is stated here so you can hold us to it, and it is written into our engagement terms for firms that ask.

Residency

You know where your data sits

Firm data is hosted in the European Union, in Frankfurt. Backups stay in the same region.

Ghanaian firms should note that Act 843 governs how personal data is handled wherever it is processed, not only where it is stored. Our handling is aligned to it, and we will answer questions from your data protection officer directly.

Firms on a Firm plan can agree residency in writing before any data is migrated.

Audit trail

Every action on a matter is recorded

Who opened it, who changed it, who uploaded the document, who sent the invoice, and when. The record is written as the work happens, not reconstructed afterwards.

Partners and admins can read the trail for any matter in their firm. It is the same record we would rely on if you ever had to show a client, a regulator or an insurer what happened and in what order.

Access control

Five roles, and they mean something

Access is granted by role, and a role is chosen when a colleague is invited. Roles can be changed by an admin or a partner at any time.

Admin: Runs the workspace: firm settings, billing, and who has access to what.
Partner: Sees the firm’s whole book of matters, and manages the team and billing.
Associate: Works the matters they are on, records their own time, and sees billing.
Paralegal: Works assigned matters, tasks and documents. No team or billing administration.
Secretary: Runs calendars, client records and filing. No team or billing administration.

Incident response

If something happens, you hear it from us

We keep a written incident procedure covering detection, containment, notification and review. If an incident involves your firm’s data, we tell you in writing with what we know at the time, what we are doing about it, and what we need from you.

We do not wait for an investigation to close before telling you it started. A late notification is worse than an incomplete one.

Sub-processors

The four companies in the chain

We use a small number of sub-processors, and we would rather you knew the shape of the list than be told there is nothing to see.

Hosting: Runs the application in the EU region.
Database and storage: Holds firm records and documents, with row-level isolation.
Model provider: Produces research answers and drafts. No training on your data.
Email delivery: Sends invitations, notifications and invoices.

The current list of named vendors, with their regions and terms, is in our security pack and is sent on request. We give notice before adding a sub-processor.

The rest of it, in writing

Everything above is a summary of how the platform is built. The binding version is in our terms and our privacy notice, and both are written to be read rather than survived.