Software for legal work, where a wrong answer is a liability.

What legal software has to get right

Legal software fails in a particular way: it produces an answer that looks authoritative and is wrong. A confident wrong answer in a legal setting is worse than no answer, so most of the engineering is in refusing to be confidently wrong.

• Cited, or withheld. A clause that cannot be tied to a section in a dated, primary source is not drafted; it is returned as a gap. In SanadEx, citations resolve against a fixed archive of Indian primary source law before any draft is shown.
• Refusing is allowed. The system refuses to draft when its sources are missing or out of date, and keeps a record of the refusal. A tool that knows the limit of what it can do is the only kind worth using for regulated work.
• The advocate signs off, always. The software does not file, serve, contact a court or registrar, or approve a document for use. A qualified person reviews, edits, signs, and sends. The tool sits under professional judgement, never over it.
• Provable checks first. Fixed, auditable checks run before any model reasoning, so the parts that must be provable are provable, and the model works inside a boundary rather than at the wheel.

The engineering behind it

A legal technology build is a regulated software build with a legal domain on top. The hard parts are the ones every regulated system shares, and we have built them before.

• Each client's data kept separate, in the database. Access rules are enforced in the database, so a bug in the application does not turn into a data breach.
• Data protection built in. Consent recorded as a full history rather than a single yes or no, retention enforced by a job rather than a setting nobody runs, and people's data rights handled as tracked steps. We wrote this up in DPDP for SaaS builders.
• Data kept in the country, and away from the model. Storage, computing, and AI processing pinned to India where the work needs it, with sensitive data kept out of the model's reach.

The same data handling sits under our build for a regulated financial institution. We point to it here as proof of the engineering, not as legal work; that project is a finance build, kept private under a non disclosure agreement.

Honest scope

SanadEx is not launched yet. Any numbers we publish about it come from test fixtures, not real advocate use, and they are not a claim about court outcomes. We have not yet delivered a commissioned legal technology project, so this page describes a capability and our own product, not a client track record. We would rather you knew that before the call than after it.