Ext Ops Panel
Open dashboard
Permissions and history

Is Browse Queue safe to install?

Browse Queue asks for 4 browser permissions and declares no blanket site access. 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.

Browse Queue

Chrome extension by Henry Schimke · Make Chrome Yours · Functionality

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
No site access
Data collection
Declares it collects none
Upkeep
Updated 211 days ago
Publisher
No store badges
Audience
45 users · 4.2/5

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

No site access is declared in the manifest, so it cannot read the pages you open on its own.

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: No site access.

The typical extension there declares 2 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

45 users

Users
-2 since 01.09
41-52 · 37 readings
  1. 2026-09-0147
  2. 2026-09-0251
  3. 2026-09-0552
  4. 2026-09-0651
  5. 2026-09-0752
  6. 2026-09-0848
  7. 2026-09-0947
  8. 2026-09-1341
  9. 2026-09-1547
  10. 2026-09-1644
  11. 2026-09-2046
  12. 2026-09-2148
  13. 2026-09-2545
  14. 2026-09-2647
  15. 2026-09-2848
  16. 2026-10-0451
  17. 2026-10-0846
  18. 2026-10-0951
  19. 2026-10-1050
  20. 2026-10-1149
  21. 2026-10-1351
  22. 2026-10-1649
  23. 2026-10-1751
  24. 2026-10-1850
  25. 2026-10-2047
  26. 2026-10-2149
  27. 2026-10-2247
  28. 2026-10-2345
  29. 2026-10-2546
  30. 2026-10-2644
  31. 2026-10-2843
  32. 2026-10-3047
  33. 2026-11-0148
  34. 2026-11-0447
  35. 2026-11-0644
  36. 2026-11-0742
  37. 2026-11-0845

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

Henry Schimke, who publishes 3 listings we track. This listing has been in the store since 2009-12-20 and was last updated on 2026-04-11.

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. Link queue — “Next” button No permissions at all · No permissions declared 3 users (last published figure)
  2. Link queue — “Add” button No permissions at all · No permissions declared 3 users
  3. Quick Open Runs its code on every site · 1 permission 6 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 Browse Queue access?
No site access is declared in the manifest, so it cannot read the pages you open on its own. It declares 4 browser permissions.
What data does Browse Queue 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 Browse Queue asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does Browse Queue 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-08.

Back to Browse Queue · Alternatives to Browse Queue

Where the data comes from: how the catalog is built