Transparency
Transparency reports
We publish quarterly reports on our governance posture, incident history, and platform reliability. If we ship something broken, it goes in the report. If a security issue is found and fixed, it goes in the report. If a design decision trades off one guarantee for another, it goes in the report.
Q1 2026 · Jan – Mar
Q1 2026 transparency report
Covers January through March 2026. Includes API reliability, known issues shipped and subsequently fixed, security posture updates, and a review of the platform’s behaviour under the 2026-05-17 deep-cycle E2E audit.
This report is in preparation and will be published shortly. The audit cycle that surfaced the items it will cover completed on 2026-05-17.
Our transparency cadence
- Quarterly reports — one per calendar quarter, published within six weeks of quarter end.
- Incident disclosures — severity-1 incidents are disclosed in the next quarterly report with a full timeline and root cause.
- Security posture — the security posture doc is updated continuously; major changes are noted in the quarterly report.
- Known limitations — honest disclosure of design trade-offs and known gaps, not just incidents. The threat model is the canonical source.
Questions about a specific incident or posture item? Contact us.