Last updated: July 6, 2026
Service providers that help Botchi operate the product.
This page lists the service providers Botchi uses to operate the Service. It is informational and does not override any signed data processing agreement or enterprise order form.
| Provider | Purpose | Data and transfer notes |
|---|---|---|
| WorkOS | Authentication, AuthKit hosted sign-in, sessions, and identity management. | Account identifiers, email addresses, session data, and authentication metadata. Global provider; transfer safeguards apply where required. |
| Convex | Primary database, file storage, realtime sync, and backend data services. | Chats, files, memories, account settings, tasks, tool records, and service metadata. Regions depend on deployment configuration and customer/service needs. |
| Vercel | Hosting, deployment, backend execution, observability, and AI Gateway routing. | Application traffic, request metadata, logs, deployment metadata, prompts and outputs where AI Gateway is used. Global provider, including the United States and European Union; transfer safeguards apply where required. |
| PostHog | Product analytics, usage telemetry, reliability events, and error diagnostics. | Account identifiers, feature usage, event metadata, AI usage telemetry, and reliability events. EU region where applicable. |
| RevenueCat | Mobile subscription entitlement management and store subscription status. | App user identifiers, product identifiers, entitlement status, and subscription metadata. Global provider; transfer safeguards apply where required. |
| Stripe | Business or web checkout, subscription, invoice, and payment processing where available. | Customer, checkout, invoice, subscription, and payment metadata. Botchi does not store payment card details. Global provider; transfer safeguards apply where required. |
| Expo | Mobile app delivery, over-the-air updates, and push notification routing. | Device/app metadata, update metadata, and push tokens where notifications are enabled. Global provider; transfer safeguards apply where required. |
Botchi uses AI infrastructure to generate responses, run automations, process attachments, transcribe audio, generate images, and create structured outputs. Production AI Gateway traffic uses retention and provider controls where supported, including zero data retention, prompt-training restrictions, provider allowlists, and log minimization.
| Provider group | Purpose | Data |
|---|---|---|
| Vercel AI Gateway | AI request routing, provider controls, usage tracking, and gateway-level retention controls. | Prompts, outputs, model parameters, routing metadata, token usage, and cost metadata. |
| Configured model providers | AI inference, embeddings, transcription, image generation, document processing, or related media processing. | Relevant prompt, file, media, context, and output data needed to complete the requested feature. |
| OpenAI, Anthropic, Google, OpenRouter, and similar providers | Underlying AI model access where configured for a given feature or model. | Prompt content, retrieved context, attachments or media where needed, outputs, and usage metadata. |
These controls reduce retention and training risk, but they do not mean every AI request is processed only inside the European Economic Area.
When you connect a third-party account or configure an integration, Botchi calls that service on your behalf. These providers may act under their own terms and privacy policies, not solely as Botchi subprocessors.
We may update this list as our infrastructure and product providers change. For questions about subprocessors or data processing, contact us at hello@botchi.ai.