How we use subprocessors
To run Conduit we rely on a limited number of third-party “subprocessors” that process data on our behalf. Every one is bound by a written contract to confidentiality and to data-protection terms at least as strict as ours, may use the data only to provide its service to us, and may never train AI models on your data. Data is processed in US data centers, encrypted in transit and at rest.
When we add or replace a subprocessor, we notify account owners — so you always know who processes your data and can raise a concern before the change takes effect.
Categories of subprocessor
The providers we rely on fall into these categories:
- Cloud hosting & application delivery
- Managed database
- Telephony & SMS
- Voice AI & speech-to-text
- Language-model (LLM) processing
- Recording storage
- Payments
- Transactional email
- Calendar & sign-in (services you choose to connect)
- Analytics & error monitoring
Google user data (your sign-in profile and any calendar you connect) is handled under the Limited Use terms described in our Privacy Policy.
Get the current list
We keep the specific, named list of subprocessors — with what each one does and what data it sees — available on request rather than published in full. Email support@conduitapp.aiand we'll send you the current list.
Data Processing Agreement
Need a Data Processing Agreement (DPA)? One — with the Standard Contractual Clauses for EU/UK transfers and the current subprocessor list attached — is available on request. Email support@conduitapp.aiand we'll send it over.