nitz privacy policy

Last updated: August 27, 2026

nitz is a browser extension for leaving feedback on web pages and handing it to coding agents. This policy describes what the extension does with data.

What nitz stores

• The feedback you write ("nits"), together with the anchor of the element you attached it to: a CSS selector, the element's visible text (trimmed), its role and stable attributes, a short HTML snippet, and the page URL and title.
• Your settings, including dispatch targets you configure and the sites you opt in to.
• A cryptographic identity (an Ed25519 key pair) if you create one; the private key is a non-extractable WebCrypto key stored in the extension's own IndexedDB.

All of this lives in chrome.storage.local and IndexedDB on your device. nitz has no servers and sends nothing to the developer.

What nitz transmits

Only when you press "Dispatch", and only to endpoints you configured yourself:

• a Hobbsidian vault (the hub URL you entered), as an MCP vault_create call authenticated with a delegation credential your identity signs, or
• a webhook URL you entered.

The payload is the brief for the current page: your nits and their anchors, and, if signing is on, your signature and DID. Copying or downloading a brief never leaves the browser.

Team mode on Hobbsidian documents

A Hobbsidian hub page announces itself with a <meta name="nitz-hub"> tag. Only on such pages, and only on shared documents (/v/<token> and vault file pages), nitz talks to that hub:

• It fetches the document's existing nits and, on token shares, the names of people you may @mention.
• When you write, resolve, or delete a nit there, it sends that change to the hub: the nit text, severity, tags, mentions, the anchor, your DID, a signature over those fields, and a request proof addressed to the hub. The hub shows your nit to everyone who can see the document, as a guest (guest <short DID>) or under your account once linked.
• It refreshes when you open the page, when you return to the tab, and after each of your changes.

Linking ("Link to this hub" in the popup) stores a device credential the hub issues, per hub origin, in your settings; nitz sends it only to that hub, and "Unlink" (options page) deletes it. When you open the popup on a web page, nitz reads the page's nitz-hub meta tag to decide whether to offer linking; it reads nothing else and nothing leaves the browser. Pages without the tag never cause any network request.

Permissions

• storage: save nits and settings locally.
• activeTab and scripting: run the overlay on the page you are looking at, when you open nitz there.
• clipboardWrite: copy the brief.
• Optional host permissions, granted per site by you: let nitz run on load on that site so pins reappear without opening it again. You can remove a site from the options page or from chrome://extensions at any time.

No tracking

nitz contains no analytics, no telemetry, no remote code, and no advertising.

Contact

Contact support, or email dylan.hobbs@vouched.id directly.