Privacy and data

Nock combines local desktop features with account-enabled cloud services. The data involved depends on the feature you use. On-device dictation and hosted agent work have different boundaries.

When you use…	On your Mac	Sent to a service when needed
On-device recognition, when supported and selected	Speech processing and transcript	Do not assume an unsupported recognizer stays offline.
Hosted recognition or spoken replies	Recording or reply text before upload	Audio for recognition, or reply text for speech synthesis.
Agent chat	Local conversations and selected context	Your request and context included in that turn.
Circle-and-ask or an attached screen region	The capture you select	The image sent with the request to the configured model.
Project work	Local index, file edits, and commands	Relevant code and results needed by the model or connected agent.
Connected apps	Connection controls in Nock	Data read or written through the app provider when a permitted task uses it.

The exact model and speech services depend on your selected provider, build, and account settings. Review those settings before using Nock with confidential material.

Where hosted model requests go

The current included DeepSeek route sends model requests through V3Code’s account relay to DeepSeek’s API. Prompts and any context attached to a request can reach that provider; do not treat the account relay as a US-only model host. If you choose another supported model or connect your own provider account, the destination and applicable provider policy change with that choice. Models and providers explains how to inspect the available settings.

V3Code plans to move the included DeepSeek model routes to US-hosted providers when paid Nock plans launch. That change has not been verified as live. Until this page is updated with a confirmed destination, assume the current DeepSeek route can send request content to DeepSeek’s API.

On-device and hosted features

The Apple speech fallback prefers on-device recognition when the selected recognizer supports it. The current implementation does not require an on-device recognizer when that support is absent, so do not treat the fallback as an unconditional offline guarantee. Hosted transcription sends audio to a speech service. Spoken replies use a text-to-speech service. Agent requests can send your prompt and the context needed for the task to the configured model service.

Do not assume that all Nock activity stays on the computer because one dictation mode works on device. Check the active mode and provider before sharing sensitive material.

Context and permissions

The desktop app can require operating-system permissions for features such as microphone capture or interacting with other apps. Grant the permissions needed for the workflow you intend to use and review them in your system settings.

Consider what is visible or selected before asking for help with on-screen or project content. Keep unrelated private material out of the context you provide.

When you use a screen-aware action such as circling an area or attaching a region, Nock captures that visual context on demand and sends the image to the model handling the request. A capture can include private material visible in or near the selected area. See Circle it and ask. This page does not promise automatic redaction of sensitive content.

Connected services

Connecting an app authorizes access through that provider. Review the requested permissions and use the intended personal or work account. Connected tools can read or change service data when execution is available and permitted.

You can disconnect through Nock and review the integration in the provider’s own security settings. Disconnecting does not reverse earlier actions or delete data already created in that service.

Account and usage information

The account service tracks access and hosted usage so it can apply plan limits. Product-email consent is a separate choice. This page describes feature boundaries; it does not establish a blanket retention period or promise that third-party providers retain no data.

For policies that apply to your account, consult the current V3Code privacy policy and relevant provider policies. See App connections for connection controls.