Zero data retention, explained

Zero data retention, explained

Zero data retention means the gateway does not keep the words you send. MagmaRouter stores what it needs to bill you (model, token counts, cost) and nothing of the prompt or the reply, so there is nothing for us to read.

What is kept and what is not

For each request MagmaRouter records the model id, prompt and completion token counts, the cost in nano-dollars, latency and outcome, for 90 days. It does not write the prompt, the completion or the tools array to its database, its request log or disk.

Encrypted on every hop

Your request reaches MagmaRouter over HTTPS, and MagmaRouter sends it on to the model host over HTTPS, so it is encrypted on the network the whole way from your machine to the model and back. In between it is handled in memory and never written to disk. The only trace it leaves is a SHA-256 fingerprint in the receipt, which proves which messages a reply was for without containing them. How your messages are protected walks through each step.

Where the claim stops

Inference still happens somewhere MagmaRouter does not retain your prompt, but the model host has to read it to answer, and for the length of one request those tokens are in memory on that hop. MagmaRouter’s claim is about its own storage, verified by the receipt, not about the model host’s handling.

How you verify it

Every chat completion returns a signed receipt: a hash of the prompt, the model and a timestamp, signed with the gateway's key. If the prompt is not recoverable from the receipt, and only a hash is, then it is not in the database either. You can check a receipt yourself on the privacy page.

Related