> ## Documentation Index
> Fetch the complete documentation index at: https://docs.trynito.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Enabling End-to-End Encryption

> What end-to-end encryption adds, and how to turn it on in the Web App and on the API.

Every request on Nito runs in privacy-preserving hardware, with attestation you can verify. End-to-end encryption adds encryption on your device.

## Side by Side

Nito never retains your conversations, on any route. Encryption adds another check on that promise: it makes it impossible for Nito to ever see the prompt or the response.

| | What it is | Protects against |
| :- | :- | :- |
| **Every request** | Runs inside privacy-preserving hardware, with attestation you can verify | The provider's operator, its host systems, or its cloud reading the request while the model runs |
| **With encryption on** | The same hardware, plus the prompt and response encrypted on your device on the way in and out | All of that, plus anyone between your device and the hardware reading the request, Nito included |

## Turning It On

* **Web App.** **End-to-end encryption** in Settings, under Privacy.
* **API.** Send a model's `:encrypted` ID with the [encryption headers](https://docs.trynito.ai/api/api-reference/chat-and-text/encrypted.md) and encrypt the messages on your client. See [Model ID Convention](https://docs.trynito.ai/models/model-id-convention.md).

## 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](https://docs.trynito.ai/privacy/tee-attestation/verify-yourself-recipe.md).

## What Changes With It On

* **Replies arrive whole in the Web App.** They are decrypted in your browser before they can be shown.
* **Web search and fetch cannot run inside the encrypted request.** In the Web App, Nito grounds the prompt with a browser-side step before encrypting, where the model supports it.
* **Fusion synthesis is an explicit step.** The model answers come first, then a **Synthesize answers** action. See [Fusion](https://docs.trynito.ai/web-app/fusion.md).
* **Fewer models.** The [Model List](https://docs.trynito.ai/models/all-models.md) shows which models support it.

## No Silent Downgrade

A call that asks for encryption and cannot be served that way fails with a clear message. When it succeeds, it ran encrypted.

## Related

> [card] [How Privacy Works](https://docs.trynito.ai/privacy/overview.md)
>
> The hardware every call runs in.

> [card] [Encrypted Inference](https://docs.trynito.ai/privacy/encrypted.md)
>
> How the encryption works, step by step.

> [card] [Model List](https://docs.trynito.ai/models/all-models.md)
>
> Which models support end-to-end encryption.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.