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
-
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.