opencode-chromium

Privacy Policy

Effective date: October 1, 2026

This privacy policy applies to the opencode-chromium extension for Chromium-based browsers (Chrome, Edge, Brave), published by Quindart.

In short

opencode-chromium is a local browser-automation bridge. It lets an AI coding assistant (OpenCode, Codex, MCP clients) drive the browser on your own machine. Cloud decision assistance is off by default. The extension communicates with a local native host. If you explicitly enable a decision provider, the native host sends bounded search/replay intent and candidate descriptions to the service you selected. Page text may contain personal information.

What the extension does

• The extension receives tool calls from a locally running native messaging host (com.opencode.browser.plugin) and executes them in your copy of the browser.
• It can create and control tabs, read pages, download files, run searches against your browsing history, and deliver click, type, scroll, drag, and screenshot automation on your behalf.
• It keeps a small, user-visible “profile label” (for example work or staging) in chrome.storage.local so you can choose which open browser profile a tool call should use. You can clear it at any time from the extension popup.

Content boundaries

• Local extension communication. The extension talks to a native messaging host installed on your computer over the browser’s native messaging channel. The native host calls TypeSafe or OpenRouter only after you enable a provider with the disclosed context sharing. Requests never silently switch providers. No data is sent to Quindart.
• Local models, local data. Optional semantic page search downloads a model bundle (a standard Hugging Face transformer) to a local cache directory you can inspect and delete from the extension popup. Local semantic inference happens in the native host. Model downloads contact the model distributor.
• No accounts, no telemetry. The extension has no accounts, does not use analytics, and does not phone home. Provider accounts and their data-handling policies apply separately when you enable cloud assistance. Keys can be supplied in Settings or the native host environment. Saved keys stay in private native-host state (DPAPI encrypted on Windows; owner-only files on macOS/Linux), never extension storage or agent responses. Local usage records retain timings and reported tokens/cost, without browsing context. Connection tests send synthetic data only.
• No device identification. The plugin, extension, and native host never read machine IDs, hostnames, usernames, MAC addresses, hardware serials, or install IDs, and never compute device fingerprints. The only persistent identifier is a random per-profile UUID generated locally for routing requests to the browser profile you selected; it never leaves your device. The extension popup shows this identifier masked by default (first and last four characters only); the full value is revealed or copied only through an explicit “Developer details” action. Cache locations are shown as “Local model cache”; the raw path is only ever copied on explicit request, never rendered. Behavioral privacy tests verify these guarantees, and store-listing images are generated from deterministic demo fixtures rather than live popups.

Action Memory

The opt-in Action Memory feature (off by default) stores a structured, vector-searchable record of agent browser actions in a local SQLite database. By design it contains no personal content: no URLs, window titles, typed text, form values, keystrokes, clipboard contents, screenshots, file paths, or accessibility trees — only action names, hostnames, bounded element labels (≤ 64 characters, passed through a privacy normalizer that strips email addresses, UUIDs, long account-like numbers, URL query strings, tokens, and filesystem paths), outcomes, and timestamps. Steps that need a value or URL at replay time are stored as flags only; the value always comes from the live agent request and is never persisted. Search queries are embedded for the lookup and never stored; searchable chain text is generated purely from the privacy-safe structured fields. There is no encryption because there is nothing personal to protect: the record is a what/where/result log, not a transcript. Delete (memory delete --yes) permanently removes the database. Confirmed actions are never auto-purged; stale failed lessons are cleaned up automatically per the quota and purge settings shown in the Action Memory dashboard (extension popup → Action Memory).

Permissions and why they exist

The extension requests the permissions it needs to operate as a general-purpose automation bridge:

• tabs, tabGroups, history, downloads, storage: read and manage the parts of the browser you explicitly ask an agent to work with.
• scripting, <all_urls>, debugger: inspect page structure, run input automation, and capture what the agent needs to see. Pages are only touched when a tool call from a session you started asks for it.
• nativeMessaging, alarms: communicate with the locally installed native host and keep the service worker responsive during active sessions.

You grant or deny these permissions at load time, and you can remove the extension at any time.

Children

This extension is not directed to children, and it does not collect information from anyone.

Changes

If this policy changes, the updated version will be published at this URL and the extension’s store listing will note the change before it takes effect.

Contact

Questions about this policy?

Email: contact@quindart.com
Website: quindart.com
Publisher: Quindart — 2/F, Tower 1, Tern Centre, 237 Queen’s Road Central, Sheung Wan, Hong Kong

This site is open source. Improve this page.