Trust Centre

Compliance

Isometric diagram of a row of bare empty display plinths in front of an open working mechanism whose interior dividers, sealed bay and keyed chain are visible, with an inspection probe resting on the running mechanism rather than on the plinths — The plinths are empty on purpose: this site names no certification, because a badge is the most common way a security page becomes untrue between one audit window and the next. The probe is on the running mechanism instead — architecture we can demonstrate rather than describe.

This page names no certification

We have not named a certification, an attestation report, or a compliance framework anywhere on this site, 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 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.

What we can evidence today

Architecture, and the fact that it is enforced where it cannot be routed around. Tenant isolation is a database policy, not a query convention. Erasure is key destruction, not a delete statement. The audit chain is verifiable by a third party without our cooperation. Every one of those is demonstrable in the product rather than described in a document, and we will demonstrate them.

Contractual terms

Data-processing terms, security addenda, penetration-test arrangements and audit rights are negotiated as part of the customer agreement. Send the questionnaire; we will answer it rather than return a brochure.

Security Data handling Subprocessors Availability Incident response Data Processing Agreement AI disclosures