Trust center
What 0mcp processes and stores.
“Payloads are not stored” applies specifically to upstream credentials and proxied request and response bodies. Operating the platform still requires stored specifications, configuration, account records, billing state, and operational metadata.
| Data category | Storage | Purpose | Retention |
|---|---|---|---|
| OpenAPI specifications and server configuration | Stored | Required to configure, version, and operate each MCP server | Until the related server or account is deleted |
| Upstream API credentials and authentication headers | Not stored | Relayed for the request where required | Not retained |
| Proxied request and response bodies | Not stored | Processed in transit to call the upstream API and return its result | Not retained |
| Operational logs | Stored | Status codes, latency, matched route, errors, and operational diagnostics | 1 day on Starter; 7 days on Pro |
| Aggregate usage and analytics | Stored | Metering, reliability, and historical platform insights | Retained for ongoing platform insights |
| Account and billing data | Stored | Account access and subscription administration; payment details are handled by Polar | For the account lifecycle and applicable legal obligations |
This inventory summarizes the current Privacy Policy. For deletion or privacy requests, email hello@0mcp.io.
Last reviewed: July 13, 2026