Three things worth saying.
Not a full control list, on purpose. These are the three a reviewer cannot assume from any vendor, so they are the three worth reading here.
Tenant isolation is enforced at the database
Not only in application code. Every query runs inside a session scoped to one tenant with row-level security applied, so a bug in a feature cannot reach across the boundary that the database itself holds.
The AI cannot write to your records
Queries the assistant generates execute read-only, inside a transaction that cannot write, with a statement timeout, a hard row limit and a keyword blocklist, on a session already scoped to your tenant. The sandbox is the load-bearing control, not the prompt.
Full email bodies are not stored
Where Pipeline reads a mailbox, message bodies are deliberately not persisted at sync. It is a documented design decision, made to limit what exists at rest rather than a side effect.
Send us the
questionnaire.
If your security review asks something we have not covered here, send it over. A person will answer in writing, at the level your team works at.