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(security): note the workbench uses a third-party model provider (data flow)

Palash Kalac2fff7772d10
diff --git a/docs/content/docs/security/data-retention.mdx b/docs/content/docs/security/data-retention.mdx
index ef7d771fd..3453ef45a 100644
--- a/docs/content/docs/security/data-retention.mdx
+++ b/docs/content/docs/security/data-retention.mdx
@@ -44,7 +44,8 @@ Choosing **Don't store data** stops Composio from persisting your payloads, but
- the **destination provider** you integrate with, which the tool call is made to;
- **Composio's execution path** while the call runs;
-- **object storage** for file payloads, a **code sandbox** if you use the workbench, and your configured **trigger destinations**, in real time.
+- **object storage** for file payloads, and your configured **trigger destinations**, delivered in real time;
+- if you use the **workbench** or code execution, an isolated **code sandbox** and a **third-party model provider** that powers it.
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).