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 | ## Canonical public sources |
| 2 | |
| 3 | - The [security overview](https://docs.composio.dev/docs/security/overview) describes Composio's security controls, including organization and project isolation, encryption for credentials and keys, TLS in transit, token redaction, and webhook signing. |
| 4 | - The [data-retention documentation](https://docs.composio.dev/docs/security/data-retention) explains tool-call log retention, per-project log-storage controls, returned-file URL lifetime, and where data flows during execution. |
| 5 | - The [Composio Trust Center](https://trust.composio.dev) provides current compliance reports and sub-processor information. |
| 6 | |
| 7 | ## Zero data retention and no-training requirements |
| 8 | |
| 9 | Standard plans do not guarantee end-to-end zero data retention or zero training. The per-project **Don't store data** setting reduces what Composio stores, but it does not govern data retained or processed by third-party providers. |
| 10 | |
| 11 | The [standard DPA](https://composio.dev/legal/dpa) is available to Pro and Enterprise Developer customers. An organization admin can review and accept it in Organization Settings > Billing > Data Processing Addendum. Acceptance is click-through; no countersignature is required. |
| 12 | |
| 13 | For bespoke data-processing terms or an end-to-end contractual no-training requirement, use the Enterprise track so the requirements can be scoped explicitly. |
| 14 | |
| 15 | ## Model training |
| 16 | |
| 17 | Do not infer a blanket no-training guarantee. Features that use third-party providers are also governed by those providers' terms. For an end-to-end contractual no-training requirement, use the Enterprise track. |
| 18 | |
| 19 | ## FedRAMP |
| 20 | |
| 21 | Composio is not FedRAMP authorized. |
| 22 | |
| 23 | ## Third-party providers |
| 24 | |
| 25 | Some toolkit executions and browser automation rely on third-party providers or sub-processors. Data can flow to those providers during execution, and their data and training terms can differ. Use the Trust Center and data-retention documentation for current public details. |