Privacy Policy for PostHog Debugger (Unofficial)

Last updated: 2026-06-07

PostHog Debugger (Unofficial) is a Chrome DevTools extension for developers who want to inspect PostHog analytics behavior on pages they are debugging.

This extension is not an official PostHog product and is not affiliated with, endorsed by, or sponsored by PostHog.

Summary

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

Data the Extension Can Inspect

When Chrome DevTools is open on a page, the extension can inspect PostHog-related debugging data from that inspected page, including:

• PostHog analytics event names and event properties;
• PostHog request URLs, endpoints, status codes, request sizes, and timing;
• PostHog request payloads and selected feature flag responses;
• PostHog distinct IDs, session IDs, session replay URLs, feature flag keys, feature flag values, feature flag payloads, group data, and SDK configuration values when exposed by the page’s posthog-js instance;
• top-frame and iframe URLs/origins used to attribute where captured events came from;
• validation warnings generated by the extension, such as missing IDs, failed requests, duplicate events, large payloads, or possible personally identifiable information in event properties.

The exact contents depend on what the inspected website sends to PostHog. If the website includes personal information, authentication-like values, location data, or other sensitive values in its PostHog event payloads, those values may appear inside the local DevTools panel.

How the Extension Uses Data

The extension uses inspected data only to provide its user-facing debugging features:

• showing live PostHog events in the DevTools panel;
• decoding and formatting PostHog payloads;
• showing raw PostHog network request health;
• showing PostHog feature flag and session state;
• generating local validation warnings for likely analytics implementation mistakes.

Local Processing and Storage

Captured data is stored in memory in the inspected page and in the DevTools panel state while DevTools is open. The extension does not use Chrome extension storage, localStorage, IndexedDB, or a remote database to persist captured analytics payloads.

Closing DevTools, navigating away from the page, reloading the page, or using the extension’s clear control removes the current in-memory debug view.

Data Sharing

The extension does not sell, share, transfer, or transmit inspected analytics data or browsing data to third parties.

The extension does not send inspected data to PostHog. It observes PostHog requests that the inspected website is already making.

The developer of this extension does not receive the inspected analytics payloads or browsing data through the extension.

Remote Code

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

Permissions and Site Access

The extension does not request Chrome extension permissions.

The content script runs on HTTP and HTTPS pages, including iframes, because developers may use PostHog on arbitrary websites, staging environments, embedded widgets, localhost tunnels, reverse proxies, and self-hosted PostHog setups. The content script is used to detect PostHog-shaped analytics requests and expose local debugging state to the DevTools panel for the currently inspected page.

Limited Use Statement

The extension’s use of inspected data is limited to the user-facing debugging features described in this policy and in the Chrome Web Store listing. The extension does not use inspected data for advertising, profiling, resale, credit worthiness, or any purpose unrelated to PostHog analytics debugging.

The use of information handled by this extension complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.

Contact

For privacy questions, support, or bug reports, use the public support page:

https://gevorg-glechyan.github.io/posthog-debugger/support/

Support requests are handled through GitHub Issues:

https://github.com/Gevorg-Glechyan/posthog-debugger/issues