What we can't see.

The extension stores your installed tool packages, the revocation (safety) list, and the known-domains list in on-device browser storage (chrome.storage.local). It never uses chrome.storage.sync, so nothing leaves your device through Chrome sync.

Loading a page with the extension installed makes no network requests. Every URL is matched locally against that on-device storage.

The only contact with webmcp.today is:

• anonymous GET requests when you install a package, to download its definition from the registry, and
• periodic fetches of the global revocation list, known-domains list, and a small stable extension-release document. The release document contains release metadata, including the version, publication time, and GitHub links, and lets self-hosted unpacked installs show an optional manual-update notice.
• when you open or use popup suggestions, the active tab's origin and pathname only — never its query, fragment, credentials, or port.

Those requests carry no account or identifier. The extension has no analytics, telemetry, or error reporting. The one thing the requests can't hide is your IP address, which our hosting provider's servers see, as any web server does (see the processor list below).

When an AI agent runs an installed tool, its request is pinned to that package's declared API origin, using your existing session; it is not proxied through WebMCP Today. Tool descriptors, inputs, and outputs can pass locally through the extension, native bridge, and MCP client to your configured MCP or AI provider. That provider's policies govern that data; WebMCP Today's hosted servers do not receive it.

Sign-in is GitHub OAuth or email and password. The site stores the profile GitHub hands over (name, email, avatar), authentication data, and sessions, which may contain IP and user-agent information. The site uses session cookies; other cookies may be used where needed for the service. If you sign in with GitHub, GitHub handles that sign-in under its own privacy policy. The service isn't directed at children under 13, and GitHub sign-in requires you to be at least 13.

Publishing a package stores the package itself and its association with your account. Community-published packages are public and offered to everyone under CC0. See the terms for what that means. A local browser install does not create an account record. Separately, an account-side install records an install row, which is how the service stores signed-in account pins. API key usage and security records are also stored to operate and protect the service.

We store all of this to run the service for you, which is the legal basis for processing it. Account data is kept until you ask us to delete it.

The website also uses Vercel Web Analytics to understand aggregate website traffic. It is cookie-free and uses anonymized data. It applies to the website's deployed hosts, including Vercel Preview deployments. The extension does not use it or send analytics, telemetry, error reports, browsing history, page contents, or queries and fragments.

The service uses these processors:

• Vercel (hosting and website-only Web Analytics). Its servers log IP addresses, as any web server does.
• Neon (database).
• Sentry (error monitoring, web app only, not in the extension). It is configured not to collect user information, cookies, HTTP headers/bodies, URL query params, GraphQL, database, or AI input/output data, or stack-frame variables/context; reports can still include browser and the page that failed.

All three are US companies, so if you're in the EU or UK your data is processed in the US.

The extension sends us no browsing history, page contents, queries, or fragments. We do not sell or share your personal information. Vercel, Neon, and Sentry process website data as described above. GitHub handles GitHub sign-in under its own privacy policy. The extension sends data only as described in section 1.

You can ask to see, correct, export, or delete the data tied to your account by emailing the address below. During beta, requests are handled manually: we delete or anonymize account data no longer needed, while retaining published packages, submission and license records, safety records, and information required by law. Community-published packages are public under CC0 (see the terms).

If you're in the EU or UK, you also have the right to object to processing and to complain to your local data protection authority.

The date at the top is the version you're reading, and every edit is visible in the repository's public history. Material changes also get called out at the top of this page. If the extension's behavior ever changes in a way this page doesn't cover, this page changes first.

WebMCP Today is run by one person, the maintainer of the GitHub repository, not a company.

Email privacy@webmcp.today for anything about your data, or open an issue on the repository for anything that isn't personal.