Trust
Isolation is structural, not a filter in a query.
What protects your data, stated as what is actually built rather than as a badge.
How your data is separated
Each customer gets their own database schema. One workspace cannot read another's rows because the rows are not in the same place — not because a filter remembered to exclude them.
Tenant isolation has been proved under adversarial testing across 379 routes, and the filter engine held against 23 SQL-injection probes.
The rest of it
- Encrypted
- In transit and at rest.
- Backed up daily
- With point-in-time restore.
- Role-based access
- Who sees what is explicit, inside your organisation and inside ours.
- Two-factor sign-in
- On every account, trial included.
- Audit trail
- Every automated action logged per workspace and per person, and reversible.
- Full export, any time
- Leaving is allowed.
Testing
2,575 tests across 184 suites run green on the Spine codebase, including the isolation and injection suites above. That is engineering evidence, not a certification — see Compliance for the difference.
Reporting something
If you have found a vulnerability, write to [email protected] with enough detail to reproduce it. We will come back to you.
Still need a person?
Write to [email protected]. We are small enough that someone reads it.