@devries-cameron20 / composio-1 / commits / eeca91139
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.

Revert "docs: add Security and Data section (#3525)" (#3668)

palash-c committed Jun 25, 2026 at 21:37 UTC eeca911392688a60ffbef829040ce2b009e887e3
4 files changed -107
docs/content/docs/meta.json
-3
@@ -22,9 +22,6 @@
22 "triggers",
23 "setting-up-triggers",
24 "webhook-verification",
25 - "---Security and Data---",
26 - "security/overview",
27 - "security/data-retention",
25 "---Direct Tool Execution Guides (Legacy)---",
26 "sessions-vs-direct-execution",
27 "tools-direct",
docs/content/docs/security/data-retention.mdx deleted
-68
@@ -1,68 +0,0 @@
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, file ttl]
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 -## How long files are available
27 -
28 -When a tool returns a file (an image, document, export, and so on), Composio shares it as a presigned URL with a time-to-live (TTL) rather than storing the file indefinitely. The default TTL is **1 hour**, and once it expires the URL stops resolving.
29 -
30 -## Choose what we store: the Log storage setting
31 -
32 -You control how much of each call is stored, per project, in **Settings → General → Log storage**:
33 -
34 -- **Store all logs** (default) — Composio stores the full request and response payloads on the execution log.
35 -- **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.
36 -
37 -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.
38 -
39 -![Log storage set to "Don't store data" in Project Settings, General](/images/log-storage-dont-store-data.png)
40 -
41 -<Callout type="info">
42 -To enable: open the Dashboard, choose your project, go to **Settings → General → Log storage**, and select **Don't store data**.
43 -</Callout>
44 -
45 -### Changing the setting takes effect going forward
46 -
47 -Log storage behaves like a pause/resume switch — it only affects calls made **after** you change it:
48 -
49 -- 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.
50 -- Selecting **Store all logs** again resumes storing payloads for new calls. It does **not** backfill the period while storage was off.
51 -
52 -Toggling off and back on therefore leaves a gap — payloads for the calls made while it was off were never stored, and turning storage back on does not recover them.
53 -
54 -## Where your data goes
55 -
56 -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:
57 -
58 -- the **destination provider** you integrate with, which the tool call is made to;
59 -- **Composio's execution path** while the call runs;
60 -- **object storage** for files returned by tool calls, held only for the file TTL (1 hour by default — see [How long files are available](#how-long-files-are-available)) and then expired;
61 -- your configured **trigger destinations**, which receive trigger events in real time;
62 -- if you use the **workbench** or code execution, an isolated **code sandbox** and a **third-party model provider** that powers it.
63 -
64 -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).
65 -
66 -## Stronger guarantees
67 -
68 -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 deleted
-36
@@ -1,36 +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]
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.
docs/public/images/log-storage-dont-store-data.png
Binary files a/docs/public/images/log-storage-dont-store-data.png and /dev/null differ