Sub-processors
A sub-processor is a third party we engage to process data on our behalf so we can provide the Services. This page lists every sub-processor we may use, what it does, and the data it sees. It supports section 10 of our Privacy Policy.
What applies to every provider on this page
None of them may train on your data. Every sub-processor that handles customer data is engaged under terms that prohibit using data we send them to train or improve their own models. Data goes to them only to produce the immediate result your configuration requires, and for nothing else.
Most are optional. Only the infrastructure providers in section 1 apply to every account. The telephony, speech, and language-model providers in sections 2 to 4 process your data only if you select them in your agent configuration. A typical customer uses one telephony provider and one or two model providers — not the whole list.
Website analytics is scoped separately. Google Analytics appears in section 1 because it is not tied to an agent configuration, but it never touches customer content: it processes marketing-website visitor data only, and only after that visitor accepts analytics cookies. We configure the tag for measurement alone — Google Signals and ad-personalisation signals are switched off. What Google may do with the measurement data it collects is governed by Google’s own Analytics terms rather than by ours.
1. Platform & infrastructure
These apply across the platform rather than to a particular agent configuration. Note the scope differences in the last two rows: Google Analytics sees only marketing-website visitors, and the IP-geolocation provider sees only the IP address of a sign-in.
| Provider | Purpose | Data processed | Primary jurisdiction |
|---|---|---|---|
| Microsoft Azure | Cloud hosting, compute, database, object storage, and backups. | All customer data at rest and in transit through the platform. | India and United States, per your residency selection |
| Email delivery (SMTP) | Transactional email — account notices, booking confirmations, invitations, invoices. | Recipient name and email address, message content. | Depends on the SMTP provider configured for your deployment |
| Razorpay | Payment processing for subscriptions and prepaid balances. | Billing contact, amount, payment reference. Card details go directly to Razorpay and are never stored by us. | India |
| Google (Google Analytics) | Aggregate usage measurement for the imatic.ai marketing website — visit counts, which pages are read, and where visitors arrived from. Loaded only after the visitor accepts analytics cookies; not present in the portal, calendar or survey applications. Configured for measurement only, with Google Signals and ad personalisation disabled. | Website visitors only, never customer content: a pseudonymous cookie identifier, pages viewed, referring page, browser, device type and language, and the approximate location Google derives from the visitor’s IP address. | United States and global |
| IP geolocation provider
(vendor to be confirmed) |
Resolves the approximate location — typically country, region and city — of the IP address used to sign in, so that sign-in audit records show where an attempt came from and unfamiliar access can be spotted. Look-ups are cached and are skipped entirely for private or unknown addresses. | The IP address of the person signing in, and nothing else. No name, email address, account identifier or customer content is sent, and the look-up carries no information about which account the sign-in relates to. | To be confirmed with the selected vendor |
2. Telephony
Active only for the provider you connect. Carries call audio and the phone numbers involved.
| Provider | Purpose | Data processed | Primary jurisdiction |
|---|---|---|---|
| Exotel | Call origination and termination, call recording where enabled. | Call audio, phone numbers, call metadata. | India |
| Twilio | Call origination and termination. | Call audio, phone numbers, call metadata. | United States |
| Plivo | Call origination and termination. | Call audio, phone numbers, call metadata. | United States |
3. Speech — recognition & synthesis
Active only for the engines you select. Speech-to-text providers receive call audio; text-to-speech providers receive the text your agent is about to say.
| Provider | Purpose | Data processed | Primary jurisdiction |
|---|---|---|---|
| Deepgram | Speech-to-text. | Call audio. | United States |
| Azure Speech | Speech-to-text and text-to-speech. | Call audio; text to be spoken. | India and United States |
| Sarvam AI | Speech-to-text (Saarika) and text-to-speech (Bulbul), including Indian languages. | Call audio; text to be spoken. | India |
| ElevenLabs | Text-to-speech. | Text to be spoken. | United States |
| Cartesia | Text-to-speech. | Text to be spoken. | United States |
| Groq | Speech-to-text (Whisper) and low-latency inference. | Call audio; conversation text. | United States |
4. Language models
Active only for the model you select for an agent. These receive the conversation context needed to generate the next reply.
| Provider | Purpose | Data processed | Primary jurisdiction |
|---|---|---|---|
| Azure OpenAI | Conversation and reasoning. | Conversation text, agent instructions, retrieved context. | India and United States |
| OpenAI | Conversation and reasoning. | Conversation text, agent instructions, retrieved context. | United States |
| Anthropic | Conversation and reasoning. | Conversation text, agent instructions, retrieved context. | United States |
| Google (Gemini) | Conversation and reasoning, including real-time voice modes. | Conversation text or audio, agent instructions. | United States and global |
| Sarvam AI | Conversation and reasoning in Indian languages. | Conversation text, agent instructions. | India |
| Groq | Low-latency model inference. | Conversation text, agent instructions. | United States |
| OpenRouter | Routing to third-party models you select. | Conversation text, agent instructions. | United States |
5. Integrations you connect
Where you connect an external account, data flows to that service at your direction and under its own terms. The main one is Google Calendar — see section 5 of our Privacy Policy for exactly what we access and store, and the Limited Use commitments that apply.
6. Providers you bring yourself
Where you supply your own credentials for a telephony, speech, or model provider, that provider is your contractual counterparty rather than our sub-processor. You are responsible for its terms, and for any data-protection commitments you need from it.
7. Changes to this list
We update this page when we add or replace a sub-processor. Where a change materially affects the processing of your data, we will notify account holders by email or in-product notice before it takes effect, giving you a reasonable opportunity to raise a concern. If you have a reasonable objection on data-protection grounds, contact us and we will work with you on an alternative, or you may terminate the affected part of the Services.
To be notified of changes, or to ask which sub-processors are active on your account, write to hello@imatic.ai.
8. Contact
- Entity
- Vizionsys Technologies Private Limited
- Address
- Bengaluru, Karnataka, India
- hello@imatic.ai
- Phone
- +91 99675 80291