Data and history

Nock keeps several kinds of local information: conversations, settings, dictation activity, saved previews, and feature-specific data. These have different controls. Removing one conversation is not a universal erase operation for every kind of data.

Chat retention

Open Settings → Agent → Keep chats for. The available choices are 30 days, 90 days, 1 year, and Forever; the default is 90 days.

Retention uses the newest message in a conversation. A chat started months ago but used recently is treated according to that recent message. When a chat reaches the selected age, its stored messages and cards are removed together.

Shortening the period can delete conversations immediately if they already exceed the new limit. Review what you want to keep before changing it. Choosing Forever prevents age-based removal going forward; it cannot restore conversations already deleted.

Delete one conversation

The chats panel provides a right-click delete action for an individual chat. Use it only when you intend to remove that conversation and its cards. Deleted chats cannot be recovered through the history panel.

Starting a new chat is different from deleting the old one. Likewise, the idle setting that starts a fresh chat does not itself define how long older conversations are retained.

History and memory are separate

Deleting a conversation does not change information the agent saved to long-term memory. Do not use chat deletion as proof that the agent has forgotten a fact. Review the appropriate memory workflow when the goal is to change retained knowledge.

Saved previews, boards, reminders, and app connections are also separate from chat history. Their own controls determine whether they remain. For example, removing a locally built item from My Apps is different from disconnecting an external service.

Insights and usage data

Insights calculates activity statistics from the local session log. Hosted allowance meters answer a different question: how much account usage is available. These displays should not be expected to match one-for-one.

Settings → General → Share usage data controls optional app-usage and setup events. It is on by default in the launch candidate. Turning it off stops new optional events and clears pending event queues. It also requests withdrawal from setup-tip emails. If the service cannot be reached, that withdrawal waits for a later retry; use an email’s unsubscribe link if you need to act from the email service directly.

Those usage events are designed around limited feature names, durations, counts, and error labels. Signed-in events can be associated with your account; do not assume they are anonymous. This switch does not turn hosted model, speech, billing, or connected-app requests into local operations.

Sharing diagnostic material

Check logs and screenshots before sending them to support. Remove conversation text, private paths, account tokens, and unrelated information. Local storage does not mean content can never leave: context needed for a hosted task is sent to the relevant service. Read Privacy and data and Support.