How SupaMail handles email data.
This page describes how SupaMail processes email data, the safeguards currently in place, and the limits of those safeguards.
How email data is processed
SupaMail returns only the data required for each operation that the user authorizes.
- Mailbox provider
IMAP and SMTP remain the source for messages, folders, and attachment bytes.
- SupaMail
Synchronizes private mirror data and serves typed operations inside the User's Tenant boundary.
- Authorized AI client
Receives only the requested result when Claude, ChatGPT, Codex, or another authorized client calls SupaMail.
Current safeguards and limitations
These statements describe the service as it operates today.
- Isolation
- Tenant-scoped rows with Postgres row-level security.
- Credentials
- Encrypted before persistence and excluded from browser responses and logs.
- Message bodies
- Application-layer encrypted before storage with a per-Tenant key.
- Headers and metadata
- Sensitive fields are application-layer encrypted before storage with a per-Tenant key.
- Attachments
- Incoming files are fetched on request; outbound uploads are transient and expire within one hour.
- Deletion
- Account deletion is self-service in Settings; mailbox disconnection remains support-assisted.
- Analytics and monitoring
- PostHog and Sentry help us understand usage and fix problems using limited usage and technical data. Email content is excluded.
- Assurance
- No SOC 2, ISO 27001, or directory certification is claimed.
Detailed information
Public information for users, customers, and service reviewers.
- SecurityEncryption, Tenant isolation, credentials, access controls, and reporting.
- SubprocessorsProviders for hosting, storage, search, billing, email, analytics, and error monitoring.
- Data & deletionWhat is retained, what is not, and which controls remain manual.
- Service statusLive component checks, reporting limits, and the incident record.
- SupportProduct help, privacy requests, and security reporting.