Security and privacy
How your account, your contacts and your conversations are protected.
Accounts kept apart
The database limits every query to one account, so one account can never read another's data.
Credentials encrypted
Channel tokens and other per-account secrets are sealed with AES-256-GCM before they're stored.
Strong sign-in
Google, passkeys, single sign-on, and passwords with two-step codes.
A record of changes
An audit log of account changes, and a log of every time Growth Dept staff open an account.
We don't hold security certifications yet. When we do, they'll be listed here.
Your contacts trusted you with their messages. We keep them separate, encrypted where it matters, and out of places they don't belong.
Privacy
Requests from your contacts
When a contact asks for their data or asks to be forgotten, the privacy requests page in your account handles it.
Deleting an account
Deleting an account disconnects its channels at once, and its data is purged 30 days later.
Consent
Opt-ins are stored with when and where they were given; opt-outs stop messages on that channel at once.
Read the privacy policy and the data processing terms.
How it's built
- In transit
- Every page and API call is served over HTTPS.
- Pages
- A strict content security policy with a fresh value per request, and pages that refuse to be framed.
- Forms
- Cross-site request checks on every change, and rate limits on sign-in and public forms.
- Personal data
- Contact names, handles, emails, phone numbers and messages stay in their own tables and never go into logs, background jobs or error reports.
- Outgoing requests
- Requests to your servers go only to public addresses over HTTPS, so a flow can't be used to reach private networks.
- Webhooks
- Every webhook we send is signed, and the platforms' webhooks to us are checked against their signatures.
Security questions
Found a security problem?