Privacy Policy
Workser AI Agent Bridge — Chrome Extension
Last Updated: February 19, 2026
Localhost Only
All data stays on your machine. The extension communicates only with the locally-running Workser Desktop app.
No External Servers
Zero data is transmitted to cloud services or third parties. Everything happens on localhost.
Minimal Storage
Only stores a WebSocket port number and a temporary session token. No browsing data is persisted.
Overview
The Workser AI Agent Bridge (“the Extension”) is a Chrome browser extension developed by Workser AI. It serves as a communication bridge between the Workser Desktop AI Agent application and the Google Chrome browser, enabling users to automate browser tasks through their locally-installed desktop agent.
Single Purpose
The Extension has a single purpose: to bridge the locally-running Workser Desktop AI Agent application to Google Chrome, enabling the desktop agent to control browser tabs, interact with web page elements, and perform browser automation tasks on behalf of the user.
Data Collection and Usage
Data the Extension Accesses
The Extension accesses the following data solely to fulfill its browser automation purpose:
- Tab Information: Reads titles and URLs of open browser tabs to provide the Workser Desktop AI Agent with a list of available tabs for navigation and management.
- Web Page Content (DOM Snapshots): Captures an accessibility-tree representation of web page content, including visible text, interactive element roles, and page structure.
- Cookies: Reads cookies for the active page or a specified URL when requested by the desktop agent, to understand authentication state during automation tasks.
- Screenshots: Captures visible tab screenshots when requested by the desktop agent, to provide visual context for automation tasks.
Data the Extension Stores
The Extension stores only two pieces of data locally on the user's device:
- WebSocket port number: The user's preferred port for connecting to the Workser Desktop app (stored in
chrome.storage.local). - Session authentication token: A temporary token used to authenticate the WebSocket connection (stored in
chrome.storage.session, cleared when the browser session ends).
How Data is Transmitted
All data accessed by the Extension is transmitted exclusively to the locally-running Workser Desktop AI Agent via WebSocket connection on localhost (default port 9333) and HTTP request to localhost (port 9334) for authentication token retrieval. The Extension does not transmit any data to external servers, cloud services, or third parties.
Data Not Collected
The Extension does not collect, store, or transmit:
Third-Party Data Sharing
The Extension does not sell, transfer, or share any user data with third parties for any purpose. All data remains on the user's local device and is only communicated between the Extension and the locally-running Workser Desktop application.
Data Retention
- Tab information and DOM snapshots are transient — captured on demand, sent to the local desktop agent, and not persisted by the Extension.
- WebSocket port preference is stored until the user changes it or uninstalls the Extension.
- Session authentication token is automatically cleared when the browser session ends.
- Cookies accessed are read-only and not stored by the Extension.
Permissions
The Extension requests the following permissions, each used solely for browser automation:
| Permission | Purpose |
|---|---|
tabs | List, create, switch, close, and navigate browser tabs |
scripting | Inject content scripts for DOM snapshots and element interactions |
activeTab | Identify the currently active tab for targeting automation commands |
cookies | Read cookies to understand page authentication state |
storage | Store WebSocket port preference and session authentication token |
alarms | Keep the service worker alive to maintain the WebSocket connection |
debugger | Execute trusted browser-level input events (clicks, keystrokes) via Chrome DevTools Protocol |
notifications | Display connection status notifications to the user |
downloads | Manage file downloads during automation tasks |
nativeMessaging | Alternative communication channel with the desktop agent |
tabGroups | Organize tabs into groups during automation workflows |
<all_urls> | Operate on any web page the user directs the agent to interact with |
Security
- The Extension communicates exclusively over localhost connections, ensuring no data leaves the user's machine.
- WebSocket connections are authenticated using a token-based handshake to prevent unauthorized local applications from sending commands.
- The Chrome DevTools Protocol debugger is attached only momentarily for each input action and immediately detached after execution.
User Control
- Users can disconnect the Extension from the desktop agent at any time via the popup interface.
- Users can uninstall the Extension at any time, which removes all stored data.
- The Extension only performs actions when explicitly commanded by the user through the Workser Desktop AI Agent — it does not act autonomously.
Children's Privacy
The Extension is not directed at children under the age of 13 and does not knowingly collect any data from children.
Changes to This Policy
We may update this privacy policy from time to time. Changes will be reflected by updating the “Last Updated” date at the top of this document. Continued use of the Extension after changes constitutes acceptance of the updated policy.
Contact
If you have questions about this privacy policy or the Extension's data practices, please contact us:
- Email: [email protected]