Ext Ops Panel
Open dashboard
Permissions and history

Is Claude Browser Inspector safe to install?

Claude Browser Inspector asks for 2 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.

Claude Browser Inspector

Chrome extension by Jekins · Productivity · Developer

Open in the Chrome Web Store
What the developer says, and 2 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 every site
Data collection
Declares it collects none
Upkeep
Updated 246 days ago
Publisher
No store badges
Audience
188 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

Worth knowing

Routine for an extension

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 2 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

188 users

Users
+49 since 01.09
139-189 · 32 readings
  1. 2026-09-01139
  2. 2026-09-02144
  3. 2026-09-03146
  4. 2026-09-04151
  5. 2026-09-06149
  6. 2026-09-07153
  7. 2026-09-08154
  8. 2026-09-10156
  9. 2026-09-13163
  10. 2026-09-15165
  11. 2026-09-17169
  12. 2026-09-21174
  13. 2026-09-25167
  14. 2026-09-26169
  15. 2026-09-28174
  16. 2026-10-04181
  17. 2026-10-08180
  18. 2026-10-09182
  19. 2026-10-10183
  20. 2026-10-16179
  21. 2026-10-18178
  22. 2026-10-19179
  23. 2026-10-20178
  24. 2026-10-21184
  25. 2026-10-22189
  26. 2026-10-23187
  27. 2026-10-24188
  28. 2026-10-26185
  29. 2026-10-28189
  30. 2026-10-30188
  31. 2026-11-01187
  32. 2026-11-02188

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

Jekins. This listing has been in the store since 2026-02-28 and was last updated on 2026-03-01.

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. Click Context No site access · 3 permissions 20 users
  2. ElementAgent Runs its code on every site · 4 permissions, 2 site patterns 9 users
  3. UI Context Access to every site · 1 permission, 2 site patterns 12 users ★ 5.0

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 Claude Browser Inspector access?
Every site you visit. This extension can read and change the content of any page you open. It declares 2 browser permissions.
What data does Claude Browser Inspector 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 Claude Browser Inspector asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does Claude Browser Inspector 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 Claude Browser Inspector · Alternatives to Claude Browser Inspector

Where the data comes from: how the catalog is built