Privacy Policy

Summary

The extension processes debugging data locally in the browser. It does not send inspected analytics data, browsing data, or page data to the developer or a developer-controlled remote service.

Data the Extension Can Inspect

When DevTools is open, the extension can inspect PostHog-related data from that page, including event names and properties, request URLs and status, payloads, selected flag responses, distinct IDs, session IDs, replay URLs, SDK configuration, frame origins, and local validation warnings.

If a site includes personal or sensitive values in PostHog payloads, those values may appear in the local DevTools panel.

How Data Is Used

Inspected data is used only for debugging features: live event inspection, payload decoding, network health, feature flag and session state, validation warnings, autocapture preview, and local lint reports.

Local Processing and Storage

Captured data is stored in memory while DevTools is open. The extension does not persist captured analytics payloads in extension storage, IndexedDB, or a remote database. LocalStorage may hold UI preferences and user-provided tracking-plan JSON.

Closing DevTools, navigating, reloading, or choosing clear removes the in-memory debug view.

Data Sharing

The extension does not sell, share, transfer, or transmit inspected analytics or browsing data. It does not send inspected data to PostHog; it observes requests the inspected site is already making.

Extension Usage Analytics

The extension may send limited, cookieless usage events containing only allowlisted interaction categories, count buckets, version, browser, build variant, and optional internal debug markers. They do not contain inspected URLs, event names, properties, payloads, distinct IDs, or inspected flag keys.

Usage analytics uses a random in-memory session ID, disables autocapture and session recording, and ends with the DevTools panel. Firefox analytics and feature-flag evaluation start only after the optional technical and interaction data permission is granted.

Remote Code and Permissions

The extension does not load or execute remotely hosted extension code. Its pages and content script run from packaged files.

The content script runs on HTTP and HTTPS pages, including iframes, because PostHog may be used on arbitrary websites, staging environments, embedded widgets, localhost tunnels, reverse proxies, and self-hosted setups.

Limited Use Statement

Inspected data is used only for user-facing PostHog debugging. It is not used for advertising, profiling, resale, credit worthiness, or unrelated purposes.

Contact

For privacy questions or support, email gevorg@glechyan.com.