Skip to main content
Two things decide how private a call is: what your harness provider sees, and what the model provider keeps.

​
What Your Harness Provider Sees

Claude Code and Codex normally send your conversation to their own model provider. The command you use decides whether a Nito exchange goes with it.
  • ask runs inside your harness conversation, so the prompt and the response travel upstream with the rest of it.
  • private does not. The prompt and the response stay out of what your harness sends.
  • session runs an entire session away from your harness’s provider, keeping history on your machine so you can return to it. private with no prompt does the same and keeps nothing.
What Each Command Protects goes command by command.

​
What the Model Provider Keeps

The model that answers carries a privacy level, and you get that level by choosing that model. Each rung keeps everything below it and adds one thing. Because the level is a property of the model, it cannot drift. Full detail: The Four Levels.

​
Proof You Can Check

Private holds the provider to zero data retention. Confidential adds evidence on top: the sealed environment produces a signed attestation you can verify yourself, so you have proof of what ran as well as the retention guarantee.

​
What Nito Keeps

Operational metadata about a call, never its contents. Prompts, responses, reasoning, tool payloads, and attachment contents are used to serve the request and are not stored. That holds at every level. Data Retention and Visibility covers exactly what is kept and who can see what.