Trust

What we can be held to, and what we cannot.

Everything below is either something we can show you, or something we are telling you we do not have.

Last reviewed 21 August 2026

  • Stated Limits
  • Traceable Claims
  • Named Review
  • Evidence On Request
  • Public Ledger

How we hold ourselves

Three commitments behind every claim

Claims carry identifiers

Every substantive statement on this site is recorded with a ledger identifier so it can be checked, challenged, or withdrawn.

Absence is stated plainly

Where a certification, customer, or benchmark does not exist yet, we say so on the page instead of implying otherwise.

Review has a date

Each trust statement is reviewed on a schedule and stamped, so you know how current the position is.

Limits

What we do not have

01

We hold no third-party security certification, and none is in progress.

Verified · CL-20
02

We do not offer single sign-on.

Verified · CL-31
03

We do not offer an uptime commitment.

Verified · CL-32
04

We do not yet publish a process for reporting a security flaw to us.

Verified · CL-33

Evidence

What we can show you

01

Before anything reaches production we verify it. We verify before we approve, and verification has blocked releases — including a hosting tier whose licence prohibited commercial use.

Verified · CL-10
02

Architecture decisions are recorded with their reasoning at the time they are made.

Verified · CL-09

Method

How we use AI

01

Our written material is drafted with AI assistance and reviewed by a person before publication.

Verified · CL-16
02

We integrate no third-party AI model provider in the product today.

Verified · CL-17
03

Where a decision is not ours to automate, a person makes it.

Verified · CL-18

This statement is withheld until its verification completes. The gap is deliberate.

Last reviewed 21 August 2026

Ask us for the evidence behind any claim

We will send the record, or tell you it does not exist yet.