Effective date: February 21, 2026
Summary: SuperSurf does not collect, transmit, or store any personal data. All communication stays on your local machine. There is no telemetry, no analytics, and no remote servers.
SuperSurf is a browser automation extension that connects your Chrome browser to a locally-running MCP (Model Context Protocol) server. It enables AI coding assistants to interact with web pages for development and testing purposes.
SuperSurf collects no data. Specifically:
SuperSurf communicates exclusively over a localhost WebSocket connection (ws://127.0.0.1) to an MCP server running on your own machine. No data ever leaves your computer through the extension.
127.0.0.1 (loopback only)SuperSurf uses Chrome's built-in storage APIs for operational state only:
chrome.storage.local — Stores extension preferences (enabled/disabled state, debug mode flag, WebSocket port, domain whitelist cache)chrome.storage.session — Stores ephemeral automation state (which tab is being controlled, cursor positions) that is automatically cleared when the browser closesNo personal data, credentials, or browsing content is stored.
SuperSurf requests browser permissions necessary for automation functionality. Each permission is used strictly for its documented purpose:
SuperSurf includes a secure credential fill feature. When used, credential values are resolved from local environment variables on your machine by the MCP server process. The AI agent never sees the raw credential values. Credentials are typed character-by-character into form fields and are not stored or logged by the extension.
SuperSurf does not integrate with any third-party services, advertising networks, or data brokers. The optional domain whitelist feature fetches the Tranco top-sites list from a public URL for safety enforcement, but no user data is sent in this request.
SuperSurf is open source. The complete source code is available for inspection at github.com/liquidbuiltit/supersurf.
If this privacy policy changes, the updated version will be published alongside the extension update. Material changes will be noted in the extension's changelog.
For questions about this privacy policy, open an issue on the GitHub repository.