Security
Last updated November 19, 2026
Infrastructure
- Soundev runs on DigitalOcean in the United States, with a managed Postgres database that is encrypted at rest and backed up daily.
- All traffic uses HTTPS (TLS 1.2 or newer), including connections to the database.
- Production access is limited to the people who run Soundev. Secrets live in encrypted environment settings, never in code.
Accounts and keys
- Passwords are hashed with scrypt and a unique salt. Session cookies are HTTP-only, secure and same-site.
- API keys and agent access tokens are shown once and stored only as SHA-256 hashes. Keys can be read-only or read-write and revoked any time.
- AI agents connect through OAuth 2.1 with PKCE; you choose the workspace and whether they may make changes, and you can disconnect them under Settings → API keys.
- HubSpot, Attio and Linear tokens are encrypted with AES-256-GCM before they are stored.
- Webhooks are signed with HMAC-SHA256 so you can check they came from us.
Your data
- Each workspace's data is separated and every query is scoped to it.
- Payments are handled by Whop; card numbers never touch our servers.
- AI scoring uses Anthropic's API, which doesn't train on the content we send.
- We collect only public content and never ask for your social media passwords.
Report a vulnerability
If you find a security issue, email [email protected] with the details and steps to reproduce it. Please give us reasonable time to fix it before telling anyone, and don't access other people's data or disrupt the service while testing. We reply within 2 business days and won't take legal action against good-faith research.