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, 06:00 UTC
| 1 | --- |
| 2 | type: "reference" |
| 3 | title: "Dashboard Log Storage" |
| 4 | description: "Public behavior of the project Log storage setting." |
| 5 | category: "sessions-and-execution" |
| 6 | visibility: "public" |
| 7 | timestamp: "2026-07-16T00:00:00Z" |
| 8 | tags: |
| 9 | - "dashboard" |
| 10 | - "logs" |
| 11 | - "data-retention" |
| 12 | --- |
| 13 | # Dashboard Log Storage |
| 14 | |
| 15 | ## “Don't store data” removes new payload content, not the audit row |
| 16 | |
| 17 | New tool executions can still appear in Tool Logs with audit metadata such as tool, status, timestamp, duration, and related identifiers. With **Don't store data** enabled, their request arguments and response payload content are not stored in those rows. |
| 18 | |
| 19 | Changing the setting does not retroactively erase older payloads. Run a new test after changing it and inspect that new row. If new request or response content remains visible, contact support with the timestamp and log reference. |
| 20 | |
| 21 | This setting does not define every contractual retention or deletion window. Use Composio's approved security and privacy documentation for those questions. |