Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
docs(security): clarify customer vs end-user data; frame ZDR around end users' data
Per the GEP call: customers care about THEIR end users' data, which lives in tool-call payloads. Composio stores only the opaque user_id, never end-user identities; "Don't store data" is what keeps end users' payload data out of Composio's storage. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Palash Kala committed
Jun 5, 2026 at 16:42 UTC
da65bc4b9e4f84278124927cf1263c1eafb83352
2 files changed
+6
-2
docs/content/docs/security/data-retention.mdx
+5
-1
@@ -6,6 +6,10 @@ keywords: [data retention, zero data retention, ZDR, logs, log storage, privacy,
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:
@@ -28,7 +32,7 @@ You control how much of each call is stored, per project, in **Settings → Gene
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
31
-Selecting **Don't store data** lets you run Composio with **zero retention of tool-call payloads** 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.
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**.
docs/content/docs/security/overview.mdx
+1
-1
@@ -4,7 +4,7 @@ description: How Composio secures your data, credentials, and tool execution, an
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.
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