Privacy Policy
Last updated 4 September 2026
The short version. ChromeBoost has no servers of its own and collects nothing about your browsing. The free extension and MCP server talk only to your own computer. The paid desktop app adds exactly three outside connections, and each one is named below: Anthropic, because the app runs on your own Claude subscription; Polar, which handles payment and licence keys; and GitHub, which hosts the update check. We never see your prompts, the pages you automate, or the files you produce.
The one thing to understand before you start is in section 4: page content you ask ChromeBoost to read is sent to the AI you are using, under that provider's terms and privacy policy, not ours. Treat it the way you would treat pasting a page into a chat window.
1. Who this covers
This policy is published by Beaverhand Inc. ("we"). It covers four things:
- The ChromeBoost Chrome extension, distributed through the Chrome Web Store and through GitHub. Free and MIT licensed.
- The ChromeBoost MCP server, installed as a Claude Code, Codex or Gemini CLI plugin. Free and MIT licensed.
- The ChromeBoost Desktop app for Mac and Windows. A paid product with a free tier.
- The chromeboost.work website, which is the page you are reading.
The extension and MCP server are open source. If any statement here about them does not match the code, the code is the truth and the difference is a bug worth reporting. The desktop app's source is not public, so for the desktop app this policy is the description you can hold us to.
Contents
- Who this covers
- The extension and MCP server
- The desktop app
- Where page content actually goes
- Extension permissions
- What is never done
- The website
- Retention and deletion
- Your rights
- Children
- Changes
- Contact
2. The extension and MCP server
Nothing is collected by us. Neither the extension nor the MCP server has a backend, a logging service, a crash reporter, or analytics. There is no network destination of ours that data could be collected at.
The extension opens a single outbound connection, and it is a local one:
| Destination | What travels over it |
|---|---|
| ws://localhost:PORT | The MCP server on your own machine. Commands from your AI agent travel in, and the results of those commands travel back. This connection never leaves your computer. |
The extension keeps a small amount of state in chrome.storage.local. It stays
in your browser profile and is never transmitted: the position, collapsed state and
visibility of the on-page status panel; which local agent sessions are connected and on
which ports; and a short random prefix used to tag elements during a page operation. No
browsing history, bookmarks, form data or credentials are stored by the extension.
3. The desktop app
The desktop app wraps the same extension and MCP server in a window so you can give instructions in plain English without a terminal. It runs on your own Claude subscription and adds a paid licence. Here is everything it stores and every outside connection it makes.
3.1 What stays on your computer
| What | Where |
|---|---|
| Your jobs: the instructions you typed, the assistant's replies, and a record of each browser step | The app's data folder: ~/Library/Application
Support/ChromeBoost on Mac, %APPDATA%\ChromeBoost on Windows |
| Settings, repeat schedules, your licence key and activation id, and the count of finished jobs this month | The same data folder |
| A short diagnostic log of what the app did: its version, when Chrome linked, when jobs started and ended, update checks, and any errors. It never contains page content or your instructions | The same data folder, logs/ |
| Crash reports, if the app ever crashes. They stay on your computer and are never uploaded; they exist so you can send one to us if you choose to | The same data
folder, Crashpad/ |
| Claude's own sign-in state, kept by Anthropic's software in a folder the app reserves for it, and in your operating system's keychain | The same data folder,
engine/, plus the system keychain |
| Files you attach to a job, and files a job produces for you | ChromeBoost Files in your home folder |
| A copy of the browser extension, when you install it from the app rather than the Chrome Web Store | ChromeBoost Extension in your home folder |
None of this is uploaded to us. We have no way to read it.
3.2 The three outside connections
| Who | When | What is sent |
|---|---|---|
| Anthropic (Claude) | When you sign in, and during every job | Sign-in happens in your own browser on Anthropic's site. The one-time code you paste into the app is passed straight through to Anthropic's own command-line software; the app does not read, parse or store it. During a job, your instructions, the page content the assistant asks to read, and its replies travel between Anthropic's software on your computer and Anthropic's servers, under your own Claude account. See section 4. |
| Polar (payments and licences) | When you buy, when you enter a licence key, and periodically afterwards | Buying happens on Polar's checkout page in your browser; Polar is the merchant of record and handles your payment details, receipts and tax. We never see your card number. When you enter a licence key, the app sends Polar the key, our organisation id, and your computer's name (so you can tell your own machines apart in Polar's portal), and receives an activation id. Afterwards the app re-checks the key and activation id with Polar from time to time; if you are offline it keeps working for 14 days without a check. |
| GitHub (update check) | At launch and about every six hours while the app is open | A plain request for a small text file that names the newest version. GitHub sees your IP address and a standard browser-style request, as any web host does. No account, identifier or usage data is included. Downloads of new versions come from the same place. |
That is the complete list. The app has no telemetry, no analytics, no crash reporting to us, and no account with us. Usage limits on the free tier are counted on your computer and never reported anywhere.
3.3 What we receive, and from whom
The only information we hold about desktop app customers comes from Polar: the email address you gave at checkout, what you bought, when, the licence keys issued to you, and the names of the computers you activated them on. We use it to run your subscription, answer support requests, and meet tax and accounting obligations. We do not receive anything about how you use the app.
4. Where page content actually goes
Read this part. ChromeBoost is the hands, not the brain. When you ask for a page to be read, a form filled or a button found, the relevant page content is handed to the AI assistant you are using. In the desktop app that is Claude, running on your own Anthropic account. With the plugin it may be Claude Code, Codex or Gemini CLI. Those tools send what they receive to their provider's servers in order to think about it.
So while ChromeBoost itself sends nothing to us, the practical result of using it is that pages you point it at can reach Anthropic, OpenAI or Google, governed by their privacy policies and your agreement with them, not this one.
Two things we do to keep this deliberate:
- Content is read only when a step asks for it. ChromeBoost does not watch, scrape or index pages in the background, and it does not read tabs you have not directed it at.
- Before page text is returned, it passes through a redaction step that strips high confidence secret patterns such as API keys and tokens, so credentials sitting on a dashboard are less likely to reach the assistant by accident. This is a safety net, not a guarantee. Do not rely on it to protect something that genuinely matters.
The desktop app also pauses and asks you before actions that publish, pay or sign in, unless you switch that off in Settings. That is a design choice for your benefit, not a promise about what any site will do with the result.
5. Extension permissions, and why each one exists
Chrome shows a blunt warning at install time. Here is the specific reason for each permission the extension requests:
| Permission | Why it is needed |
|---|---|
| debugger | The core of the product. Clicks, drags and keystrokes are dispatched through the Chrome DevTools Protocol so they arrive as real, trusted input events. Ordinary synthetic events are silently ignored by many modern web apps. |
| <all_urls> | You decide which sites to automate, so the extension cannot know the list in advance. It acts only on the tab you direct it to. |
| tabs | Listing, opening, switching and closing tabs on request. |
| activeTab | Reading and screenshotting the tab currently being worked on. |
| scripting | Injecting the content script that performs DOM work such as hit testing, form filling and shadow DOM traversal. |
| offscreen | Holding the WebSocket connection open. An MV3 service worker is shut down when idle, which would drop the connection. |
| storage | Remembering the status panel position and which local sessions are connected. |
| windows | Focusing and arranging browser windows during multi-tab work. |
| downloads | Saving a file when you explicitly ask for a download, and reading back files the assistant was told to fetch. |
6. What is never done
- Your data is never sold, rented or licensed to anyone. There is no commercial data relationship of any kind.
- Your data is never used for advertising, profiling, training AI models by us, or any purpose unrelated to the feature you invoked.
- No part of ChromeBoost transmits your browsing, your jobs or your files to us, and nothing we operate could receive them.
- We never ask for, see or store your Claude password or session token. Sign-in is Anthropic's, on Anthropic's site, and stays with Anthropic's software.
7. The website
The site is static and hosted on Vercel. Three things about it differ from the software, and it would be misleading not to say so:
- Google Analytics runs on the landing page. It records ordinary aggregate visit data such as page views, referrer, approximate region and browser. It is not present in the extension or the desktop app and has no visibility into anything you automate. You can block it with any content blocker without affecting the software.
- Vercel, as the host, keeps standard server logs including IP addresses, as any web host does.
- The buy buttons link to Polar's checkout. Payments are handled entirely by Polar under their own privacy policy, and no payment details reach this site or us.
8. Retention and deletion
- On your computer. Jobs, settings and files stay until you delete them.
Deleting a job in the app removes its transcript and its attachments. Uninstalling the app
does not remove the data folder,
ChromeBoost FilesorChromeBoost Extension; delete them yourself if you want a clean slate. The Claude sign-in state inengine/and the keychain belongs to Anthropic's software; signing out through the app removes what it can. - At Polar. Purchase and licence records are kept by Polar for as long as its own policy and tax law require. You can see and manage them in Polar's customer portal, which the app links to from Settings.
- At Anthropic, OpenAI or Google. Whatever those providers keep of the content your assistant sent them is governed by their policies. We cannot delete it for you.
- With us. Support emails are kept for as long as needed to resolve the request and for a reasonable period afterwards.
9. Your rights
Depending on where you live, you may have rights to access, correct, delete or export personal data about you, to object to or restrict its processing, and to complain to a data protection authority. Because we hold so little, exercising them is simple:
- For purchase and licence records, use Polar's customer portal or contact us and we will work with Polar on your behalf.
- For anything else, email us at the address in section 12. We will respond within 30 days.
- Everything on your computer is already in your hands: the data folder and
ChromeBoost Filesare plain files you can read, copy or delete.
Our lawful basis for the little processing we do is performance of the contract with you (running your subscription and support) and our legitimate interest in keeping the website working and understanding aggregate traffic. We do not make automated decisions about you. Polar and Vercel may process data outside your country under their own safeguards.
10. Children
ChromeBoost is not directed at children. The extension and MCP server are developer tools for people 13 and over. The desktop app is a paid product for people 18 and over, or the age of majority where you live if that is higher. We do not knowingly collect information from children; if you believe a child has given us any, contact us and we will delete it.
11. Changes to this policy
If this policy changes in a way that affects how data is handled, the date at the top will change and the revision will be visible in the public commit history of this file. If a change materially reduces your privacy, the desktop app will also tell you in its update notice before the new version applies.
12. Contact
Privacy questions, corrections, or requests about your data: me@lordamdal.com. For the open source parts you can also open an issue at github.com/lordamdal/chromeboost/issues. For suspected security issues, see SECURITY.md.