Browser Operator Privacy

Last updated: July 2025

Last updated: July 2026

This policy explains what the DevsHub AI Browser Operator Chrome extension (the "Extension") does with data on your device. It supplements the DevsHub Privacy Policy and applies specifically to the Extension published on the Chrome Web Store.

1. What the Extension Does

The Extension lets your DevsHub AI agent operate the browser you already use — navigating pages, opening and grouping tabs, scrolling, clicking, typing, and reading page content — inside your existing, authenticated sessions, and only on your explicit instruction. It does not browse on its own and takes no action unless your DevsHub agent asks it to.

2. Single Purpose

The Extension has a single purpose: to allow your DevsHub AI agent to operate your own browser on your behalf. Every permission it requests exists solely to serve that purpose.

3. Information the Extension Handles

• Page content & interactions (transient): To carry out a request, the Extension reads rendered page content and performs input on the pages you direct it to. This data is relayed to your DevsHub agent to complete the task. It is not stored by the Extension and is not sold or shared with third parties.
• Local storage: The Extension stores a random per-install browser identifier and — if you choose to connect your account — a short-lived account token, in Chrome's local extension storage on your device.
• No credentials collected: The Extension operates within your existing logged-in sessions. It does not read, collect, or transmit your passwords, and it never asks you to enter credentials into it.

4. How Data Flows

• Local mode (default): When a DevsHub session is running on your machine, the Extension connects to it directly over a local WebSocket on 127.0.0.1. Data stays on your device.
• Cloud relay (optional): If you explicitly connect your DevsHub account, the Extension can reach your agent over an encrypted relay (wss://devshub.ai) using a short-lived, per-user token so you can drive the browser while away from your machine. You can revoke this at any time by clicking Disconnect in the Extension's options.

5. Data We Do NOT Collect or Sell

• We do not sell or rent any data handled by the Extension.
• We do not use or transfer this data for any purpose unrelated to the Extension's single purpose.
• We do not use or transfer this data to determine creditworthiness or for lending purposes.
• We do not build advertising profiles from your browsing.

The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.

6. Permissions & Why They Are Needed

• tabs — open, query, switch, and close tabs to navigate to and act on the pages you ask about.
• tabGroups — group agent-opened tabs under a visible "DevsHub" group so automated tabs are always distinguishable from your own.
• debugger — attach the Chrome DevTools Protocol to perform reliable input and read rendered page state; this is the core operator capability.
• scripting — run the requested read/interaction routines within the active page.
• storage — persist a per-install id and your optional account token locally.
• alarms — keep the background connection to the DevsHub bridge alive across Chrome's idle/suspend cycles.
• host access (all sites) — you may ask the agent to operate any site you are signed in to, so target domains cannot be known in advance. The Extension only ever acts on your explicit instruction.

7. Remote Code

The Extension does not load or execute remote code. All logic ships inside the published package.

8. Your Control

• Every action happens live in your own browser, and you can stop at any time.
• Disconnecting your account in the options screen immediately revokes cloud-relay access and clears the stored token.
• Uninstalling the Extension removes all of its locally stored data.

9. Contact

Questions about this policy or the Extension's data practices? Contact [email protected] or [email protected].