Privacy policy

Last updated: October 29, 2026

This policy covers the WebMCP Toolbench Chrome extension ("Toolbench") and this website. Toolbench is published by Shubham Patel. Questions: support@solvemybizz.org.

In short

We run no servers for Toolbench and receive none of your data. There is no account, no analytics, no tracking and no advertising.
Toolbench reads a page only while its side panel is open on that tab.
What it keeps stays in your browser profile.
It sends data only when you use an AI feature, and only to the AI provider you choose. That provider's own privacy policy then applies.

What Toolbench reads from pages

When you open the panel on a tab, Toolbench reads from that page and its frames:

the WebMCP tools the page registers (names, descriptions, input schemas, annotations);
for forms that are tools, their fields, labels and choices, but not what you typed into them;
the results of tools you or the agent run;
the page's address, title and icon (the icon comes from Chrome's own cache).

It does not read pages where the panel isn't open, and nothing is injected into pages by itself. You can limit the sites it may run on in Chrome's settings for the extension.

What Toolbench keeps, on your computer only

Data	Where and for how long
Settings and tool overrides	Chrome's extension storage, until you change or clear them.
AI provider API keys	In memory (Chrome's session storage) until the browser closes. If you choose "Remember", in Chrome's local extension storage, unencrypted in your browser profile, until you remove the key.
Conversations, tool runs, logs and model calls	The browser's IndexedDB, when "Keep history" is on (the default). Bounded: the last 2,000 log entries and 50 model calls. A tab's conversation and runs are deleted when the tab closes and when the browser restarts.
Addresses Toolbench contacted	Host names and counts, shown in Settings → Network.

Settings → Data → Clear all data deletes all of it. Uninstalling the extension deletes all of it too. Logs, model calls and session bundles have API keys and other secrets removed.

What Toolbench sends, and to whom

Inspecting and running tools by hand sends nothing anywhere. Data leaves your browser only in these cases, all of which you start:

The agent and the provider checks. Toolbench sends your messages, a system prompt with the page's address (origin) and title, the page's tool definitions, and the results of the tools it runs, together with your API key, to the AI provider you selected. That can be OpenAI, Anthropic, Google (Gemini), OpenRouter, Groq, a server on your own computer (Ollama, LM Studio), or a server address you enter. Requests go only to the provider you selected and to providers you saved a key for.
Voice (off by default). While voice is on, your microphone audio, the conversation and the tool definitions go to Google's Gemini Live API with your Gemini key. The microphone is used only while voice is on.
Chrome built-in AI. This model runs on your device. Chrome downloads it from Google when you ask it to. Your conversation does not leave your computer.
Files you export (tools, logs, session bundles, evals) are saved where you choose. Toolbench does not upload them.

What a provider does with the data is governed by your agreement with that provider. We have no access to it.

What we don't do

We don't sell or transfer your data to anyone, or use it for advertising or credit decisions.
We don't collect your browsing history; Toolbench reads only the tab you inspect.
No person reads your data, because none of it reaches us.

The use of information received through Toolbench complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.

This website

This website uses no cookies, analytics or third-party scripts. It is hosted on Google's Firebase Hosting, which processes standard request data (such as IP addresses) to serve it.

Children

Toolbench is a developer tool and is not directed at children.

Changes

If this policy changes, the new version will be posted here with a new date.