tab-mcp: privacy
What the relay at tab-mcp.ractive.ch and the
tab-mcp browser extension pass on, store and log. Both are run by
Jean-Pierre Bergamin, Zurich, Switzerland
(james@ractive.ch). The relay serves the
tab-mcp examples on this site, the
sign-in example and, unless you choose
another relay, the extension.
The relay
What passes through
While a page is connected, every request of the AI app and every answer of the page passes through the relay: the tool's name, its arguments and its result. The connections from your browser and from the AI app to the relay are encrypted, but the traffic passes through the relay itself in clear text, so that the relay can pass it on.
The relay does not store this content and does not write it to its logs.
What is stored
When you pair an AI app, the relay stores a grant:
- a random id for the page's connection address;
- the AI app's client id (a web address) and the name it gives itself;
- the permissions granted, when the grant was made, and when its tokens were issued or refreshed;
- SHA-256 hashes of the app's access and refresh tokens. A hash cannot be used as a token, so a copy of the stored data cannot connect anything.
- on the sign-in example only: a SHA-256 hash of your Google account's subject id (see signing in with Google).
No names, email addresses or tool contents are stored, and IP addresses only shortened, in the logs. A grant ends when you disconnect the app, on the page or in the extension's side panel, and 90 days after pairing at the latest. Access tokens last one hour.
Signing in with Google
On the sign-in example, an AI app is
paired by your Google account instead of a code. When the AI app connects, the
relay sends you to Google to sign in, with the scope openid only. So
Google's ID token gives the relay your account's subject id, not your name or email
address. The relay checks that it is the account signed in to the page and keeps
only a hash of it in the grant: the grant works for that account only. Google's
privacy policy applies to the
sign-in. Google processes it in the United States; Google LLC is
certified under the
Swiss-U.S. Data Privacy Framework, which Switzerland recognises as adequate.
Logs
The relay logs events such as "a page connected" or "a request took too long", with shortened ids. Logs never contain requests, answers, tokens or codes. IP addresses are shortened before they are logged (IPv4 cut to /24, IPv6 to /48), and only when a rate limit is hit. In memory only, your IP address (by network prefix) limits how many sessions, pairing attempts and token requests one network can make.
Where it runs
The relay runs on bunny.net (BunnyWay d.o.o., Slovenia) in Germany, behind bunny.net's CDN. Your connections end at a CDN server near you, which passes them on to the relay; like the relay, it handles the traffic in clear text. Some of these servers are in countries whose data protection Switzerland does not recognise as adequate, such as the United States; bunny.net's data processing agreement with standard contractual clauses covers that. Like any hosting provider, bunny.net processes connection data such as IP addresses to deliver the traffic. Its access logs for the relay keep no IP addresses. See bunny.net's privacy policy.
The browser extension
The tab-mcp browser extension (for Chrome, Edge and Firefox; called tab-mcp for Chrome up to 0.1.0) passes the WebMCP tools of the page in front to an AI app you connect, through a tab-mcp relay, and lets that AI app open pages in that tab.
What it reads
Only tabs you gave it, and only pages of http(s) sites (no file:
pages, no Incognito tabs or private windows): the tab where you clicked the extension's icon, until
that tab goes to another origin (example.com and www.example.com are two origins),
or every tab after you clicked "Give access to all sites".
From such a tab it reads the page's address (with its query and fragment, as the
browser shows it), title and language, and the tools the page registered with
WebMCP (document.modelContext): their names, titles, descriptions,
input schemas and annotations (such as read-only).
Apart from that, and what the page's tools return when the AI app calls them, it reads nothing of the page: no page text, no form fields, no cookies, no screenshots. It reads no browsing history, with one exception: when the AI app asks to go back or forward, it checks in the page whether the page before or after is on the same origin (and its address if so), and how long the tab's history is. That stays in the browser.
After you click "Give access to all sites", every https page (and localhost) can tell that it is
installed. Where the browser has no WebMCP of its own (Firefox, and Chrome or Edge
without their WebMCP flag or a site's origin trial), the extension then gives each
page document.modelContext as it starts loading, so that it can
register its tools; in Firefox, a tab you gave it by clicking its icon gets it
then. A page's script can see that the API is there and, from how it behaves, that
it is this extension's. It learns nothing else from it: not who you are, not the
relay, not the AI app.
What it stores
In the extension's own storage in your browser:
- the address of the relay you chose (by default
https://tab-mcp.ractive.ch); - whether AI access is on, and whether another tab or program took the connection's address over;
- a random secret from which the connection's address is derived;
- the tools you allowed to run without asking, per site: the site's origin and the tool names.
Nothing is synced to your browser account or kept outside the browser, and removing the extension deletes it all. The grants the relay holds for paired AI apps end when you disconnect an app, and 90 days after pairing at the latest (see what is stored).
What leaves the browser
Only while AI access is on, and only to the relay you chose:
- the connection to the relay and the pairing of an AI app (the relay stores a grant for each paired app, see what is stored);
- what the paired AI app asks for: the address, title and language of the tab in front, and the list of its WebMCP tools. The address goes with its query and fragment, so a link that carries a token in it is sent as it is;
- for each tool call: the tool's name, the AI app's arguments and the page's result;
- after the AI app opened a page in the tab, went back or forward, or reloaded it, or a page's tool took the tab to another page: the new page's address, title and language.
The AI app can open pages in the tab in front: open an address, go back or forward, and reload. A navigation on the page's own origin runs without a question, as a link on the page would. A tool that the page does not mark read-only runs only after you allowed it, in the side panel or a notification, or after you allowed that tool on that site. A navigation to another origin runs only after you allowed it, each time. The relay passes requests and results between the extension and the AI app. The AI app's own privacy policy applies to what it does with them. A relay you run or choose yourself has its operator's policy.
What it does not do
- No analytics, no tracking, no advertising, no crash reports.
- No data is sold or given to third parties, except the relay and the AI app you chose, and the relay's host (for the default relay bunny.net).
- No use of the data for anything but passing a page's tools to your AI app and opening pages in the tab for it, and none to determine creditworthiness or for lending.
- No remote code: all of the extension's code is in its package.
Your rights
You can ask what data about you is held, and have it corrected or deleted: write to james@ractive.ch. The answer is free and comes within 30 days. Disconnecting an AI app deletes its grant at once. If you think your data is processed wrongly, you can report it to the Swiss Federal Data Protection and Information Commissioner (FDPIC). Other questions: open an issue at github.com/ractive/tab-mcp.
Last changed: 15 November 2026.