Security

Last updated 3 September 2026

You are handing us your clients’ papers. Here is what actually protects them — mechanisms, not adjectives — including the parts we are still working on.

Chambers cannot reach each other

Every record carries the chamber that owns it, and row-level security is enforced in the database rather than in application code. A query that forgets to filter returns nothing instead of returning somebody else’s matters.

Documents go further: the storage path begins with the chamber’s identifier and the storage policy checks it, so a signed link for one chamber’s file cannot be reissued for another’s even by someone who guessed the key.

What we deliberately do not store

Not held	Why
Passwords	There are none. Sign-in is an eight-digit code to your email, stored hashed, salted with a server secret and bound to the address — so a leaked table is useless and a code for one address cannot verify another. Five attempts, ten minutes.
Identification numbers	Solon records that you saw a PAN or an Aadhaar, never the number. Holding it would be a liability with no benefit to the chamber.
Card details	Payments go directly to Razorpay. Nothing touches our servers.
Audio	Dictation is transcribed and discarded. Nothing is kept.
Petitions uploaded for formatting	The layout is read out of the file and the file is discarded. It may concern a matter we have nothing to do with.

Masked matters stay masked

Where a court has protected party names — domestic violence, family, POCSO — Solon does not display them, does not allow them to be typed in by hand, and never surfaces them to a client portal. There is no setting that turns this off.

Your clients see status, and nothing else

The client portal reads from a view containing only the stage, the dates, the orders and messages you sent. Drafts, notes, research and bench data are absent by construction, not filtered out — a column that is not in the view cannot leak from it.

A portal link is a bearer credential. Anyone holding it sees that client’s matters, which is why it can be revoked from the Clients page at any time.

Infrastructure

Database and documents in a private, region-locked instance in Seoul
Encrypted in transit and at rest
Documents in private storage, reachable only through links that expire in five minutes
Daily database backups
A ledger of every uploaded file, with a content hash — so a restored file can be proved identical to the one that was filed

AI providers

Text is sent to AI providers to classify judgments, write headnotes, explain sections and transcribe dictation. Our providers are engaged on terms that prohibit training on data we send.

Solon does learn your chamber’s habits — but by remembering what you chose, rejected and corrected, held against your chamber alone. There is no cross-chamber learning and no plan for one.

What we are still working on

Stating this rather than leaving you to discover it.

Point-in-time recovery. Backups run daily. We are enabling second-level recovery before onboarding chambers at scale — until then, a failure could cost up to a day’s work.

Independent audit. Solon has not been through SOC 2 or ISO 27001. We would rather say so than imply otherwise.

Found something?

Write to security@solonai.legal. We acknowledge within 24 hours and will keep you posted on the fix.

We will not threaten anyone who reports a vulnerability in good faith. Please give us reasonable time before publishing, do not access data that is not yours, and do not degrade the service for anyone else.