What are the two of them worth to your firm? Run your numbers
Security

Every step on the record.

Two hires, one set of controls. What follows is how client material is handled, who holds which key, how long anything is kept, and where you can check each of those yourself.

Neverused to train a model — ours or anyone's
Alwaysencrypted in transit and at rest
100%of steps logged, in plain language — calls included
0–∞days' retention — purge on delivery, or never. Your firm sets the clock
A lawyer working through a marked-up agreement at a boardroom table
The standard is not ours to set.It is the one your document system already meets.

Isolation, access discipline, auditability, retention. The same four, applied to the AI.

Role-based access control

Named people, narrow keys.

Access is role-based. Every key belongs to a named person, every action is attributed in the log, and the two hires hold the narrowest role of the three.

Operator

Runs the matters. Sends instructions, receives the work, and reads the log of everything they've sent — and nothing they haven't.

Most of the firm
Admin

Holds the dials. The whitelist, retention, connectors and roles — every change signed with a name and written to the log.

One or two people
Solicia

One role, shared by both hires. They read what a matter scopes and write to your thread. They hold no key to settings, senders or retention.

The staff themselves
ActionOperatorAdminSOLICIA
Send instructionsYesYesNever
See work productTheir mattersAll mattersDelivers, then purges
Read the audit logTheir mattersEverythingWrites it — append-only
Approve senders—YesNever
Set retention & purge—YesEnforces it
Reach connectorsPer instructionGrant & revokeRead-only, on instruction
Place or take a callYesYesOnly when asked — logged like an email
Deliver outside the firm——Never

Every "yes" above belongs to a named person or to the two hires, and is attributed in the log.

Client confidentiality

Your matters, not the market's.

Most enterprise AI runs every customer through the vendor’s own shared service, under the vendor’s terms. Solicia runs inference on its own Azure OpenAI service in Australia, with storage disabled on every call; your matters are tenant-isolated and never trained on, and a firm can take a dedicated deployment of its own on request.

The shared-service model your matters on the vendor's systems
Firm A Firm B Firm C Firm D Firm E
One shared service same endpoint · same queue · vendor's terms
  • Retention is set by the vendor, and can change without your firm’s signature.
  • Material is held on the vendor’s systems, under the vendor’s terms.
  • One shared model endpoint: every customer’s prompts run through the same inference service.
SOLICIA isolated per firm · dedicated Azure account
Firm Aisolated
Firm Bisolated
Firm Cisolated
  • Inference on Solicia’s own Azure OpenAI service in Australia, storage disabled on every call — a dedicated deployment per firm on request.
  • Nothing is pooled or cross-learned between firms.
  • Purged on your schedule — and the purge writes itself to the log.
Enterprise option: dedicated, single-tenant compute, provisioned per engagement

The full argument, including where prompts actually go in consumer tools, is in the briefing: Why law firms banned ChatGPT — and what should lift the ban

The bar we build to

The same bar as the rest of the stack.

The document system, the practice management suite and the mail server all carry privileged work, and between them they set the standard a system meets before a firm stops asking about it. Solicia is built to that standard rather than to a separate one for AI.

✓Tenant isolation
✓Role-based access
✓Encryption in transit & at rest
✓Audit logging
✓Retention policy
✓Preferred residency

If anything on this page would fail your firm's security review, we want to hear about it — admin@solicia.ai, a person reads every note.

Retention & training

Ninety days, seven, or none at all.

The work product returns by reply and lives in your archive. What remains in the workspace sits on a clock your firm winds — presets from 7 to 90 days, a schedule of your own, or purge on delivery, where nothing outlives the reply.

We delete our copy. Yours stays put.

Every finished file was already delivered by reply — so when the workspace purges, the work itself is still sitting in your inbox and your archive, for as long as the firm chooses to keep it. Deletion here never touches the record there.

Retention, set by your firm.

Change it any time from the admin page — the change is logged, like everything else, and every purge writes itself to the log.

On delivery 7 days 30 days 90 days Your schedule
Purge schedule30 days after delivery
Next purgeFriday, 2:00 am
Proof it ranLog entry, per purge
Training

Your documents train nothing.

Not our models and not another provider’s. It is a term of your firm’s agreement rather than a policy page.

  • Never used to trainOurs or any other provider's models.
  • Never read to improve the serviceNo human review of client material.
  • Never pooled across firmsNothing is aggregated across firms.
The controls

Each control, and where you check it.

Its standing today, and the page or document that shows it.

ControlStandingWhere you verify
Inbound authentication16 checks per emailMatter log
Sender whitelistEnforcedTeam page
Role-based accessAdmin · OperatorTeam page
Workspace isolationPer-firmOn request
No training on client dataPolicyIn your agreement
Retention & purgeFirm-set · 0–90 daysLog entry per purge
Plain-language audit logEvery matter · every step · every callapp.solicia.ai
EncryptionTLS 1.3 · AES-256Security summary
Regional residencyFirm-preferredCustomer agreement

What Solicia does not do.

  • Train on your documents. Client material is never used to train models.
  • Keep what you've purged. Once material reaches its scheduled purge, no copy remains.
  • Talk to strangers. An address you haven't whitelisted gets no work and no acknowledgement.
  • Learn from one firm to serve another. Workspaces are sealed; nothing crosses between clients.
  • Hold keys it does not need. The two hires are a role in your permission matrix, and the narrowest of the three.

Ask for the evidence.

The controls register, the data processing agreement and a sample audit trail, calls included, are available for review on request.

Request access