Security
Call recording security, mechanism by mechanism.
Callnsight holds a record of who called whom, and often the audio of what was said. This page is the specifics: who gets in, what they reach once they have, where the recordings actually sit, and what we do not claim.
Who gets in, and what they reach
- Two factors, and a code you keep
- Sign in with a password and a time-based second factor, with recovery codes for the phone that ends up in a drawer. Two-factor is on every plan, not held back for the top one.
- Google signs people in, never up
- Turn on Google Workspace sign-in and Callnsight matches a Google-verified address against a user that already exists here. An address nobody set up is refused, and you can restrict sign-in to your own domain.
- Deactivating a user closes every door
- One flag. Password sign-in, Google sign-in and every API token check the same thing, so a leaver loses the browser and the integration in the same move — and deactivating an account does it for everyone on it.
- Downloading is a permission, not a link
- Recordings play in the browser with a waveform, so listening never needs a copy of the file. Downloading one is a permission you grant per user, and on the API a separate ability you grant per token.
Where the recordings live
Secure call recording storage starts with owning the storage.
On any plan, recordings can be written to your own S3 bucket or SFTP server instead of ours. The audio is then never held at rest on our infrastructure — it passes through our systems to be retrieved, indexed and given a waveform, and then it sits in a location you chose, under the encryption and access rules you already wrote. We hold the call record and a pointer to the file; you hold the file.
Retention runs one way. Your plan sets how long the app remembers a call — thirty days on the Trial through three years on Business — and when that window passes we prune our own rows and our own copies. We never delete a byte from your storage. The audio stays in your bucket under your own lifecycle rules, which is also why an upgrade can re-index history rather than lose it.
Callnsight itself is operated from the United States, and our application and databases run there. Where you have brought your own storage, the recordings sit wherever you put them: that location is your choice, and ours only to read from. The privacy policy sets out what is held where, and who else touches it.
Inside the application
Five properties of the system, rather than five promises about it.
- Tenancy
- Every read of your calls, recordings, files and users carries your account id, attached by the model layer rather than by whichever page asked for them — with tests that assert one account cannot reach another’s calls.
- Credentials
- PBX, storage and transcription provider secrets are encrypted before they reach the database, and the audit log records a redaction where the value would be.
- Passwords
- Twelve characters at minimum, with mixed case, a number and a symbol, checked against known breach corpora at the moment they are set, and stored only as a bcrypt hash.
- Audit log
- Who changed what, against an actor and an account — and your own admins can read your account’s log, rather than having to ask us for it.
- API tokens
- Bearer tokens carry abilities. A token that lists calls cannot fetch recording audio unless you granted it that separately.
What we do not claim
No badges. Nobody has audited us, and we will not imply otherwise.
Callnsight holds no SOC 2, ISO 27001, HIPAA or PCI DSS attestation, and calls itself compliant with nothing. A certificate is a statement an auditor makes, not one a vendor makes about itself, and we have not engaged one. So the page above lists mechanisms instead — things you can ask us to demonstrate, rather than things you have to take on faith.
Nor do we claim that nobody here can reach your data. Somebody on our side connects your phone system and picks up your support ticket, and the operator accounts that make that possible are not fenced out of an account. Changes made from them land in the audit log exactly as your own do. If you would rather the audio never sat on our disks at all, that is what bringing your own storage is for.
The obligations stay yours as well. Recording law differs by state and by country, and consent, notification and how long you are required to keep a call are your calls to make — our terms say so plainly. What the product can do is make the parts a reviewer usually argues about concrete: the audio can live in infrastructure you have already had assessed, access is granted per user and per permission, and the log says who did what.
If procurement needs our infrastructure providers named, or an answer this page does not carry, ask and we will put it in writing.
Questions
- Where are call recordings stored?
- On your own S3 bucket or SFTP server if you want it that way — the option is there on every plan. Callnsight writes the audio to your storage and keeps the call record and a pointer to it, so the recording is never held at rest on our infrastructure. If you would rather we kept it, we can.
- Can I choose where my call recording data lives?
- For the audio, yes. Bring your own storage and the recordings sit wherever you put that bucket or server — your region, your keys, your lifecycle rules. Callnsight itself is operated from the United States, and the call records, the metadata and any transcripts are held there.
- Are call recordings encrypted?
- Be precise about what any vendor means by that. What Callnsight encrypts in its own database is credentials — the keys and passwords for your PBX and your storage — which are encrypted before they are written and never sent to the browser. The recording audio is protected by the storage it sits on, so when the bucket is yours, your encryption settings and your keys are the ones that apply. We do not add a layer of our own on top of that, and we would rather say so than let you assume one.
- Who can download a call recording?
- Only a user you have given the download permission to. Listening does not require it: recordings play in the browser with a waveform and scrub without the file being downloaded first. On the JSON API it is a separate token ability, so an integration that lists calls cannot pull audio unless you said it could.
- Can one customer see another customer’s calls?
- No. Callnsight is multi-tenant, and the tenant filter is attached to the records themselves rather than remembered by each screen: a query for calls, recordings, files or users is constrained to the account of the user who made it, whether it came from a page, an export or the API.
- Is Callnsight SOC 2 certified or HIPAA compliant?
- No, and be wary of a vendor that certifies itself. Callnsight holds no SOC 2, ISO 27001, HIPAA or PCI DSS attestation, because no auditor has assessed us against one. What we can do is describe mechanisms — per-account isolation, permissions, encrypted credentials, an audit log, and the option to keep the audio in infrastructure you have already had assessed — and answer your questionnaire in writing.
- What happens when someone leaves the company?
- Deactivate them, and the same check that gates password sign-in gates Google sign-in and every API token they held, so the browser and the integration close together. What they did stays in the audit log, and the calls stay with the account rather than with the person.
Send us the security questionnaire.
We would rather answer it than have you guess. Tell us what you run, where the recordings have to live, and what your reviewer needs to see.