Chrome extension privacy

Chrome Bridge Privacy Policy

Effective 2 November 2026. This is the privacy policy for the Open Desktop Agent Chrome Bridge extension (Chrome Web Store item id iinbjhdeegmfgepencebhmffcppjdjpi) and its native messaging host. It supplements the full Open Desktop Agent privacy policy.

Summary Data handled Where data goes Not collected Permissions Retention Security Contact

Summary

The extension reads and controls only tabs in the visible blue Agent tabs group that you approve.
Page data goes only to the local Open Desktop Agent app on your computer over Chrome native messaging. The extension has no network endpoints, no analytics and no remote code.
It does not read passwords, autofill data, cookies, downloads outside the group, or browsing history outside the group.
Uninstalling the extension deletes its local storage; revoking pairing stops control immediately.

Data the extension handles

For tabs in the Agent tabs group, while a task is running, the extension handles:

Data	Purpose
Tab URLs and titles	To show the group, enforce the approved site and record the action in the app’s local audit log.
Page content: accessibility tree, DOM structure, visible text, element attributes and screenshots	To let the agent understand and act on the page you asked it to use.
Actions performed: clicks, typing, scrolling, hover, key presses, option selection, navigation, dialogs and uploads	To carry out the task and show status/approval information.
A random profile id and local UI state	To distinguish Chrome profiles for pairing and remember the popup state.
Pairing state and pending approval metadata	To pair with the app and show pending approvals in the popup.

Where data goes

The extension sends page data and action results only to the local Open Desktop Agent app through a Chrome native messaging host. The host connects to the app over a local Unix domain socket that is protected by a per-start token. The extension does not make HTTP requests and has no server component.

If you run a task that uses Chrome, the local app may include the page data in the context it sends to the model provider you configured. That transfer is made by the app under the full privacy policy, not by the extension. Choose trusted providers and avoid sensitive pages unless you are comfortable with that provider processing them.

What the extension does not collect

Passwords or password-field values, payment card values or authentication cookies.
Chrome autofill data or saved credentials.
Browsing history, open tabs or page content outside the Agent tabs group.
Downloads outside the Agent tabs group. Downloads started by an Agent tab are observed for the app’s local download list.
Keystrokes or mouse activity outside the actions the agent performs in Agent tabs.
Analytics, advertising identifiers, telemetry or crash reports sent to us.

Permissions and why they are needed

Permission	Use
`debugger`	Attach the Chrome DevTools Protocol to Agent tabs only, for DOM, accessibility, input and screenshots.
`tabs`	List, create, activate and close Agent tabs, and read their title/URL for the app and audit log.
`tabGroups`	Create and maintain the Agent tabs group so you can see and pause what the agent controls.
`storage`	Keep the random profile id, pending approval state and local UI state.
`nativeMessaging`	Talk to the local Open Desktop Agent native host.
`alarms`	Wake the Manifest V3 service worker to reconnect after Chrome or the app sleeps.

There are no host permissions, content scripts, web_accessible_resources or remote scripts. The extension does not request access to all websites.

Retention

The extension stores a random profile id, the last pairing display state and local UI state in chrome.storage. Pending approvals are kept in session storage and expire after about 120 seconds.
Page content and screenshots are not written to the app’s audit log; the app records action metadata.
Removing the extension deletes its local storage. Data the app already stored is controlled by the app and can be deleted with the data-deletion steps.

Security

The extension id is pinned by a fixed manifest key, and the native host allowlists that exact origin.
The app’s main process re-checks Agent-tabs group membership before every DevTools command.
The native host requires a per-start socket token and rejects other origins.
Dangerous DevTools methods (crash, close, request interception, script injection on new documents) are denied.
Chrome shows its standard debugging infobar while attached; Pause detaches the debugger immediately.

Report a vulnerability privately through the security page. Do not include credentials or personal data in a public issue.

Contact

Privacy questions: open a non-sensitive issue at github.com/beniaminp/desktop-agent/issues or contact the maintainer through github.com/beniaminp. For security reports, use the security process. The full product policy is at /privacy/.