Who's responsible for what: controller and processor roles
For the personal data in your leads and campaigns, the responsibilities split a specific way. Here's exactly how.
You are the data controller
For personal data contained in the leads and campaign data you upload or connect, you, the customer, act as the data controller. You determine the purposes and lawful basis for processing that data.
Dialbotix is the data processor
Dialbotix processes personal data only on your documented instructions, for the purpose of providing the AI voice automation service. We don't determine the purposes or legal basis for processing your lead data.
What this means practically
Ensuring you have valid consent to contact the people in your leads, and complying with telemarketing and privacy laws in your jurisdiction, is your responsibility as the controller. We provide the technical tooling; we don't independently verify your consent basis.
Frequently asked
No, as a processor we're still responsible for how we handle data on your behalf, security of our systems, and processing only on your instructions. The controller/processor split specifically concerns who determines the purpose and legal basis for processing your lead data.
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.
