Security & data trust
Where your data lives, who can reach it, and what the AI never sees.
This is the page to send your IT reviewer. What we hold is marked live. What we are working towards is marked in progress and will stay that way until it is signed - we would rather lose a deal than overstate one.
01 · The short answers
Four things reviewers ask first.
{{ s.q }}
{{ s.a }}
{{ s.note }}
03 · Access & permissions
Enforced in the data layer, not on the screen.
The security model most SaaS ships hides records in the interface while the API still returns them. Ours attaches access to the records themselves, which is why it holds for the API, for exports and for Q.
{{ a.tag }}
{{ a.head }}
{{ a.body }}
04 · Residency & hosting
Three places your data can sit.
{{ r.tag }}
{{ r.head }}
{{ r.body }}
{{ r.note }}
05 · How we run it
Encryption, backups, and who at UseKase can look.
{{ o.k }}
{{ o.v }}
06 · Sub-processors
Everyone who touches your data.
The current list is maintained as part of the data processing agreement and provided before you sign. Your own clients increasingly ask you to name yours - this is the document that lets you answer.
{{ s.k }} - {{ s.v }}
Material changes are notified in advance, and the agreement gives you the right to object. Ask for the current list at any point in the conversation - you do not need to be a customer.
In progress, and said plainly
What we can't claim yet.
{{ p.head }}
{{ p.body }}
If a certification is a hard procurement requirement today, tell us early. We will either point you at the control documentation that satisfies the underlying question, or tell you to come back when the report is issued.