Data handling

What the platform holds

A receivable is priced from the file behind it, so the platform holds the file: the underlying matter, the treatment record, the lien and its filing, the counterparty correspondence, and the retrieval trace behind every figure produced. It also holds the financial skeleton of each position — the ledger a trustee or auditor needs.

This marketing site holds none of that. It is a static export with no database and no form; the only thing it collects is what you choose to put in an email to us.

Where it is processed

EliAI runs on Microsoft Azure. Data at rest is encrypted, data in transit is encrypted, and the application reaches its database over a private network path rather than the public internet. Infrastructure is declared in source and deployed by pipeline, so what is running is what was reviewed.

Erasure is destruction of a key, and it is provable

An append-only ledger and a real erasure obligation are not usually compatible. Destroying a subject key renders every record of that subject permanently unreadable — immediately, per subject, without rewriting history.

The certificate enumerates what was destroyed and what deliberately survives, rather than implying the remainder is gone. That second half is the honest part: the financial skeleton of a funded position does not disappear because a subject exercised a right, and a certificate that implied otherwise would be the lie.

The model is never trained on your book

There is no training and no fine-tuning anywhere in this product. Valuation is grounded in retrieval over comparable settled matters, which means your data is never absorbed into weights another tenant could query. It also means a mark can be re-derived years later, because the corpus and the engine version are both pinned to the artifact.