Privacy in the App

Two separate things protect a conversation. The privacy level is how a request reaches the model. An Incognito chat is whether the conversation is saved in your browser.

​

Privacy Levels

The picker shows each model’s level on its row. All four are available in the Browser App. Pick a model once and its level applies to every message in the chat. Full definitions and what each level protects: Privacy Levels and How Privacy Works. Nito stores nothing you send or receive, at any level. The Receipt on each reply records the level that ran.

​

Incognito Chats

An Incognito chat is never saved. Refreshing or closing the tab erases it. It stays out of history, search, Knowledge, and sharing, and sits in the Incognito (not saved) slot in the rail while open. Start one from + New, or make it the default with Start new chats as incognito in Settings. An Incognito chat can run at any privacy level.

​

Where Your Data Lives

• Chat history, folders, and Workbench items are encrypted in your browser with a key that stays in this browser. Nothing is stored on Nito’s side.
• Encrypted backups (Plus and up) and Live sync (Advanced and up) move that data between devices as ciphertext protected by your passphrase. See Backups and Sync.
• Browser memory, when on, stores facts from your chats, encrypted on this device. See Memory.
• Attestation evidence on Confidential and Encrypted replies is kept inside the encrypted chat record so you can export it later.
• Purge chat data in Settings under Storage removes local chats, folders, and Workbench data. Signing out does not.

​

Protected History

A chat remembers the strongest level it has used. Once it holds Confidential turns, Anonymous and Private rows read Incompatible; once it holds Encrypted turns, only Encrypted rows stay selectable. Start a new chat for a weaker route. The same rule applies to Fusion drafts and the summary model.

​

Encrypted in the App

• Replies arrive whole rather than streaming; they are decrypted in your browser first.
• Attachments are parsed in the browser. Auto parser mode is hidden, and Server warns that the server sees the file before encryption.
• Raw image uploads are not sent on Encrypted routes yet.
• Web Search and Web Fetch run through a browser-side helper before the request is encrypted. See Web Search and Tools.
• Fusion synthesis is an explicit step you trigger. See Fusion.

​

Next