Ext Ops Panel
Open dashboard
Permissions and history

Is PostHog Event Debugger (Unofficial) safe to install?

PostHog Event Debugger (Unofficial) asks for 3 browser permissions and 1 site pattern. We do not audit code and we do not judge intent; what we can show is what the listing declares and whether that has changed while we have been watching.

PostHog Event Debugger (Unofficial)

Chrome extension by Justin Luttrell · Productivity · Developer

Open in the Chrome Web Store
What the developer says, and 1 screenshot

Loading from the Chrome Web Store. Open the listing if it does not appear.

At a glance

Facts, not a score: an ad blocker needs every page and a theme needs nothing, so one number would be wrong about both. Each fact links to its detail.

Site access
Access to every site
Data collection
Declares it collects none
Upkeep
Updated 251 days ago
Publisher
No store badges
Audience
420 users

What data it declares

The developer declares that it does not collect or use your data.

The developer also certifies that your data is not sold to third parties outside approved uses, not used for purposes unrelated to the extension's core function, and not used to decide creditworthiness or lending.

The listing links to a privacy policy.

This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.

What Chrome asks you to allow

When you add it, Chrome asks you to allow it to:

Derived from the manifest by Chrome's documented rules; the dialog's exact wording depends on your Chrome version and language. Chrome asks again if an update requests more.

What it can reach

Every site you visit. This extension can read and change the content of any page you open. What access to every site means

Reaches your browsing data or every site

Routine for an extension

Pages it runs its code on

It runs its own code on every page you open: the manifest declares a content script for all sites.

A content script is code the extension injects into pages matching these patterns. On those pages it can read and change what you see, whether or not a host permission is listed above.

How usual this is for its category

In Productivity · Developer, 30% of extensions ask for access to every site. This one: Access to every site.

The typical extension there declares 3 browser permissions; this one declares 3 browser permissions.

Counted over the live extensions of the same category after our latest full pass of the store. A share is context, not a verdict: what is normal depends on what the extension is for.

Who uses it and how it is kept up

420 users

Users
+29 since 01.09
389-476 · 31 readings
  1. 2026-09-01391
  2. 2026-09-03392
  3. 2026-09-04389
  4. 2026-09-08401
  5. 2026-09-09413
  6. 2026-09-13408
  7. 2026-09-15405
  8. 2026-09-17415
  9. 2026-09-21426
  10. 2026-09-25440
  11. 2026-09-26445
  12. 2026-09-28454
  13. 2026-10-05461
  14. 2026-10-08467
  15. 2026-10-10470
  16. 2026-10-13476
  17. 2026-10-16474
  18. 2026-10-18465
  19. 2026-10-19463
  20. 2026-10-20468
  21. 2026-10-21469
  22. 2026-10-22471
  23. 2026-10-23469
  24. 2026-10-24467
  25. 2026-10-25469
  26. 2026-10-26462
  27. 2026-10-28454
  28. 2026-10-29444
  29. 2026-10-30439
  30. 2026-11-01424
  31. 2026-11-02420

What the store shows

The store shows none of its badges on this listing. Most listings carry none.

Has it asked for more over time?

This is the question a permission list on its own cannot answer. An extension that shipped narrow and widened later is a different proposition from one that always asked for the same thing.

The permissions this extension requests have not changed since we started watching it.

Who publishes it

Justin Luttrell, who publishes 2 listings we track. This listing has been in the store since 2026-02-09 and was last updated on 2026-02-25.

Similar extensions that ask for less

Listings close to this one in what they say they do, which declare less reach. Less reach is not a verdict on either: compare what each needs for the job.

  1. Mixpanel Debugger No permissions at all · No permissions declared 34 users (last published figure)
  2. Mixpanel Data Inspector Runs its code on every site · 2 permissions 2k users ★ 4.4
  3. PostHog Debugger (Unofficial) Runs its code on every site · 2 permissions, 4 site patterns 47 users

How to check or remove it in Chrome

  1. Type chrome://extensions in the address bar and find the extension in the list.
  2. Open its details. The site access setting shows where it can run; set it to run only on click and it reaches a page only after you press its icon.
  3. To uninstall it, choose Remove on the same page.

Questions people ask

What can PostHog Event Debugger (Unofficial) access?
Every site you visit. This extension can read and change the content of any page you open. It declares 3 browser permissions.
What data does PostHog Event Debugger (Unofficial) collect?
The developer declares that it does not collect or use your data. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.
Has PostHog Event Debugger (Unofficial) asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does PostHog Event Debugger (Unofficial) publish a privacy policy?
Yes, the store listing links to a privacy policy.

We read the public store listing up to 2 times a day and keep what it declared. We do not install the extension, do not audit its code, do not judge its intent and publish no contact details for its developer. Last read on 2026-11-02.

Back to PostHog Event Debugger (Unofficial) · Alternatives to PostHog Event Debugger (Unofficial)

Where the data comes from: how the catalog is built