Privacy

What jotkit stores, and where

Everything jotkit records is written to your own computer, by default under~/.jotkit. That includes:

• the text and tags of comments you write;
• the page context captured with a comment: the page URL and title, the selected element and its attributes, a summary of computed CSS, and framework component context when available;
• screenshots or screen recordings you choose to attach to a comment;
• the repositories you register, and the branch and commit a comment was made against;
• logs written by coding agents that act on your comments.

These files are yours. You can read them, back them up, or delete them at any time. Removing~/.jotkit removes everything jotkit has stored.

What is never sent anywhere

All of it. jotkit has no backend service. The extension makes network requests to exactly one destination, the local daemon on 127.0.0.1, and the daemon does not forward anything to the internet. There is no telemetry, no crash reporting, no usage analytics and no sync.

The one exception is entirely under your control: if you connect a third-party coding agent (for example Claude Code) to jotkit over MCP or ACP, that agent reads your comments in order to act on them, and that agent's own provider handles the data according to their policy. jotkit does not send anything to them itself, and no agent is connected unless you configure one.

Browser permissions, and why each is needed

• Host access to all sites - jotkit is for annotating whatever you are looking at, so its toolbar has to be able to run on any page. The toolbar stays hidden and jotkit reads no page data until you switch it on for that tab.
• scripting - used only to register the deep-context inspector, a script that reads framework component details (for example React component names) so an agent gets better context. It is registered only for localhost and127.0.0.1, so it never runs on a public website. It is not what draws the jotkit toolbar; that is an ordinary content script.
• tabs - to know which tab a comment belongs to, to send the toolbar its state, and to capture the right tab when you ask for a screenshot.
• storage - to remember your settings locally: the daemon port, your pairing token, your pin colour and recently used tags.
• tabCapture and offscreen - only used when you explicitly start a screenshot or a recording to attach to a comment. Capture never starts on its own. The offscreen document exists solely to encode a recording into a GIF, which cannot be done in the background worker. The result is written to your machine.

Children

jotkit is a developer tool and is not directed at children. It collects no personal information from anyone.

Changes

If this policy changes, the updated date above changes with it. Because jotkit collects nothing, any future change would be about clarifying behaviour rather than expanding data collection.

Contact

Questions about privacy in jotkit can go tobrennacodes@gmail.com.