Who this applies to
This policy covers the OpenCode Browser Annotation Chrome extension (the “Extension”).
The Extension is the browser half of an open-source developer tool; it pairs with the
opencode-browser-annotation-plugin that runs locally on your own machine or server.
What the Extension does
When you invoke it (via Alt+A, Alt+Shift+A, or the toolbar button), you can select an
element on the current page and type an instruction. The Extension gathers structured metadata about that
element — such as its tag, id, data-testid, ARIA role, CSS classes, visible text, DOM ancestors, and
(where available) its UI-framework component path — and sends it, together with your typed instruction, to
your own locally-running OpenCode agent.
Data we collect
None. The developer does not collect, receive, store, sell, or transmit any user data. There are no analytics, no telemetry, no advertising identifiers, and no third-party services.
Where your data goes
- Annotation data (your instruction text and the selected element's metadata) is sent
only to the endpoint you configure, which defaults to your own local OpenCode server at
http://127.0.0.1:39517. - When your OpenCode agent runs on a remote server, that traffic travels through an SSH tunnel you set up yourself. The Extension never opens a public connection and never contacts the developer.
- No screenshots are sent. A small element thumbnail may be rendered locally inside the sidebar for your reference only; it is stripped from the payload before submission and never leaves your browser.
- Values that look sensitive (for example CSRF tokens, passwords, and auth fields) are redacted from captured markup before anything is sent.
Local storage
The Extension stores exactly one setting locally in your browser using chrome.storage: the OpenCode
endpoint URL. This never leaves your device except as the destination you yourself configured.
Permissions and why they are used
- activeTab — to run the annotation overlay on the tab you are currently viewing, only when you invoke the Extension.
- scripting — to inject the element-picker and sidebar UI into the current tab on demand.
- storage — to remember your endpoint URL setting.
- Host access to
127.0.0.1/localhost— to deliver annotations to your own local OpenCode plugin. No remote hosts are contacted.
Remote code
All code is bundled in the Extension package. No remote or dynamically-evaluated code is loaded or executed.
Children
This is a developer tool and is not directed to children under 13.
Changes to this policy
If this policy changes, the updated version will be posted at this URL with a new “Last updated” date.
Contact
Questions or requests can be raised on the project's issue tracker: github.com/caoool/opencode-browser-annotation-plugin/issues.