Ask a private model. Get a proof you can check yourself.

What happens when you send a message

Before sending, this browser checks the model's hardware evidence and looks its signing key up in a public log on NEAR. No key in the log, nothing is sent.
The message is encrypted to that key. Our server and the gateway see the ciphertext, its size, timing, the model id and the settings of the request, not the contents.
The reply comes back signed inside the model's enclave. The hashes are recomputed here and shown on a proof card you can re-check yourself or hand to an auditor.

Try the honest path or one of the catches

Model Demo: swap the key before the log check (tamper) Demo: a deployment no verifier has logged, behind the real key Stricter: send only when a verifier you trust has marked this state of the enclave (the release rule)