Privacy Policy

Overview

DOMShell does not collect, transmit, or store any personal data. The extension operates entirely within your local browser environment. No analytics, no tracking, no telemetry.

Local Processing

All data processing happens locally in your browser. DOMShell reads the browser's Accessibility Tree and maps it into a virtual filesystem representation. This data never leaves your machine. No information is sent to external servers, cloud services, or third parties.

Permissions Explained

DOMShell requests the following Chrome permissions, each for a specific technical purpose:

• debugger — Required to access the Chrome DevTools Protocol (CDP), which provides the Accessibility Tree data that DOMShell maps into the filesystem. This is the core mechanism that enables all shell commands.
• activeTab — Required to interact with the currently active tab when you invoke DOMShell commands.
• Host permissions (all_urls) — Required so DOMShell can operate on any website you navigate to. Without this, the filesystem would only work on specific pre-approved domains.
• sidePanel — Required to render the terminal interface in Chrome's Side Panel.
• storage — Used to persist your local settings, command history, and bookmarks. This data is stored locally in Chrome's extension storage and is never transmitted externally.

Network Communication

DOMShell's MCP server communicates exclusively over localhost (127.0.0.1, port 3001). This local-only WebSocket connection enables AI agents running on your machine to interact with the browser. No data is sent to any external network endpoint.

Third-Party Services

DOMShell does not integrate with any third-party analytics, advertising, or tracking services. There are no cookies set by the extension, no usage metrics collected, and no crash reports transmitted.

Contact

If you have questions about this privacy policy or DOMShell's data practices, please open an issue on GitHub.