Ext Ops Panel
Open dashboard
Permissions and history

Is BugShot safe to install?

BugShot 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.

BugShot

Chrome extension by BugShot · Productivity · Developer

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 every site
Data collection
4 kinds of data declared
Upkeep
Updated 205 days ago
Audience
84 users

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

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

Worth knowing

Routine for an extension

Pages it runs its code on

It runs its own code on specific pages only: 1 site pattern.

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

84 users

Users
-2 since 01.09
77-90 · 32 readings
  1. 2026-09-0186
  2. 2026-09-0290
  3. 2026-09-0483
  4. 2026-09-0782
  5. 2026-09-0888
  6. 2026-09-1085
  7. 2026-09-1386
  8. 2026-09-1587
  9. 2026-09-2088
  10. 2026-09-2186
  11. 2026-09-2585
  12. 2026-09-2884
  13. 2026-10-0486
  14. 2026-10-0882
  15. 2026-10-0985
  16. 2026-10-1085
  17. 2026-10-1680
  18. 2026-10-1778
  19. 2026-10-1877
  20. 2026-10-1978
  21. 2026-10-2081
  22. 2026-10-2185
  23. 2026-10-2282
  24. 2026-10-2383
  25. 2026-10-2681
  26. 2026-10-2883
  27. 2026-10-2986
  28. 2026-11-0184
  29. 2026-11-0483
  30. 2026-11-0686
  31. 2026-11-0784
  32. 2026-11-0884

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.

Who publishes it

BugShot. This listing has been in the store since 2022-04-06 and was last updated on 2026-04-17.

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. BugSnitch Access to specific sites only · 6 permissions, 11 site patterns 4 users
  2. Capture - Instant bug reports Runs its code on every site · 6 permissions, 2 site patterns 279 users ★ 5.0
  3. Ybug - Visual feedback tool for websites Access to every site · 2 permissions, 3 site patterns 741 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 BugShot access?
Every site you visit. This extension can read and change the content of any page you open. It declares 4 browser permissions.
What data does BugShot collect?
The developer declares that it collects these kinds of data: Personally identifiable information, Authentication information, Web history, Website content. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.
Has BugShot asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does BugShot 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-08.

Back to BugShot · Alternatives to BugShot

Where the data comes from: how the catalog is built