Security and tenancy
The controls are in the ledger, not in the process.
A control that depends on somebody remembering is not a control. Everything below is enforced where it cannot be routed around — in the database, in the key material, or in the chain — and every one of them is checkable in the product rather than described here as an intention.
Tenant isolation fails closed
Isolation is enforced in the database by row-level security, not by a WHERE clause somebody has to remember. A query issued without a tenant context does not return the wrong rows — it returns nothing. That distinction matters more than it sounds: a filter that is merely forgotten leaks; a policy that is absent starves. We take the failure mode that is loud on our side and silent on yours.
Personal data is sealed on the way in
Identifying and clinical fields are encrypted per data subject under a key that exists only for that subject. The ledger stores ciphertext. Nothing downstream — no report, no export, no backup tape — holds a readable copy that could survive the key.
Erasure is destruction of a key, and it is provable
An append-only ledger and a real erasure obligation are not usually compatible. Destroying the subject key renders every record of that subject permanently unreadable, immediately, without rewriting history. The certificate enumerates what was destroyed and what deliberately survives — the financial skeleton a trustee or an auditor needs — rather than implying the remainder is gone.
The audit trail is hash-chained
Each audit record commits to the one before it. Editing a row invalidates every row after it, so the question "has this log been altered" has an answer that does not depend on trusting us. Valuations are superseded and never overwritten; the mark you were shown last quarter is still the mark you were shown last quarter.
Secrets live in a vault, and nothing holds a password
Every credential is held in Azure Key Vault and read through a managed identity at runtime. There are no secrets in the source, in the pipelines, or in a configuration file anyone can copy. Administrative access to the database is through identity, not a shared password.
Every action is attributable to a person and a session
Authentication is multi-factor. Authorisation is role-based and evaluated on the server for every request, because a control enforced only in the interface is decoration. Sensitive actions — funding, releasing a lien, moving money — record who, when, from where, and on what evidence.
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 matters, which means your data is never absorbed into weights that 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.
It runs where you can see it
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.
What this page does not claim
We have not named a certification, an attestation report, or a compliance framework, and the omission is deliberate. Publishing a badge is easy and it is the single most common way a security page becomes untrue between one audit window and the next.
If your diligence needs a specific attestation, ask us directly and you will get a straight answer about what exists, what is in progress, and what does not exist yet. A vendor who will tell you the third thing is worth more than a page of logos.
Architecture questions, penetration-test arrangements and data-processing terms all go to the same address: sales@mindhyve.io.