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): consolidate Security and Data into one page with redacted screenshot
- single page docs/content/docs/security-and-data.mdx (replaces the 3-page security/ folder) - adds redacted Log-storage screenshot (project/org/email/user_id blurred; "Don't store data" highlighted) at docs/public/images/log-storage-dont-store-data.png - nav: single "Security and Data" section, below Triggers and webhooks Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Palash Kala committed
Jun 5, 2026 at 21:15 UTC
9cfbb653717b43440a351609e7e01300845d8a80
6 files changed
+89
-130
docs/content/docs/meta.json
+1
-3
@@ -23,9 +23,7 @@
23
"setting-up-triggers",
24
"webhook-verification",
25
"---Security and Data---",
26
- "security/overview",
27
- "security/data-retention",
28
- "security/sub-processors",
26
+ "security-and-data",
27
"---Direct Tool Execution Guides (Legacy)---",
28
"sessions-vs-direct-execution",
29
"tools-direct",
docs/content/docs/security-and-data.mdx
new
+88
@@ -0,0 +1,88 @@
1
+---
2
+title: Security and data
3
+description: How Composio secures your data, what it stores, how long it is retained, and how to run with Zero Data Retention.
4
+keywords: [security, data retention, zero data retention, ZDR, log storage, sub-processors, compliance, trust center, encryption]
5
+---
6
+
7
+Composio is built with security at its core. We use least-privilege defaults, isolate every organization and project, encrypt credentials, and give you controls over what we store, including your end users' data.
8
+
9
+## Compliance and the Trust Center
10
+
11
+Composio is SOC 2 Type II compliant. For our latest reports and certifications (the SOC 2 Type II report, our sub-processor list, and more), visit the [Composio Trust Center](https://trust.composio.dev).
12
+
13
+{/* TRUST-OWNER: confirm the full certification list to name inline (ISO 27001?). SOC 2 Type II is the only one currently stated in our public FAQ. */}
14
+
15
+## Isolation and access control
16
+
17
+- Organizations and projects isolate your resources. Data from one project is not visible to another.
18
+- API keys are scoped, support per-key IP allowlisting, and can opt in to capabilities such as Proxy Execute at creation.
19
+- Multi-factor authentication (MFA) is available for Dashboard sign-in and can be enforced by an organization admin.
20
+
21
+## Credential protection
22
+
23
+- Connected-account credentials, auth configs, and API keys are encrypted at rest using AES-256-GCM, and all traffic is encrypted in transit using TLS.
24
+- Connected-account tokens are redacted by default in API responses, for both Composio-managed and custom auth configs. To act on a provider directly, use [Proxy Execute](/docs/proxy-execute).
25
+- Webhook deliveries are signed; verify the `webhook-signature` header (see [Webhook verification](/docs/webhook-verification)).
26
+
27
+## Customer data vs. your end users' data
28
+
29
+Throughout this guide, *you* are the Composio customer, and *your end users* are the people your agent acts on behalf of, each identified by the opaque `user_id` you supply. When a tool runs, its request and response often contain **your end users' data**. Composio never stores your end users' identities (only the `user_id` you provide), so their data lives entirely in the **tool-call payloads**, which is exactly what the **Log storage** control below governs.
30
+
31
+## What Composio stores
32
+
33
+When your agent runs a tool, Composio writes an execution log. Each log records:
34
+
35
+- which toolkit and action ran, success or failure and the status, the connection and auth-config IDs, the `user_id` you supplied, timing, and the runtime/source;
36
+- by default, the **request arguments** and the **response data** of the call.
37
+
38
+Trigger events are logged similarly.
39
+
40
+## How long we retain it
41
+
42
+Tool execution logs and trigger event logs are retained for up to **one year**, after which they are automatically deleted.
43
+
44
+{/* TRUST-OWNER: code-confirmed TTL is 1 year for tool/trigger logs. Confirm windows for other data classes before stating them. */}
45
+
46
+## Zero Data Retention: the Log storage setting
47
+
48
+You control how much of each call is stored, per project, in **Settings → General → Log storage**:
49
+
50
+- **Store all logs** (default) — the full request and response payloads are stored on the execution log.
51
+- **Don't store data** — Composio does not persist the request arguments or the response data of your tool calls. It keeps only the audit record: which tool ran, when, success or failure, the IDs, and timing.
52
+
53
+Selecting **Don't store data** lets you run Composio with **zero retention of tool-call payloads**, including your end users' data, while keeping an audit trail. The same setting governs [Proxy Execute](/docs/proxy-execute) logging, which fails closed: if the setting cannot be read, payloads are not stored.
54
+
55
+
56
+
57
+<Callout type="info">
58
+To enable: open the Dashboard, choose your project, go to **Settings → General → Log storage**, and select **Don't store data**.
59
+</Callout>
60
+
61
+### What "Don't store data" does and does not cover
62
+
63
+- **Covered:** the request arguments and response data are dropped from the durable execution log.
64
+- **Not covered** (inherent to running a tool call): while a call runs, the data is still sent to the destination provider and passes through Composio's execution path; file payloads may transit object storage; and trigger payloads are delivered to your configured destinations in real time.
65
+
66
+## Data flow and sub-processors
67
+
68
+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** lives in the [Composio Trust Center](https://trust.composio.dev/subprocessors). At a category level:
69
+
70
+- **Tool calls** are made to the **destination provider** you integrate with, which receives the request and returns the response.
71
+- **Execution and logging** run on Composio's infrastructure; whether payloads are stored is governed by your Log storage setting above.
72
+- **Files** in tool calls may pass through object storage while a call runs.
73
+- **Code execution** runs in an isolated sandbox, only when you use the workbench or code execution.
74
+- **Triggers** are delivered to the destinations you configure, in real time.
75
+- **Tool discovery** sends your natural-language search query (not your execution payloads) to a model and embeddings provider.
76
+
77
+Composio's primary processing region is the United States (AWS `us-east-1`).
78
+
79
+{/* TRUST-OWNER: reconcile the sub-processor list (Trust Center lists 5; actual egress is broader) and confirm EU/region options before pointing customers here as authoritative. */}
80
+
81
+## Stronger guarantees
82
+
83
+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).
84
+
85
+## Reporting a vulnerability
86
+
87
+{/* TRUST-OWNER: confirm the disclosure channel. */}
88
+To report a security issue, contact `security@composio.dev`. Please do not disclose vulnerabilities publicly until we have addressed them.
docs/content/docs/security/data-retention.mdx
deleted
-56
@@ -1,56 +0,0 @@
1
----
2
-title: Data retention and Zero Data Retention
3
-description: What Composio stores from your tool calls, how long it is retained, and how to minimize or eliminate payload storage with the Log storage setting.
4
-keywords: [data retention, zero data retention, ZDR, logs, log storage, privacy, dont store data]
5
----
6
-
7
-Composio stores an audit log of tool executions so you can observe and debug your agents. You control how much of each call is stored, including running with no payload retention at all.
8
-
9
-## Customer data vs. your end users' data
10
-
11
-Throughout this guide, *you* are the Composio customer, and *your end users* are the people your agent acts on behalf of, each identified by the opaque `user_id` you supply. When a tool runs, its request and response often contain **your end users' data**. Composio never stores your end users' identities (only the `user_id` you provide), so their data lives entirely in the **tool-call payloads**, which is exactly what the **Log storage** control below governs. Set it to **Don't store data** to keep an audit trail of which tools ran while ensuring Composio does not retain your end users' data.
12
-
13
-## What Composio stores
14
-
15
-When your agent runs a tool, Composio writes an execution log. Each log records:
16
-
17
-- which toolkit and action ran, success or failure and the status, the connection and auth-config IDs, the `user_id` you supplied, timing, and the runtime/source;
18
-- by default, the **request arguments** and the **response data** of the call.
19
-
20
-Trigger events are logged similarly. Composio identifies your end users only by the opaque `user_id` you provide; it does not store end-user identities beyond that.
21
-
22
-## How long we retain it
23
-
24
-Tool execution logs and trigger event logs are retained for up to **one year**, after which they are automatically deleted.
25
-
26
-{/* TRUST-OWNER: code-confirmed TTL is 1 year for tool_execution_logs and trigger_event_logs. Confirm retention windows for other data classes (connected-account data, webhook delivery records, support transcripts) before stating them. The "30 days" figure mentioned on a call is NOT in code. */}
27
-
28
-## Log storage: control what we store
29
-
30
-You control how much of each call is stored, per project, in **Settings → General → Log storage**:
31
-
32
-- **Store all logs** (default) — the full request and response payloads are stored on the execution log.
33
-- **Don't store data** — Composio does not persist the request arguments or the response data of your tool calls. It keeps only the audit record: which tool ran, when, success or failure, the IDs, and timing.
34
-
35
-Selecting **Don't store data** lets you run Composio with **zero retention of tool-call payloads**, including your end users' data, while keeping an audit trail. The same setting governs [Proxy Execute](/docs/proxy-execute) logging, which fails closed: if the setting cannot be read, payloads are not stored.
36
-
37
-<Callout type="info">
38
-To enable: open the Dashboard, choose your project, go to **Settings → General → Log storage**, and select **Don't store data**.
39
-</Callout>
40
-
41
-## What "Don't store data" does and does not cover
42
-
43
-- **Covered:** the request arguments and response data are dropped from the durable execution log.
44
-- **Not covered** (this is inherent to running a tool call): while a call runs, the data is still sent to the destination provider and passes through Composio's execution path; file payloads may transit object storage; and trigger payloads are delivered to your configured destinations in real time. See [Sub-processors and data flow](/docs/security/sub-processors).
45
-
46
-{/* TRUST-OWNER: real-time trigger delivery is not gated by this setting; confirm phrasing. */}
47
-
48
-## Encryption
49
-
50
-Connected-account credentials, auth configs, and API keys are encrypted at rest using AES-256-GCM, and all traffic is encrypted in transit using TLS.
51
-
52
-{/* TRUST-OWNER: at-rest encryption of the execution-log store itself is NOT asserted here. Only secret-field AES-256-GCM is code-confirmed. Confirm with the Trust Center before adding a broader at-rest claim. */}
53
-
54
-## Stronger guarantees
55
-
56
-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/overview.mdx
deleted
-43
@@ -1,43 +0,0 @@
1
----
2
-title: Security
3
-description: How Composio secures your data, credentials, and tool execution, and where to find our compliance reports.
4
-keywords: [security, compliance, SOC 2, trust center, encryption, isolation, data]
5
----
6
-
7
-Composio is built with security at its core. We use least-privilege defaults, isolate every organization and project, encrypt credentials, and give you controls over what we store, including your end users' data.
8
-
9
-## Compliance and the Trust Center
10
-
11
-Composio is SOC 2 Type II compliant. For our latest reports and certifications (the SOC 2 Type II report, our sub-processor list, and more), visit the [Composio Trust Center](https://trust.composio.dev).
12
-
13
-{/* TRUST-OWNER: confirm the full certification list to name inline. SOC 2 Type II is the only one currently stated in our public FAQ; add ISO 27001 etc. only if confirmed. */}
14
-
15
-## Isolation and access control
16
-
17
-- Organizations and projects isolate your resources. Data from one project is not visible to another.
18
-- API keys are scoped, support per-key IP allowlisting, and can opt in to capabilities such as Proxy Execute at creation.
19
-- Multi-factor authentication (MFA) is available for Dashboard sign-in and can be enforced by an organization admin.
20
-
21
-## Credential protection
22
-
23
-- Connected-account credentials, auth configs, and API keys are encrypted at rest using AES-256-GCM, and all traffic is encrypted in transit using TLS.
24
-- Connected-account tokens are redacted by default in API responses, for both Composio-managed and custom auth configs. To act on a provider directly, use [Proxy Execute](/docs/proxy-execute).
25
-
26
-## Webhooks and triggers
27
-
28
-Webhook deliveries are signed. Verify the `webhook-signature` header before trusting a payload. See [Webhook verification](/docs/webhook-verification).
29
-
30
-## Your responsibilities
31
-
32
-Composio executes the tools and connections you configure. You control which toolkits are enabled, which accounts are connected, and what your agents are allowed to do. Review the access you grant, and treat connected-account scopes as you would any production credential. Composio does not security-audit the third-party tools or MCP servers you choose to connect.
33
-
34
-## Reporting a vulnerability
35
-
36
-{/* TRUST-OWNER: confirm the disclosure channel (security@composio.dev / bug-bounty URL). */}
37
-To report a security issue, contact `security@composio.dev`. Please do not disclose vulnerabilities publicly until we have addressed them.
38
-
39
-## Related resources
40
-
41
-- [Data retention and Zero Data Retention](/docs/security/data-retention)
42
-- [Sub-processors and data flow](/docs/security/sub-processors)
43
-- [Composio Trust Center](https://trust.composio.dev): security certifications and compliance.
docs/content/docs/security/sub-processors.mdx
deleted
-28
@@ -1,28 +0,0 @@
1
----
2
-title: Sub-processors and data flow
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
-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
-This page explains, at a category level, where your data goes so you can reason about exposure.
10
-
11
-## How your data flows
12
-
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
-
20
-## What is not sent
21
-
22
-Operational monitoring and billing systems receive metadata and usage information, not your tool-call payloads.
23
-
24
-## Data residency
25
-
26
-Composio's primary processing region is the United States (AWS `us-east-1`).
27
-
28
-For the current list of sub-processors and our data-processing terms, see the [Composio Trust Center](https://trust.composio.dev/subprocessors).
docs/public/images/log-storage-dont-store-data.png
Binary files /dev/null and b/docs/public/images/log-storage-dont-store-data.png differ