How your data is held, in plain terms.
A summary of the controls that matter to a buyer's security review. The binding text is in the Information Security Addendum, linked below - this page exists to be read, not to replace it.
Encryption
- TLS 1.2 or above on every connection, including between the application and the database, which refuses unencrypted connections.
- Data at rest encrypted with AES-256 by the cloud platform.
- Credentials you connect - an AI provider key, a CRM token - encrypted at the application layer with AES-256-GCM under a separate key. An authenticated cipher, so tampering is detected rather than silently decrypted.
Access
- Authentication through WorkOS. We do not store passwords.
- Two-factor authentication available to every account, by authenticator app or emailed code, and an administrator can require it for the whole organisation.
- Signing out, revoking another device, or resetting a password ends that session on the next request rather than waiting for a token to expire.
- Roles are re-checked on the server for every request. Hiding a control in the interface is never treated as an access control.
Tenancy
- Every watch list, signal, page capture and report is scoped to the owning organisation in the query itself, not filtered after the fact.
- The organisation is resolved from the session on the server. It is never read from a request body, which is where multi-tenant leaks usually come from.
What we collect, and what we refuse to
- Publicly accessible pages only. We do not sign in to anything, create accounts, or reach content behind a login.
- Every URL you supply is resolved before it is fetched and rejected if it points anywhere private, and every redirect is re-checked rather than followed blindly.
- Content we fetch is treated as untrusted input everywhere it is used, including when it reaches a model.
Audit
- Sign-ins, role changes, invitations, API tokens, exports, connected assistants and billing events are recorded with the actor and the time.
- Every claim the product makes about a competitor is linked to the observation behind it, and that record is exportable.
- Assistant access is logged too - it happens outside the dashboard, where nobody watching the interface would see it.
Your data, on your terms
- Export everything your organisation holds, from settings, at any time.
- Delete your account yourself. Deletion is scheduled with a grace window rather than immediate, so a mistake is recoverable.
- History retention follows your plan and is enforced, not advertised. You can shorten your own window; you cannot extend it past what the plan includes.
The full documents
- Information Security Addendum
Every control, including the ones we describe as planned rather than operational.
- Security practices
Our statement under the IT Act and the CERT-In directions.
- Data Processing Agreement
Including the sub-processors we use and what each one does.
- Responsible disclosure
How to report something you have found, and what to expect back.
What we do not have yet
No SOC 2 report and no ISO 27001 certificate. SAML single sign-on is not offered; sign-in is by password or a single-use email code, with a second factor where enrolled. If any of these is a requirement for you, say so in a demo and we will tell you where it sits rather than let a procurement cycle find out.
Send this to your security reviewer.
Everything above is on the site, with the binding documents linked. No form, no gate.