Zero Data Retention on every account
Nexus is Zero Data Retention (ZDR) on every account and every plan: Pro, Team, and Enterprise.- Nexus does not store prompts, responses, code, or tool calls.
- Nexus never keeps traces.
- Nexus keeps service metadata to provide the routing service and de-identifies it after 30 days.
Service metadata
Service metadata is information about each request, not its content. Nexus uses it to choose a model for each turn, check the quality of those choices, and show your usage and cost. It includes:- Account ID and request time
- Token counts and billing
- Harness and Nexus CLI version
- Request shape, such as message size and whether it includes code or images
- The model that served each turn
- Routing quality scores
Where your requests go
- Open models run on Fireworks under the same Zero Data Retention policy.
- Subprocessors. Fireworks may send data to its registered subprocessors to serve a request. These subprocessors are held to Zero Data Retention as well.
- Your own provider accounts. When Nexus Auto sends a turn to Anthropic, OpenAI, or Amazon Bedrock on your own account, that provider’s data policies apply. The same is true for MCP servers you connect.
How Nexus protects your data
- Your key stays on your machine.
nexus loginsaves your Nexus key in the OS keychain, or in an encrypted file when no keychain is available. - Provider credentials stay with admins. Model Providers are encrypted at rest and never returned in full, so developers never handle them.
- Platform security. Fireworks encrypts data in transit and at rest, and holds SOC 2 Type II, ISO 27001, ISO 27701, and ISO 42001 certifications. Reports are available in the Trust Center.