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
+## What Composio stores
10
+
11
+When your agent runs a tool, Composio writes an execution log. Each log records:
12
+
13
+- 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;
14
+- by default, the **request arguments** and the **response data** of the call.
15
+
16
+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.
17
+
18
+## How long we retain it
19
+
20
+Tool execution logs and trigger event logs are retained for up to **one year**, after which they are automatically deleted.
21
+
22
+{/* 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. */}
23
+
24
+## Log storage: control what we store
25
+
26
+You control how much of each call is stored, per project, in **Settings → General → Log storage**:
27
+
28
+- **Store all logs** (default) — the full request and response payloads are stored on the execution log.
29
+- **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.
30
+
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.
32
+
33
+<Callout type="info">
34
+To enable: open the Dashboard, choose your project, go to **Settings → General → Log storage**, and select **Don't store data**.
35
+</Callout>
36
+
37
+## What "Don't store data" does and does not cover
38
+
39
+- **Covered:** the request arguments and response data are dropped from the durable execution log.
40
+- **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).
41
+
42
+{/* TRUST-OWNER: real-time trigger delivery is not gated by this setting; confirm phrasing. */}
43
+
44
+## Encryption
45
+
46
+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.
47
+
48
+{/* 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. */}
49
+
50
+## Stronger guarantees
51
+
52
+For a contractual zero-data-retention agreement or shorter retention windows, contact your Composio account team or support. For our data-handling policies and the current sub-processor list, see the [Composio Trust Center](https://trust.composio.dev).