Chrome Web Store Submission

Use this guide to prepare the public Chrome Web Store listing for PostHog Debugger (Unofficial). Keep it aligned with manifest.json, docs/privacy-policy.md, docs/chrome-web-store-privacy.md, docs/chrome-web-store-review.md, and the current release ZIP.

Current Readiness

Already present:

public privacy policy: docs/privacy-policy.md;
live privacy policy URL: https://glechyan.com/extensions/posthog-debugger/privacy-policy/;
Chrome Web Store privacy worksheet: docs/chrome-web-store-privacy.md;
Chrome review notes and permission justification: docs/chrome-web-store-review.md;
public support page: docs/support.md;
live support URL: https://glechyan.com/extensions/posthog-debugger/support/;
live Chrome Web Store listing: https://chromewebstore.google.com/detail/posthog-debugger-unoffici/plleaelmjcemocibhcgdcganbiebdpfj;
canonical changelog: CHANGELOG.md;
16, 48, and 128 px icons in public/;
screenshots and promo images in screenshots/;
release packaging and validation scripts in package.json.

Still missing before final submission:

final store category, language, and region/distribution selections in the Chrome Web Store Developer Dashboard;
final uploaded ZIP confirmation for artifacts/posthog-debugger-chromium-<version>.zip;
final screenshot ordering and crop review inside the dashboard preview;
final confirmation that the dashboard privacy answers match docs/chrome-web-store-privacy.md.

Extension Description

Short description:

Debug PostHog setup, events, payloads, identity, flags, replay, privacy, autocapture, and network health in Chrome DevTools.

Detailed description:

PostHog Debugger (Unofficial) adds a dedicated PostHog panel to Chrome DevTools for developers validating analytics on their own sites, staging environments, localhost apps, embedded widgets, and self-hosted or reverse-proxied PostHog setups.

It helps you inspect live PostHog behavior without leaving the page you are debugging:

- Start with a Config view for loaded state, SDK version, destination, capture settings, consent/opt-out state, identity, and visible PostHog instances.
- Inspect live PostHog events, custom properties, PostHog `$` properties, `$set`, `$groups`, timestamps, API keys, and raw JSON payloads.
- Decode requests sent through fetch, XHR, sendBeacon, batch payloads, gzip, base64, form-encoded bodies, and query-string payloads.
- Use the Network view to spot blocked requests, failed requests, wrong hosts, missing tokens, non-2xx responses, endpoint timing, and decoded-event matching.
- Read feature flags, payloads, local override state, identity state, session IDs, replay diagnostics, and cookieless identity mode evidence when the page exposes a readable PostHog SDK instance.
- Follow identify, alias, group, and reset activity in a dedicated Identity view.
- Filter captured activity by search text, event kind, issue state, frame source, and request status.
- Export captured sessions as JSON or HAR for local debugging, bug reports, and support handoffs.
- Compare captured events against a local JSON tracking plan for naming convention drift and missing required properties when the linting feature is enabled.
- Preview likely PostHog autocapture output locally so you can inspect target elements and property shape without sending a real autocapture event.

Validation checks flag common implementation problems such as missing event names, missing distinct IDs, missing API keys, failed requests, duplicate fires, reserved prefixes, large payloads, clock skew, inconsistent naming, and likely PII in event properties.

PostHog Debugger displays inspected analytics data locally in the DevTools panel. It does not send inspected event payloads, browsing data, or SDK state to the developer or to any external service, and it does not sell, share, or use inspected data for advertising or profiling.

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

Chrome Submission Instructions

Confirm the repository state is clean enough for release.
```
git status --short
```
Confirm the version in package.json, package-lock.json, and manifest.json matches the release being uploaded.
```
node -p "require('./package.json').version"
node -p "require('./manifest.json').version"
```
Run the release gate.
```
npm run check:release
```
This runs typecheck, unit tests, Chromium and Firefox external/internal packaging, package validation, and Firefox package linting.
Upload the Chromium external ZIP.
```
artifacts/posthog-debugger-chromium-<version>.zip
```
Do not upload the -internal.zip package to the public Chrome Web Store.
In the Store listing tab, paste the short and detailed descriptions from this guide.

Add screenshots and promo images from screenshots/.

Suggested order:

screenshots/Config.png
screenshots/Events.png
screenshots/Network.png
screenshots/Flags and sessions.png
screenshots/Identity.png
screenshots/Autocapture.png
screenshots/Promo tile.png
screenshots/Marquee promo tile.png

Set the public support and privacy URLs.

Privacy policy: https://glechyan.com/extensions/posthog-debugger/privacy-policy/
Support: https://glechyan.com/extensions/posthog-debugger/support/

Complete the privacy questionnaire from docs/chrome-web-store-privacy.md.

Key answers:
- remote code: no;
- Chrome extension permissions: storage only, to retain the non-identifying first-run onboarding state;
- host access: HTTP and HTTPS pages, required for DevTools debugging on arbitrary developer sites and iframes;
- data use: inspected analytics data is processed locally for debugging and is not sold, shared, transferred, or used for advertising or profiling.
Use the host access justification from docs/chrome-web-store-review.md.
Before submitting for review, preview the listing and confirm:
- the public listing says the extension is unofficial;
- the privacy policy and support URLs open successfully;
- the uploaded package is the external Chromium ZIP for the intended version;
- the dashboard lists only the expected storage permission;
- screenshots are legible in the dashboard preview;
- no internal-only debug-session language appears in public listing copy.
Submit for review.
After approval, confirm the public Chrome Web Store URL still matches the README, support page, and docs index.