Kapso Subprocessor List
Last updated: August 25, 2026
Effective date: September 1, 2026
Kapso, Inc. uses the affiliates and third parties below to provide the Services. A provider is a subprocessor when it processes Customer Personal Data on Kapso’s behalf. Some providers are used only when a customer enables a particular feature, model, integration, or route.
Corporate names below identify the provider or an applicable contracting affiliate. Exact contracting affiliates and processing locations may vary by customer location, product, and provider configuration.
Core service providers
| Provider | Purpose | Data involved | Typical processing location |
|---|---|---|---|
| Kapso SpA (Chile) | Affiliated engineering, operations, and support | Customer Content, account and technical data as needed to provide and support the Services | Chile; remote access to U.S.-hosted systems |
| Render Services, Inc. | Application hosting, compute, workers, and managed Redis | Customer Content, application data, logs, secrets, and operational metadata | United States |
| PlanetScale, Inc. | Managed PostgreSQL database infrastructure | Customer Content, account data, configurations, and application records | United States |
| Cloudflare, Inc. | Object storage, edge functions, delivery, and security | Media, files, request data, identifiers, and technical metadata | United States and global network locations |
| Google LLC / Google Cloud | Pub/Sub, agent infrastructure, and related cloud services | Prompts, invocation data, results, identifiers, and technical metadata | United States and other configured provider locations |
| E2B, Inc. | Isolated execution and sandbox infrastructure | Commands, files, prompts, project identifiers, tool inputs/results, and temporary credentials supplied for execution | United States |
| Elasticsearch B.V. / Elastic | Operational logging and search | Logs, message metadata, diagnostics, and limited Customer Content where included in operational events | United States or configured Elastic Cloud location |
| Functional Software, Inc. (Sentry) | Error monitoring and diagnostics | Error details, stack traces, request context, user and device identifiers | United States |
| PostHog, Inc. | Product analytics and session replay | Account identifiers, product events, device/browser data, and selected interaction recordings | United States |
| Better Stack, Inc. | Uptime monitoring, status pages, and incident telemetry | Service availability and incident metadata; limited request data | United States and provider locations |
| Datadog, Inc. | Infrastructure, performance, security, and log monitoring | Logs, metrics, traces, diagnostics, and limited customer or user identifiers | United States |
| Plus Five Five, Inc. (Resend) | Transactional email delivery | Names, email addresses, message content, delivery and engagement metadata | United States |
| Pipedream, Inc. | Connected-app authentication, account management, and action execution | User and project identifiers, connected-account metadata and credentials, configured action inputs and outputs, and technical metadata | United States |
Messaging, billing, and third-party platform providers
| Provider | Purpose | Data involved | Typical processing location |
|---|---|---|---|
| Meta Platforms, Inc., WhatsApp LLC, and applicable affiliates | WhatsApp Business Platform connectivity, messages, media, templates, account management, and managed billing | WhatsApp messages, media, contacts, phone numbers, business-account information, templates, delivery and billing metadata | United States and global provider locations |
| Stripe, Inc. and applicable affiliates | Payment processing, subscriptions, prepaid credits, invoicing, usage, and fraud prevention | Account, contact, billing, transaction, usage, tax, and limited device information | United States and global provider locations |
Meta, WhatsApp, and Stripe may act as independent controllers for some processing governed by their own terms and privacy notices.
AI, speech, and transcription providers
These providers are used only when the relevant feature, model, or route is selected or enabled.
| Provider | Purpose | Data involved | Typical processing location |
|---|---|---|---|
| OpenAI, L.L.C. | AI model inference and related features | Prompts, context, files, tool inputs, and generated outputs | United States |
| Anthropic PBC | AI model inference and related features | Prompts, context, files, tool inputs, and generated outputs | United States |
| OpenRouter, Inc. | Routing requests to customer-selected or Kapso-supported AI models | Prompts, context, model-selection metadata, and generated outputs | United States; downstream model-provider locations may vary |
| ElevenLabs, Inc. | Speech synthesis, voice, and audio processing | Text, audio, voice settings, and generated audio | United States and provider locations |
| Exa Labs, Inc. | Web search and research for AI and agent features | Search objectives, queries, customer-provided context, results, and technical metadata | United States and provider locations |
Additional model providers may be made available from time to time. Kapso will update this list and provide notice under the Data Processing Addendum before a new provider materially processes Personal Data.
Telephony providers
These providers are used only when the relevant number, calling, verification, or voice feature is enabled.
| Provider | Purpose | Data involved | Typical processing location |
|---|---|---|---|
| Twilio Inc. | Telephone numbers, verification, messaging, calling, and related communications infrastructure | Phone numbers, call/message routing data, recordings or content where enabled, and technical metadata | United States and global network locations |
| SignalWire, Inc. | Telephone numbers, calling, voice, and communications infrastructure | Phone numbers, call routing data, recordings or content where enabled, and technical metadata | United States and global network locations |
| Telnyx LLC | Telephone numbers, calling, messaging, and communications infrastructure | Phone numbers, call/message routing data, recordings or content where enabled, and technical metadata | United States and global network locations |
Website analytics and advertising recipients
The following providers may receive information from Kapso’s websites or marketing properties. They do not ordinarily process Customer Content as subprocessors for the core Services, but are disclosed here for transparency and are also addressed in the Privacy Policy.
| Provider | Purpose | Data involved |
|---|---|---|
| X Corp. | Advertising measurement and campaign attribution | Cookie/device identifiers, IP address, browser information, page and campaign events |
| PostHog, Inc. | Website and product analytics and session replay | Cookie/device identifiers, account identifiers, browser information, product and interaction events |
Updates and objections
Kapso will provide at least 15 days’ advance notice before a new subprocessor materially processes Customer Personal Data, except where urgent use is necessary to protect security or availability. Customers may object on reasonable data-protection grounds as described in the Kapso Data Processing Addendum.
Questions and notification-subscription requests may be sent to legal@kap.so.