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): tie file payloads in object storage to the file TTL
Split the "Where your data goes" file/trigger bullet: file payloads live in object storage only for the file TTL (1h default) then expire, distinct from trigger destinations which receive events in real time. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Palash Kala committed
Jun 25, 2026 at 19:17 UTC
a072697252d696425b5bdc41650447b9fecb86e8
1 file changed
+2
-1
docs/content/docs/security/data-retention.mdx
+2
-1
@@ -57,7 +57,8 @@ Choosing **Don't store data** stops Composio from persisting your payloads, but
57
58
- the **destination provider** you integrate with, which the tool call is made to;
59
- **Composio's execution path** while the call runs;
60
-- **object storage** for file payloads, and your configured **trigger destinations**, delivered in real time;
60
+- **object storage** for files returned by tool calls, held only for the file TTL (1 hour by default — see [How long files are available](#how-long-files-are-available)) and then expired;
61
+- your configured **trigger destinations**, which receive trigger events in real time;
62
- if you use the **workbench** or code execution, an isolated **code sandbox** and a **third-party model provider** that powers it.
63
64
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).