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, 08:30 UTC
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>