Security, roles & access
Understand the boundaries around workspace data and operational access.
Tenant isolation
API keys are bound to one tenant. API authorization and PostgreSQL row-level security apply tenant scope to business data. Support, finance, and platform administrator permissions are distinct. Keep each integration’s keys separate.
Team roles
Owners manage membership; owners, admins, and developers manage integrations and sending. Campaign managers operate audiences and campaigns. Billing members access finance. Analysts read workspace data. Platform staff have additional, explicitly scoped access. Production platform access requires multi-factor authentication.
Protect credentials
Store API keys in a server secret manager or environment. Use narrow scopes and rotate keys deliberately. Never include secrets in frontend code, screenshots, public logs, contact messages, or support tickets. Enroll multi-factor authentication from Account security.
Operational records
The platform retains durable delivery events, consent changes, audit actions, and immutable financial records. Message-content retention can be configured within your plan allowance. Body expiry does not delete accounting evidence or backups. Contact inquiries are stored separately for administrator follow-up.