Privacy policy
Effective 23 October 2026 · applies to the BrowserZap Chrome extension, the BrowserZap bridge and MCP server, and BrowserZap Pro.
The short version
- BrowserZap has no server. The extension and the bridge run on your computer and talk to each other over
127.0.0.1only. We do not receive your data, because nothing is sent to us. - No telemetry, no analytics, no advertising, no tracking. The extension makes no network requests of its own, and its pages load no remote scripts, styles or fonts.
- We do not sell or share data, and we do not use it for anything other than doing what you or your agent asked, on your computer.
- Your AI client is separate. When your agent reads a page through BrowserZap, that content goes to the agent you chose, and from there possibly to its model provider, under their privacy terms.
What BrowserZap handles, locally
To act on the tab your agent works in, BrowserZap reads what it needs from that page: element roles, accessible names, labels and bounded visible text, so it can find the right control and confirm the action worked. It does this only in the tab the agent session is acting on, at the moment it acts. There is no content script in the pages you browse.
- It never returns the contents of form fields to the agent, only whether a field is filled.
- It never types into password, one-time-code, card or government-ID fields; those steps are handed to you.
- Screenshots are taken only when your agent asks for one.
What is stored on your computer
In BrowserZap's own folder (%LOCALAPPDATA%\BrowserZap on Windows, ~/.config/BrowserZap elsewhere), readable only by your user account:
| What | Holds | Never holds |
|---|---|---|
| Pairing token | A random token that lets the extension and the bridge recognise each other | Anything else |
| Saved workflows | Steps you chose to save: tool names, element names, URLs, and {{placeholders}} for what you type | Typed values (unless you explicitly keep them as defaults), passwords, cookies, page content |
| Session log (14 days) | Each tool call: what it acted on (by name), the outcome, timing, page origin and path | Typed values, URL query strings, page text |
| Run and batch reports (Pro) | Each run's steps, outcomes and timings; for a failed step its error and likely cause | Parameter values and typed values |
| Screenshots (7 days, at most 200) | Images your agent asked for | They are never uploaded by BrowserZap |
| Pro licence | Plan, licence id and expiry, checked offline | Your name, email or payment details |
The extension keeps its settings (pairing token, port, the name you gave this Chrome profile) in Chrome's local extension storage.
Permissions, in plain language
- debugger: drive the tab your agent works in the way Chrome's DevTools does (read the page, send clicks and keys), inside your existing logged-in session. Chrome shows its "started debugging this browser" bar while this is active; BrowserZap never hides it.
- All sites (
<all_urls>): your agent may work on any site you choose. You can limit an agent to specific sites withBROWSERZAP_ALLOWED_ORIGINS. - scripting, tabs, tab groups: find and act on the right element, and keep the agent's tabs grouped and labelled.
- side panel, notifications, storage, alarms: the approval and status panel, approval prompts, local settings, and keeping the connection to the local bridge alive.
BrowserZap Pro
A Pro licence is a signed token checked on your computer. Activating or checking it sends nothing anywhere. If you buy Pro, the payment provider (named at checkout) processes your payment under its own privacy policy; we receive the order details we need to issue and support your licence.
This website
browserzap.com sets no cookies and runs no analytics or advertising scripts. It is served through Cloudflare, which processes standard request data (such as IP addresses) to deliver and protect the site, under Cloudflare's privacy policy. If you email us, we use your email only to reply.
Deleting your data
There is nothing to delete on our side. To remove everything locally: remove the extension in chrome://extensions, then delete BrowserZap's folder named above.
Children
BrowserZap is a developer tool and is not directed at children under 13.
Changes and contact
If this policy changes, the new version will be posted here with a new effective date. Questions: [email protected].