Blacktea Browser Bridge

Local browser control

Your browser stays yours.

Blacktea Browser Bridge connects Chrome to Blacktea running on the same computer. It operates only the sites you approve, without taking over your desktop.

Loopback only Site-by-site access No advertising or analytics

At a glance

A narrow bridge with explicit boundaries

Local connection

Only loopback WebSocket addresses such as 127.0.0.1 and localhost are accepted.

Permission first

Website access is optional and requested one origin at a time from extension settings.

No desktop takeover

The extension cannot move the system pointer, type through the OS, or control other apps.

Information handling

Blacktea Browser Bridge has one purpose: connecting Chrome to a Blacktea process on the same device so Blacktea can inspect and operate web pages the user has explicitly approved.

Information the extension may handle

  • The address, title, and identifier of open Chrome tabs.
  • Text and structural information from an approved web page.
  • Form values used in a user-requested action. Password and credential-like fields are redacted from snapshots.
  • A screenshot of the tab already visible to the user when a screenshot is requested.
  • The local bridge address and pairing token stored in the current Chrome profile.

How information is used

Information is used only to perform browser actions requested through Blacktea, maintain and secure the local connection, and return action results to the user.

Sharing and transmission

The extension connects only to loopback addresses on the same computer. It does not send page data, browsing activity, or pairing credentials to a Blacktea cloud service, analytics provider, advertising service, or data broker.

If a user separately configures Blacktea to send selected page content to an AI provider, that transfer is performed by the local Blacktea application under its own disclosure and consent controls, not by this extension.

Storage and retention

The bridge address and pairing token are stored in chrome.storage.local for the current browser profile. Page content and screenshots are not retained by the extension after an action completes. Removing the extension or clearing its stored data removes the local configuration.

Chrome Web Store Limited Use

The use of information received from Chrome APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. Information is used only for the extension's user-facing single purpose and is never used for personalized advertising, creditworthiness, lending, or sale to third parties.

Controls that protect your session

01
Per-profile pairing

A local process must present the matching random pairing token before the extension accepts commands.

02
Optional site grants

The extension cannot read or modify a website before the user approves that origin.

03
Bundled code only

All executable extension code ships in the package. No remote code is downloaded or executed.

04
Non-disruptive automation

New tabs open in the background, tab-activation commands are rejected, and screenshots never switch tabs.

Support

Questions or privacy requests?

For help, security reports, data questions, or deletion requests, contact the Blacktea team.