What It Protects

​

What Stays Private

​

What It Relies On

• The key belonging to the sealed hardware. The model’s public key arrives with the attestation evidence. Checking the evidence, and confirming the key is bound to the attested workload, is what ties the key to the hardware. See Verify It Yourself.
• Your device. Plaintext exists on it, before encryption and after decryption.
• Fresh keys for every message. Each message uses a fresh ephemeral key, and the cipher authenticates the ciphertext. The authenticated variant also binds a per-request nonce, a timestamp, the model, and the message position into every envelope. Which variant applies depends on the backend. See Protocol.
• The code that encrypts. In the Browser App that code arrives from Nito over TLS. With your own client on the API, it is yours. See How It Works.

​

Outside the Envelope

• That a call happened. Nito sees the time, the model, the account, and the size of the encrypted envelope, and settles usage from the token counts the provider reports. The content is sealed. The fact of the call is not.
• Work done on your side. Function tools at Encrypted run on your device, in plaintext, by design. In the Browser App, web grounding runs through a browser-side helper before encryption, so the search query leaves your browser before the prompt is encrypted. See What Works at Encrypted.

​

Related