- Section
- Trust centre
- Ref
- BM-TR
- Updated
How we keep our own night.
The controls behind BreachModal and when each was last checked, the response times we commit to, who handles data for us, and the limits of what we claim. Dated, so you can tell how fresh it is.
§1Controls, verified
Each control, and the day it was last checked.
| Control | Status | Last verified |
|---|---|---|
| Backups tested | passing | |
| DR drill conducted | passing | |
| Security headers | passing |
§2 · Response commitments
- Incident intake
- 15 minutes
- Target time to acknowledge a reported incident.
- Containment guidance
- 60 minutes
- Target time to first containment guidance.
§3Data handling
In transit, at rest, and who else touches it.
- In transit
- HTTPS on every request
- At rest
- Provider-managed (e.g., AES-256)
| Subprocessor | Purpose | Their attestations |
|---|---|---|
| Vercel | Hosting | SOC 2, ISO 27001 |
§4 · What we do not claim
Informational only; not legal advice. For any handling of ePHI, a BAA is required. We are not a PCI QSA; PCI certification requires a QSA attestation.
§5 · Further records
- ComplianceHow the record maps to SOC 2, ISO 27001, NIST CSF, GDPR, HIPAA and PCI DSS
- AI securityHow our AI is held to account, and how we test yours
- Disclosure policyReport a vulnerability under safe harbour
- Privacy policyWhat this website collects, and where it goes
- security.txtOur security contact, machine-readable (RFC 9116)
For your due diligence
Ask for anything not on this page.
Security questionnaires, architecture questions, a call with the people who run it. Talk to us and a person will answer.