Who's responsible for consent and disclosure
Placing calls, especially AI assisted ones, comes with legal obligations around consent and disclosure. Here's specifically where that responsibility sits.
You're responsible for consent
You are solely responsible for ensuring that everyone contacted through the platform has provided valid consent for automated or AI-assisted voice communication where required by applicable law, including the TCPA in the US and GDPR/ePrivacy in the EU/UK.
You're responsible for call recording disclosure
Where applicable law requires notifying call recipients that a call is being recorded or is AI-assisted, providing that disclosure is your responsibility as the party initiating the campaign. We provide recording and transcription as a technical feature.
What we provide to help
Do Not Call scrubbing, internal DNC list support, and time-of-day calling windows are available as tooling. We don't independently verify or validate end-user consent, and rely on customer-provided compliance configuration for lawful use of the platform.
Frequently asked
No, we don't independently verify or validate end-user consent. That responsibility sits with you as the calling party.
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 help configuring compliance tooling?
Talk to our team about DNC scrubbing and calling windows.
