Zero Data Retention (ZDR)
The ISMS Copilot API does not store your prompts or model outputs. Upstream providers are ZDR. Usage metadata only for billing.
The ISMS Copilot API is built for Zero Data Retention (ZDR) of request content: your prompts and model outputs are not kept as customer records after the response is returned.
This is a deliberate product and compliance choice, and a commercial difference from providers that retain API traffic for 30 days (or longer) for abuse monitoring.
What ZDR means here
| Layer | What happens to your content |
|---|---|
| ISMS Copilot API data layer | Request content and model outputs are not stored in Supabase. Inference is transient in process memory. |
| Usage history (console) | Only metadata: model alias, token counts, cost, status, timestamps, key label. No prompt or completion text. |
| Upstream (global aliases) | OpenRouter with account-level mandatory ZDR, plus in-request ZDR flags, on zero-retention endpoints for the closed host pin. |
| Upstream (EU aliases) | Mistral AI under our ZDR agreement; EU processing path. |
| Training | Your content is not used to train models. |
Legal detail and sub-processor lists: API DPA §7 and API sub-processors.
What we do retain (not request content)
As an independent controller, we keep a usage and billing ledger so we can meter prepaid credits, show spend history, prevent fraud, and meet French accounting and tax retention rules. That ledger includes fields such as:
- Token counts and cost
- Model requested / served and status
- API key and account identifiers
- Timestamps and request duration metrics
It does not include the text of your messages or the model reply.
How to verify in product
- Call
POST /v1/chat/completionswith a real prompt. - Open platform.ismscopilot.com/usage.
- You will see tokens, cost, model, and status. You will not see the prompt or the answer text.
The platform console also surfaces a ZDR callout on Dashboard, Models, Usage, and Docs.
Regions and modes
ZDR applies to both processing modes:
- EU aliases (
isms-fast-eu,isms-thinking-eu): Mistral in the EU, ZDR agreement. - Global aliases (
isms-fast,isms-thinking): OpenRouter ZDR path when global mode is on; otherwise the EU/Mistral path.
Region is reported on each successful response via x-isms-processing-region (eu or global). See Models and regions.
What ZDR is not
- It is not a claim that content never exists in memory while a request is processed. Inference needs the text in flight.
- It is not a claim that infrastructure sub-processors never see content in transit (Fly.io, Kong, TLS hops). See the sub-processor list.
- It is not the same as the chat product. Chat conversations are a different product with different retention controls (including Advanced Data Protection). This page is for the Model API only.
Binding legal terms for API customers live on the Trust Center: API Terms, API DPA, API sub-processors. This docs page is the product explanation of the same posture.