Built so a query can't walk out the wrong door.
Multi-tenant isolation isn't a runtime check — it's a row-level filter on every query, enforced by a kernel guard that refuses any batch straddling tenants. Below: the live shape of how Customer Data stays in its lane.
Financial logs can't be silently rewritten.
Every create, submit, cancel, or edit on a financial document writes a hash-chained, append-only row. Tampering shows.
- Append-only at the schema
- AuditLog has no UPDATE or DELETE permissions in the production role — even an admin can't quietly rewrite a row.
- Hash-chained entries
- Each row's hash includes the prior row's hash, so the slightest tamper invalidates everything that came after it.
- Exportable in one click
- Auditors get the full ledger as CSV / JSON, scoped to whatever date range and doctype they ask for.
- #8d3f2c1e14:32:01 UTC· ip 10.0.4.72
- #5b91a40714:31:47 UTC· ip 10.0.4.18
- #f0c2b8e914:31:22 UTC· ip 10.0.4.72
- #7a14d6c214:30:58 UTC· ip 10.0.4.41
- #3e90b1a814:30:11 UTC· ip 10.0.4.18
Exactly what's in place — and what isn't yet.
We'd rather be specific than reassuring. This matrix shows every control in plain language; if you don't see a checkmark, we haven't earned the right to claim it yet.
We won't publish a status we can't back up on request. Ask us for the relevant evidence.
The paperwork your counsel will want.
All six operative documents are published and versioned. When you sign up we record the exact version you accepted, with a SHA-256 hash of the text — so 'what I agreed to' is always provable.