Data handling & retention
What data Syncanix processes, how zero-data-retention (ZDR) works with model providers, what the discovery CLI sends, and how long data is kept.
Syncanix processes only what it needs to run your assistant. Here’s what that is, what leaves your environment, and how long anything is kept.
What Syncanix processes
Three kinds of data flow through Syncanix:
- Your API catalog
- The capabilities the CLI discovers from your codebase — method, path, and argument names — used to let the assistant act on your behalf.
- Conversations
- Messages between your end users and the assistant, used to answer in the moment and, if you enable it, to remember across sessions.
- Knowledge content
- Documentation and content you add so the assistant can ground its answers in your material.
Zero data retention with model providers
Syncanix is built so that model providers don’t retain your data. Managed model access runs under zero-data-retention (ZDR) terms, and the discovery CLI refuses to send anything to a provider unless ZDR is confirmed.
- The CLI sends only a small, redacted excerpt of each handler (no more than a couple of kilobytes) plus capability, method, path, and argument names.
- It never sends your full source code, file locations, environment variables, secrets, or customer data.
- Managed enrichment refuses to run unless ZDR is enabled; bring-your-own-key uses your own provider account.
How long data is kept
Retention is tied to your plan, and you can always keep data for a shorter time than your plan allows:
- Conversations are retained for a period that grows with your plan, from days on Dev up to a configurable window on Enterprise.
- Audit logs are kept for a plan-dependent period for security and accountability.
- Operational logs — the technical logs we use to run the service — are kept for 14 days.
- Workspace admins can shorten retention below the plan default.