DeepWork Chrome Bridge Privacy Policy

Data The Extension Handles

DeepWork Chrome Bridge can handle the following data when the user connects the extension to DeepWork and requests browser actions:

• Website content, such as page text, DOM state, visible screenshots, selected page content, images, links, and page structure needed for the requested task.
• Web history, such as tab URLs, page titles, tab state, and navigation state for tabs used by DeepWork browser tasks.
• User activity, such as user-requested clicks, typing, scrolling, screenshots, file-upload actions, and waits for page conditions.
• Local connection metadata, such as whether the extension is connected to the native host and metadata used to keep DeepWork-created tabs grouped by session.

The extension does not intentionally collect health information, financial and payment information, authentication information, location information, or personal communications as separate data categories. If a user directs DeepWork to automate a page that visibly contains sensitive information, that information may be present in the page content handled for that user-requested task. DeepWork Chrome Bridge uses redaction and session-boundary checks where available, but users should avoid directing browser automation at sensitive pages unless their organization policy allows it.

How Data Is Used

DeepWork Chrome Bridge uses handled data only to provide or improve its single purpose: local, user-approved browser automation for the DeepWork desktop app. For example, the extension may read page content so DeepWork can summarize what is visible, capture a screenshot requested by the user, click or type into a target tab, wait for text or a selector to appear, or report the current tab URL and title.

The extension does not use handled data for advertising, behavioral targeting, creditworthiness, lending, or unrelated analytics.

How Data Is Shared

DeepWork Chrome Bridge sends browser-task data to the locally installed DeepWork desktop app through the local Chrome native messaging host. The extension itself does not sell user data, show ads, or independently upload browsing data as a standalone cloud service.

Depending on the user's DeepWork configuration and the task the user requests, the DeepWork desktop app may send task context to user-configured model providers, organization-managed services, or remote agents. Those transfers are controlled by the DeepWork desktop app, the user's configured providers, and the user's organization policy.

DeepWork Chrome Bridge may also disclose data if required by law or to protect against security abuse, fraud, or malware.

Storage And Retention

DeepWork Chrome Bridge stores local connection and session metadata in Chrome extension storage so the bridge can reconnect and keep DeepWork-created tabs organized. The extension does not store long-term copies of page content or screenshots as a standalone service.

Users can remove locally stored extension data by disabling or uninstalling the extension in Chrome. Users can also clear DeepWork desktop app data according to the desktop app's own settings and organization policy.

Security

The extension communicates with the DeepWork desktop app through Chrome native messaging on the user's device. Browser-task data routed beyond the device is handled by the DeepWork desktop app and the user's configured providers.

The extension package runs JavaScript included in the submitted Chrome Web Store bundle. It does not load remotely hosted JavaScript for extension logic.

Chrome Web Store Limited Use Statement

DeepWork Chrome Bridge's use of user data complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.

Changes To This Policy

Braincrew may update this policy as the extension, DeepWork desktop app, or legal requirements change. Updates will be published with a revised effective date.

Contact

For privacy questions about DeepWork Chrome Bridge, contact dev@brain-crew.com.