Trust
Your workspace, your data, and a way out.
Isolation is enforced in the database rather than by code remembering to filter. And when you leave, you leave with your data and a document stating what was destroyed.
Two questions decide whether a platform is safe to put your customers on. Who can reach your data while you are using it, and what happens to it when you stop.
Isolation between workspaces is enforced in the database itself, rather than by application code remembering to filter, which is the difference between a rule and a habit. Our own staff cannot simply look: entry needs a session with a recorded reason, it expires by itself, and it is written into your own audit log, so you do not have to ask us whether it happened.
Leaving is deliberately undramatic. Contacts, conversations and analytics export to CSV, and the API extracts everything programmatically. Delete a customer and their messages and media go with them. Close the account and we issue a document stating exact record counts before and after, what was destroyed, and anything retained by law, with a verification hash. Measured facts rather than assurances.
Your workspace is yours alone
Isolation is enforced in the database, not by application code remembering to filter.
Optional two-factor login
Any user can add an authenticator app, and once they do it is enforced for them at every login.
Support access you can see
Our staff can only enter your workspace through a session that needs a recorded reason, expires by itself, and is written into your own audit log.
Erasure on request
Delete a customer and their messages and media go with them, not just the record with the conversation left behind.
A certificate of deletion
Close your account and we issue a document stating exact record counts before and after, and what was destroyed, with a verification hash.