Opt out of request and response storage entirely — no prompt or completion is persisted anywhere in the pipeline.
Toggle this at Settings → Privacy (the "Zero data retention" switch). When on, OpenDunes routes only to providers that don't retain request data (forwarded upstream as a deny-data-collection routing preference). The same page also lets you opt out of provider training and choose your PII-redaction mode.
When Zero Data Retention (ZDR) is enabled, OpenDunes does not persist the content of your requests or responses anywhere — not in logs, not in databases, not in transit buffers. The prompt goes in, the completion comes out, and nothing is stored.
This is OpenDunes' implementation of an important Algerian compliance requirement: under Law 18-07 on the protection of personal data, organisations that process personal information must restrict retention to what is strictly necessary. ZDR mode gives you a documented, auditable way to meet that requirement.
With ZDR enabled on your account:
messages — including system prompts, user inputs, and assistant turns — are never written to disk.Usage metadata (token counts, model used, timestamp, request ID, cost) is still recorded. This is billing data, not content, and is necessary to maintain your ledger. It contains no text from your conversations.
ZDR is an account-level setting — it applies to every API key and every chat session on your account. Flip the Zero data retention switch at Settings → Privacy; the change takes effect on your next request.
OpenDunes is built to comply with Algerian Law 18-07 on the protection of personal data. Everything OpenDunes itself stores — your account, ledger, and logs — lives on OpenDunes infrastructure hosted in Algeria. Model inference is served by the upstream provider running the model, which may process the request outside Algeria; ZDR restricts routing to providers that don't retain request data, and nothing is persisted on OpenDunes' side.
ZDR mode, combined with OpenDunes' Algeria-hosted platform storage and the PII redaction pipeline, gives you three complementary controls:
| Control | What it does |
|---|---|
| Platform storage in Algeria | Everything OpenDunes stores stays in Algeria |
| PII redaction | Detected PII patterns are scrubbed before storage |
| Zero Data Retention | No request or response content is stored at all |
Use ZDR when your application handles highly sensitive data — medical records, financial disclosures, legal documents, identity information — where even redacted storage is not acceptable.
Even with ZDR enabled, OpenDunes maintains a minimal audit row per request: timestamp, model, token counts, cost, and the UUID-v7 request ID. This audit trail is required for billing integrity and can be provided as evidence of compliance. The audit row contains no user-supplied text.
You can export audit records from your dashboard or pull the daily rollup via GET /api/v1/activity.