Evidence · for a security review, a regulator, or an investor
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 |
| A chained record that was sealed and later held back shows as a gap; the log refuses a chain position out of turn | Completeness chains; the signed list at GET /api/v2/evidence/chain; the construction | Anyone given the chain’s tag, with chains.mjs or the Python verifier, offline. It cannot show that a record was chained at all |
| One field of a sealed record can be shown and checked while the others stay sealed | Selective disclosure; the construction and its vectors | Anyone holding the disclosure, with either verifier |
| A spot-check sample cannot be steered by the firm or the auditor | Spot checks; the draw, with a vector seeded from Bitcoin’s first block | Anyone, by repeating the draw; the block hash is checked on any Bitcoin node |
| 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 | /witnesses; keys in anchors/checkpoint/witnesses.json, cosignatures in anchors/checkpoint/cosigned/ | Yes, since 23 October 2026: six staging witnesses of the public witness network cosign each new C2SP checkpoint. Nobody runs our own portable witness (witnesses/) yet |
| 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, with the history measured from outside by GitHub Actions on a schedule of once every two hours that GitHub often runs late or skips, in practice every few hours; /uptime.json | 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 the API | 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: what each drill checks; daily 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 daily backup copy kept 90 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. In our own analysis it 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, and the FSMA replied by email on 29 September 2026, and again on 5 October 2026 to the same effect, pointing to its contact point for innovative business models. It restated the definitions of insurance intermediary and insurance distribution in the Act of 4 April 2014, and said that whether an activity needs registration, and under which status, is for the business to analyse itself, with a specialised legal adviser if need be, because the FSMA does not know its business model. It did not rule on ours, and its emails state that they are not official information from the FSMA. The boundary is therefore still our own analysis, not the FSMA’s; this page will say when a legal opinion settles it. 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
- Measured from outside since 30 September 2026: GitHub Actions, which runs on none of our infrastructure, probes the site and the API on a schedule of once every two hours that GitHub often runs late or skips, in practice every few hours. Time it did not probe is shown as not measured, never as up. Status.
- What would change this page
- A witness key, a conformance result published by someone else, a first outside entry on /usage, or a specialised legal opinion on the registration question. Each is a fact, not a promise, and each changes a row above from “none yet” to a number or a link.