Ext Ops Panel
Open dashboard
Permissions and history

Is BigCommerce Debugging Tool safe to install?

BigCommerce Debugging Tool asks for 1 browser permission 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.

BigCommerce Debugging Tool

Chrome extension by Andrew Eliseev · 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
Publisher
No store badges
Audience
57 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 does not link 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

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 1 browser permission.

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

57 users

Users
-6 since 31.08
55-67 · 31 readings
  1. 2026-08-3163
  2. 2026-09-0265
  3. 2026-09-0466
  4. 2026-09-0567
  5. 2026-09-0665
  6. 2026-09-0766
  7. 2026-09-1061
  8. 2026-09-1360
  9. 2026-09-1564
  10. 2026-09-1763
  11. 2026-09-2161
  12. 2026-09-2763
  13. 2026-09-2862
  14. 2026-10-0561
  15. 2026-10-0963
  16. 2026-10-1061
  17. 2026-10-1358
  18. 2026-10-1662
  19. 2026-10-1760
  20. 2026-10-1861
  21. 2026-10-1960
  22. 2026-10-2059
  23. 2026-10-2161
  24. 2026-10-2260
  25. 2026-10-2358
  26. 2026-10-2460
  27. 2026-10-2555
  28. 2026-10-2856
  29. 2026-10-2957
  30. 2026-10-3059
  31. 2026-11-0157

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

Andrew Eliseev. This listing has been in the store since 2022-10-19 and was last updated on 2022-10-19.

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. Shopify Product Exporter No site access · 1 permission 7 users
  2. Shopify Admin Quick Access No site access · 2 permissions 131 users ★ 5.0
  3. Shopify Private App Access to specific sites only · 2 permissions, 2 site patterns 352 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 BigCommerce Debugging Tool access?
Every site you visit. This extension can read and change the content of any page you open. It declares 1 browser permission.
What data does BigCommerce Debugging Tool 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 BigCommerce Debugging Tool asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does BigCommerce Debugging Tool publish a privacy policy?
No, the store listing does not link 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 BigCommerce Debugging Tool · Alternatives to BigCommerce Debugging Tool

Where the data comes from: how the catalog is built