How your data is kept apart

Separation is enforced by the database

Every workspace's rows are protected by PostgreSQL row-level security as well as by the application, and the application connects as a role that is not exempt from it. A query that forgets to filter by workspace returns nothing rather than somebody else's data. The one way past it is a deliberate switch in our own code, used for signing in, incoming webhooks and our own admin panel — a short list we review, rather than something every query has to remember.

Signing in

• Company sign-on over SAML 2.0 or OpenID Connect, with your identity provider.
• Passkeys, and authenticator-app two-factor — required for Owners, Admins and Developers, and for everyone if you choose.
• Roles map from your provider's groups, and cannot be used to grant ownership.
• SSO can be enforced so passwords and passkeys stop working once you are ready.

Everything is recorded

Changes are written to an activity record you can read and export: who did what, to which record, and when. Support access to a workspace is time-limited, read-only, shown to your team while it is happening, and emailed to you — and you can switch it off. Nobody looks at your account quietly.

Your data on request

Contacts can be exported to CSV from the product, and the Owner can export the activity record. A copy of your whole workspace is a request to us, worked by our staff.

When one of your own customers asks what you hold about them, you answer it in the product. Owners and Admins log the request and see the days left of the 30 that PIPEDA and Quebec's Law 25 allow. An access request produces a download of everything held on that person, behind a link that expires after seven days. Erasure is the Owner's alone, confirmed with their password and two-step code: the person's details are removed rather than hidden, call recordings are deleted at the phone network, your connected apps are told, and you get a certificate listing what was kept and why. The activity record is the one thing never rewritten, and the certificate says so.

What we do not claim

We are not currently certified against SOC 2 or ISO 27001. If your procurement process needs either, tell us where you are in it and we will be straight with you about timing rather than leaving it implied.