Zime does not sell customer data. The providers below receive customer data to run Zime's service. Zime gives 30 days' notice before adding or replacing a sub-processor, and you can object on reasonable data protection grounds.
Sub-processor list
| Provider | What it does for Zime | Customer data involved | Location |
|---|---|---|---|
| Amazon Web Services | Hosting, databases and file storage; AI models through Amazon Bedrock; email sending (Amazon SES) | All service data except meeting recordings | US East (N. Virginia); email sending from US West (Oregon) |
| Backblaze | Storage of meeting recordings | Meeting video and audio | United States (US East) |
| Google Cloud | Storage of meeting recordings; AI models (Vertex AI, Gemini); translation | Recordings, transcripts, emails logged in your CRM, AI prompts and outputs | Storage: United States. AI processing: Google regions in the US, Canada, the EU and Japan, and Google's global endpoint |
| Recall.ai | Notetaker bot that joins and records meetings | Meeting audio, video, captions and participant names | US (N. Virginia) |
| OpenAI | AI for Ask Zime, prep notes, deal highlights and search | Questions, call excerpts, CRM, email and calendar context | US |
| Anthropic | AI for document generation; backup model for Ask Zime and prep notes | Deal details, call summaries and questions, when these features are used | US |
| OpenRouter | Routes backup AI requests to other model providers; powers the in-app search box | Prompts, including call transcripts, when a backup model is used; text typed into the search box | US; the model provider it routes to can be outside the US |
| Deepgram | Transcription of multilingual calls, calls without captions and uploads; live transcription | Call recordings and live meeting audio | US |
| ElevenLabs | Voice in AI Roleplay and Ask Zime; live speech to text | Voice audio, roleplay transcripts and answer text | US |
| Qdrant | Search index for Ask Zime | Transcript and document excerpts, embeddings, participant names and emails, deal fields | US (N. Virginia) |
| Langfuse | Monitoring of AI quality and cost | AI prompts and outputs, with the user's email | EU |
| LangSmith | Tracing of AI requests | AI prompts and outputs | US |
| Judgment Labs | Evaluation of AI output quality | AI prompts and outputs from Ask Zime, prep notes and deal highlights | US |
| New Relic | Application monitoring and logs | Application logs and request data | US |
| Exa, with Firecrawl as backup | Web search for Ask Zime | AI-written search queries, which can include company, prospect or competitor names | Exa: not published; Firecrawl: US |
| Amplitude | Product usage analytics and session replay | User names, emails, roles and clicks; screen recordings of app sessions, which can show call and CRM content | US |
| PostHog | Usage analytics and session replay in the Zime mobile app | User email, company name, meeting titles and app screens | US |
| Microsoft | Azure Bot Service relays messages between Teams and the Zime app for Teams; Azure Speech serves an older transcription path | Messages exchanged with the Zime bot; meeting titles and recording links sent for transcription | Bot Service: Microsoft global service. Speech: US |
| GitHub | Hosts Zime's code, including the skills Zime builds for a customer | Skill files built for a customer | US |
Zime's own team in the United States and India, including Zime's subsidiary Inner Fit Labs Private Limited, can access data for support and engineering. Zime's email (Google Workspace) keeps copies of the prep-note, post-call and account emails Zime sends to users. Zime's Slack receives operational alerts that include company names, user emails and meeting titles.
Not sub-processors
Not sub-processors: Microsoft 365, Zoom, Google Calendar, your CRM, the call tools you import from, and AI assistants you connect to Zime (such as Claude) are your own systems, used at your direction. So is your own cloud storage, if Zime keeps your recordings there.