How Privacy Works

Three parties handle every call: you (your browser, your harness, or your application), Nito, and the provider running the model. The surface you use decides who is in the path on your side. The model’s privacy level decides what the provider can see and keep.

On Your Side

Nito Browser App. Your browser, Nito, and the provider. Chat history is encrypted in your browser. An Incognito chat is never saved.
Nito Plugin. The command decides what your harness sees: ask runs inside the harness conversation, private keeps the prompt and the response out of what the harness sends, and a session runs away from the harness’s provider entirely. See What Each Command Protects.
Nito API. Your application, Nito, and the provider.

Web search and web fetch, when on, add a search provider to the path for that request. See Data Retention and Visibility.

The Four Levels

Every model carries a privacy level. Each level builds on the last.

Level	Description (each level builds on the last)
Anonymous	Frontier models, with no identity attached to the request.
Private	Open-weight models with zero data retention upstream.
Confidential	Runs inside sealed hardware, with attestation you can verify on every request.
Encrypted	Runs inside the same sealed hardware as Confidential, with prompt and response encrypted on your device on the way in and out. Browser App and API today, coming soon to the Plugin.

At Encrypted, the prompt is unreadable to everything between your device and that hardware, Nito included. It is Nito’s end-to-end encrypted inference and has its own section. The level is part of the model ID, so what you asked for is what runs, or the call fails. See Privacy Levels.

What Each Level Protects

	Anonymous	Private	Confidential	Encrypted
Your identity	Detached from the request	Detached	Detached	Detached
Retention by the provider	Under the provider’s terms	Required to keep nothing	Sealed hardware, so the operator cannot read it	Sealed hardware, so the operator cannot read it
The provider’s operator during the call	Serves the request	Serves the request	Kept out by sealed hardware	Kept out by sealed hardware
Nito	Relays the request, stores nothing	Relays it, stores nothing	Relays it, stores nothing	Relays ciphertext it cannot read

“The provider’s operator” is the company running the model: its staff, its host systems, and its cloud. The model reads the prompt to answer it at every level. At Confidential and Encrypted it does so inside the sealed hardware.

Evidence You Can Check

At Confidential and Encrypted, the sealed hardware produces signed attestation evidence. Before every Confidential call, Nito fetches it, checks that it is bound to the provider and model that will run the call, and refuses the call without it. An Encrypted call starts from that same fetch on your side, because the key your device encrypts with comes from the evidence. Nito hands the evidence to you and does not verify the hardware signatures itself. See How Attestation Works.

Nito Stores Nothing

Prompts, responses, reasoning, tool payloads, and attachment contents are used to serve the request and are never stored, at every level and on every surface.

Privacy Levels

What each level protects against, and where each is available.

What's a TEE

Sealed hardware and attestation, from the start.

Data Retention and Visibility

What Nito keeps, what the provider keeps, who sees what.

​On Your Side

​The Four Levels

​What Each Level Protects

​Evidence You Can Check

​Nito Stores Nothing

​Related