@devries-cameron20 / composio Mirror · read-only
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, 06:00 UTC

next
md 40 lines 2.29 KB
Rendered Raw
1 ---
2 type: "reference"
3 title: "Compliance, Data Retention, and Model Training"
4 description: "Public guidance for data retention, model training, compliance, and enterprise security reviews."
5 category: "security-and-trust"
6 visibility: "public"
7 timestamp: "2026-07-24T00:00:00Z"
8 tags:
9 - "compliance"
10 - "retention"
11 - "security"
12 - "privacy"
13 ---
14 # Compliance, Data Retention, and Model Training
15
16 ## Canonical public sources
17
18 - 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.
19 - 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.
20 - The [Composio Trust Center](https://trust.composio.dev) provides current compliance reports and sub-processor information.
21
22 ## Zero data retention and no-training requirements
23
24 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.
25
26 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.
27
28 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.
29
30 ## Model training
31
32 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.
33
34 ## FedRAMP
35
36 Composio is not FedRAMP authorized.
37
38 ## Third-party providers
39
40 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.