How the protection works
How we protect your call recordings
Where the audio lives, how your integration keys are encrypted, who inside the company can open which calls, and what happens to the data if you decide to leave.
The foundation
4 safeguards that work by default
The path a recording takes
What happens to a file between the phone system and the dashboard
The phone system's webhook is checked against a secret. A request without the right signature creates no call.
The audio is uploaded to encrypted storage. File links are signed and short-lived.
Transcription and analysis happen inside your workspace. The result is bound to your company.
Only the roles that should see data can see it. Every request is token checked.
Access
A rep never sees anyone else's calls
This is not a setting you have to remember to switch on. It is how the roles work by default.
- Token authentication on every request
- Rate limiting on the API
- Secret checking on inbound webhooks
- SSO on the Enterprise plan
| Role | What they see |
|---|---|
| Owner | The whole company, the team, integrations, billing |
| Admin | The whole company, the team, integrations |
| Sales rep | Only their own calls and their own metrics |
| Coach | Team analytics for coaching |
| Analyst | Data and export |
Retention and deletion
The data is yours — you can take it at any time
Security questions
Need something for your legal or security team?
Tell us which documents you need and we will send what exists, without vague language.