Workspace isolation
Every record belongs to one workspace. Requests and background jobs run inside that workspace, and the database enforces the same boundary with row-level security.
Every record belongs to one workspace. Requests and background jobs run inside that workspace, and the database enforces the same boundary with row-level security.
Mailbox passwords and connector keys are encrypted at rest with AES-256-GCM and never shown again after you save them. API keys are stored only as hashes.
Verified email or Google sign-in, sessions in HttpOnly cookies, same-origin checks on every change, and role-based access within each workspace.
Opt-outs are honoured immediately. Anyone can ask us to stop all email to their address and erase it from every customer workspace at our privacy request page.
Owners can export workspace data at any time and schedule deletion. Deletion stops all work at once and removes the data after a 30-day grace period.
AI requests go to providers configured not to train on or retain your data, with structured outputs and spending limits.
See the sub-processor list and the data processing addendum.