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

docs: add Zero Data Retention page and rename Don't store data (#4612)

Adds the Zero Data Retention page and renames Don't store data to ZDR across the docs. Data retention now covers the standard policy for every plan and points to ZDR with a screenshot of the new setting. Security and data moves to the Platform sidebar, and a changelog entry announces the change.

Shubham Mehta committed Sep 29, 2026 at 10:40 UTC dea6a16744aca0689ca551c673c97ec5f615fb99
16 files changed +410 -53
docs/agent-guidance/context/markdown-components.md
+1 -1
@@ -13,7 +13,7 @@ Audit for DEVREL-35, 2026-09-10. Scope: components registered in `mdx-components
13 | Media | `Figure`, `YouTube`, `Video` | Preserve captions and source links. Video links now survive conversion. Transcription of media is outside this audit. |
14 | Example source | `FileBuildup`, `RepoBrowser` | Existing converters expose staged source or an explicit repository-availability notice. |
15 | Structural wrappers and icons | `Cards`, `ProviderGrid`, `TemplateGrid`, `QuickstartFlow`, `FrameworkSelector`, `ToolTypeFlow`, `ConnectFlow`, `Accordions`, `CapabilityList`, `MediaSplit`, `AppLogo`, registered Lucide icons | Wrappers have no task instructions; their child content survives. Icons are decorative. |
16 -| Visual explanations | `SessionFlow`, `TriggersFlow`, `SlackBotFlow`, `LocalWorkbenchFlow`, `LocalSandboxBoundary`, `ImessageFlow`, `WorkbenchFlow`, `AuthConfigFlow`, `WhiteLabelFlow`, `ImportConnectionFlow`, `ManageConnectionsVisual`, `ConnectionRefreshVisual`, `InChatAuthTerminal`, `ClaudeMockUI` | Diagrams illustrate the surrounding guide. The authored instructions remain the executable path. Full visual-to-text parity is a follow-up, not claimed by this fix. |
16 +| Visual explanations | `SessionFlow`, `TriggersFlow`, `SlackBotFlow`, `LocalWorkbenchFlow`, `LocalSandboxBoundary`, `ImessageFlow`, `WorkbenchFlow`, `AuthConfigFlow`, `WhiteLabelFlow`, `ImportConnectionFlow`, `ManageConnectionsVisual`, `ConnectionRefreshVisual`, `InChatAuthTerminal`, `ClaudeMockUI`, `ZdrLogVisual` | Diagrams illustrate the surrounding guide. The authored instructions remain the executable path. Full visual-to-text parity is a follow-up, not claimed by this fix. |
17 | Mermaid | `Mermaid` | `getLLMText` preserves processed diagram code. Raw component diagrams in search require separate parity coverage. |
18 | Homepage and catalogs | `DocsHero`, `HomeFeatures`, `HomeResources`, `ToolkitsLanding`, `ManagedAuthList` | Dynamic content is not fully serialized by the generic converter. Product selection survives through `HomeSurfaces`; toolkit routes have dedicated Markdown renderers, and managed-auth prose includes the API lookup. Full catalog and homepage parity remains a follow-up. |
19
docs/app/global.css
+91
@@ -1255,3 +1255,94 @@ html.docs-product-transition .docs-product-shell {
1255 mask-image: none;
1256 }
1257 }
1258 +
1259 +/* ZdrLogVisual: the request and response dissolve to "not stored" as the ZDR switch turns on. */
1260 +.zdr-log-payload,
1261 +.zdr-log-state-off {
1262 + animation: zdr-log-show-when-off 10s ease-in-out infinite;
1263 +}
1264 +
1265 +.zdr-log-not-stored,
1266 +.zdr-log-state-on {
1267 + opacity: 0;
1268 + animation: zdr-log-show-when-on 10s ease-in-out infinite;
1269 +}
1270 +
1271 +.zdr-log-thumb {
1272 + animation: zdr-log-thumb 10s ease-in-out infinite;
1273 +}
1274 +
1275 +.zdr-log-hatch {
1276 + background-image: repeating-linear-gradient(
1277 + 135deg,
1278 + transparent 0 6px,
1279 + color-mix(in oklab, currentColor 12%, transparent) 6px 7px
1280 + );
1281 +}
1282 +
1283 +@keyframes zdr-log-show-when-off {
1284 + 0%,
1285 + 38% {
1286 + opacity: 1;
1287 + filter: blur(0);
1288 + }
1289 + 48%,
1290 + 88% {
1291 + opacity: 0;
1292 + filter: blur(3px);
1293 + }
1294 + 98%,
1295 + 100% {
1296 + opacity: 1;
1297 + filter: blur(0);
1298 + }
1299 +}
1300 +
1301 +@keyframes zdr-log-show-when-on {
1302 + 0%,
1303 + 38% {
1304 + opacity: 0;
1305 + }
1306 + 48%,
1307 + 88% {
1308 + opacity: 1;
1309 + }
1310 + 98%,
1311 + 100% {
1312 + opacity: 0;
1313 + }
1314 +}
1315 +
1316 +@keyframes zdr-log-thumb {
1317 + 0%,
1318 + 38% {
1319 + transform: translateX(0);
1320 + }
1321 + 48%,
1322 + 88% {
1323 + transform: translateX(12px);
1324 + }
1325 + 98%,
1326 + 100% {
1327 + transform: translateX(0);
1328 + }
1329 +}
1330 +
1331 +@media (prefers-reduced-motion: reduce) {
1332 + .zdr-log-payload,
1333 + .zdr-log-state-off {
1334 + animation: none;
1335 + opacity: 0;
1336 + }
1337 +
1338 + .zdr-log-not-stored,
1339 + .zdr-log-state-on {
1340 + animation: none;
1341 + opacity: 1;
1342 + }
1343 +
1344 + .zdr-log-thumb {
1345 + animation: none;
1346 + transform: translateX(12px);
1347 + }
1348 +}
docs/components/zdr-log-visual.tsx new
+116
@@ -0,0 +1,116 @@
1 +import { EyeOff } from 'lucide-react';
2 +
3 +const LOGO_CDN = 'https://logos.composio.dev/api';
4 +
5 +const PAYLOADS: { label: string; lines: [string, string][] }[] = [
6 + {
7 + label: 'request',
8 + lines: [
9 + ['recipient_email', '"maya@example.com"'],
10 + ['subject', '"Q3 renewal terms"'],
11 + ['body', '"Hi Maya, the updated terms are…"'],
12 + ],
13 + },
14 + {
15 + label: 'response',
16 + lines: [
17 + ['id', '"18f2c9a1e4b7"'],
18 + ['labelIds', '["SENT"]'],
19 + ],
20 + },
21 +];
22 +
23 +/**
24 + * ZdrLogVisual — a Gmail tool call's execution log as Zero Data Retention
25 + * switches on. The request and response dissolve to "not stored" while the
26 + * tool, status, and latency stay, mirroring the dashboard's ZDR upgrade screen.
27 + * Server component, light/dark via fd-* tokens. The loop is CSS in global.css
28 + * (`zdr-log-*`) and holds the ZDR-on state under reduced motion.
29 + */
30 +export function ZdrLogVisual() {
31 + return (
32 + <figure className="not-prose my-6">
33 + <div
34 + aria-hidden="true"
35 + className="mx-auto w-full max-w-[420px] overflow-hidden rounded-sm border border-fd-border bg-fd-background font-mono"
36 + >
37 + {/* tool row */}
38 + <div className="flex items-center gap-2 border-b border-fd-border px-3 py-2.5">
39 + <span className="flex size-6 shrink-0 items-center justify-center rounded-md bg-white ring-1 ring-fd-border">
40 + <img
41 + alt=""
42 + className="size-[15px] object-contain"
43 + draggable={false}
44 + src={`${LOGO_CDN}/gmail`}
45 + />
46 + </span>
47 + <code className="truncate text-[12px] font-medium text-fd-foreground">
48 + GMAIL_SEND_EMAIL
49 + </code>
50 + <span className="ml-auto rounded-sm bg-green-500/10 px-1.5 py-0.5 text-[10px] text-green-600 dark:text-green-400">
51 + 200
52 + </span>
53 + <span className="text-[10px] text-fd-foreground/45">412 ms</span>
54 + </div>
55 +
56 + {/* metadata that ZDR keeps */}
57 + <div className="flex gap-1.5 px-3 pt-3 text-[10px] text-fd-foreground/45">
58 + <span>production</span>
59 + <span>·</span>
60 + <span>user_7f3a</span>
61 + <span>·</span>
62 + <span>just now</span>
63 + </div>
64 +
65 + {/* payloads that ZDR drops */}
66 + <div className="space-y-3 px-3 pb-3 pt-3">
67 + {PAYLOADS.map((payload) => (
68 + <div key={payload.label}>
69 + <span className="mb-1.5 block text-[9px] uppercase tracking-[0.06em] text-fd-foreground/40">
70 + {payload.label}
71 + </span>
72 + <div className="grid">
73 + <div className="zdr-log-payload col-start-1 row-start-1 border border-fd-border bg-fd-card px-2.5 py-2 text-[11px] leading-[18px]">
74 + {payload.lines.map(([key, value]) => (
75 + <div key={key} className="truncate">
76 + <span className="text-fd-foreground/45">{key}: </span>
77 + <span className="text-fd-foreground">{value}</span>
78 + </div>
79 + ))}
80 + </div>
81 + <div className="zdr-log-not-stored zdr-log-hatch col-start-1 row-start-1 flex items-center justify-center gap-1.5 border border-dashed border-fd-border text-[11px] text-fd-foreground/60">
82 + <EyeOff className="size-3.5" />
83 + not stored
84 + </div>
85 + </div>
86 + </div>
87 + ))}
88 + </div>
89 +
90 + {/* the ZDR switch */}
91 + <div className="flex items-center gap-2 border-t border-fd-border px-3 py-2.5">
92 + <span className="text-[11px] text-fd-foreground">
93 + Zero Data Retention
94 + </span>
95 + <span className="ml-auto grid text-[10px]">
96 + <span className="zdr-log-state-off col-start-1 row-start-1 text-right text-fd-foreground/45">
97 + off
98 + </span>
99 + <span className="zdr-log-state-on col-start-1 row-start-1 text-right text-[var(--composio-brand)]">
100 + on
101 + </span>
102 + </span>
103 + <span className="relative inline-flex h-4 w-7 shrink-0 items-center rounded-full p-0.5">
104 + <span className="zdr-log-state-off absolute inset-0 rounded-full bg-fd-foreground/15" />
105 + <span className="zdr-log-state-on absolute inset-0 rounded-full bg-[var(--composio-brand)]" />
106 + <span className="zdr-log-thumb relative size-3 rounded-full bg-white shadow-sm" />
107 + </span>
108 + </div>
109 + </div>
110 + <figcaption className="mt-3 text-center text-[11px] text-fd-foreground/50">
111 + With ZDR on, the log keeps the tool, status, and latency. The request and
112 + response are not stored.
113 + </figcaption>
114 + </figure>
115 + );
116 +}
docs/content/changelog/09-29-26-zero-data-retention.mdx new
+13
@@ -0,0 +1,13 @@
1 +---
2 +title: "Don't store data is now Zero Data Retention"
3 +description: "The project setting that stopped payload storage is now Zero Data Retention, an organization add-on in Billing. Every project kept its setting."
4 +date: "2026-09-29"
5 +---
6 +
7 +The **Don't store data** option under **Log storage** is now **Zero Data Retention** (ZDR). You manage it as an organization add-on in **Organization Settings > Billing > Add-ons**. Every project kept its setting, so projects that had **Don't store data** on now show ZDR on.
8 +
9 +### What's new
10 +
11 +- An organization admin can turn on ZDR for all projects at once. Admins can also turn it on or off for one project in **Project Settings > General**.
12 +- ZDR is available on paid plans for a usage-based price and included on Enterprise, where new projects start with ZDR on. Hobby plan projects that already had **Don't store data** keep ZDR on until an admin turns it off.
13 +- The [Zero Data Retention](/docs/security/zero-data-retention) page lists what ZDR covers, what it does not cover, and what Composio still stores.
docs/content/docs/configuring-sessions.mdx
+2
@@ -764,6 +764,8 @@ When disabled:
764 - Sandbox-related system prompt lines are stripped
765 - Direct sandbox calls are rejected with a 400 error
766
767 +[Zero Data Retention](/docs/security/zero-data-retention) does not cover the sandbox, so disable it in sessions that handle data that needs ZDR.
768 +
769 To keep the sandbox but block raw HTTP calls from it, set `enable_proxy_execution` (Python) or `enableProxyExecution` (TypeScript) to `false`. See [Proxy execute](/docs/extending-sessions/proxy-execute#session-restrictions) for how session restrictions apply to proxy calls.
770
771 <Callout>
docs/content/docs/poc-to-prod/meta.json
-1
@@ -3,7 +3,6 @@
3 "pages": [
4 "../authentication/custom-app-vs-managed-app",
5 "[Rate limits](/reference/rate-limits)",
6 - "../security/data-retention",
6 "stream-logs-to-a-siem"
7 ]
8 }
docs/content/docs/poc-to-prod/stream-logs-to-a-siem.mdx
+1 -1
@@ -111,4 +111,4 @@ Alert when the last completed window falls behind your expected collection delay
111
112 Select the fields your security team needs before forwarding logs. Messages, metadata, and full tool payloads can contain end-user data. Store keys in your secret manager and restrict access to local exports and destination indexes.
113
114 -Fetch [individual log details](/reference/api-reference/logs#get-a-single-log) only when you need the additional context or stored request and response payloads. The project's [Log storage setting](/docs/security/data-retention#choose-what-we-store-the-log-storage-setting) controls payload retention. Configure retention and deletion separately for copies you send to your SIEM.
114 +Fetch [individual log details](/reference/api-reference/logs#get-a-single-log) only when you need the additional context or stored request and response payloads. The project's [Zero Data Retention](/docs/security/zero-data-retention) setting controls whether Composio stores payloads. Configure retention and deletion separately for copies you send to your SIEM.
docs/content/docs/security/data-retention.mdx
+12 -30
@@ -1,17 +1,15 @@
1 ---
2 title: Data retention
3 -description: What Composio stores from tool calls, how long logs and files are retained, 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]
3 +description: The standard retention policy for every plan. What Composio stores from tool calls, how long logs and files are retained, and where your data flows.
4 +keywords: [data retention, retention policy, log retention, privacy, zero data retention, sub-processors, data flow, file ttl]
5 ---
6
7 -Composio stores audit logs for tool executions so you can observe and debug your agents. You control whether the request and response payloads for each call are stored.
7 +Composio stores logs for tool executions so you can observe and debug your agents. This retention policy applies on every plan.
8
9 ## Customer data vs. your end users' data
10
11 Throughout this guide, *you* are the Composio customer. *Your end users* are the people your agent acts on behalf of. Each end user is identified by the `user_id` you provide. Composio stores this value as supplied and uses it to associate connected accounts, sessions, and execution logs.
12
13 -Tool requests and responses may contain additional end-user data. The **Log storage** setting controls whether these payloads are retained; it does not remove the `user_id` or other audit metadata.
14 -
13 ## What Composio stores
14
15 Composio creates logs for tool executions and trigger events. These logs contain:
@@ -35,48 +33,32 @@ Workbench storage has two separate lifecycles:
33 - Files written to `/mnt/files` are backed by temporary object storage and are automatically deleted after **24 hours**.
34 - Other sandbox files, variables, and runtime state are temporary and may be cleared after approximately **12 hours** of inactivity.
35
38 -## Choose what we store: the Log storage setting
39 -
40 -You control whether call payloads are stored for each project in **Settings → General → Log storage**:
41 -
42 -- **Store all logs** (default) — Composio stores the full request and response payloads in the execution log.
43 -- **Don't store data** — Composio does not store the request arguments or response data from your tool calls. It keeps only the audit record: which tool ran, when it ran, whether it succeeded, the relevant IDs, and timing information.
44 -
45 -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. This setting also applies to [Proxy Execute](/docs/extending-sessions/proxy-execute). If Composio cannot retrieve your project's log-storage setting, Proxy Execute does not store the request or response payload.
46 -
47 -![Log storage set to "Don't store data" in Project Settings, General](/images/log-storage-dont-store-data.png)
48 -
49 -<Callout type="info">
50 -To stop storing payloads, open the Dashboard, choose your project, go to **Settings → General → Log storage**, and select **Don't store data**.
51 -</Callout>
52 -
53 -### Changing the setting affects new calls
36 +## Stop storing payloads with Zero Data Retention
37
55 -You can switch between the two log-storage options at any time. Each change applies only to new calls:
38 +To stop storing request and response payloads for a project, turn on [Zero Data Retention](/docs/security/zero-data-retention) (ZDR) in **Project Settings > General**. Organization admins can also turn it on for every project in **Organization Settings > Billing**. With ZDR on, the log for each covered call keeps metadata only. ZDR is available on paid plans for a usage-based price and included on Enterprise.
39
57 -- 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.
58 -- Selecting **Store all logs** again resumes storing payloads for new calls. It does **not** backfill the period while payload storage was disabled.
40 +![Zero Data Retention turned on in Project Settings, General](/images/zdr-project-setting.png)
41
60 -Payloads for calls made while storage was disabled were never stored and cannot be recovered later.
42 +ZDR covers tool calls and [Proxy Execute](/docs/extending-sessions/proxy-execute) requests. See [what ZDR does not cover](/docs/security/zero-data-retention#what-zdr-does-not-cover).
43
44 ## Where your data goes
45
64 -Choosing **Don't store data** stops Composio from persisting your payloads, but data may still pass through the following locations during execution:
46 +Whether or not ZDR is on, data can pass through the following locations during execution:
47
48 - The **destination provider** that receives the tool call.
49 - **Composio's execution infrastructure** while the call runs.
68 -- **Temporary object storage** for files used or returned by tool calls. Presigned URL expiry is configurable per project, while the underlying staged file is deleted after 24 hours. See [How long files are available](#how-long-files-are-available).
50 +- **Temporary object storage** for files used or returned by tool calls. See [How long files are available](#how-long-files-are-available).
51 - Your configured **trigger destinations**, which receive trigger events in real time.
52 - An isolated third-party **code sandbox**, if you use Workbench or remote code execution. Ordinary Python or shell execution does not inherently send code or sandbox files to an LLM provider. Model-provider processing occurs only in the cases described below.
53
54 ### When Workbench uses an LLM
55
74 -When a task requires advanced processing, the agent or MCP client may use Workbench and call `invoke_llm` from the submitted code—for example, to summarize, analyze, extract, or generate content. Only the information passed to `invoke_llm` is sent to the model provider; sandbox files and previous results are not sent unless the submitted code includes them.
56 +When a task requires advanced processing, the agent or MCP client may use Workbench and call `invoke_llm` from the submitted code, for example to summarize, analyze, extract, or generate content. Only the information passed to `invoke_llm` is sent to the model provider. Sandbox files and previous results are not sent unless the submitted code includes them.
57
58 There is one separate case: if submitted Python contains a syntax error and automatic repair is enabled, Composio may send the code and error details to the configured model provider to fix it before execution. Valid Python and ordinary shell commands do not trigger this repair.
59
78 -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).
60 +ZDR controls what Composio stores, 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).
61
62 ## Stronger guarantees
63
82 -If your organization needs a contractual zero-data-retention arrangement or shorter retention windows, [contact sales](https://composio.dev/contact?utm_source=docs&cta_placement=docs-data-retention). For our data-handling policies and sub-processor list, see the [Composio Trust Center](https://trust.composio.dev).
64 +If your organization needs shorter retention windows, [contact sales](https://composio.dev/contact?utm_source=docs&cta_placement=docs-data-retention). For our data-handling policies and sub-processor list, see the [Composio Trust Center](https://trust.composio.dev).
docs/content/docs/security/meta.json
+3 -1
@@ -3,6 +3,8 @@
3 "defaultOpen": false,
4 "pages": [
5 "overview",
6 - "token-custody"
6 + "token-custody",
7 + "data-retention",
8 + "zero-data-retention"
9 ]
10 }
docs/content/docs/security/overview.mdx
+2 -1
@@ -35,5 +35,6 @@ To report a security issue, contact `security@composio.dev`. Please do not discl
35
36 ## Related resources
37
38 -- [Data retention](/docs/security/data-retention): what we store, for how long, and how to stop storing payloads.
38 +- [Data retention](/docs/security/data-retention): what we store and for how long, on every plan.
39 +- [Zero Data Retention](/docs/security/zero-data-retention): how to stop storing call payloads, and what ZDR covers.
40 - [Composio Trust Center](https://trust.composio.dev): security certifications and compliance.
docs/content/docs/security/token-custody.mdx
+1 -1
@@ -127,6 +127,6 @@ If your organization has an active customer-managed keyring, retrieve its public
127
128 Your backend must bind the signed-in user to the correct Composio `user_id` and connected accounts. A caller-supplied user ID is not proof of identity. Choose [provider scopes](/docs/authentication/controlling-scopes), [session tools](/docs/configuring-sessions), and [API-key permissions](/reference/authenticating-to-composio/project-api-key-permissions) for the operations your application needs.
129
130 -Credential redaction and payload retention are separate controls. Tool arguments and results are stored in execution logs by default. The project's **Don't store data** setting stops storage of new call payloads while retaining audit metadata. It does not prevent processing during execution, delete existing logs, or govern your own logs and model provider. See [data retention](/docs/security/data-retention) for file storage, Workbench processing, and retention details.
130 +Credential redaction and payload retention are separate controls. Tool arguments and results are stored in execution logs by default. A project's [Zero Data Retention](/docs/security/zero-data-retention) setting stops storage of new call payloads for covered calls while retaining audit metadata. It does not prevent processing during execution, delete existing logs, or govern your own logs and model provider. See [data retention](/docs/security/data-retention) for file storage, Workbench processing, and retention details.
131
132 For compliance reports and the current sub-processor list, use the [Composio Trust Center](https://trust.composio.dev).
docs/content/docs/security/zero-data-retention.mdx new
+127
@@ -0,0 +1,127 @@
1 +---
2 +title: Zero Data Retention
3 +description: What Zero Data Retention covers, what Composio still stores, what it does not cover, and how organization admins turn it on.
4 +keywords: [zero data retention, ZDR, data retention, payloads, privacy, compliance, dont store data, log storage]
5 +---
6 +
7 +When Zero Data Retention (ZDR) is on, Composio does not store the payloads of covered calls. It runs each covered tool call and Proxy Execute request and returns the result without writing the request arguments, response data, or error text to its execution logs. The log for each call keeps metadata only, such as IDs, the tool, timing, and the HTTP status code.
8 +
9 +<Callout type="info">
10 +ZDR is available on paid plans for a [usage-based price](https://composio.dev/pricing) and included on Enterprise. An organization admin turns it on in **Organization Settings > Billing > Add-ons**.
11 +</Callout>
12 +
13 +## How ZDR works
14 +
15 +For each covered call, Composio writes a log that holds metadata only:
16 +
17 +| Data | Fields |
18 +| --- | --- |
19 +| Stored | IDs for the log, project, connected account, auth config, API key, session, sandbox, and request. The user ID you pass. The toolkit, tool, and tool version. The SDK source, runtime, and framework. Timing, the HTTP status code, and whether the call errored. |
20 +| Not stored | Request arguments, response data, and error text. |
21 +
22 +Composio stores the user ID you pass, so use opaque IDs, such as a database key, rather than emails or names.
23 +
24 +## Scope
25 +
26 +ZDR applies per project. It covers requests that use a ZDR project's API key, session, or MCP URL.
27 +
28 +On the Enterprise plan, new projects start with ZDR on, whether you create them in the dashboard or through the API. On other paid plans, new projects start with ZDR off, even when ZDR is on for all projects. Turn it on for each new project in the dashboard.
29 +
30 +<Callout type="warn">
31 +Projects without ZDR keep storing payloads. Send requests that need ZDR only to projects that have it on.
32 +</Callout>
33 +
34 +## What ZDR covers
35 +
36 +In a ZDR project, Composio does not store payloads for:
37 +
38 +- Tool calls, whether you execute a tool directly or through a session.
39 +- [Proxy Execute](/docs/extending-sessions/proxy-execute) requests.
40 +
41 +**ZDR covers calls through Composio Managed apps only on the Enterprise plan.**
42 +
43 +<ZdrLogVisual />
44 +
45 +## What ZDR does not cover
46 +
47 +ZDR does not cover the following, even in a ZDR project. For how long Composio keeps logs, files, and sandbox data, see [Data retention](/docs/security/data-retention).
48 +
49 +| Feature | Details | What to do |
50 +| --- | --- | --- |
51 +| Composio Managed apps, except on the Enterprise plan | Auth configs that use Composio's own OAuth app. | Use [your own OAuth app](/docs/authentication/custom-app-vs-managed-app#create-a-custom-auth-config) for toolkits that need ZDR. Existing users reconnect through the new auth config. You can also [contact sales](https://composio.dev/contact?utm_source=docs&cta_placement=docs-zero-data-retention) about Enterprise. |
52 +| Instant Tools | Composio does not store their payloads, but the third-party provider behind each [hosted account](/docs/instant-tools#know-which-account-runs-the-tool) may keep data under its own policy. | Set `instant=False` in Python or `instant: false` in TypeScript when you create Sessions that handle data that needs ZDR. |
53 +| Triggers | With ZDR on, trigger logs leave out event payloads, but Composio still stores the events to process and deliver them. | Do not use triggers for data that needs ZDR. |
54 +| Sandbox | The sandbox includes the Workbench and remote Bash. Sessions also offload large responses to it. Sessions turn on the sandbox by default. | [Disable the sandbox](#disable-the-sandbox-in-sessions) when you create sessions. |
55 +| Files | Composio stages files that tools upload or download, including Proxy Execute binary responses, and cleans them up after 24 hours. | Do not use tools that upload or download files for data that needs ZDR. |
56 +| Requests with the `x-debug: true` header | Composio archives these requests for debugging. | Do not send this header from ZDR projects. |
57 +| Tool search in sessions | Composio can cache search queries to improve results. | Keep sensitive data out of search queries, or use the [direct tools preset](/docs/configuring-sessions#direct-tools-preset) to turn off tool search. |
58 +| Third parties | The destination apps you connect, your model provider, external MCP servers, and your own logs keep their own data policies. | Review each provider's data policy, and set retention for your own logs. |
59 +
60 +### Disable the sandbox in sessions
61 +
62 +Turn off the sandbox when you create a session:
63 +
64 +<Tabs groupId="language" items={['Python', 'TypeScript']} persist>
65 +<Tab value="Python">
66 +```python
67 +from composio import Composio
68 +
69 +composio = Composio()
70 +
71 +session = composio.sessions.create(
72 + user_id="user_123",
73 + sandbox={"enable": False},
74 +)
75 +```
76 +</Tab>
77 +<Tab value="TypeScript">
78 +```typescript
79 +// @noErrors
80 +import { Composio } from '@composio/core';
81 +const composio = new Composio({ apiKey: 'your_api_key' });
82 +// ---cut---
83 +const session = await composio.create("user_123", {
84 + sandbox: { enable: false },
85 +});
86 +```
87 +</Tab>
88 +</Tabs>
89 +
90 +See [Disabling the sandbox](/docs/configuring-sessions#disabling-the-sandbox) for what changes in the session.
91 +
92 +## Always stored
93 +
94 +Composio stores audit logs and telemetry on every plan, and ZDR does not change them:
95 +
96 +- **Audit logs** record who did what and when, including the metadata row for each tool call.
97 +- **Telemetry** is the metrics, traces, application logs, error reports, and usage metering that Composio uses to run and bill the service. Telemetry can include error messages returned by providers.
98 +
99 +## Existing data
100 +
101 +ZDR applies only to new calls. Logs written before you turned it on keep their payloads for up to one year under the [standard retention policy](/docs/security/data-retention#how-long-logs-are-retained). To delete them sooner, email [support@composio.dev](mailto:support@composio.dev) with the project ID. If you turn ZDR off, new calls store payloads again.
102 +
103 +## Turn ZDR on or off
104 +
105 +Only organization admins can turn ZDR on or off. Other members can see its status but cannot change it.
106 +
107 +1. In the dashboard, open [**Organization Settings > Billing**](https://dashboard.composio.dev/~/org/settings/billing?utm_source=docs&utm_medium=content&utm_campaign=docs-zero-data-retention).
108 +2. Under **Add-ons**, turn on **Zero Data Retention**.
109 +3. Review the price and what ZDR does not cover, then confirm. ZDR turns on for every current project.
110 +
111 +To turn ZDR on or off for one project, open [**Project Settings > General**](https://dashboard.composio.dev/~/project/settings/general?utm_source=docs&utm_medium=content&utm_campaign=docs-zero-data-retention) and use the **Zero Data Retention** setting. To turn it off for every project, turn off **Zero Data Retention** in Billing.
112 +
113 +### Hobby plan
114 +
115 +ZDR is not available on the Hobby plan. Projects that already had **Don't store data** on keep ZDR on, and an admin can turn it off. Turning it back on requires a paid plan.
116 +
117 +### Projects that used Don't store data
118 +
119 +ZDR replaces the **Don't store data** option under **Log storage**. Projects that had it on now have ZDR on, and the rest have it off.
120 +
121 +## Related
122 +
123 +- [Data retention](/docs/security/data-retention): the standard retention policy for every plan.
124 +- [Token custody architecture](/docs/security/token-custody): where credentials live and how Composio uses them.
125 +- [Composio Trust Center](https://trust.composio.dev): compliance reports and the sub-processor list.
126 +- [Data Processing Addendum](https://composio.dev/legal/dpa) and [Business Associate Agreement](https://composio.dev/legal/baa).
127 +- [Pricing](https://composio.dev/pricing).
docs/lib/home-navigation.ts
+7 -4
@@ -43,10 +43,12 @@ interface DocsProductConfig {
43 home: Omit<HomeIntent, 'productId' | 'product'>;
44 }
45
46 -const SHARED_SIDEBAR_ITEMS = [
46 +/** A sidebar entry that both products list: one page or one content folder. */
47 +type SharedSidebarItem = Extract<ProductSidebarItem, { type: 'page' | 'folder' }>;
48 +
49 +const SHARED_SIDEBAR_ITEMS: readonly SharedSidebarItem[] = [
50 { type: 'page', url: '/docs/using-composio-skill' },
48 - { type: 'folder', path: 'security', label: 'Security and data' },
49 -] as const satisfies readonly ProductSidebarItem[];
51 +];
52
53 const SHARED_ROUTE_PREFIXES = SHARED_SIDEBAR_ITEMS.map(item =>
54 item.type === 'page' ? item.url : `/docs/${item.path}`
@@ -137,7 +139,7 @@ export const DOCS_PRODUCTS = {
139 '/docs/extending-sessions',
140 '/docs/setting-up-triggers',
141 '/docs/poc-to-prod',
140 - '/docs/security/data-retention',
142 + '/docs/security',
143 '/docs/sessions-vs-direct-execution',
144 '/docs/tools-direct',
145 '/docs/auth-configuration',
@@ -216,6 +218,7 @@ export const DOCS_PRODUCTS = {
218 { type: 'page', url: '/docs/production-readiness' },
219 { type: 'page', url: '/docs/authentication/white-labeling-authentication' },
220 { type: 'folder', path: 'poc-to-prod' },
221 + { type: 'folder', path: 'security', label: 'Security and data' },
222 ],
223 },
224 {
docs/mdx-components.tsx
+2
@@ -52,6 +52,7 @@ import { MediaSplit } from '@/components/media-split';
52 import { PackageInstall } from '@/components/package-install';
53 import { ManageConnectionsVisual } from '@/components/manage-connections-visual';
54 import { ConnectionRefreshVisual } from '@/components/connection-refresh-visual';
55 +import { ZdrLogVisual } from '@/components/zdr-log-visual';
56 import {
57 ShieldCheck,
58 Route as RouteIcon,
@@ -164,6 +165,7 @@ export function getMDXComponents(components?: MDXComponents): MDXComponents {
165 PackageInstall,
166 ManageConnectionsVisual,
167 ConnectionRefreshVisual,
168 + ZdrLogVisual,
169 // Lucide icons
170 ShieldCheck,
171 RouteIcon,
docs/public/images/zdr-project-setting.png
Binary files /dev/null and b/docs/public/images/zdr-project-setting.png differ
docs/tests/static/product-navigation.test.ts
+32 -13
@@ -43,14 +43,17 @@ describe('Docs product navigation', () => {
43 expect(classifyDocsProduct('/docs/production-readiness')).toBe('platform');
44 expect(classifyDocsProduct('/docs')).toBeNull();
45 expect(classifyDocsProduct('/docs/using-composio-skill')).toBeNull();
46 - expect(classifyDocsProduct('/docs/security/overview')).toBeNull();
46 + expect(classifyDocsProduct('/docs/security/overview')).toBe('platform');
47 + expect(classifyDocsProduct('/docs/security/token-custody')).toBe('platform');
48 expect(classifyDocsProduct('/docs/security/data-retention')).toBe('platform');
49 + expect(classifyDocsProduct('/docs/security/zero-data-retention')).toBe('platform');
50 });
51
52 test('uses route inference before persistence and the documented default last', () => {
53 expect(resolveDocsProduct('/docs/quickstart', 'for-you')).toBe('platform');
52 - expect(resolveDocsProduct('/docs/security/overview', 'for-you')).toBe('for-you');
53 - expect(resolveDocsProduct('/docs/security/overview', 'platform')).toBe('platform');
54 + expect(resolveDocsProduct('/docs/using-composio-skill', 'for-you')).toBe('for-you');
55 + expect(resolveDocsProduct('/docs/using-composio-skill', 'platform')).toBe('platform');
56 + expect(resolveDocsProduct('/docs/security/overview', 'for-you')).toBe('platform');
57 expect(resolveDocsProduct('/docs', 'invalid')).toBe('platform');
58 expect(parseDocsProduct('for-you')).toBe('for-you');
59 expect(parseDocsProduct('anything-else')).toBeNull();
@@ -77,15 +80,18 @@ describe('Docs product navigation', () => {
80 '/docs/agent-plugins',
81 );
82 expect(docsProductDestination('/docs/cli', 'platform')).toBe('/docs/quickstart');
80 - expect(docsProductDestination('/docs/security/overview', 'for-you')).toBe(
81 - '/docs/security/overview',
83 + expect(docsProductDestination('/docs/using-composio-skill', 'for-you')).toBe(
84 + '/docs/using-composio-skill',
85 );
83 - expect(docsProductDestination('/docs/security/data-retention', 'platform')).toBe(
84 - '/docs/security/data-retention',
86 + expect(docsProductDestination('/docs/security/overview', 'for-you')).toBe(
87 + '/docs/agent-plugins',
88 );
89 expect(docsProductDestination('/docs/security/data-retention', 'for-you')).toBe(
90 '/docs/agent-plugins',
91 );
92 + expect(docsProductDestination('/docs/security/zero-data-retention', 'for-you')).toBe(
93 + '/docs/agent-plugins',
94 + );
95 });
96
97 test('animates only when view transitions are available and motion is allowed', () => {
@@ -164,12 +170,26 @@ describe('Docs product navigation', () => {
170 expect(forYouUrls).not.toContain('/docs');
171 expect(platformUrls).not.toContain('/docs');
172
167 - for (const sharedUrl of [
168 - '/docs/using-composio-skill',
173 + expect(forYouUrls).toContain('/docs/using-composio-skill');
174 + expect(platformUrls).toContain('/docs/using-composio-skill');
175 +
176 + const securityUrls = [
177 '/docs/security/overview',
170 - ]) {
171 - expect(forYouUrls).toContain(sharedUrl);
172 - expect(platformUrls).toContain(sharedUrl);
178 + '/docs/security/token-custody',
179 + '/docs/security/data-retention',
180 + '/docs/security/zero-data-retention',
181 + ];
182 + const security = platformTree.children.flatMap(node =>
183 + node.type === 'folder' ? [node, ...node.children] : [node],
184 + ).find(node => node.type === 'folder' && node.name === 'Security and data');
185 + expect(security?.type).toBe('folder');
186 + if (security?.type !== 'folder') throw new Error('Security and data folder missing');
187 + expect(security.children.flatMap(node => node.type === 'page' ? [node.url] : [])).toEqual(
188 + securityUrls,
189 + );
190 + for (const url of securityUrls) {
191 + expect(platformUrls.filter(candidate => candidate === url)).toHaveLength(1);
192 + expect(forYouUrls).not.toContain(url);
193 }
194
195 const readiness = platformTree.children.flatMap(node =>
@@ -181,7 +201,6 @@ describe('Docs product navigation', () => {
201 expect(readinessUrls).toEqual([
202 '/docs/authentication/custom-app-vs-managed-app',
203 '/reference/rate-limits',
184 - '/docs/security/data-retention',
204 '/docs/poc-to-prod/stream-logs-to-a-siem',
205 ]);
206 for (const url of readinessUrls) {