Skip to content
Start here

POPULAR GUIDES

    FROM THE DOCUMENTATION

    Open this guide ↗
    ↑ ↓ select ↵ open esc closeV3Code Docs
    Nock · Privacy and controlnock

    Privacy and data

    ↗ View as Markdown

    Understand what stays on your computer, what is sent for hosted features, and the separate controls for sharing.

    Nock can recognize speech and synthesize spoken replies on your computer. In local-only dictation mode, speech audio stays on the computer and Polished cleanup is unavailable; choose Light or Off. Automatic recognition is local-first and may use cloud speech when eligible. Other features have separate online routes, so you can choose local voice processing without making all of Nock offline.

    Feature Local behavior When data leaves the computer
    Local dictation A local recognizer processes microphone audio. Recognition audio stays local. With Never send my voice off this computer enabled, Polished is blocked; choose Light or Off. When that switch is off, Polished can separately send recognized text for cleanup.
    Cloud dictation The app records and displays recognition status. Audio, language, and any vocabulary hints go to the configured speech route.
    Local spoken replies A local voice synthesizes the answer. Reply text is not sent to a speech service for local synthesis. The answer may have come from a hosted model.
    Cloud spoken replies The app plays returned speech. Reply text is sent to the configured voice route.
    Agent request Nock uses your selected context and local app controls. The prompt, conversation context, and selected attachments are sent to the configured model route.
    Screen-aware request Screen capture is used only by a screen action you invoke or enable. The selected image accompanies that request.
    Usage sharing Nock records limited feature and performance events. When Share usage data is on, events go to Nock’s account service. This switch is on by default.
    Help improve Nock A separate opt-in setting. When enabled, request and answer text may be shared after cleanup. It is off by default.
    Shared Discover posts and ideas Reading the curated feed is separate from sharing your likes. Sharing is off until you opt in. Yes on the sharing question submits that eligible post or idea and enables sharing of later eligible likes/saves. Shared items include short content and sources, not your chats or project files; personal work and conversation-saved ideas are excluded. See Ideas and Discover.
    Team conversations and files Nock keeps the conversation workspace on the computer that hosts it. Text and supported recorded clips you explicitly send use Team’s connection to the selected recipient. Files require an updated Nock inbox that advertises file support; standard outside-agent MCP tools do not attach files. Forwarding to a coding chat is a separate action; sharing that chat does not publish its existing transcript. See Team messaging and Team files.
    Nock Social A separate community website and login, not Nock’s local chat history. Posts, private messages, stories, and profile changes are sent to Social. AI-character chats also send conversation context to Social’s AI provider after the first-use disclosure. See Nock Social.

    Other connections may include sign-in, update checks, model downloads, billing/usage accounting, and external apps or providers used for a task. A task using a connected service sends the data needed for that service. Screen-aware actions can include a selected region or an image of the screen with the request; review the capture and privacy controls before using them with sensitive material.

    Your local Your words list can be sent as a spelling hint with cloud recognition. Phrase replacements are applied on-device after polishing. Treat the text in replacements as local settings data, and remember that a replacement’s expanded output may be sent later if you dictate it into a hosted model or service.

    Settings → Privacy → What leaves your computer summarizes routes and sharing controls associated with your current settings. Where your requests go is a general statement about Nock’s service, not a per-request destination history. The screen does not show the provider, model, or country used for each individual request. Do not use it as a log of which service handled a past request.

    Social audiences are separate from Nock privacy switches

    Section titled “Social audiences are separate from Nock privacy switches”

    Signing in to Nock does not sign you into Social, and Nock does not automatically transfer local chats or project files there. Reading or submitting content on Social follows that website’s own account, audience controls, and privacy policy. Nock’s local-only dictation switch and Share usage data setting do not make Social local or stop content you choose to submit there.

    On Social, Post privately hides the author’s name and avatar; it does not make a feed post a private message. Private messages are hosted on Social, not a local-only or end-to-end encrypted vault. Check the intended audience before posting. See Social friends and messages.

    Sign-in and account services, update checks, model downloads, optional usage events, and connected apps or providers may also use the network. Share usage data is on by default and can send limited app-use events even when dictation itself runs locally. Turn it off under Settings → General → Advanced to stop optional usage events; billing counts and requests needed for features remain separate.

    Before dictating or asking about sensitive material, check the recognition choice, polishing style, speech-output route, agent provider, screen actions, and data-sharing controls. Nock’s Settings → Privacy screen summarizes current settings and sharing controls; it does not replace the provider’s terms or describe every external service’s retention and processing.

    Local history is separate from cloud-service processing. You can choose how long Nock keeps voice history on this computer, delete individual entries, or delete all of that history in data and history. Do not interpret local deletion as deletion of data already sent to another service.