Fourpromises.Eachoneauditable.
Each promise below maps to architecture we can point at and clauses that live in the MSA. Click one to see exactly how it is enforced in code and contract.
Every sensitive action is entered into the audit trail.
Every backup, every restore, every retention run and legal-hold change is recorded on a hash-chained trail whose every hash is recomputable from its own record. An edited record fails that recheck and a deleted one leaves a reference that no longer resolves — the recheck hourly over the newest events and again in a full daily sweep, the dangling-reference scan in that daily sweep; and because each chain’s head is anchored nightly and signed with a key held outside the database, a rewrite that re-computes the chain produces a head that no longer matches the one that was signed.
The platform is designed around four commitments: an integrity-chained audit trail, per-tenant cryptographic isolation, contracted regional residency, and detectable change-control. A material, uncured failure against any of these entitles you to the remedies defined in your Master Services Agreement, including termination for cause where that MSA provides it.
These are engineering commitments, not marketing copy. Specific notice periods, cure windows, service credits, and exit remedies are set out in the signed agreement and govern in the event of conflict with anything on this page.
Read the full MSA →LAST REVIEWED · 2026-05-30