Every claim, and where to check it

This page exists so that due diligence takes an hour rather than a week. Each row is a claim we make somewhere on this site, the artefact that supports it, and who other than us can check it. Where the honest answer is “nobody yet” or “no”, the row says so. Nothing linked here needs an account, a call, or our cooperation.

The record

What the ledger and the evidence log prove

Claim	Check it at	Who else can check
Every recorded quote is chained; an altered, deleted or inserted entry is detectable	/verify: the live head, and an in-browser checker for an export. Canonical form	Anyone holding an export, with the public verifier, offline
The head is signed, so we cannot later deny having published it	Live attestation; public key at /api/v1/ledger/pubkey and in the verifier repository	Anyone, with `verify-attestation.mjs` or the Python verifier
A signed head existed before a given date	How old the record is: the anchors and their Bitcoin proofs, figures computed from the files at build time; proof-of-age.json	Anyone with `ots verify` against the Bitcoin block
The evidence log holds digests only, in an RFC 6962 Merkle tree, and never a record	The specification, with test vectors; the database refuses anything that is not a 64-hex digest	Any implementer, with the vectors; any holder of a proof, with either verifier
The formats are open and can be implemented and checked without us	The conformance suite, in the kit at `/kit/conformance/`	Any implementer; their result is theirs to publish. None published by others yet
Independent parties co-sign the log	How witnesses work; keys in `witnesses/`	No independent witness yet. The page says so rather than leaving it out
How much is recorded, and by whom	/usage, counted live from the ledger by your browser	Anyone; `GET /api/v1/usage` is public

The service

What runs, and how it is kept running

Claim	Check it at	Who else can check
The API is up and the ledger is reachable, right now	/status, checked live by your browser; no uptime history is shown until one has been measured externally	Anyone, on every page load
What is deployed is what was reviewed	`build.commit` on /api/v1/health names the commit CI deployed	Anyone; the commit is on the deploying workflow’s run
No third-party code runs in production	The bill of materials, derived from the Workers’ own imports on every build	Anyone reading the SBOM
The API is documented as it runs	OpenAPI 3.1, held identical to the routes by a test; reference	Anyone generating a client from it
Backups exist, restore, and match the anchored head	Continuity: last drill date and what it checked; weekly and automatic	Our records; a customer can ask for the latest drill report
A customer can leave with their evidence intact	The exit plan; the export format and the verifiers are public	Any customer, by exporting today

Security and data

What we hold, and what we do not

Claim	Check it at	Who else can check
A quote holds no personal data; an evidence entry is a salted digest of a record we never see	Data protection, what the client sends	Any integrator, by reading what their code sends
Where data lives, and every sub-processor	Sub-processors and Trust: EU hosting, plus one encrypted weekly backup copy kept 30 days on GitHub, outside the EU	The list is complete; there is no second list
How to report a vulnerability, and the headers every page ships with	security.txt (RFC 9116), Security	Anyone, with a scanner
The answers a vendor-risk team asks for	Security questionnaire, answered, each answer linked to its evidence	Any reviewer
Whether the browser ever computes a price	It never does: pricing is server-side only; the rating matrix and its fingerprint are published per version	Anyone, by comparing the API’s answer with the published matrix

What we do not claim

The plain answers

Registration: RiskRouter is not registered with the FSMA and is not an insurance intermediary. It is software for licensed distributors. A written question about the boundary was sent to the FSMA on 19 September 2026; its answer will be published here when it arrives. Regulatory position.
Customers, carriers, certifications: None. No customer, carrier, certification or testimonial appears anywhere on this site, because none exists yet. A vendor’s name appears only once they have agreed to it in writing.
Cover: No cover is in force anywhere behind this system. Every price is a simulation of a published rating matrix, and every page says so.
Uptime: No history is shown until an external monitor has measured one. Status.
What would change this page: A witness key, a conformance result published by someone else, a first outside entry on /usage, or the FSMA’s answer. Each is a fact, not a promise, and each changes a row above from “none yet” to a number or a link.