Agents prepare. Attorneys approve.

Built for privileged information.

Your clients trust you with the most sensitive moments of their lives — a green card interview, a custody dispute, a felony charge. JurisAgent is designed to protect that trust at every layer, and to keep a licensed attorney in charge of everything that leaves the firm.

Request early access Book a security walkthrough

This page describes how JurisAgent is designed. Where something isn’t built yet, it says so.

Illustration: the security panel of a sample matter, showing encryption, access, an ethical wall, retention and model-training settings.
Designed for
  • Encryption
  • No training on client data
  • Matter-level access
  • Full audit trail
  • Attorney approval
§ 01Data protection

Protected from the upload to the approval.

A client’s passport scan, a bank statement, an hour of body-cam footage: each one is encrypted on the way in, stored encrypted inside your firm’s own workspace, and read by agents only for the matter it belongs to.

Diagram: the path a client document takes — upload, firm workspace, agent work on the matter, attorney approval — with the protection applied at each stage.
  1. 01 · Upload
    passport-rivera.pdf
    Encrypted in transit

    Client portal or firm upload

    Documents travel over encrypted connections, whether a client uploads from a phone or a paralegal drags in a production.

  2. 02 · Store
    Firm workspace · isolated Encrypted at rest

    Your firm’s own workspace

    Each firm’s data is logically separated from every other firm’s. Documents, drafts and logs are encrypted at rest.

  3. 03 · Prepare
    FMEVDRReading #2026-0412 only No training · matter-scoped

    Agents work on one matter

    Agents read only what belongs to the matter they’re assigned to. Client data is used to do your work — never to train models.

  4. 04 · Approve
    Attorney approval Logged to audit trail

    Nothing leaves without you

    Before anything is filed, sent or signed, an attorney approves it. The decision is recorded with the sources behind it.

Encryption

In transit and at rest

TLS for every connection; documents, drafts, transcripts and audit logs encrypted at rest with managed keys.

Isolation

One firm, one workspace

Firm data is logically separated, and access checks run on every request — not just at sign-in.

Least privilege

Scoped agents

Each agent is given the documents of one matter, for one task, and nothing else in your firm.

Operations

Restricted staff access

Our team is not given standing access to client data. Support access is designed to be requested, time-limited and logged.

§ 02Your data, your matters

Client data is never used to train models.

Not ours, not anyone else’s. What a client tells you about their marriage, their finances or their arrest is used to do work on their matter — and for nothing else.

Used for
  • Prefilling forms on the matter it came from
  • Drafting letters, motions and disclosures for that matter
  • Indexing evidence and building timelines for that matter
  • Showing you the source behind every fact
Never used for
  • Training or fine-tuning AI models
  • Work on another firm’s matters
  • Marketing, profiling or resale
  • Benchmarks or examples shown to anyone else
Illustration: the firm settings page, where model training on firm data is shown as off and locked.
§ 03Access control

Access follows your firm, not the software.

Roles decide what each person can do. Matters decide what each person can see. Ethical walls keep screened lawyers out, and the walls apply to agents too.

  1. 1

    Roles

    Partner, attorney, paralegal, staff and client portal — each with a defined set of actions. Only attorneys can approve, file or sign.

  2. 2

    Matter-level permissions

    People and agents see the matters they’re staffed on. A family-law paralegal doesn’t see the criminal docket unless you say so.

  3. 3

    Ethical walls

    Screen a lawyer from a matter after a lateral hire or a conflict. The wall is enforced in search, in the docket and in what agents can read.

  4. 4

    Sign-in

    Designed for multi-factor sign-in on every account. Single sign-on through your identity provider is Roadmap

Illustration: a roles and permissions matrix for a sample firm, with an ethical wall on one matter.
§ 04Attorney in the loop

The most important control is you.

Encryption protects data. Approval protects judgment. Agents in JurisAgent can prepare almost anything — but the actions that carry professional consequences are reserved for a licensed attorney, and the software is built so they can’t be skipped.

  • 01

    Filing, sending and e-signing require attorney approval. Agents propose; they can’t submit.

  • 02

    Every proposal carries its sources — the page, line or timestamp behind each fact.

  • 03

    Flags, not guesses. Inconsistencies and unverified authority are surfaced before you approve.

  • 04

    Approvals are recorded with who, when and what changed — part of the matter’s audit trail.

JurisAgent is software for attorneys. It does not provide legal advice and is not a law firm.

Illustration: a client message drafted by an agent is held at the approval gate; the send action stays locked until an attorney approves, with sample data.
§ 05Audit trail

A record of every action, by every agent and every person.

What each agent read, what it produced, what it changed — and who approved it. The trail is append-only, kept per matter, and exportable when a supervising partner, a client or a court asks how the work was done.

Illustrative interface with sample data.
  • Who & what

    Every entry names the actor — a person or a named agent — the action, and the documents involved.

  • Append-only

    Entries are added, never edited. A correction is a new entry that points to the old one.

  • Exportable

    Export a matter’s trail alongside its documents, for supervision, client questions or your own records.

§ 06Professional responsibility

For your ethics committee.

ABA Formal Opinion 512 (July 2024) addresses lawyers’ use of generative AI tools. Here is how JurisAgent is designed against each duty it discusses.

Designed around the duties you already have.

Opinion 512 doesn’t ask lawyers to avoid AI. It asks them to understand it, protect confidences, supervise it and stay responsible for the result. Those are product requirements for us.

1.1

Competence

Understand a tool’s capabilities and limits, and review its output with care appropriate to the task.

Every fact and drafted sentence links to its source, so review means checking — not trusting.

1.6

Confidentiality

Assess the risk that client information is disclosed or used beyond the matter — especially by tools that learn from inputs.

No training on client data, matter-scoped agents, encryption and firm isolation. You decide when to seek client consent.

1.4

Communication

Consider when clients should be told about the use of AI on their matter.

A per-matter record of which agents did what, and attorney-approved client messages.

3.1 · 3.3

Candor & claims

Verify citations and legal assertions before they reach a tribunal.

The Research Agent links every citation and flags any authority it can’t find in a primary source.

5.1 · 5.3

Supervision

Set firm policies for AI use and supervise lawyers and nonlawyers who use it.

Roles, firm playbooks, approval gates and an audit trail make supervision visible.

1.5

Fees

Charge reasonable fees, and be thoughtful about billing for time AI saves.

Agent activity is logged per matter, so you can see what was prepared and when.

A design summary, not a legal opinion. Opinion 512 is advisory; your jurisdiction’s rules and guidance govern, and attorneys remain responsible for their work product.

§ 07Data ownership

Your firm’s data stays your firm’s.

You own what you upload and what agents prepare for you. You decide how long it’s kept, you can take it with you, and you can have it deleted.

Export anytime

Documents, forms, drafts and the audit trail, per matter or for the whole firm — in standard formats.

Retention you set

Set retention by practice area or matter type, in line with your file-retention policy and state rules.

Deletion on request

Delete a matter or close your account and your data is removed from the workspace — with a record that it happened.

§ 08Compliance roadmap

Building toward SOC 2 Type II, in the open.

We are not SOC 2 certified today, and we won’t show a badge until an independent auditor says we’ve earned it. Our controls are designed to that standard from day one. We’ll publish our status on this page as it progresses.

  1. Now

    Controls designed to the standard

    Access control, encryption, logging, change management and vendor review — designed against the SOC 2 trust services criteria.

    In progress
  2. Next

    Independent readiness review

    An outside assessor reviews our controls and policies before any formal audit begins.

    Roadmap
  3. Then

    SOC 2 Type II audit

    An observation period, then an independent report on whether controls operated effectively over time.

    Roadmap
  4. Always

    Status published here

    Each milestone appears on this page when it’s real — not before. Ask us anytime where things stand.

    Ongoing
Security review support

Clearing a new tool with your IT lead?

We’ll walk your team through our architecture and controls, answer your security questionnaire, and tell you plainly what is built, what is in progress and what isn’t.

  • Architecture & data-flow walkthrough
  • Answers to your security questionnaire
  • Sub-processor list on request
  • Direct line to the people building it
Book a security walkthrough
§ 09Responsible AI

Agents that show their work and admit what they don’t know.

Principle A

Source linking

Click any prefilled field or drafted sentence to see the exact page, line or timestamp it came from.

Principle B

Flags, not guesses

When sources disagree or data is missing, agents surface it for you instead of picking an answer.

Principle C

Citation checking

Every citation links to a primary source. Anything the agent can’t locate is marked for verification.

§ 10Questions

Found a vulnerability?

Please report it to [email protected]. We read every report and will respond.

Security questions, straight answers.

Is JurisAgent SOC 2 certified?

No, not yet. We’re building toward SOC 2 Type II and designing our controls to that standard from the start. We’ll publish our status on this page as it progresses, and we’re happy to walk your IT lead through our current approach.

Is our client data used to train AI models?

No. Client data is used only to do work on your matters. It isn’t used to train or fine-tune models — ours or any model provider’s — and there is no setting that turns this on.

Can JurisAgent file, send or sign anything on its own?

No. Agents prepare proposals. Filing, sending to clients or opposing counsel, and e-signing all require approval from an attorney, and each approval is recorded in the matter’s audit trail.

Who at JurisAgent can see our data?

Our team is not given standing access to client data. Support access is designed to be requested, time-limited and logged.

Does JurisAgent give legal advice?

No. JurisAgent is software for licensed attorneys and their staff. It is not a law firm and does not create an attorney-client relationship with anyone. Attorneys remain responsible for all work product.

Can we get our data out if we leave?

Yes. You can export documents, forms, drafts and audit trails at any time, and request deletion when you’re done.

Do you support single sign-on?

Accounts are designed for multi-factor sign-in. SSO/SAML through your identity provider is on our roadmap — tell us which provider you use.

Bring your hardest security questions.

We’ll walk your team through how JurisAgent handles client data — on sample matters, in your practice area.

Request early access Book a demo

Security contact: [email protected]