Ext Ops Panel
Open dashboard
Permissions and history

Is PSP Detector safe to install?

PSP Detector asks for 4 browser permissions and 2 site patterns. 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.

PSP Detector

Chrome extension by Adam Stiskala · Productivity · Tools

Open in the Chrome Web Store
What the developer says, and 3 screenshots

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 specific sites only
Data collection
Declares it collects none
Publisher
No store badges
Audience
655 users · 5.0/5

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

Specific sites only: 2 match patterns.

Worth knowing

Routine for an extension

What it may ask for later

Not granted when you add it: Chrome asks you the moment the extension requests one of these, and you can refuse. It may later ask for access to every site.

How usual this is for its category

In Productivity · Tools, 20% of extensions ask for access to every site. This one: Access to specific sites only.

The typical extension there declares 3 browser permissions; this one declares 4 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

655 users

Users
+61 since 01.09
594-673 · 35 readings
2026-09-27: released 3.2026.927.242026-10-06: released 3.2026.1005.2347
  1. 2026-09-01594
  2. 2026-09-02596
  3. 2026-09-04604
  4. 2026-09-06603
  5. 2026-09-07604
  6. 2026-09-09608
  7. 2026-09-10613
  8. 2026-09-13624
  9. 2026-09-15633
  10. 2026-09-17639
  11. 2026-09-20642
  12. 2026-09-22651
  13. 2026-09-25657
  14. 2026-09-26651
  15. 2026-09-28645
  16. 2026-10-04633
  17. 2026-10-08640
  18. 2026-10-09637
  19. 2026-10-10650
  20. 2026-10-11641
  21. 2026-10-13643
  22. 2026-10-16660
  23. 2026-10-17666
  24. 2026-10-18668
  25. 2026-10-19662
  26. 2026-10-20667
  27. 2026-10-21673
  28. 2026-10-22672
  29. 2026-10-23661
  30. 2026-10-24656
  31. 2026-10-25667
  32. 2026-10-28664
  33. 2026-10-29662
  34. 2026-10-30663
  35. 2026-11-01655

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.

Versions we have seen

  1. Version 3.2026.1005.2347
  2. Version 3.2026.927.24

Who publishes it

Adam Stiskala. This listing has been in the store since 2024-10-04 and was last updated on 2026-10-06.

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. XPayr Merchant Desk No site access · 1 permission 3 users (last published figure)
  2. Test Card Filler No site access · 4 permissions 5 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 PSP Detector access?
Specific sites only: 2 match patterns. It declares 4 browser permissions.
What data does PSP Detector 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 PSP Detector asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does PSP Detector 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-01.

Back to PSP Detector · Alternatives to PSP Detector

Where the data comes from: how the catalog is built