Security
Security at Growth Dept Email
How the platform is built to keep accounts and shoppers' data safe. To report a vulnerability, email hello@growthdept.ai with “Security” in the subject line.
Hosting
- Where it runs
- The application runs on Vercel and the database is Neon Postgres, both in the US east region (Washington, D.C. area).
- Secrets
- Platform secrets are held as sensitive environment variables, never in the code repository.
Separation between accounts
- Row-level security
- Every table with account data carries the account's id, and Postgres row-level security limits each transaction to one account. The application's database role cannot bypass it, so a query that forgets its filter still sees only one account.
- API keys
- A private key belongs to one account and carries the scopes chosen when it was created.
Personal data
- Where it lives
- Shoppers' names, emails, phones, addresses, event properties and message bodies are stored only in the account's own tables. Logs, job payloads, the audit log and error messages carry ids.
- Credentials you connect
- Shopify tokens and provider keys are sealed with AES-256-GCM before they are stored, with a separate derived key for each purpose.
Sign-in
- Methods
- Google sign-in or a password. Passwords are stored as hashes, never as text.
- Two-factor
- Any user can add an authenticator app for two-factor sign-in.
- Lockout
- Five failed sign-ins within 15 minutes lock that address for 15 minutes, whether or not an account exists for it.
- Requests
- Signed-in requests that change data need a CSRF token tied to the session.
Reporting a vulnerability
- What to send
- Email hello@growthdept.ai with what you found, how to reproduce it and the account or URL involved. Please do not access other people’s data or disrupt the service while testing.
- What we do
- We confirm we have it, look into it, and tell you what we changed.