How MagmaRouter protects your messages
What you send to MagmaRouter is encrypted on the way in and the way out, is never written to our database, logs or disk, and comes back with a receipt that holds a one-way fingerprint of it instead of the words. Here is each step.
Encrypted in transit
Your request reaches MagmaRouter over HTTPS, and MagmaRouter passes it to the model host over HTTPS. Nobody on the network between you and the model can read it, on either leg, there or back.
Never written down
MagmaRouter keeps zero data retention. The prompt and the answer are handled in memory for as long as the request takes and are never written to our database, our request log or disk. What we keep is what billing needs: the model, the token counts, the cost and the timing. What is stored lists every field.
Your messages become a fingerprint
Every chat completion comes back with a signed receipt. It holds a SHA-256 hash of the messages you sent, the model and the time, signed with the gateway's key. A hash only goes one way: it proves which messages a reply was for, and the words cannot be read back out of it. You can check any receipt against your own messages on the privacy page.
Your key is stored as a hash
An API key is shown once, when you make it. After that MagmaRouter keeps only a hash of it and finds your account by that hash, so the key itself is not sitting anywhere to be copied.
Where the claim stops
And the answers
The models on the line are Xploded: open models with the refusal taken out of the weights. Refusals explains how that is done and what it means for what you can ask.