@devries-cameron20 / composio Mirror · read-only / commits / c2fff7772
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.

Mirrored from https://github.com/Camo67/composio.git

Synced Nov 21, 19:45 UTC

docs(security): note the workbench uses a third-party model provider (data flow)

Disclosed low-key in the "Where your data goes" list, scoped to "if you use the workbench", deferring specifics to the Trust Center. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Palash Kala committed Jun 5, 2026 at 21:40 UTC c2fff7772d10dfaa0014f4550051fd267775d148
1 file changed +2 -1
docs/content/docs/security/data-retention.mdx
+2 -1
@@ -44,7 +44,8 @@ Choosing **Don't store data** stops Composio from persisting your payloads, but
44
45 - the **destination provider** you integrate with, which the tool call is made to;
46 - **Composio's execution path** while the call runs;
47 -- **object storage** for file payloads, a **code sandbox** if you use the workbench, and your configured **trigger destinations**, in real time.
47 +- **object storage** for file payloads, and your configured **trigger destinations**, delivered in real time;
48 +- if you use the **workbench** or code execution, an isolated **code sandbox** and a **third-party model provider** that powers it.
49
50 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).
51