Last updated 1 August 2026
What we collect
Two categories. Account data — name, work email, company and billing details — which you give us when you create a workspace. And request metadata: timestamp, chosen model, token counts, latency, cost and the scoring record that explains the routing decision.
Prompt and completion bodies are not in either category by default. They pass through the routing layer in memory and are discarded once the response is returned.
Optional retention
If you enable live-traffic evals, a sample of requests is retained so it can be graded. You choose the sample rate and the retention window, and the window is enforced automatically. Retention can be switched off at any time, which purges anything held under it.
Where data lives
Metadata is stored in the region attached to your workspace. Available regions are listed in your dashboard. Changing region applies to new data; existing records are migrated on request.
Model training
Nothing that passes through Zentic is used to train any model, ours or a provider's, on any plan. This is contractual with every provider in the pool, not merely a setting.
Sub-processors
We use a small number of sub-processors for hosting, payment and error reporting. The current list is published and updated before any change takes effect, with notice to workspace owners.
Your rights
You can export or delete your data from the dashboard at any time. For requests that cannot be self-served — access requests, restriction of processing, or objections — write to privacy@zentic.io and we will respond within thirty days.
Cookies
We set a session cookie for authentication and a preference cookie for your dashboard layout. There is no advertising or cross-site tracking on this site.
Contact
Questions about this policy go to privacy@zentic.io. Our data protection officer can be reached at the same address.