How Dialbotix actually handles your data
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.
What data passes through the platform
Lead information you provide, name, phone, email, and company, along with the resulting call recordings, transcripts, and outcomes generated by each call.
Where that data goes
Calls are placed through Vapi and Twilio, transcripts are analyzed by OpenAI to determine call outcome, and bookings are created through Google Calendar when connected. Each of these is a named service your data passes through as part of running a call.
What's stored and for how long
Call logs, including the transcript and recording, are retained for 14 days, matching the retention window used by our voice infrastructure provider, Vapi. After that window, the recording and transcript are no longer available, even if the call log entry itself remains.
Frequently asked
Not yet. We're actively working toward SOC 2. See the compliance page for a straightforward summary of where things stand and how to get more detail for your specific requirements.
More security topics
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.
Every call produces a recording alongside its transcript. Here's how that recording is actually handled, from creation to the end of its retention window.
Have a specific security question?
Talk to our team directly about your requirements.
