Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
Mirrored from https://github.com/Camo67/composio.git
Synced Nov 21, 19:45 UTC
docs(security): generic data-flow page (defer named vendors to Trust Center); contact sales CTA
- sub-processors page no longer names vendors; describes data-flow categories and links trust.composio.dev/subprocessors as the authoritative list (Trust Center lists 5 today; keep docs consistent + minimal) - ZDR page CTA -> [contact sales](composio.dev/contact?utm_source=docs) Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Palash Kala committed
Jun 5, 2026 at 16:39 UTC
652893c19751d3853a7996669bf7e5f203fcfd38
2 files changed
+16
-18
docs/content/docs/security/data-retention.mdx
+1
-1
@@ -49,4 +49,4 @@ Connected-account credentials, auth configs, and API keys are encrypted at rest
49
50
## Stronger guarantees
51
52
-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).
52
+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).
docs/content/docs/security/sub-processors.mdx
+15
-17
@@ -1,30 +1,28 @@
1
---
2
title: Sub-processors and data flow
3
-description: Where your data goes when you use Composio, and which providers may process tool payloads versus only metadata.
3
+description: How your data flows when you use Composio, and where to find the authoritative list of our sub-processors.
4
keywords: [sub-processors, subprocessors, data flow, third parties, data residency, gdpr]
5
---
6
7
-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.
7
+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.
8
9
-## Providers that may process tool payloads
9
+This page explains, at a category level, where your data goes so you can reason about exposure.
10
11
-- **The destination tool provider** (for example Gmail, Slack, Salesforce) — the tool call is made directly to them.
12
-- **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)).
13
-- **Object storage** (AWS S3 / Azure Blob) — for file payloads in tool calls.
14
-- **Code sandbox** (E2B) — only when you use the remote workbench or code execution.
15
-- **Real-time trigger delivery** — trigger payloads are streamed to the destinations you configure.
11
+## How your data flows
12
17
-## Providers that process only metadata or non-payload data
13
+- **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.
14
+- **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.
15
+- **Files** in tool calls may pass through object storage while a call runs.
16
+- **Code execution** runs in an isolated sandbox, only when you use the workbench or code execution.
17
+- **Triggers** are delivered to the destinations you configure, in real time.
18
+- **Tool discovery** sends your natural-language search query (not your execution payloads) to a model and embeddings provider to find relevant tools.
19
19
-- **Observability** (Datadog) — operational metadata and diagnostics.
20
-- **Tool search, grounding, and embeddings** providers — receive your natural-language search query when discovering tools, not your execution payloads.
21
-- **Vector store** — stores the tool catalog and query embeddings.
22
-- **Product analytics and billing** — usage and account data, not tool payloads.
20
+## What is not sent
21
24
-## Data residency
22
+Operational monitoring and billing systems receive metadata and usage information, not your tool-call payloads.
23
26
-Composio's primary processing region is AWS **us-east-1 (US)**.
24
+## Data residency
25
28
-{/* 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. */}
26
+Composio's primary processing region is the United States (AWS `us-east-1`).
27
30
-For the current, authoritative list of sub-processors and our data-processing terms, see the [Composio Trust Center](https://trust.composio.dev).
28
+For the current list of sub-processors and our data-processing terms, see the [Composio Trust Center](https://trust.composio.dev/subprocessors).