Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
[codex] restore Security and Data docs (#3720)
Abhishek Patil committed
Jul 28, 2026 at 22:10 UTC
11686484d13d4f70fe6cc41325e166e1d2766bcb
4 files changed
+121
docs/content/docs/meta.json
+3
@@ -27,6 +27,9 @@
27
"setting-up-triggers/subscribing-to-events",
28
"setting-up-triggers/managing-triggers",
29
"setting-up-triggers/custom-oauth-webhooks",
30
+ "---Security and Data---",
31
+ "security/overview",
32
+ "security/data-retention",
33
"---Direct Tool Execution Guides (Legacy)---",
34
"sessions-vs-direct-execution",
35
"tools-direct",
docs/content/docs/security/data-retention.mdx
new
+82
@@ -0,0 +1,82 @@
1
+---
2
+title: Data retention
3
+description: What Composio stores from tool calls, how long logs and files are retained, how to stop storing payloads, and where your data flows.
4
+keywords: [data retention, log storage, privacy, dont store data, sub-processors, data flow, file ttl]
5
+---
6
+
7
+Composio stores audit logs for tool executions so you can observe and debug your agents. You control whether the request and response payloads for each call are stored.
8
+
9
+## Customer data vs. your end users' data
10
+
11
+Throughout this guide, *you* are the Composio customer. *Your end users* are the people your agent acts on behalf of. Each end user is identified by the `user_id` you provide. Composio stores this value as supplied and uses it to associate connected accounts, sessions, and execution logs.
12
+
13
+Tool requests and responses may contain additional end-user data. The **Log storage** setting controls whether these payloads are retained; it does not remove the `user_id` or other audit metadata.
14
+
15
+## What Composio stores
16
+
17
+Composio creates logs for tool executions and trigger events. These logs contain:
18
+
19
+- For tool executions, the toolkit and action, execution status, connection and auth-config IDs, supplied `user_id`, timing, and runtime/source.
20
+- By default, the **request arguments** and **response data** for each tool execution.
21
+- For trigger events, similar audit metadata and, by default, the trigger payloads.
22
+
23
+## How long logs are retained
24
+
25
+Tool execution logs and trigger event logs are retained for up to **one year**, after which they are automatically deleted.
26
+
27
+## How long files are available
28
+
29
+When a tool uses or returns a file (an attachment, image, document, export, and so on), Composio stages it in temporary object storage and shares it through a presigned URL. The URL is valid for **1 hour by default**. You can configure this URL TTL per project in **Project Settings**, up to 24 hours.
30
+
31
+Presigned URL expiry and file deletion are separate. When the URL expires, the link stops resolving, but that does not delete the underlying object. Files staged for tool execution are automatically deleted from temporary object storage after **24 hours**.
32
+
33
+Workbench storage has two separate lifecycles:
34
+
35
+- Files written to `/mnt/files` are backed by temporary object storage and are automatically deleted after **24 hours**.
36
+- Other sandbox files, variables, and runtime state are temporary and may be cleared after approximately **12 hours** of inactivity.
37
+
38
+## Choose what we store: the Log storage setting
39
+
40
+You control whether call payloads are stored for each project in **Settings → General → Log storage**:
41
+
42
+- **Store all logs** (default) — Composio stores the full request and response payloads in the execution log.
43
+- **Don't store data** — Composio does not store the request arguments or response data from your tool calls. It keeps only the audit record: which tool ran, when it ran, whether it succeeded, the relevant IDs, and timing information.
44
+
45
+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. This setting also applies to [Proxy Execute](/docs/extending-sessions/proxy-execute). If Composio cannot retrieve your project's log-storage setting, Proxy Execute does not store the request or response payload.
46
+
47
+
48
+
49
+<Callout type="info">
50
+To stop storing payloads, open the Dashboard, choose your project, go to **Settings → General → Log storage**, and select **Don't store data**.
51
+</Callout>
52
+
53
+### Changing the setting affects new calls
54
+
55
+You can switch between the two log-storage options at any time. Each change applies only to new calls:
56
+
57
+- Selecting **Don't store data** stops Composio from storing payloads for new calls. It does **not** delete payloads that were already stored: existing logs stay available until they age out under the one-year retention window.
58
+- Selecting **Store all logs** again resumes storing payloads for new calls. It does **not** backfill the period while payload storage was disabled.
59
+
60
+Payloads for calls made while storage was disabled were never stored and cannot be recovered later.
61
+
62
+## Where your data goes
63
+
64
+Choosing **Don't store data** stops Composio from persisting your payloads, but data may still pass through the following locations during execution:
65
+
66
+- The **destination provider** that receives the tool call.
67
+- **Composio's execution infrastructure** while the call runs.
68
+- **Temporary object storage** for files used or returned by tool calls. Presigned URL expiry is configurable per project, while the underlying staged file is deleted after 24 hours. See [How long files are available](#how-long-files-are-available).
69
+- Your configured **trigger destinations**, which receive trigger events in real time.
70
+- An isolated third-party **code sandbox**, if you use Workbench or remote code execution. Ordinary Python or shell execution does not inherently send code or sandbox files to an LLM provider. Model-provider processing occurs only in the cases described below.
71
+
72
+### When Workbench uses an LLM
73
+
74
+When a task requires advanced processing, the agent or MCP client may use Workbench and call `invoke_llm` from the submitted code—for example, to summarize, analyze, extract, or generate content. Only the information passed to `invoke_llm` is sent to the model provider; sandbox files and previous results are not sent unless the submitted code includes them.
75
+
76
+There is one separate case: if submitted Python contains a syntax error and automatic repair is enabled, Composio may send the code and error details to the configured model provider to fix it before execution. Valid Python and ordinary shell commands do not trigger this repair.
77
+
78
+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).
79
+
80
+## Stronger guarantees
81
+
82
+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/extending-sessions/proxy-execute).
23
+- Webhook deliveries are signed; verify the `webhook-signature` header when handling trigger events. For custom OAuth webhook setup, see [Custom OAuth webhooks](/docs/setting-up-triggers/custom-oauth-webhooks).
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.
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