Most conversation intelligence is SaaS-only, which means your customer recordings leave your network and live on a vendor's infrastructure. For a lot of insurers, banks, and health systems that single fact ends the evaluation. Overtone was architected the other way round.
Transcripts, scores, metrics, and the search index all persist in your SQL Server. Audio is streamed into memory from your recorder and discarded after transcription — never written to disk anywhere.
We ship containers and Terraform into your own Azure, AWS, or GCP subscription. You hold the keys, own the network, keep the logs, and pay the cloud bill directly.
Single-tenant storage per customer in a US or EU region. Fastest path to value, and you can migrate to private cloud later without re-implementing.
This is the diagram your security architect actually wants. In an on-premises deployment there are exactly three places data exists, and only one of them persists anything.
Recordings stay in the source system. Overtone reads them over your own network via API, into memory, and releases the buffer the moment transcription returns. Nothing is copied to a staging store.
Speech and language models receive a call and return text. Nothing is retained, logged, cached, or used for training — enforced contractually with providers and verified by architecture tests in every release.
Transcripts, scores, metrics, and the full-text index persist only in your SQL Server. Retention, backup, and destruction follow your policy, on your schedule, under your DBA's control.
Negative guarantees are usually more useful in a security review than positive ones, so here are ours in plain language.
Redaction runs between transcription and persistence — not as a display filter afterwards. By the time a transcript reaches your database, the sensitive spans are already gone or tokenized.
You choose per data class whether a masked span is recoverable by privileged role for dispute resolution, or irreversibly destroyed at capture. Most regulated customers destroy PCI data and tokenize everything else.
Reports, penetration test summaries, and our completed CAIQ are available under NDA. Ask your account team or write to security@alphadecibel.com.
Security, availability, and confidentiality. Annual audit with continuous control monitoring between cycles.
Information security management system covering product, infrastructure, and corporate operations.
BAA available. PHI masked before persistence; on-premises deployment keeps PHI entirely inside your covered entity.
EU region election, standard contractual clauses, DPA, and documented subprocessor list with change notice.
Consumer rights request handling, including deletion propagation into transcripts and the search index.
Card data destroyed at capture, so Overtone reduces rather than expands your cardholder data environment.
Disclosure, replacement, and suitability evidence packs for insurance regulators across 50 states.
Pursuing authorization for public sector deployments. Target authorization in the next fiscal year.
| Area | Practice |
|---|---|
| Encryption | AES-256 at rest, TLS 1.3 in transit. Customer-managed keys on private cloud and on-premises. |
| Access control | Least privilege, enforced MFA, quarterly access reviews. Production access is break-glass, ticketed, time-boxed, and logged. |
| Network | Outbound-only from on-premises deployments. Private endpoints and no public ingress in private cloud. |
| Secrets | Hardware-backed key storage. No credentials in source, enforced by pre-commit and CI scanning. |
| SDLC | Mandatory peer review, SAST and dependency scanning on every pull request, signed builds, reproducible releases. |
| Testing | Automated architecture tests assert no audio write path and no cloud storage resource exists in on-prem builds. |
| Penetration testing | Independent third-party test annually plus after any material architecture change. Summary shared under NDA. |
| Vulnerability management | Critical patched within 7 days, high within 30. Continuous dependency monitoring with automated PRs. |
| Monitoring | Centralized audit logging with tamper-evident storage. Customer-side events streamable to your SIEM. |
| Incident response | 24×7 on-call, documented runbooks, tabletop exercises twice yearly. Customer notification within 24 hours of confirmed incident. |
| Business continuity | Active-passive DR with documented RPO of 15 minutes and RTO of 4 hours. Restore tested quarterly. |
| Personnel | Background checks, annual security training, role-based training for engineers handling customer data. |
| Subprocessors | Published list with 30 days' notice before any addition. On-premises deployments can run with none. |
If you believe you've found a vulnerability in Overtone or in our infrastructure, we want to hear about it before anyone else does. Write to security@alphadecibel.com. We acknowledge within one business day, keep you updated through remediation, and credit researchers who ask to be named.
We'd rather start with your security team than end with them. Send over your vendor assessment and we'll return it completed, with architecture diagrams, before the first commercial conversation.