Data handling & privacy

Developer workspace data

Project profiles retain names, allowed origins, read/write choices and excluded domains locally until removed. Profiles restrict browser operations, not companion files, desktop access or already dispatched jobs. Incremental context keeps page baselines in extension-worker memory for up to two minutes, bounded to 16 entries and 1 MiB, with current access checks.

Bug capture starts only after consent and records new top-frame console errors and failed request metadata for up to five minutes, bounded to 100 errors and 100 requests. It does not retain cookies, headers or request/response bodies. Common secrets and URL queries/fragments are filtered, but arbitrary sensitive text may remain; screenshots contain unredacted pixels. Review before exporting. Drafts are removed by Discard or when the worker stops, not merely when invalidated. Downloaded JSON remains until deleted. Nothing is automatically shared or sent to an AI.

Up to 24 WebMCP scenarios retain owner-entered schemas, inputs and assertions locally. Do not enter secrets. Up to 32 run summaries retain outcomes, not raw tool output. Deleting a scenario does not delete older summaries. Each execution needs explicit short-lived approval; uncertain mutations are not retried. The connection checklist does not verify an AI account or make a model request.

What ToolBraid processes

ToolBraid connects an MCP-compatible AI client to browser pages using a Windows companion. It can process the URL, title, visible text, links, forms, field values, accessibility information and media on pages to which the extension has access. Depending on the pages you permit, this content can include personal information, private communications, location, health or financial information.

Requested visual features can process screenshots, images, video frames and audio from the selected page. The form extractor omits password and recognized payment-field values; this does not guarantee that sensitive information elsewhere in page text or captured media is removed.

Browser tools can manage tabs, navigate pages, fill or submit forms, inspect downloads and attach a user-selected file. The companion also provides desktop accessibility controls and bounded file operations. File and folder grants use local selectors and opaque handles; granting access permits the corresponding tool to process that content.

Where the data goes

The browser-to-companion connection uses native messaging. The companion-to-client connection uses an authenticated local named pipe. The distributed runtime does not include a ToolBraid analytics or advertising endpoint.

Tool results and requested page content are returned to the MCP client you configure. If that client uses a cloud AI provider, that provider may receive this data under its own terms and privacy policy. Local transport is not a promise that all AI processing is local.

The built-in ChatGPT chat is optional. Using only an external local-model client does not require signing in to ChatGPT. Local inference can stay on your machine, but the chosen client's other integrations, logging and cloud settings are separate; review them before sharing private pages. See the three connection routes.

An optional OpenAI-compatible multimodal endpoint can be configured in the extension. When enabled, captured media and analysis requests are sent to that endpoint. The endpoint and model configuration are stored locally; an entered API key is stored in browser session storage, not in the persistent settings record. Browser session storage is not an encrypted password vault.

Page actions may run site JavaScript. Sensitive-control preflight checks are not a sandbox for site event handlers or network requests. Enable mutation access only on sites you trust.

Normal browser requests to the websites you visit still occur. Submitted forms, uploads and other actions send data to those websites as part of the requested action.

Limited use

ToolBraid uses the data it handles to provide the browser, media and local workflow features the user enables. The distributed software contains no mechanism for selling page data, advertising profiles or publisher-side model training, and no publisher endpoint that receives page contents. Transfers to the user's selected MCP client, AI endpoint or target website are made to carry out those features.

Data sent to a separately configured AI provider is also subject to that provider's policy. Feedback is handled separately through the support form described below; never send credentials or private page contents in a support request.

Storage, retention and removal

The extension stores local preferences, approval and audit records, workflow state and explicitly saved semantic memory. Live page bindings, nonces and captured-media handles are transient. The companion stores authentication configuration and local job, schedule, workflow or media-job records in its installation data directories. Retention is feature-dependent; this release does not promise automatic deletion after a fixed number of days.

Removing the extension through the browser removes its browser-local storage. The companion uninstaller removes program files and registrations but deliberately preserves settings, authentication configuration, backups and local data. Remove the retained installation data separately if you no longer need it. Removing local data does not remove copies held by websites, the MCP client or its AI provider.

Your controls

The public edition starts with AI control paused. Its side panel explains direct control and requires an explicit checkbox and enable action. Enabling control permits the connected AI to use available tools without repeated approval, including form submission. The choice persists across browser restarts. Site access is requested for the selected origin. The debugger permission is declared at installation or re-enablement; advanced screenshots, accessibility inspection and file attachment use it when needed. Basic page tools do not attach the debugger. AI-control and site-access checks still apply.

Pause control blocks new extension commands and disconnects the companion connection. Actions already dispatched, including long-running local jobs, may finish; pause cannot undo them. Review or revoke site permissions in the browser. Disable or remove the extension to revoke its required debugger permission. Configure only trusted MCP clients and only connect AI endpoints whose data handling you accept.

Integrated chat and quiet community checks

Chat uses official Codex App Server with ChatGPT sign-in only, and the account's Codex limits. API-key accounts are rejected. Codex manages authentication; the extension does not receive or copy login tokens, passwords or account email. OpenAI receives messages and page/tool context you choose to share. No publisher account or credentials are included.

Up to 40 recent chat messages, further bounded by context size, are stored locally in the companion's assistant-state.json and reused as conversation context. This is ordinary local storage, not an encrypted vault. Clear chat deletes that local copy, not provider-side records; your OpenAI account data controls still apply.

Quiet X monitoring stores one watched tab/account, up to 1,000 observed post IDs and 60 inbox items in browser-local storage. It makes ordinary requests to X when refreshing the watched page, but does not call a model or post replies. Notifications are opt-in and contain counts rather than message previews. Monitoring pauses on account/page changes or when control is paused.

Site-provided WebMCP descriptions and results are untrusted page data. Execution handles are bound to the discovered page/frame/session. Integrated chat asks for approval before mutations, separately from external MCP direct control. Stop and Pause cannot undo actions already dispatched.

This website and feedback

The website is hosted by Cloudflare, which processes ordinary web requests. Our website code uses no analytics, advertising scripts, cookies or browser storage. Images and styles are served from this website.

When you submit the feedback form, your message and any optional name or reply email go to FormSubmit for delivery to the publisher's private inbox. Feedback is not posted to GitHub or published on this website. FormSubmit documents a 30-day submission archive; delivered messages also remain in the publisher's inbox until removed. You can request removal through the feedback form.

Submission takes you to FormSubmit, which may use reCAPTCHA and cookies for abuse prevention. See FormSubmit's privacy policy. Do not send confidential information through the form. You do not need to provide a name or email unless you want to identify yourself or receive a reply.

Optional project support

The extension's GitHub and Buy Me a Coffee links open their respective websites only when clicked. Their icons are bundled locally; the extension does not load a donation widget, tracking script or payment form. Support is optional and does not unlock features. Buy Me a Coffee handles any payment under its own terms and privacy policy; ToolBraid does not receive payment details or send page contents, chat messages or a referrer through these links. Microsoft does not sponsor or collect this support.

Publisher contact

For privacy questions or support, use the Feedback form. Never include API keys, authentication tokens, private page contents or personal documents in a support report.

Store companion diagnostics and data

The Microsoft Store companion is a separate distribution with its own update schedule. Its connection/authentication and chat/workflow data live under %LOCALAPPDATA%\ToolBraid\store, separate from the ZIP edition's public directory.

Check connection inspects configuration and requests MCP initialization, ping and extension status. It performs no browser actions or model requests. Reports omit page URLs/titles, tokens, paths and raw errors, stay in the local window and are not uploaded. AI sign-in is not tested.

Close browser connections and choose Disconnect browsers before removing the Store app in Windows Settings. Previous registrations still owned by the app are restored; local data is retained. Direct uninstall may leave a stale registration; reinstall and disconnect to restore it. Browser extension storage and provider records are separate. Store status and setup.

Optional automatic site connection

Automatic connection is off by default. Enabling it requests HTTP/HTTPS host access and permits your connected AI to access eligible existing and new tabs in that browser profile. Excluded domains and subdomains remain blocked in both automatic and manual mode. The preference and exclusions are stored locally in the browser. Turning it off returns to manually connected sites; global pause blocks new commands. Browser-granted host permissions can be revoked separately in extension settings. Action approval settings are unchanged.