To identify the categories of third-party providers used to deliver infrastructure, communications, AI, security, and onboarding services
Subprocessors
This page explains how ChatnCall.ai approaches subprocessors and the types of third-party services that may process customer or platform data when a deployment is active.
The active provider mix can vary depending on the channels, regions, and integrations enabled for a customer deployment
Customers can request deployment-specific subprocessor details during onboarding, procurement, or contract review
How we use subprocessors
ChatnCall.ai may use carefully selected third-party service providers to help host, secure, operate, monitor, and deliver the platform. These providers may process customer or platform data only to the extent needed to deliver the relevant service. We use a mix of standard platform providers and deployment-specific providers depending on the channels and workflow configuration agreed with the customer.
Common subprocessor categories
- Infrastructure and hosting providers used to run the website, application, storage, and operational environments
- Communications providers used for voice, telephony, chat, or business messaging delivery
- Meta and WhatsApp Business services used when a customer chooses to connect WhatsApp or related business messaging assets
- AI and workflow providers used when customers enable language-model or automation features within the platform
- Security, monitoring, support, analytics, or authentication providers used to protect and operate the service
Examples of deployment-linked providers
- Meta Platforms services for WhatsApp Business onboarding, connected messaging configuration, and WhatsApp message delivery where Meta channels are enabled
- Twilio or similar communications providers for voice or messaging routing where those channels are enabled for the deployment
- AI model providers such as OpenAI or other approved model vendors where customers enable AI-assisted workflows using those services
Customer-specific and region-specific configurations
Not every customer deployment uses the same providers. The enabled channels, selected models, geographic footprint, procurement requirements, and agreed architecture can all change the final provider set. Where a customer needs a formal subprocessor schedule, deployment-specific legal review, or notice commitments, those items should be addressed during onboarding or in the relevant contract documents.
Questions and notices
If your team needs the current deployment-specific subprocessor list, supporting DPA materials, or additional information about data handling, contact sales@chatncall.ai as part of procurement, onboarding, or compliance review.