Privacy Policy

DevSnoop

Effective date: April 22, 2026

DevSnoop is a browser extension and local native host that let coding agents inspect, interact with, and debug web pages on your machine. This policy describes what the product accesses, how it is used, and where it is stored.

What DevSnoop accesses

  • Page URL, title, DOM structure, element attributes, and selected computed styles when you or your coding agent run inspection commands.
  • Page interaction targets and values you explicitly ask the extension to click, fill, hover, or scroll.
  • Console logs, JavaScript exceptions, network request metadata, and screenshots when you run debugging commands.
  • License key and activation state stored locally in the extension.

How DevSnoop uses data

  • To execute browser inspection and interaction commands that you initiate through the extension or the connected local agent bridge.
  • To verify license activation with `https://backend.devsnoop.com/verify`.
  • To return requested results to the local native host running on your machine so your coding agent can use them.

Where data goes

  • Extension command results are sent to the local DevSnoop native host via Chrome Native Messaging.
  • The native host exposes a local HTTP server on `127.0.0.1:9400` for your coding agent.
  • License verification requests are sent to `backend.devsnoop.com`.
  • DevSnoop does not sell page data or use inspected page content for advertising.

Local storage and retention

  • The extension stores license key, activation state, and last verification timestamp in `chrome.storage.local`.
  • The native host currently writes diagnostic logs to `/tmp/devsnoop-host.log`.
  • Screenshot commands currently write image files to `/tmp/devsnoop-screenshots/` on the local machine.

Permissions summary

  • `activeTab` and runtime site access: run inspection and interaction commands on pages you choose.
  • `scripting`: execute inspection and interaction logic in the active page context.
  • `debugger`: capture console, network, exception, and screenshot data for debugging commands.
  • `nativeMessaging`: communicate with the local DevSnoop host installed on your machine.
  • `tabs`: identify and target the current tab and list open tabs for agent commands.
  • `storage`: save license activation state and related local settings.

Sharing

DevSnoop shares data only as needed to operate the product: with the local native host on your machine, with the local coding agent that calls that host, and with `backend.devsnoop.com` for license verification. DevSnoop does not sell personal data.

Contact

Questions about this policy: hboon@devsnoop.com