Trust & Security
We verify it. We don't just say it.
We don't tell you your data is isolated — we run automated checks against live infrastructure on a schedule and show you the result. This page explains exactly what we check and renders our own current, live status below.
Live status
Verified RLS-Isolated
Each workspace's records are kept apart by rules inside the database — confirmed live, not just configured.
How verification works
Every claim on this page traces to exactly one automated check the platform actually runs — never a hardcoded assertion. A check that has never run shows as unverified, not a false green. A check that's currently failing shows as failing, immediately — it does not get quietly upgraded because the rest of the system looks healthy.
Some facts below are labelled Documented rather than Verified — architecture-wide design facts (like which subprocessors we use) that don't yet have a live per-deployment check behind them. We label the difference so you always know which is a running check and which is a design statement.
What we check
The live catalog of automated checks backing this deployment's posture.
- Cron job livenessVerified 10m ago
- SMS delete-on-deliveryVerified 10m ago
- Call recordings: none at the carrierVerified 10m ago
- AI inference never leaves our networkEvery embedding and chat completion is probed to confirm it routes through our own on-network inference relay — there is no cloud fallback for it to fall back to.Verified 10m ago
- RLS policy matches the declared baselineEvery table's row-level security policies are diffed against our committed manifest — any drift between what's declared and what's live is caught immediately.Verified 10m ago
- Row-level security on every tableWe continuously scan for any table missing its isolation policy — a gap here would silently let one tenant see another's rows.Verified 10m ago
- Isolation cannot be bypassedRow-level security is FORCE-enabled everywhere it's required, so even a misconfigured query can't skip it.Verified 10m ago
- Audit trail actively recordingWe verify the append-only audit log is still receiving new events, not silently stalled.Verified 10m ago
- Database schema kept currentYour schema is checked against the platform's applied migration ledger, so nothing silently drifts out of date.Verified 10m ago
Also documented (not a live check)
- DocumentedYour data stays with usWe keep your records in our own database. We run sign-in ourselves. Your files go to private storage under our account. Your requests do not pass through an outside network service.
- DocumentedOutside services get only what the job needsWe use outside services only to send email, send text messages and take payments. Each one gets only what that job needs. None of them receives medical records. We give the full list of these services to any customer who asks.
