Subprocessors

To provide the Services, Callario engages third-party providers ("subprocessors") that process personal data on our behalf. This page lists the categories of subprocessor we use, organised by the function each performs.

Callario is an early-stage company running a supervised alpha, so these arrangements may change as the Services evolve. This page mostly describes functions rather than naming providers; we name a provider where the arrangement is settled, and will add the others as they are formalised.

Each subprocessor is engaged only for the function described and is expected to process personal data under appropriate data protection obligations, as set out in our Data Processing Addendum.

Infrastructure providers host the application, store its data and run the compute and networking that operate the Services.

Callario currently runs in a single hosting region and does not offer a choice of data-residency region. If that changes, it will be described on this page before it is offered.

An email-delivery provider sends the messages the Services send today — sign-in codes, invitations, password resets, notifications, updates to a customer about their request, and your team’s replies to customers who wrote in by email — and an inbound-email provider (today, Postmark) receives the emails customers send to your support address.

When a Customer connects a messaging channel — WhatsApp, Facebook Messenger, Instagram, Telegram, Slack or SMS — messages between the Customer and its own customers pass through that channel’s provider so they can be delivered.

Apps a Customer connects with its own key or token (for example a store, payment or calendar app) act on the Customer’s instructions under the Customer’s own agreement with that provider.

Error-monitoring and logging providers help us detect, diagnose and fix technical problems and keep the Services reliable and secure.

This category may process technical data and the limited context needed to identify and fix an error. It supports operational stability, not profiling.

Large-language-model providers power the platform's AI features: the AI agent, Copilot, AI triage, the knowledge writing assistant, workflow AI steps and search over your knowledge.

Data sent to these providers is used to produce results for the Customer within the Services. Callario does not permit Customer data to be used to train foundation models. AI processing runs under the controls described on our Security page, including guardrails on every turn and the scrubbing of personal data from the AI traces we store.

Callario does not use a third-party product-analytics provider today, on this website or in the console. If we add one, it will be listed in this category first.

We will keep this page current as our subprocessor categories change, and will give customers a way to learn of material changes so they can raise reasonable data protection concerns.

For questions about our subprocessors, or for more detail in connection with a customer agreement, write to us through our contact page.