Zero data retention

Metering and content are two different things. The gateway always records that a request happened and what it cost. Whether it records what was in it is up to you.

The header

Webway-ZDR: required

With it set, a request is refused rather than routed to a provider that would retain the prompt or the completion. It fails loudly — an error you can see in logs — rather than quietly downgrading to a provider that keeps a copy.

Without it, routing prefers non-retaining providers where they can serve the model, but will fall back.

Refusal is the feature. A flag that silently does nothing when it cannot be honoured is worse than no flag, because you would ship believing it held.

What is always kept

• The metering row: model, token counts, cost, latency, status.
• The ledger entry the cost produced.

Neither contains prompt or completion text.

What is kept only if you ask

Request and response bodies, for debugging. Off unless enabled, and worth turning back off once the bug is found.

Turning it on

The toggle on each model card in the catalogue adds the header to the sample request so you can see the shape. In your own client it is one more entry in the headers map.