AutomateBrowserPrivacy Policy
For the AutomateBrowser browser extension for Chrome and Edge.
Last updated 21 September 2026
The short version. The extension does not collect anything, does not send anything to us, and has no analytics, no tracking and no third-party services of any kind.
It passes what you ask it to pass — page content, screenshots, cookies — over a connection to software running on your own computer. Nothing is transmitted anywhere else unless you deliberately point it at another machine, which is a setting you have to type in yourself.
What this extension is
AutomateBrowser lets an AI assistant in your code editor operate the browser you already use — your tabs, your existing sign-ins. The extension is one half of that. It listens on a local connection and carries out instructions from the AutomateBrowser server running on the same computer.
That means the extension is, by design, capable of reading anything you can read in your browser. This page sets out exactly what that covers, and where it goes.
What the extension can access
These are the permissions it requests and why each one exists.
| Access | Why |
|---|---|
| All websites | An assistant can be asked to work on any page, so the extension cannot know in advance which sites it will need. It acts only on a tab when instructed. |
| Tabs | To list your open tabs, switch between them, and open or close one on request. |
| Page scripting | To click, type, read text and fill forms — the actual automation. |
| Cookies | So an assistant can read or set a cookie when a task requires it. |
| Network activity | To report which requests a page made — addresses, methods and status codes. Request and response bodies are not collected. |
| Downloads | To report where a downloaded file was saved. This is the only way a browser can tell you the final path. |
| Request blocking | To enforce a site block list you have configured, at the network level rather than by trusting the tool to behave. |
| Proxy | Only used if an assistant is explicitly asked to set one. A proxy applies to your whole browser profile, not one tab — it affects your own browsing too. |
| Debugger | Off by default. A small number of advanced features need it, and turning it on shows the browser's own "started debugging" banner so you always know. |
| Storage & alarms | To remember a few local settings, and to reconnect after the browser puts the extension to sleep. |
What leaves your browser, and where it goes
When an assistant asks for something, the extension sends the answer over a connection to
127.0.0.1 — your own computer, a connection that cannot be reached from the internet.
Depending on what was asked, that can include page text, a screenshot, form values, cookies, or a
list of network requests.
It goes to the AutomateBrowser server on your machine, and from there to whichever AI assistant you connected. We do not operate that assistant and we never receive any of it. What your assistant does with what it is shown is governed by whoever provides it.
The one exception, and it is yours to switch on
The extension can be pointed at a different computer, so an editor on another machine can drive this browser. That is a setting you type into the extension's popup yourself; it is empty by default, and it is refused unless you also set a shared secret. If you do use it, everything described above travels to that machine instead. Nothing enables this on your behalf.
What is stored, and where
Three things, all kept in your browser's own local extension storage on your device. Nothing is stored anywhere else:
- An optional label you can set to tell one browser from another.
- An optional shared secret, if you have set one.
- An optional address of another machine, if you have set one.
Page content and screenshots are passed straight through. The extension does not keep a copy, and there is no history or log of your browsing inside it.
What we never do
- No analytics, telemetry or usage statistics — of any kind.
- No advertising, and no profiling.
- No selling or sharing of data, because none is collected.
- No remote code. The extension runs only the code it was reviewed and installed with.
- No account, and no sign-up.
Staying in control
- Stop it instantly by disabling or removing the extension in
chrome://extensions(oredge://extensions). It can do nothing while disabled. - It only acts when driven. With no assistant connected, it sits idle.
- Removing it deletes the local settings listed above with it.
- You can see who is connected at any time from the extension's popup, which lists every connected assistant and the tab it is working in.
Children
This is a developer tool. It is not directed at children and is not designed for anyone under 13.
Changes to this policy
If it changes, the date at the top changes with it, and the previous wording remains in the project's public history.
Contact
Questions, or something here that does not match what you observe? Please open an issue at github.com/farazpawle/automatebrowser/issues. If you believe you have found a security problem, please say so in the report and avoid including anything sensitive.