@devries-cameron20 / composio Mirror · read-only / commits / 6257cda67
Fork 0

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): split into two docs (Security overview + Data retention); no ZDR promise

- security/overview.mdx: posture, compliance/Trust Center, isolation, credential protection - security/data-retention.mdx: what's stored, 1-year retention, the Log storage "Don't store data" option, and an honest "Where your data goes" section (data still flows to sub-processors during execution; defers the list to the Trust Center) - frames "Don't store data" as controlling what Composio retains, not a Zero-Data-Retention guarantee; contractual ZDR is a contact-sales option only Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Palash Kala committed Jun 5, 2026 at 21:27 UTC 6257cda674305853e07e01c92a2f57c20acba96f
4 files changed +91 -82
docs/content/docs/meta.json
+2 -1
@@ -23,7 +23,8 @@
23 "setting-up-triggers",
24 "webhook-verification",
25 "---Security and Data---",
26 - "security-and-data",
26 + "security/overview",
27 + "security/data-retention",
28 "---Direct Tool Execution Guides (Legacy)---",
29 "sessions-vs-direct-execution",
30 "tools-direct",
docs/content/docs/security-and-data.mdx deleted
-81
@@ -1,81 +0,0 @@
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 -## Isolation and access control
14 -
15 -- Organizations and projects isolate your resources. Data from one project is not visible to another.
16 -- API keys are scoped, support per-key IP allowlisting, and can opt in to capabilities such as Proxy Execute at creation.
17 -- Multi-factor authentication (MFA) is available for Dashboard sign-in and can be enforced by an organization admin.
18 -
19 -## Credential protection
20 -
21 -- 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.
22 -- 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).
23 -- Webhook deliveries are signed; verify the `webhook-signature` header (see [Webhook verification](/docs/webhook-verification)).
24 -
25 -## Customer data vs. your end users' data
26 -
27 -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.
28 -
29 -## What Composio stores
30 -
31 -When your agent runs a tool, Composio writes an execution log. Each log records:
32 -
33 -- 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;
34 -- by default, the **request arguments** and the **response data** of the call.
35 -
36 -Trigger events are logged similarly.
37 -
38 -## How long we retain it
39 -
40 -Tool execution logs and trigger event logs are retained for up to **one year**, after which they are automatically deleted.
41 -
42 -## Zero Data Retention: the Log storage setting
43 -
44 -You control how much of each call is stored, per project, in **Settings → General → Log storage**:
45 -
46 -- **Store all logs** (default) — the full request and response payloads are stored on the execution log.
47 -- **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.
48 -
49 -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.
50 -
51 -![Log storage set to "Don't store data" in Project Settings, General](/images/log-storage-dont-store-data.png)
52 -
53 -<Callout type="info">
54 -To enable: open the Dashboard, choose your project, go to **Settings → General → Log storage**, and select **Don't store data**.
55 -</Callout>
56 -
57 -### What "Don't store data" does and does not cover
58 -
59 -- **Covered:** the request arguments and response data are dropped from the durable execution log.
60 -- **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.
61 -
62 -## Data flow and sub-processors
63 -
64 -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:
65 -
66 -- **Tool calls** are made to the **destination provider** you integrate with, which receives the request and returns the response.
67 -- **Execution and logging** run on Composio's infrastructure; whether payloads are stored is governed by your Log storage setting above.
68 -- **Files** in tool calls may pass through object storage while a call runs.
69 -- **Code execution** runs in an isolated sandbox, only when you use the workbench or code execution.
70 -- **Triggers** are delivered to the destinations you configure, in real time.
71 -- **Tool discovery** sends your natural-language search query (not your execution payloads) to a model and embeddings provider.
72 -
73 -Composio's primary processing region is the United States (AWS `us-east-1`).
74 -
75 -## Stronger guarantees
76 -
77 -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).
78 -
79 -## Reporting a vulnerability
80 -
81 -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 new
+53
@@ -0,0 +1,53 @@
1 +---
2 +title: Data retention
3 +description: What Composio stores from your tool calls, how long it is kept, how to stop storing payloads, and where your data flows.
4 +keywords: [data retention, log storage, privacy, dont store data, sub-processors, data flow]
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, and you can choose not to store the payloads 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** setting below governs.
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.
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 +## Choose what we store: the Log storage setting
27 +
28 +You control how much of each call is stored, per project, in **Settings → General → Log storage**:
29 +
30 +- **Store all logs** (default) — Composio stores the full request and response payloads on the execution log.
31 +- **Don't store data** — Composio does not store 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.
32 +
33 +With **Don't store data**, Composio keeps an audit trail but does not retain your tool-call payloads (including your end users' data) in its logs. The same setting governs [Proxy Execute](/docs/proxy-execute) logging, which fails closed: if the setting cannot be read, payloads are not stored.
34 +
35 +![Log storage set to "Don't store data" in Project Settings, General](/images/log-storage-dont-store-data.png)
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 +## Where your data goes
42 +
43 +Choosing **Don't store data** stops Composio from persisting your payloads, but running a tool still moves data through a few places while the call executes:
44 +
45 +- the **destination provider** you integrate with, which the tool call is made to;
46 +- **Composio's execution path** while the call runs;
47 +- **object storage** for file payloads, a **code sandbox** if you use the workbench, and your configured **trigger destinations**, in real time.
48 +
49 +So "Don't store data" controls what Composio retains, not whether data is processed during execution. For the current list of our sub-processors and our data-handling terms, see the [Composio Trust Center](https://trust.composio.dev/subprocessors).
50 +
51 +## Stronger guarantees
52 +
53 +If your organization needs a contractual zero-data-retention arrangement or shorter retention windows, [contact sales](https://composio.dev/contact?utm_source=docs). For our data-handling policies and sub-processor list, see the [Composio Trust Center](https://trust.composio.dev).
docs/content/docs/security/overview.mdx new
+36
@@ -0,0 +1,36 @@
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]
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.
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 +## Isolation and access control
14 +
15 +- Organizations and projects isolate your resources. Data from one project is not visible to another.
16 +- API keys are scoped, support per-key IP allowlisting, and can opt in to capabilities such as Proxy Execute at creation.
17 +- Multi-factor authentication (MFA) is available for Dashboard sign-in and can be enforced by an organization admin.
18 +
19 +## Credential protection
20 +
21 +- 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.
22 +- 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).
23 +- Webhook deliveries are signed; verify the `webhook-signature` header (see [Webhook verification](/docs/webhook-verification)).
24 +
25 +## Your responsibilities
26 +
27 +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.
28 +
29 +## Reporting a vulnerability
30 +
31 +To report a security issue, contact `security@composio.dev`. Please do not disclose vulnerabilities publicly until we have addressed them.
32 +
33 +## Related resources
34 +
35 +- [Data retention](/docs/security/data-retention): what we store, for how long, and how to stop storing payloads.
36 +- [Composio Trust Center](https://trust.composio.dev): security certifications and compliance.