Updated: October 9, 2026
Dialbot MCP is a Chrome extension and a local MCP bridge for Windows. This policy describes the information the software may handle and who can receive it.
In short: Dialbot sends no page data to the developer and operates no remote data service. The extension and bridge process requests locally. However, the MCP client or AI provider chosen by the user may receive page content, and a website may receive information when the user submits a form or selects a file. Therefore, not every workflow is end-to-end local.
When the user or their MCP client invokes a tool, Dialbot transiently processes the target tab's URL and title, visible text, links, screenshots or text supplied for an action. This is user-directed processing of website content, not background collection. Dialbot does not query Chrome's saved browsing-history database, build user profiles or maintain separate datasets about health, finances, authentication, personal communications or location. These kinds of information could appear in a page a user chooses; if so, they are processed as website content for that requested action.
The file-selection tools receive local paths and make Chrome select the indicated files. Dialbot does not read or transmit the file bytes through the MCP server, though the website may upload a selected file after Chrome hands it to the page.
The local bridge uses a credential generated on the machine to authenticate inter-process communication. The paste feature may temporarily place the requested text on the Windows clipboard.
Tool requests and results pass from the extension through Chrome Native Messaging to the companion local bridge, and then over stdio to the MCP client configured by the user. The extension's Content Security Policy blocks its own network connections. Dialbot has no developer-operated server, analytics or telemetry and does not send page data to the developer.
The configured MCP client may send the page content, screenshots, text or tool results to the AI provider selected by the user. That processing is governed by the client's and provider's own policies, not by Dialbot. Review their privacy settings before using Dialbot with sensitive information. For end-to-end local processing, use a local MCP client and local AI model.
Browser actions still take place on the website. Submitting a form or selecting a file may send information from Chrome to that site; the site controls that transfer. Dialbot does not upload files to its own service. Check the site and the file before selecting or submitting.
The bridge credential and installation configuration are stored locally in the project's `.local` directory and are not included in the public repository. Chrome local storage remembers the extension's connection preference. Page content, screenshots and tool results are processed transiently by the local extension/bridge and are not retained by Dialbot after the operation. Dialbot does not keep a browsing history, user profile or content database. The user controls actions through their MCP client and can disconnect the extension, close the client or uninstall the software.
Dialbot MCP limits its access, use and transfer of user data to providing its disclosed browser-control features when requested by the user. The extension sends tool inputs and results to the user's local bridge and configured MCP client; it has no developer-operated data service. The developer does not access or sell page data, use it for advertising, or use it for creditworthiness or lending. The user's MCP client or AI provider may process data under its own privacy terms.
These informational pages are hosted on GitHub Pages; the host may process HTTP requests according to the GitHub Privacy Statement. The use of Chrome, the MCP client, the AI provider and the visited sites is subject to their respective providers' policies.
For questions or privacy requests, email support@r2100.com or open an issue on GitHub. Do not post personal data, screenshots, credentials or sensitive information in public issues.