Extension privacy
Browser-extension data handling, permissions, and privacy policy.
Effective date: 2026-08-28
This policy describes how the Herdr browser extension handles user data. It applies to the Chrome extension distributed by the Herdr project and should be read together with the extension's product documentation.
The extension's single purpose is to connect supported Web AI conversations to the user's local Herdr / herdr-mcp workstation so the browser can show live workspace state, bind conversations to workspaces, preserve long-task and long-conversation continuity, queue the user's next turn, and provide bounded recovery and control UI in the Chrome Side Panel.
Data the extension handles#
To provide that user-facing functionality, the extension may handle the following data on supported Web AI sites:
- Website content and personal communications: conversation text and page state needed for continuity, queued messages, handoff/recovery, optional LLM analysis, and the user-invoked handoff fallback described below.
- Web history: the current supported-site URL, conversation/project identifiers derived from that URL, and limited navigation state needed to associate the active page with a Herdr workspace. The extension does not build or sell a general-purpose browsing-history profile.
- User activity: turn state, submit/settle/recovery timestamps, extension button/toggle state, and other bounded interaction state needed to determine when continuity and recovery actions are safe.
- Authentication information: current semantic-provider API keys are not stored or used by the extension. During upgrade, the extension may read historical browser-stored provider settings only to remove those retired credentials and permissions.
- Local Herdr state: workspace, pane, agent, status, output-tail, binding, and pinned-target information returned by the locally installed Herdr / herdr-mcp runtime.
The extension does not request or intentionally collect health information, financial/payment information, precise location, or data for advertising profiles.
Where data is stored#
The extension uses chrome.storage.local to keep settings and continuity state on the user's Chrome profile, including:
- workspace/conversation bindings;
- queued next-turn messages;
- automation preferences and recovery budgets/state;
- pinned local targets and locale settings;
- the local herdr-mcp endpoint configuration.
This local state exists so the Manifest V3 service worker and browser pages can recover safely after Chrome suspends or reloads them. The publisher does not operate an extension analytics or telemetry service that receives this local state.
Users can remove this locally stored extension data by removing the extension or clearing its extension/site data in Chrome. Semantic-provider routes and credentials stay outside extension storage: workstation-specific values live only in mode-0600 herdr-mcp config.json, while fleet-wide fallback values live in the authenticated Cloudflare Worker route pool.
Network destinations#
The extension communicates only as needed for its user-facing features:
- Local Herdr / herdr-mcp on the same computer. Native Messaging is used to exchange bounded requests and live workspace state with the installed native host. This traffic stays on the user's computer.
- Browser pages and supported/experimental Web AI sites. The extension requests required
<all_urls>host access when it is installed or loaded so Generic Web BrowserPage tasks can operate on arbitrary user-selected http/https pages without a new Chrome permission prompt for every site. Page Assist is injected only for a BrowserPage request targeting a specific page; it is not registered as an always-on content script for the whole web. ChatGPT is the primary supported WebChat surface and Claude uses its documented adapter. z.ai and DeepSeek remain experimental and disabled by default; enabling those switches controls whether their packaged content scripts are registered, while browser host access is already covered by the install-time permission. - User-configured semantic routes through herdr-mcp. The extension sends bounded semantic inputs only to the local herdr-mcp Runtime. Runtime may route typed evaluation to user-configured TypeSafe System One, OpenRouter Decisions, or Vercel Evaluation endpoints and may route bounded Goal-Supervisor or handoff-fallback text to a user-configured OpenAI-compatible chat endpoint. Ordinary Auto can include a bounded latest user/assistant turn; Goal-aware Auto can additionally include a bounded objective/open-TODO/runtime summary plus recent user/assistant text; handoff fallback can include a bounded source transcript (currently at most 70,000 characters, preserving early task framing plus recent operational state when truncation is required). Planning, Work Memory, and Parent orchestration boundaries may send their own bounded structured inputs through the same Runtime route pool: compatible-agent candidates for planning, frozen child-task summaries for attention, frozen validation candidates, bounded recent Agent text for optional closeout, and already-computed cleanup safety features for cleanup triage. These semantic results remain advisory and do not replace the underlying task/Git/validation/cleanup facts. Routes can be configured locally or on the enrolled Cloudflare Worker. When a Worker route is used, provider credentials remain at Edge and are never returned to the extension or workstation; only bounded semantic/chat results return. Each provider endpoint is user-selected and its own privacy and retention terms apply.
The extension does not sell user data, send user data to advertising networks, or transfer user data for unrelated profiling or credit/lending decisions.
Permissions and remote code#
The extension requests Chrome permissions only to provide the described functionality:
storage— persist local settings and continuity state;scripting— recover/reinject the packaged content-script stack on supported Web AI tabs after MV3/page reloads and perform bounded browser-side continuity actions;alarms— wake the MV3 service worker periodically so it can restore missing local Herdr state streams and timers after Chrome suspends it;nativeMessaging— connect to the locally installed herdr-mcp native host;debugger— attach the Chrome DevTools Protocol to a Herdr-owned page so the extension can read that page's navigation history, move the pointer over a known element, and capture a screenshot of that page, used to carry out and verify a browser action the user asked for. The attachment is bounded to Herdr-owned pages and to a fixed set of DevTools commands; the navigation entries it reads are not stored or sent anywhere, and the permission is not used to read or alter page content beyond those commands;sidePanel— host Herdr Browser Control Center;- host access — the extension requires
<all_urls>at install/load time so BrowserPage can control arbitrary user-selected http/https pages without per-site permission prompts. Generic Page Assist is still invoked only for a specific BrowserPage target and checks Chrome's live permission for that exact origin before page access. Users can restrict site access from Chrome's extension controls; such a restriction makes BrowserPage fail closed for that origin. Semantic providers are contacted by Runtime/Edge rather than directly by the extension, so provider routes do not require separate Chrome host permissions.
No remote executable code is used. All executable JavaScript is packaged with the extension. Network responses are handled as data and are not evaluated, imported, or executed as JavaScript or Wasm.
Limited Use#
Use of information received through Chrome APIs complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. In particular:
- user data is used only to provide or improve the extension's single purpose and user-facing features;
- user data is not sold or transferred to third parties outside permitted/necessary uses for those user-facing features;
- user data is not used for personalized or interest-based advertising;
- user data is not used to determine creditworthiness or for lending purposes;
- the publisher does not permit humans to read users' extension data except when the user explicitly asks for support involving specific data, or when required for security or legal compliance.
Chrome Web Store policy reference: https://developer.chrome.com/docs/webstore/user_data
Security#
Public network connections initiated by the extension use HTTPS/WSS where applicable. Native Messaging traffic between the extension and the native program on the same computer remains local. Semantic-provider secrets live only in mode-0600 workstation config.json or the authenticated Cloudflare Worker-wide route pool; the extension does not retain them as active configuration, and they are not intentionally written to project repositories or publisher telemetry.
Changes to this policy#
If extension behavior changes in a way that materially changes data handling, this policy and the Chrome Web Store disclosures will be updated before that behavior is published.
Contact and support#
Project homepage: https://whshang.github.io/herdr-mcp/
Support and issue tracker: https://github.com/whshang/herdr-mcp/issues