Security overview
Understand how Kabaido isolates, encrypts and protects your commercial data.
Commercial data is competitive data. Kabaido is built tenant isolated from the first table, so your requests, quotes, customers and catalogue stay yours. This section documents the practices in force today, in enough detail for a security review. We publish practices rather than badges, so you can assess them now.
The model in one view
| Layer | Practice |
|---|---|
| Isolation | Every row is organisation scoped with database enforced row level security. Storage paths are tenant prefixed. |
| Encryption | TLS in transit, AES-256 at rest and application layer encryption for integration credentials. |
| Access | Five roles enforced at the database, owner safeguards and an audit log of administrative actions. |
| AI | Anthropic only, configured for zero retention. No training on customer data. Every value cited, never guessed. |
| Hosting | Data resides in the United Kingdom region of our infrastructure providers. |
| Payments | Stripe holds card details. Kabaido never sees or stores them. |
| Your data | Full export anytime and deletion on request. |
Sealed Tenancy tiers
| Tier | What it gives you |
|---|---|
| Standard | Organisation scoped isolation on shared infrastructure, on every account. |
| Sealed | Dedicated project isolation for Enterprise. Talk to us. |
| Sovereign | Customer held keys for Enterprise. Talk to us. |
Why it is built this way
A quote reveals more about a business than almost any other document it produces: what it buys, from whom, at what margin, for which customer. A platform that reads those documents is holding the commercially sensitive core of your business, and the honest response to that is not a padlock icon but an architecture where a mistake in application code cannot leak another organisation's rows.
That is why the isolation boundary is the database rather than the application. An application filter is a line of code somebody can forget to write; a row level security policy runs inside Postgres on every read and every write, including ones nobody thought about when the policy was written.
What we do not claim
This section is written to be checkable. Where something is a practice we follow rather than a control somebody else has audited, it says so. Where something is planned rather than in force, it says that too, and it says it in the same sentence rather than in a footnote.
Assurance roadmap
ISO 27001 and SOC 2 programmes are on the roadmap. We publish our practices today rather than badges, so you can assess them now.
The rest of this section goes deeper: tenant isolation and access control, encryption and credential handling, how the AI handles your data, compliance and UK GDPR, platform and payment security, and how to export or delete everything.