daniel156161
809c73c3a3
- Drop the ServiceLink submodule, link-serve command, and serve --rpc mode. - Remove the now-unused httpx dependency and regenerate uv.lock. - Add a privacy policy for Chrome Web Store publication. - Refresh extension icons and bump package/extension version to 0.14.2. - Keep the native TCP serve path as the only remote-control endpoint.
1.6 KiB
Privacy Policy for browser-cli
Last updated: 2026-06-14
browser-cli does not collect, transmit, sell, or share user data with the developer or any third party.
browser-cli is a local browser automation tool. The browser extension communicates with the locally installed browser-cli native messaging host so the user can control their own browser through the command line or Python SDK.
Local data access
Depending on the command explicitly run by the user, browser-cli may locally access browser data such as:
- tab URLs, titles, status, and window or tab group information
- page content, links, images, HTML, text, screenshots, or DOM data
- cookies, local storage, session storage, and saved browser-cli session data
This access happens only to perform the command requested by the user. The data stays on the user's device unless the user explicitly configures browser-cli to connect to another machine they control.
Remote control mode
browser-cli includes an optional remote control mode. If the user enables this mode, command data may be transmitted between the user's configured browser-cli client and server endpoints. This is user-configured infrastructure. The developer does not receive or operate these endpoints.
No analytics or tracking
browser-cli does not use analytics, telemetry, advertising, behavioral tracking, or remote code. The extension does not send data to the developer.
Contact
For privacy questions or security reports, please open an issue in the project repository or contact the project maintainer through the repository hosting platform.