:encrypted row in the picker, and on the Nito API, where your client encrypts the messages and sends the Encrypted headers. The Plugin cannot run it yet. Choosing an :encrypted model there returns a message pointing you to Anonymous, Private, or Confidential.
What It Protects Against
Anyone between your device and the sealed hardware reading the prompt or the reply, Nito included, on top of everything Confidential gives you.The Key
The key your device encrypts with arrives with the attestation evidence. Nito checks that the key is present and the right shape for the declared algorithm, and hands it to you with the evidence. Confirming the key belongs to the attested workload is part of verifying the evidence. See Verify It Yourself.Constraints
- In the Browser App the reply arrives whole. It is decrypted in your browser before it can be shown.
- Web search and fetch cannot run inside the encrypted request. In the Browser App, Nito grounds the prompt with a browser-side step before encrypting, where the model supports it.
- Raw image and file uploads are not sent. Documents are parsed to text in your browser, or with an explicit server parse you choose, before encryption.
- Fusion synthesis is an explicit step. Encrypted Fusion shows the model answers first, then a Synthesize in Encrypted action. See Fusion.
When to Use It
The most sensitive work, where the prompt must stay unreadable to everything between your device and the sealed hardware.Related
Confidential
Sealed hardware with attestation, on every surface.
Privacy in the Browser App
Where Encrypted lives today.
Encrypted Inference
The full treatment: how it works, what it protects, what works, protocol.

