DevSnoop

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, screenshots, and opt-in redacted network request or response bodies when you run debugging commands that ask for them.
• License key and activation state stored locally in the extension.
• A stable DevSnoop profile ID and an optional profile label that you enter in the extension popup, stored locally in that Chrome profile.
• Product analytics events such as extension install, popup open, Chrome Web Store link clicks, buy button clicks, license activation status, native host connection status, and first successful command.

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.
• To understand extension setup and purchase conversion so DevSnoop can improve onboarding.
• To record a fixed, sanitized reason code when the extension cannot connect to the native host, so reliability problems can be diagnosed.

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`.
• Website and extension usage analytics may be sent to PostHog at `us.i.posthog.com`.
• Sanitized native-host connection diagnostics may be sent to `backend.devsnoop.com`. They include a fixed reason code, extension version, and anonymous installation ID, but not raw error messages, file paths, profile labels, page URLs, tab data, or inspected page content.
• Analytics events do not include page URLs, page titles, DOM content, screenshots, console logs, network payloads, command parameters, selectors, license keys, or inspected page content.
• DevSnoop does not sell page data or use inspected page content for advertising.

Local storage and retention

• The extension stores license key, activation state, last verification timestamp, a stable DevSnoop profile ID, and your optional profile label in `chrome.storage.local`.
• The extension stores an anonymous analytics ID 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 metadata, opt-in network bodies, 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 and sanitized connection diagnostics. DevSnoop also sends limited product analytics to PostHog to improve onboarding and conversion. DevSnoop does not sell personal data.

Contact

Questions about this policy: hboon@devsnoop.com