Ext Ops Panel
Open dashboard
Permissions and history

Is UX-Ray by Baymard: UX Issue Scanner safe to install?

UX-Ray by Baymard: UX Issue Scanner asks for 7 browser permissions and 4 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.

UX-Ray by Baymard: UX Issue Scanner

Chrome extension by Baymard · Make Chrome Yours · Functionality

Open in the Chrome Web Store
What the developer says, and 4 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
3 kinds of data declared
Audience
739 users · 5.0/5

What data it declares

The developer declares that it collects these kinds of 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: 4 match patterns.

Reaches your browsing data or every site

Worth knowing

Routine for an extension

How usual this is for its category

In Make Chrome Yours · Functionality, 12% of extensions ask for access to every site. This one: Access to specific sites only.

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

739 users

Users
-14 since 01.09
725-785 · 30 readings
2026-09-24: released 0.1.22026-10-20: released 0.1.3
  1. 2026-09-01753
  2. 2026-09-02757
  3. 2026-09-04748
  4. 2026-09-06735
  5. 2026-09-07739
  6. 2026-09-08747
  7. 2026-09-13751
  8. 2026-09-15745
  9. 2026-09-17768
  10. 2026-09-20736
  11. 2026-09-21739
  12. 2026-09-25748
  13. 2026-09-26749
  14. 2026-09-28751
  15. 2026-10-04753
  16. 2026-10-08762
  17. 2026-10-09760
  18. 2026-10-10756
  19. 2026-10-13757
  20. 2026-10-16763
  21. 2026-10-18772
  22. 2026-10-19778
  23. 2026-10-21781
  24. 2026-10-22785
  25. 2026-10-24778
  26. 2026-10-27770
  27. 2026-10-29757
  28. 2026-11-01725
  29. 2026-11-03739
  30. 2026-11-04739

What the store shows

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 0.1.3
  2. Version 0.1.2

Who publishes it

Baymard. This listing has been in the store since 2026-07-08 and was last updated on 2026-10-20.

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. UX Risk Detector No site access · 3 permissions 87 users
  2. UX Intelligence Agent Access to specific sites only · 4 permissions, 1 site pattern 12 users
  3. Website Roast AI: UX & Landing Page Audit Runs its code on every site · 6 permissions, 1 site pattern 35 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 UX-Ray by Baymard: UX Issue Scanner access?
Specific sites only: 4 match patterns. It declares 7 browser permissions.
What data does UX-Ray by Baymard: UX Issue Scanner collect?
The developer declares that it collects these kinds of data: Personally identifiable information, Authentication information, Website content. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.
Has UX-Ray by Baymard: UX Issue Scanner asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does UX-Ray by Baymard: UX Issue Scanner 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-04.

Back to UX-Ray by Baymard: UX Issue Scanner · Alternatives to UX-Ray by Baymard: UX Issue Scanner

Where the data comes from: how the catalog is built