Your calls are private. Here’s how we keep them that way.
ListenFox stores your calls on servers it manages at Hetzner in the EU, doesn’t train AI models on them or sell them, and hides card numbers by default. It holds no SOC 2, ISO 27001 or HIPAA certification today.
Last reviewed: 12 November 2026
Call recording security at a glance
| Where data lives | Servers we manage at Hetzner, in the EU, behind Cloudflare |
|---|---|
| Who else processes it | Speech-to-text and AI providers, listed by kind on the subprocessor list |
| AI training | We don’t train models on your calls or sell your data |
| Sensitive details | Card numbers are hidden by default; you switch the other categories on per workspace, before the transcript is stored |
| Certifications | None today: no SOC 2, ISO 27001 or HIPAA |
| Deleting | A call, a source, a caller, a workspace or your account, audio first |
What protects your calls today.
Sign-in
Passwords are hashed with argon2id; we never see them. Sessions are random tokens in httpOnly cookies, every change carries a CSRF token, and repeated failed sign-ins lock the account for a while.
One door to every workspace
Every request for workspace data, from the app or an API key, checks that the person is a member and what their role allows. Share links you create are the one exception.
Encrypted source credentials
Tokens and passwords for your phone systems are encrypted at rest.
Sensitive details masked
Card numbers, ID numbers, bank account numbers, and passwords or codes said aloud can be masked. Redaction happens before the transcript is stored, so the AI, search, alerts, exports and share links only ever see the masked text.
Verified email before spending
For a new account, no call is transcribed until someone on the account verifies their email address.
Audit log
Sensitive actions, like adding a source or deleting a call, are recorded with who did them and when.
Delete for good
Delete a call, a whole source, every call from one caller, a workspace or your account. The audio goes first, then the transcript, every finding and AI note attached. Admins can also set how long calls are kept and download everything.
Share links that end
A shared call link expires on the date you set, stops working as soon as you revoke it, and counts its views.
Outbound requests guarded
Webhooks we send and websites we read for your knowledge base can’t be pointed at internal addresses.
Four roles. Each sees what it should.
Invite your team by email and give each person a role. Whoever created the account is its owner and always an admin.
Everything, including deleting calls for good.
Runs the team: coaching, digests and team-wide settings.
Reads calls, dashboards and contacts, and uses Ask.
The team’s calls, or only their own on Growth and above. Only their own scores.
Where your data lives, and who else touches it.
Transcription and AI analysis are done by outside providers, some in the US. The subprocessor list shows each kind, what it receives and where, and we tell customers before a new one starts.
- Standard and Deep send audio to a speech-to-text provider’s EU region; we ask it to delete each transcript once we have it.
- AI analysis allows only zero-data-retention providers, except at Deep, where offered: its AI provider may keep call data briefly.
- Quick sends audio through an AI routing provider to a speech model, under that provider’s retention terms.
Business customers can accept our Data Processing Agreement in Settings.
Not available yet.
If any of these is a must-have for you, tell us at hello@listenfox.com or in a demo.
Redacting the audio of a recordingRedaction works on the transcript; anyone allowed to play a call can still hear it
On the roadmapSingle sign-on (SSO)
On the roadmapCustom roles
On the roadmapSecurity certificationsSOC 2, ISO 27001, HIPAA or similar
Not yet
Security questions
Are you SOC 2 or HIPAA certified?
No. ListenFox doesn’t hold security certifications today. If you need one, tell us.
Where is our data stored?
On servers we manage at Hetzner, in the EU. Transcription and analysis providers receive a call to process it.
Do you train AI on our calls?
We don’t train models of our own on your calls, and we don’t sell your data. AI analysis goes only to providers that keep no copy and don’t train on it, except at the Deep effort level where it is offered. We ask our main speech-to-text provider to delete each transcript once we have it.
How do I delete our data?
Delete a call, a source, a workspace or your account in the app. Or email us from the account address and we remove it within 30 days.
Found a security problem?
Email security@listenfox.com (the address in our security.txt) with what you found and how to reproduce it. Please don’t test against other customers’ data.
Read the privacy policy for what we hold, why, and how to have it deleted.
Test the controls on your own calls.
Plans from US$9 a month.
Book a demo and we’ll answer your security questions against the code, not a brochure.