Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
TypeScript agentic-aiagentsaiai-agentsaiagentsdeveloper-toolsfunction-callinggpt-4javascriptjsllmllmopsmcppythonremote-mcp-serverssetypescript
docs(security): generic data-flow page (defer named vendors to Trust Center); contact sales CTA
Palash Kala652893c19751
diff --git a/docs/content/docs/security/data-retention.mdx b/docs/content/docs/security/data-retention.mdxindex 1c5bec668..a34b05860 100644--- a/docs/content/docs/security/data-retention.mdx+++ b/docs/content/docs/security/data-retention.mdx@@ -49,4 +49,4 @@ Connected-account credentials, auth configs, and API keys are encrypted at rest## Stronger guarantees-For a contractual zero-data-retention agreement or shorter retention windows, contact your Composio account team or support. For our data-handling policies and the current sub-processor list, see the [Composio Trust Center](https://trust.composio.dev).+For a contractual zero-data-retention agreement or shorter retention windows, [contact sales](https://composio.dev/contact?utm_source=docs). For our data-handling policies and the current sub-processor list, see the [Composio Trust Center](https://trust.composio.dev).diff --git a/docs/content/docs/security/sub-processors.mdx b/docs/content/docs/security/sub-processors.mdxindex 1f3a6f949..cb36047bd 100644--- a/docs/content/docs/security/sub-processors.mdx+++ b/docs/content/docs/security/sub-processors.mdx@@ -1,30 +1,28 @@---title: Sub-processors and data flow-description: Where your data goes when you use Composio, and which providers may process tool payloads versus only metadata.+description: How your data flows when you use Composio, and where to find the authoritative list of our sub-processors.keywords: [sub-processors, subprocessors, data flow, third parties, data residency, gdpr]----When you execute tools through Composio, data flows to a small set of infrastructure providers. The authoritative, maintained sub-processor list lives in the [Composio Trust Center](https://trust.composio.dev); this page explains the categories so you can reason about exposure.+Composio relies on a small set of infrastructure providers to host the platform, execute your tool calls, and deliver triggers. The **authoritative, current list of our sub-processors** — with each provider's purpose and region — lives in the [Composio Trust Center](https://trust.composio.dev/subprocessors). Always refer to that list for specific vendors and regions.-## Providers that may process tool payloads+This page explains, at a category level, where your data goes so you can reason about exposure.-- **The destination tool provider** (for example Gmail, Slack, Salesforce) — the tool call is made directly to them.-- **Composio's execution backend and log store** — payloads are stored only when **Log storage** is set to **Store all logs** (see [Data retention](/docs/security/data-retention)).-- **Object storage** (AWS S3 / Azure Blob) — for file payloads in tool calls.-- **Code sandbox** (E2B) — only when you use the remote workbench or code execution.-- **Real-time trigger delivery** — trigger payloads are streamed to the destinations you configure.+## How your data flows-## Providers that process only metadata or non-payload data+- **Tool calls** are made to the **destination provider** you are integrating with (for example, your CRM or email service). That provider receives the request and returns the response.+- **Execution and logging** run on Composio's infrastructure. Whether the request and response payloads are stored is controlled by your [Log storage setting](/docs/security/data-retention) — set it to "Don't store data" to keep only the audit record.+- **Files** in tool calls may pass through object storage while a call runs.+- **Code execution** runs in an isolated sandbox, only when you use the workbench or code execution.+- **Triggers** are delivered to the destinations you configure, in real time.+- **Tool discovery** sends your natural-language search query (not your execution payloads) to a model and embeddings provider to find relevant tools.-- **Observability** (Datadog) — operational metadata and diagnostics.-- **Tool search, grounding, and embeddings** providers — receive your natural-language search query when discovering tools, not your execution payloads.-- **Vector store** — stores the tool catalog and query embeddings.-- **Product analytics and billing** — usage and account data, not tool payloads.+## What is not sent-## Data residency+Operational monitoring and billing systems receive metadata and usage information, not your tool-call payloads.-Composio's primary processing region is AWS **us-east-1 (US)**.+## Data residency-{/* TRUST-OWNER: confirm regional/EU options and whether to list named vendors + regions here vs. only on the Trust Center. Temporal payload-transit is unverified in env.ts — confirm before listing it as a payload sub-processor. */}+Composio's primary processing region is the United States (AWS `us-east-1`).-For the current, authoritative list of sub-processors and our data-processing terms, see the [Composio Trust Center](https://trust.composio.dev).+For the current list of sub-processors and our data-processing terms, see the [Composio Trust Center](https://trust.composio.dev/subprocessors).