Is my data isolated from other tenants?
Yes. Every organization's records are isolated at the database level by Postgres row-level security, not just application code — a session scoped to one organization cannot read or write another organization's rows. This is proven by an automated cross-organization deny test that runs against the real database role, not just asserted in application code.
- Row-level security, not app logicA database session scoped to one organization cannot read or write another organization's rows. Postgres enforces it, independent of the application code doing the querying. Live
- Branch-level restrictionInside one multi-branch organization a role can be restricted to its own branches. An unrestricted session — owner, dispatch-all, scheduled jobs — sees every branch by default. Live
- Isolation is tested, not assumedAn automated cross-organization and cross-branch deny test runs against the real restricted database role, so the boundary is proven rather than documented. Live
This is one of six questions answered individually. The full picture — access control, audit trail, data handling, integrations, and what we haven't built — is on the security page.
02
The other five.
Each one is its own page, so you can forward the single answer somebody asked for.
03
Still not satisfied?
Fair. Bring the question to a call and we'll show you the control running against real records, not a slide about it.