privacy
Privacy policy
Last updated: 21 June 2026
This policy covers the brw Chrome extension and the brw daemon (brwd). The short version: brw is a local tool. It collects no personal data, runs no analytics or telemetry, has no servers of its own, and nothing the extension sees leaves your machine.
What brw does not collect
- No personal data, accounts, analytics, telemetry, advertising identifiers, or usage tracking.
- No cookies, passwords, passkeys, autofill, or Chrome profile files are read, exported, or transmitted.
- No data is sold or shared with third parties. There is no third party — brw has no backend.
How the extension works
The extension connects only to a brw daemon running locally on your own computer over ws://127.0.0.1 / ws://localhost. It uses Chrome's debugger protocol to drive visible tabs on your instruction and report back what happened. All activity stays between Chrome and the local daemon on the same machine (or, for remote setups you configure yourself, over your own SSH connection). brw operates a normal, visible browser — it adds no stealth, CAPTCHA bypass, MFA bypass, or cookie extraction.
Permissions, and why
debugger— drive tabs via the Chrome DevTools Protocol (open, read, click, type), the core of browser control.tabs/activeTab/tabGroups— see and organise the tabs brw is acting on.notifications— alert you at human-handoff points (MFA, CAPTCHA, purchase confirmation) and on completion or error.webNavigation,alarms,storage,offscreen— track navigation, keep the local connection alive, and store local connection settings. None of this leaves your device.- Host access is restricted to
127.0.0.1andlocalhost— the local daemon only.
Open source
brw is open source under AGPL-3.0. You can read exactly what the extension and daemon do, including this behaviour, on GitHub.
Contact
Questions about privacy? Open an issue on the brw repository or reach Revitt.