Skip to content

Privacy policy

Your browsing goes to your agent, and nowhere else

The extension and the app behind it have no server, no account and no analytics. What they read on a page goes to the AI agent you chose, and from there to that agent’s model provider. This website is the one exception: it uses Google Analytics, described below.

Updated 29 September 2026

The short version

Three things that are true by construction

Nothing reaches us

There is no Browsentic server to send anything to. The extension, the daemon and the desktop apps carry no analytics and no telemetry, and there is no account.

Your agent sees the task

What a task needs from a page goes to the agent CLI you picked, and that CLI sends it to its model provider, under your account and their policy.

Secrets stay in the browser

Passwords, keys, tokens and cookies are swapped for a sealed placeholder before a result leaves the browser. The model never sees the real value.

What the extension reads

When you give the agent a task, the extension reads what that task needs from the tabs involved: the page’s structure and text, screenshots, form fields, the files you attach, and the pages the agent opens on the way.

Between tasks it reads nothing and sends nothing, except what you set running yourself: a recording you started, a monitor or timer you asked for, a scheduled task, or a saved tool you set to run on every visit.

Where it goes

The extension talks to one thing: the Browsentic daemon on your own computer, over a connection to 127.0.0.1 that only a browser you paired with a one-time code can use. It makes no other network request.

The daemon hands the task to the agent CLI you chose, such as Claude Code or Codex, running on your computer. That CLI sends it to its model provider, for example Anthropic or OpenAI, under your account with them and their privacy policy. Browsentic does not pick the provider, cannot see your account, and keeps no copy anywhere else.

If you drive the browser from an MCP client instead, the same holds for that client and its provider.

Passwords and other secrets

Passwords, keys, tokens and cookies that a page holds are replaced by a sealed placeholder before a result leaves the browser, so neither the daemon nor the model ever holds the real value. The value itself stays in the browser’s session storage, which the browser empties when it restarts, and is typed into a field only when the agent hands the placeholder back there.

Your profile

If you fill in the Profile on the settings page, the details and standing instructions you save there are kept in ~/.browsentic/profile.json and shared with the browsers you paired. They are added to the agent’s instructions for every side-panel task, so they reach your model provider with each task. Save only what you are happy for your agent to see.

Voice

Dictation and hands-free mode use your browser’s own speech recognition. In Chrome, that service can send your audio to Google to turn it into text, under Google’s privacy policy. Browsentic only ever receives the text.

What stays on your computer

  • In your browser, in the extension’s own storage: conversations, recordings, saved tools, attached files and settings.
  • In ~/.browsentic: the daemon’s settings, pairing, your Profile, schedules, site maps and the daemon’s log.
  • In ~/browsentic: files you asked to keep, such as saved screenshots.
  • In your agent CLI’s own folder: its history of each run, kept under its own terms.

Removing the extension deletes what it stored in the browser, and browsentic uninstall removes the daemon and its folders.

The only other connections

  • The browsentic command asks registry.npmjs.org whether a newer version exists when you run setup or update.
  • The Mac and Windows apps ask GitHub for new releases, and download Node.js from nodejs.org if your computer does not have it.
  • Firefox checks the GitHub release for a newer version of the add-on, and a copy installed from the Chrome Web Store updates through Google.

These requests carry nothing about you or your browsing. Like any download, they show that service your IP address.

This website

browsentic.com is a static site hosted on Vercel. It uses Google Analytics 4 to see which pages help people and where they get stuck. It records:

  • The pages you view, and the page or site that sent you
  • Your approximate location, worked out from your IP address, which Google Analytics does not store
  • Your device, browser and screen size
  • What you do on a page: copying an install command, starting or finishing a demo film, opening an answer, following a link to GitHub or to a download, and how far down a page you read

Google Analytics sets _ga cookies, which last up to two years. Google Signals and ad personalisation are switched off, so none of this is used for advertising. Vercel Web Analytics also counts page views, without cookies. Fonts and videos are served from this domain.

To opt out, block Google Analytics with any content blocker or with Google’s opt-out add-on. The site works exactly the same without it.

Selling, sharing, and changes

The software sends us nothing, so there is nothing of yours to sell or share. The website’s analytics are used only to make the site better, and are never sold or used for advertising.

Browsentic is open source, so every statement here can be checked against the code. When the software changes what it does with data, this page changes with it and the date at the top moves. Questions go to the issue tracker on GitHub.

Give your browser a superpower.

Free and open source. No API key, no subscription, no account. A fresh install connects to nothing until you pair it yourself.

npx browsentic setup