How connections are secured
Rather than a general statement about encryption, here's what's specifically true about how connections into and out of the platform are secured.
Webhook connections require a valid TLS certificate
The public endpoint that receives live call events must have a valid TLS certificate matching its exact hostname. A mismatched or missing certificate, for example a certificate that only covers a bare domain when a www subdomain is used, will cause the connection to fail rather than fall back to an unencrypted one.
Why this requirement exists
Live call data, transcript content and call status, travels over this connection as a call happens, so requiring a valid, correctly matched certificate is a deliberate part of how that connection is set up.
Encryption at rest
We don't publish a specific at-rest encryption spec on this page. For a complete technical answer covering encryption at rest and any details specific to your deployment, reach out to our team directly.
Frequently asked
The connection will fail. This is a known, documented setup issue, for example a certificate that only covers a bare domain won't work for a www prefixed version of that domain.
More security topics
This page describes, plainly, what data moves through Dialbotix, where it goes, and what protections are actually in place today, rather than a generic security statement.
Running a call involves more than one system working together. Here are the specific named services involved, and what each one is responsible for.
Retention isn't the same for every type of data in the platform. Here's specifically what's kept, for how long, and what deleting something actually does.
Need a detailed technical answer on encryption?
Talk to our team directly about your specific setup.
