Ext Ops Panel
Open dashboard
Permissions and history

Is RaidBeacon Pairer safe to install?

RaidBeacon Pairer asks for 1 browser permission 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.

RaidBeacon Pairer

Chrome extension by RaidBeacon · Productivity · Tools

Open in the Chrome Web Store
What the developer says, and 3 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 specific sites only
Data collection
1 kind of data declared
Upkeep
Updated 92 days ago
Publisher
No store badges
Audience
18 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

Specific sites only: 2 match patterns.

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 · Tools, 20% of extensions ask for access to every site. This one: Access to specific sites only.

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

18 users

Users
+10 since 01.09
7-18 · 29 readings
  1. 2026-09-018
  2. 2026-09-029
  3. 2026-09-0610
  4. 2026-09-078
  5. 2026-09-089
  6. 2026-09-108
  7. 2026-09-139
  8. 2026-09-1510
  9. 2026-09-179
  10. 2026-09-218
  11. 2026-09-227
  12. 2026-09-258
  13. 2026-09-279
  14. 2026-10-058
  15. 2026-10-089
  16. 2026-10-0911
  17. 2026-10-1314
  18. 2026-10-1612
  19. 2026-10-1814
  20. 2026-10-1913
  21. 2026-10-2012
  22. 2026-10-2211
  23. 2026-10-2312
  24. 2026-10-2413
  25. 2026-10-2514
  26. 2026-10-2815
  27. 2026-10-2916
  28. 2026-10-3017
  29. 2026-11-0118

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

RaidBeacon. This listing has been in the store since 2026-07-11 and was last updated on 2026-08-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. RustAndRaids No permissions at all · No permissions declared 1k users ★ 4.5
  2. RustPlusBot No permissions at all · No permissions declared 8k users ★ 3.7
  3. RustGlass Pairing Access to specific sites only · 2 site patterns 10 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 RaidBeacon Pairer access?
Specific sites only: 2 match patterns. It declares 1 browser permission.
What data does RaidBeacon Pairer collect?
The developer declares that it collects these kinds of data: Authentication information. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.
Has RaidBeacon Pairer asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does RaidBeacon Pairer 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-01.

Back to RaidBeacon Pairer · Alternatives to RaidBeacon Pairer

Where the data comes from: how the catalog is built