@devries-cameron20 / composio-1 / commits / 231122de1
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(security): model-training and retention policy (#4944)

## Summary Updates the public docs to state the data-use and retention policy in ComposioHQ/landing#614. ## Changes - `security/data-retention.mdx`: 30-day deletion on org deletion; new **Model training** and **Your account data** sections. ## Type of change - [x] Documentation ## Before merging - [ ] **Legal review** of the final wording, especially the de-identification standard and the CCPA/GDPR treatment of de-identified data. - [ ] **Engineering confirms the system matches the text:** - [ ] De-identification exists (or ships first). It must strip org, project, user and connected-account IDs and IP addresses, and must never carry payloads or error text. Until then, no training or analytics may run on execution metadata. - [ ] Deleting an org purges its payloads and execution logs within 30 days, including backups and replicas. - [ ] An explicit deletion request hard-deletes account data within 30 days, keeping a hashed-email suppression entry. - [ ] Churned members are suppressed from marketing and product-update emails. - [ ] **Notice:** Privacy Policy §9 promises an email and an in-product notice, and Terms §2 promises an in-product notice. Customers who accepted the DPA should get notice too. - [ ] Merge together with ComposioHQ/landing#614 and ComposioHQ/support-knowledge#19 (which deletes the compliance KB page upstream), set the real effective date (drafted as Oct 17, 2026), and update the Trust Center FAQ the same day. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: Shubham Mehta <shubham@composio.dev>

Srujan committed Oct 17, 2026 at 10:24 UTC 231122de19abd820eac91549382e407e2d2cbe06
4 files changed +17 -5
docs/content/docs/production-readiness.mdx
+1 -1
@@ -112,7 +112,7 @@ See [Subscribing to trigger events](/docs/setting-up-triggers/subscribing-to-eve
112
113 ## 8. Set security and data-retention expectations
114
115 -Review which tool inputs, outputs, logs, and files your integration creates. Align retention with your own product policy and customer commitments. See [Data retention](/docs/security/data-retention) for the controls Composio provides.
115 +Review which tool inputs, outputs, logs, and files your integration creates. Align retention with your own product policy and customer commitments. See [Data retention and handling](/docs/security/data-retention) for the controls Composio provides.
116
117 Document who can access production projects, rotate keys, manage auth configs, and inspect logs. Keep those permissions limited to the people and services that need them.
118
docs/content/docs/security/data-retention.mdx
+13 -1
@@ -1,5 +1,5 @@
1 ---
2 -title: Data retention
2 +title: Data retention and handling
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 ---
@@ -22,6 +22,18 @@ Composio creates logs for tool executions and trigger events. These logs contain
22
23 Tool execution logs and trigger event logs are retained for up to **one year**, after which they are automatically deleted.
24
25 +When an organization is deleted, Composio deletes its execution logs, including request and response payloads, within **30 days**.
26 +
27 +## Model training
28 +
29 +Composio does not use request arguments, response data, or trigger payloads to train or improve AI or machine learning models, on any plan.
30 +
31 +Composio may use execution metadata to improve the platform, train models, or produce aggregate analytics, but only after de-identifying it. Execution metadata is the toolkit and action, status, error codes, timing, and counts. De-identification removes organization, project, user, and connected-account identifiers and IP addresses. Composio may keep de-identified metadata indefinitely, and it never contains payloads or error message text. See the [Terms of Service](https://composio.dev/terms), [Privacy Policy](https://composio.dev/privacy), and [Data Processing Addendum](https://composio.dev/legal/dpa).
32 +
33 +## Your account data
34 +
35 +Composio keeps account data about your organization and its members until you ask for it to be deleted. Members who stop using Composio are deactivated and receive no marketing emails or product updates. To permanently delete account data, email [support@composio.dev](mailto:support@composio.dev). Composio completes deletion within 30 days and keeps only a hashed email address to suppress future emails, plus records the law requires, such as billing records.
36 +
37 ## How long files are available
38
39 When a tool uses or returns a file (an attachment, image, document, export, and so on), Composio stages it in temporary object storage and shares it through a presigned URL. The URL is valid for **1 hour by default**. You can configure this URL TTL per project in **Project Settings**, up to 24 hours.
docs/content/docs/security/overview.mdx
+1 -1
@@ -35,6 +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 and for how long, on every plan.
38 +- [Data retention and handling](/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/zero-data-retention.mdx
+2 -2
@@ -44,7 +44,7 @@ In a ZDR project, Composio does not store payloads for:
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).
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 and handling](/docs/security/data-retention).
48
49 | Feature | Details | What to do |
50 | --- | --- | --- |
@@ -119,7 +119,7 @@ ZDR replaces the **Don't store data** option under **Log storage**. Projects tha
119
120 ## Related
121
122 -- [Data retention](/docs/security/data-retention): the standard retention policy for every plan.
122 +- [Data retention and handling](/docs/security/data-retention): the standard retention policy for every plan.
123 - [Token custody architecture](/docs/security/token-custody): where credentials live and how Composio uses them.
124 - [Composio Trust Center](https://trust.composio.dev): compliance reports and the sub-processor list.
125 - [Data Processing Addendum](https://composio.dev/legal/dpa) and [Business Associate Agreement](https://composio.dev/legal/baa).