Your client work is yours.
Never trained on. Never shared. Never used for anything but your work. Every model call runs through a gateway inside Jubal's own AWS account; your desktop and your browser never call a model provider themselves, with one exception: voice dictation streams audio from the desktop straight to our speech-to-text provider.
Every control, and where it stands.
- Encryption at rest and in transitLiveDocuments are encrypted at rest with AWS KMS, and every connection is TLS.Live
- Per-matter wallsLiveA session is scoped to one matter, and the server enforces it, not just the prompt.Live
- Audit trailLiveEvery question, every document added and every privilege-relevant action is recorded with who, when and which matter.Live
- Model calls inside Jubal's AWS accountLiveEvery model call runs through a gateway inside Jubal's own AWS account; the desktop and the browser never call a model provider themselves.Live
- No vendor vector databaseLiveNothing is chunked into a vendor-hosted vector database.Live
- No training on your workLiveJubal does not train any model on your prompts and documents, and configures its providers not to. Check it →Live
- Delete, purge and exportLiveA deleted matter is recoverable for 30 days; a purged one is hard-deleted from Jubal's live systems; export a whole matter as a zip at any time.Live
- Encrypted backupsLiveEncrypted backups, which only Jubal can restore, expire on schedule: nightly copies within 35 days, monthly copies within 12 months.Live
- Subprocessor listLiveEvery provider that touches your data is named, provider by provider. Check it →Live
- Business associate agreementLiveJubal will sign one with a firm that asks; write to legal@jubal.law before onboarding protected health information.Live
- Data processing addendumLiveIf your firm requires one, Jubal makes it available on request, and it forms part of the Customer Terms. Check it →Live
- Sign in with GoogleLiveSign in with Google is live.Live
- Single sign-on (Okta and other providers)PlannedOkta and other SSO providers are planned.Planned
- SOC 2 Type IIPlannedPlanned, not yet held.Planned
Where your work goes.
Every model call runs through a gateway inside Jubal's own AWS account. Models that run on AWS are covered by the AWS Business Associate Agreement; for applicable services the gateway also calls xAI, a partner model provider, over an encrypted connection. The desktop app and the browser never call a model provider themselves. The one direct connection from the desktop is voice dictation, whose audio streams to Deepgram, our speech-to-text provider.
Documents are stored in Jubal's own S3 bucket under a KMS key Jubal controls, scoped by firm and by matter. Model providers have no access to that store; they receive the text and page images a single request needs, through the gateway, and nothing else.
Every provider that touches your data is named on the subprocessor list, with what it does and whether written no-training terms are on file.
Read the subprocessor list →A privacy sentence is a promise. These are the controls a firm can check for itself, from inside the product or by asking.
- The audit trail. Every question asked of Jubal, every document added, every lookup that left the building, and every privilege-relevant action is recorded with who, when, and against which matter. Read it on the matter's Details tab and on each client's page. The trail stores names and actions, never document content.
- Per-matter walls, enforced on the server. A session is scoped to one matter. Open a document from another matter in a chat and the server refuses, whatever the prompt says. Related matters are pooled only by a deliberate, recorded decision.
- Delete, purge, export, on your schedule. Try it on a test matter. Export produces a zip with the folders intact; purge removes the matter from Jubal's live systems, and the audit log records the purge.
- The same commitments, in the contract. The commitments above are written into the Customer Terms every firm accepts when it joins. We record who accepted, when, and which version. When the Terms change, every firm is asked again.
- What to read and ask for. The subprocessor list, which names every provider that touches your data. The relevant section of the partner-firm agreement. Answers to your client's outside-counsel guidelines, section by section. Send the questionnaire to security@jubal.law.
Most legal AI tools take ownership of your documents the moment you upload them. They chunk your matter files into a vendor-hosted vector database, feed them to a third-party model, and reserve the right to “improve their service” with your data. Jubal is engineered the other direction: your documents live in storage we run, scoped to your firm and each matter, encrypted, exportable, and purgeable — and no model ever learns from them. Three promises follow, each backed by the architecture below.
We never train on your work.
Your matter files, the prompts you send, and the documents Jubal generates for you are never used by Jubal to train a model, and Jubal configures its model providers not to train on them. The subprocessor list says, provider by provider, whether written no-training terms are on file. Jubal does not have a separate “use client data to improve our product” pathway and we will not add one. If we ever change this, it will require an opt-in from your firm — and the default will always be no.
We never sell or share your work.
We don’t sell your work, and we don’t share it with our partner firm, researchers or other firms. It goes only to the providers on our subprocessor list, which process it for us to run Jubal. Our own staff see it only in the cases the Customer Terms list, such as support your firm asks for. If we are served with legal process for your content, we tell you first where the law allows.
Your matters stay yours.
Your documents are stored encrypted in Jubal's own cloud storage, scoped to your firm and to each matter, with a working copy mirrored to each attorney's machine — never a vendor vector database. AI requests travel through Jubal's private gateway to the model providers, which Jubal configures not to train on them, and Jubal uses your matters only to do the work you ask for. Export a matter at any time; purge it and it is deleted from Jubal's live systems, with encrypted backups expiring within 12 months.
How the promises are structurally enforced
Where your documents are
Your documents are stored in Jubal's own cloud storage (Amazon S3, in the United States), encrypted at rest with AWS KMS and in transit with TLS, under storage keys scoped to your firm and to each matter. The matter's index — extracted text, summaries, chats, and what Jubal has learned about the matter — lives in Jubal's application database under the same firm and matter scoping. Nothing is chunked into a vendor-hosted vector database.
Each attorney's desktop keeps a working copy of the matter on their own machine so Jubal's agent can read and draft against it locally. That copy is a mirror of the cloud record, synced both ways — not a second, separate store. Matters can stay linked to the folders on your office drive, so the case file keeps itself current; the working copy is searched with a fast full-text index on the attorney's machine (ripgrep + manifest ranking) — there is no chunking-into-a-vendor-vector-database step anywhere in the product. The boundary is the firm, not a single machine: every desktop on the team sees the same matter, and so does the browser view at jubal.law.
How a model request travels
When Jubal calls a model, the request goes from Jubal's servers through Jubal's private model gateway — running in Jubal's own AWS account, in US regions only — to the model provider. Most models run on Amazon Web Services itself; for applicable services Jubal also uses xAI, a partner model provider, reached through the same gateway — never for a matter marked as containing protected health information. Only what is needed to answer the request is sent. Jubal does not train any model on your prompts and documents, and configures its providers not to. Written no-training terms are on file for the models on AWS, for xAI and for Deepgram, and zero-data-retention terms are on file for the models on AWS and for xAI; the subprocessor list shows each provider. Provider-side retention of a request is governed by each provider's terms, and we will state it precisely rather than round it up. Jubal routes each task to the best frontier model for it and may use more than one provider; you never pick the model, and every model provider is reached only through that gateway. Voice dictation is the one exception: if you dictate, the audio streams from your desktop straight to our speech-to-text provider.
Delete, purge, export
Delete a matter and it is recoverable for 30 days. Purge it and it is hard-deleted from Jubal's live systems — documents, extracted text, chats, memory — and the working copies on your team's desktops are removed the next time the app runs. Encrypted backups, which only Jubal can restore, are not edited; they expire on schedule: nightly copies within 35 days, monthly copies within 12 months. Export the whole matter as a zip at any time, folders intact.
Encryption at rest and in transit
Document storage is encrypted at rest with AWS KMS; the storage bucket refuses any upload that is not, and refuses any connection that is not TLS. Every connection between the desktop app, the browser, and Jubal's services is TLS. The working copy on each attorney's machine inherits that machine's disk protection — we recommend FileVault on macOS and BitLocker on Windows, as you would for any client file on a laptop.
Audit logs and matter walls
Jubal records who at your firm asked what, when, and against which matter, in your firm's audit trail. Per-matter walls are first-class: a Jubal session is scoped to one matter and cannot draw on documents outside it unless your firm has deliberately pooled related matters — and that scoping is enforced on the server, not just in the prompt.
Protected health information
Built for a HIPAA/BAA posture — documents encrypted at rest and in transit, matter-scoped access, privilege-relevant actions audit-logged, and model traffic processed in Jubal's own AWS account. Jubal has business associate agreements with Amazon Web Services, Convex and Deepgram, and will sign one with a firm that asks; write to legal@jubal.law before onboarding protected health information.
The partner-firm data wall
Jubal's partner firm is a separate corporate entity from Jubal. The partner firm's attorneys are co-designers of the product; they are not employees of Jubal and they do not have access to Jubal's production environment. There is no shared infrastructure between Jubal's production environment and the partner firm's practice environment. The participation agreement between the two entities forbids cross-access. Customer firms can request a copy of the relevant section of that agreement.
The two do share one thing: a mailing address. Jubal Inc's registered agent is at the partner firm's office in Boca Raton, so legal notices addressed to Jubal are delivered there. Receiving Jubal's mail gives the firm no access to Jubal's systems or to any customer's content.
The partner-firm data question, answered again
“Wait — your partner firm? Does that mean my matter data is going to a competitor of mine?”
No. Our partner firm is a co-designer and investor. They helped build Jubal. They do not have access to Jubal client data — yours or anyone else's. The data wall is enforced architecturally (separate corp entity, separate production environment, no cross-access) and contractually (their participation agreement explicitly forbids it). Customer firms can request a copy of the relevant section of the agreement.
Contact for IT and security teams
Send your security questionnaire to security@jubal.law. We'll respond inside three business days.
Tell us where to send it. We email the subprocessor list, an architecture summary, and the data processing addendum on request.