Skip to content

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: add Security and Data section (overview, data retention/ZDR, sub-processors)

Palash Kalaf4cccd2de87c
diff --git a/docs/content/docs/meta.json b/docs/content/docs/meta.json
index 57f4b8b03..ff7286f4f 100644
--- a/docs/content/docs/meta.json
+++ b/docs/content/docs/meta.json
@@ -22,6 +22,10 @@
"triggers",
"setting-up-triggers",
"webhook-verification",
+ "---Security and Data---",
+ "security/overview",
+ "security/data-retention",
+ "security/sub-processors",
"---Direct Tool Execution Guides (Legacy)---",
"sessions-vs-direct-execution",
"tools-direct",
diff --git a/docs/content/docs/security/data-retention.mdx b/docs/content/docs/security/data-retention.mdx
new file mode 100644
index 000000000..1c5bec668
--- /dev/null
+++ b/docs/content/docs/security/data-retention.mdx
@@ -0,0 +1,52 @@
+---
+title: Data retention and Zero Data Retention
+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.
+keywords: [data retention, zero data retention, ZDR, logs, log storage, privacy, dont store data]
+---
+
+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.
+
+## What Composio stores
+
+When your agent runs a tool, Composio writes an execution log. Each log records:
+
+- 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;
+- by default, the **request arguments** and the **response data** of the call.
+
+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.
+
+## How long we retain it
+
+Tool execution logs and trigger event logs are retained for up to **one year**, after which they are automatically deleted.
+
+{/* 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. */}
+
+## Log storage: control what we store
+
+You control how much of each call is stored, per project, in **Settings → General → Log storage**:
+
+- **Store all logs** (default) — the full request and response payloads are stored on the execution log.
+- **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.
+
+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.
+
+<Callout type="info">
+To enable: open the Dashboard, choose your project, go to **Settings → General → Log storage**, and select **Don't store data**.
+</Callout>
+
+## What "Don't store data" does and does not cover
+
+- **Covered:** the request arguments and response data are dropped from the durable execution log.
+- **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).
+
+{/* TRUST-OWNER: real-time trigger delivery is not gated by this setting; confirm phrasing. */}
+
+## Encryption
+
+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.
+
+{/* 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. */}
+
+## Stronger guarantees
+
+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).
diff --git a/docs/content/docs/security/overview.mdx b/docs/content/docs/security/overview.mdx
new file mode 100644
index 000000000..979435af2
--- /dev/null
+++ b/docs/content/docs/security/overview.mdx
@@ -0,0 +1,43 @@
+---
+title: Security
+description: How Composio secures your data, credentials, and tool execution, and where to find our compliance reports.
+keywords: [security, compliance, SOC 2, trust center, encryption, isolation, data]
+---
+
+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.
+
+## Compliance and the Trust Center
+
+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).
+
+{/* TRUST-OWNER: confirm the full certification list to name inline. SOC 2 Type II is the only one currently stated in our public FAQ; add ISO 27001 etc. only if confirmed. */}
+
+## Isolation and access control
+
+- Organizations and projects isolate your resources. Data from one project is not visible to another.
+- API keys are scoped, support per-key IP allowlisting, and can opt in to capabilities such as Proxy Execute at creation.
+- Multi-factor authentication (MFA) is available for Dashboard sign-in and can be enforced by an organization admin.
+
+## Credential protection
+
+- 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.
+- 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).
+
+## Webhooks and triggers
+
+Webhook deliveries are signed. Verify the `webhook-signature` header before trusting a payload. See [Webhook verification](/docs/webhook-verification).
+
+## Your responsibilities
+
+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. Composio does not security-audit the third-party tools or MCP servers you choose to connect.
+
+## Reporting a vulnerability
+
+{/* TRUST-OWNER: confirm the disclosure channel ([email protected] / bug-bounty URL). */}
+To report a security issue, contact `[email protected]`. Please do not disclose vulnerabilities publicly until we have addressed them.
+
+## Related resources
+
+- [Data retention and Zero Data Retention](/docs/security/data-retention)
+- [Sub-processors and data flow](/docs/security/sub-processors)
+- [Composio Trust Center](https://trust.composio.dev): security certifications and compliance.
diff --git a/docs/content/docs/security/sub-processors.mdx b/docs/content/docs/security/sub-processors.mdx
new file mode 100644
index 000000000..1f3a6f949
--- /dev/null
+++ b/docs/content/docs/security/sub-processors.mdx
@@ -0,0 +1,30 @@
+---
+title: Sub-processors and data flow
+description: Where your data goes when you use Composio, and which providers may process tool payloads versus only metadata.
+keywords: [sub-processors, subprocessors, data flow, third parties, data residency, gdpr]
+---
+
+When you execute tools through Composio, data flows to a small set of infrastructure providers. The authoritative, maintained sub-processor list lives in the [Composio Trust Center](https://trust.composio.dev); this page explains the categories so you can reason about exposure.
+
+## Providers that may process tool payloads
+
+- **The destination tool provider** (for example Gmail, Slack, Salesforce) — the tool call is made directly to them.
+- **Composio's execution backend and log store** — payloads are stored only when **Log storage** is set to **Store all logs** (see [Data retention](/docs/security/data-retention)).
+- **Object storage** (AWS S3 / Azure Blob) — for file payloads in tool calls.
+- **Code sandbox** (E2B) — only when you use the remote workbench or code execution.
+- **Real-time trigger delivery** — trigger payloads are streamed to the destinations you configure.
+
+## Providers that process only metadata or non-payload data
+
+- **Observability** (Datadog) — operational metadata and diagnostics.
+- **Tool search, grounding, and embeddings** providers — receive your natural-language search query when discovering tools, not your execution payloads.
+- **Vector store** — stores the tool catalog and query embeddings.
+- **Product analytics and billing** — usage and account data, not tool payloads.
+
+## Data residency
+
+Composio's primary processing region is AWS **us-east-1 (US)**.
+
+{/* TRUST-OWNER: confirm regional/EU options and whether to list named vendors + regions here vs. only on the Trust Center. Temporal payload-transit is unverified in env.ts — confirm before listing it as a payload sub-processor. */}
+
+For the current, authoritative list of sub-processors and our data-processing terms, see the [Composio Trust Center](https://trust.composio.dev).