Ext Ops Panel
Open dashboard
Permissions and history

Is Bug Session Recorder safe to install?

Bug Session Recorder asks for 4 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.

Bug Session Recorder

Chrome extension by Kaique Martins · Productivity · Developer

Open in the Chrome Web Store
What the developer says, and 5 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
Publisher
No store badges
Audience
53 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

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

53 users

Users
+8 since 01.09
44-59 · 35 readings
2026-10-18: released 0.4.02026-10-21: released 0.5.02026-10-23: released 0.5.1
  1. 2026-09-0145
  2. 2026-09-0244
  3. 2026-09-0349
  4. 2026-09-0451
  5. 2026-09-0654
  6. 2026-09-1048
  7. 2026-09-1551
  8. 2026-09-1748
  9. 2026-09-2051
  10. 2026-09-2248
  11. 2026-09-2551
  12. 2026-09-2649
  13. 2026-09-2847
  14. 2026-10-0449
  15. 2026-10-0848
  16. 2026-10-0949
  17. 2026-10-1048
  18. 2026-10-1347
  19. 2026-10-1649
  20. 2026-10-1751
  21. 2026-10-1854released 0.4.0
  22. 2026-10-1955
  23. 2026-10-2156released 0.5.0
  24. 2026-10-2257
  25. 2026-10-2359released 0.5.1
  26. 2026-10-2458
  27. 2026-10-2555
  28. 2026-10-2652
  29. 2026-10-2851
  30. 2026-10-2949
  31. 2026-10-3051
  32. 2026-11-0154
  33. 2026-11-0256
  34. 2026-11-0455
  35. 2026-11-0653

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 0.5.1
  2. Version 0.5.0
  3. Version 0.4.0

Who publishes it

Kaique Martins. This listing has been in the store since 2026-07-08 and was last updated on 2026-10-22.

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. TraceBug: Bug Report Recorder & Replay No site access · 7 permissions 34 users ★ 5.0
  2. Bug Report Recorder Pro - Screen Recorder for Bug Reports Access to specific sites only · 7 permissions, 1 site pattern 32 users
  3. PlayLog - Screen Recorder & Bug Reporter Access to specific sites only · 10 permissions, 1 site pattern 19 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 Bug Session Recorder 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 Bug Session Recorder collect?
The developer declares that it collects these kinds of data: Authentication information, Web history, User activity, Website content. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.
Has Bug Session Recorder asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does Bug Session Recorder 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-06.

Back to Bug Session Recorder · Alternatives to Bug Session Recorder

Where the data comes from: how the catalog is built