Skip to main content
Short answers on what is private and what is not. The full treatment is in the Privacy section.

​
Does using the plugin send my prompt to my harness’s model provider?

It depends on the command. A plain ask runs inside your harness conversation, so your harness can see that prompt. private is the command built to keep a turn out of your harness’s upstream entirely. See Ask and Private.

​
What does Private actually guarantee?

A private turn is not sent to your harness’s own model provider. What it does not do is turn off local disk writes or act as a sandbox by itself. The Private page spells out exactly what is and is not covered.

​
What are the privacy levels?

Anonymous, Private, Confidential, and Encrypted. The level follows the model you choose and never silently downgrades. Three of them work in this release; Encrypted is coming soon to the plugin. See Privacy Levels at a Glance and The Four Levels.

​
Does Nito see my prompt at Confidential?

The prompt passes through Nito in transit and is never stored. Confidential keeps the provider’s operator out while the model runs. Encrypted, coming soon to the plugin, keeps Nito out too. See How Privacy Works.

​
Can I verify the privacy claim myself?

Yes, for Confidential. Nito fetches attestation evidence before every Confidential call and fails closed without it. The plugin does not show the evidence yet. Fetch it with your own challenge from the API, or see it on the Attestation Report in the Browser App, and verify it with the hardware maker’s tooling. See Verify It Yourself.

​
Does Nito store my prompts?

No. Prompts, completions, reasoning, tool payloads, and attachment contents are used to serve the request and are not stored. What the model provider keeps is a separate question: at Private and above the provider is held to zero data retention, and at Anonymous it handles the request under its own terms with your identity detached. See Data Retention and Visibility.