Trust
Security and data isolation
Last updated August 2026
Kaide holds the working knowledge of your business. Keeping it separate from every other business on the platform is a structural decision, not a setting.
Every record belongs to one organisation
Websites, requests, reports, recommendations, files and conversations all carry the organisation they belong to. There is no shared pool.
Access is enforced in the database
Row-level security policies decide what each signed-in account can read and write. Hiding a link in the interface is never the control; the database refuses the query.
Privileged actions run on the server
Roles are never trusted from the browser. Anything privileged is authorised server-side against the signed-in session.
Files are scoped per organisation
Uploads are stored under organisation-specific paths and served through access-checked links, not public URLs.
The demo is isolated
The public product demonstration runs against a dedicated demo tenant. It cannot read or write real customer data.
Reporting a concern
If you believe you have found a security issue, contact us directly. We will acknowledge and investigate.