Evidence / Security pack
The due-diligence answers, assembled once
Isolation, encryption, identity, audit, retention, recovery and release process — written down in the form a carrier’s security review actually asks for.
Including the places our position is weaker than we would like. A questionnaire that answers everything perfectly is the one that gets trusted least.
The question this answers
Can you fill in our 90-question vendor assessment?
Yes, and most of it is already written. The pack covers the standard sections directly, cites the mechanism behind each answer rather than asserting a posture, and marks the handful of items where the honest answer is weaker than the question hopes for.
What the pack contains
Section by section
Tenant Isolation and Access Control
The two walls in detail — the read filter and forced row-level security with organization and client walls — and entitlement then role, enforced server-side on every request.
Data Protection
All of your data under your own key in your own cloud account; withdraw it from your console and access closes within 60 minutes. Identity numbers in a separate vault; credentials never shown again.
Identity
Required authenticator codes, OpenID Connect and SAML sign-in, SCIM provisioning, idle sign-out and the 8-hour session cap.
Audit and Retention
Add-only audit rows, retention by line of business, legal holds, defensible disposal and permanent proof of disposal.
Resilience
Hourly write-locked backups, the isolated backup account, the standby region, the 4-hour and 1-hour targets, and the weekly restore test.
AI Governance
The platform AI lock, the four gates, the single door, identity numbers blacked out before anything is sent, and decision logging with the model version.
Known gaps
The items we mark as weaker
Listing these costs us some deals. It also means the rest of the pack is believable, which is worth more than the deals it costs.
Region Switching
Run by a person on an alarm, by checklist; in-region failover is automatic
Availability
A 99.9% uptime target measured every minute by an outside monitor — not a contractual SLA
Third-party Attestation
Ask us for the current certification position rather than inferring one
Records Disposal
Built, and switched off for every client until counsel confirms the state-by-state default periods
Customer Offboarding
Built and recorded step by step; no customer has yet left
On-call Depth
Small team. Not a follow-the-sun operations center
Where we are honest
How to read a security pack
Ours included. A pack is a set of claims about a running system, and the useful ones can be checked with the engineers who built it in the room.
Claims Should Be Testable
Every mechanism we describe can be examined in a technical session. Ask to see the row-level security policies rather than the paragraph about them.
Absent Answers Matter Most
Read what a pack does not address. A document with no “weaker than we would like” section has either an unusually complete platform or an unusually optimistic author.
It Is A Snapshot
Positions change as the platform ships. Ask for the current version and the date, and treat anything older than a quarter as history.
Read next
Send us your questionnaire
The long one, in your own format. We will complete it and flag every answer where our position is weaker than the question hopes for.