Security
CallPlus keeps each workspace's data apart, stores the keys you connect encrypted, and serves everything over HTTPS. To report a vulnerability, email support@autobot360.com.
How data is protected
- Workspaces are isolated
- Every workspace's data sits behind row-level rules in the database, so one workspace cannot read another's even if a query is wrong.
- Keys are stored encrypted
- API keys and tokens you connect (telephony, WhatsApp, speech and email providers) are stored encrypted, not in plain text.
- Encrypted in transit
- The site and API are served over HTTPS with HSTS, and send security headers such as a content security policy and no framing.
- Limits on abuse
- Sign-in and public endpoints are rate limited. Concurrent calls and spend can be capped per workspace.
- An audit trail
- Important actions in a workspace, such as launching a campaign or recording consent, are written to an audit log.
- Privacy by default
- Call recording is off until turned on. Consent and opt-outs are recorded, and STOP applies across channels.
Reporting a vulnerability
Email support@autobot360.com with what you found and how to reproduce it. Please do not access other people's data, disrupt the service, or publish details before we have had a chance to fix it. Our machine-readable contact is at /.well-known/security.txt.
We do not claim any security certification on this page. See also privacy and the terms.