Ext Ops Panel
Open dashboard
Permissions and history

Is Stigmabase LGBTDiversity safe to install?

Stigmabase LGBTDiversity declares no browser permissions and no site access in its manifest, which is as narrow as an extension gets. 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.

Stigmabase LGBTDiversity

Chrome extension by Stigmabase global initiative · Lifestyle · News

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
No permissions at all
Data collection
Declares it collects none
Audience
259 users · 5.0/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 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

From the permissions it declares, Chrome shows no permission warning when you add it.

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.

We have not read this listing's manifest since we started keeping permission names. The counts on the card come from the last time we did.

How usual this is for its category

In Lifestyle · News, 12% of extensions ask for access to every site. This one: No permissions at all.

The typical extension there declares 2 browser permissions; this one declares no 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

259 users

Users
-11 since 01.09
258-286 · 36 readings
2026-10-05: released 8.02026-10-08: released 8.1
  1. 2026-09-01270
  2. 2026-09-03278
  3. 2026-09-04271
  4. 2026-09-05276
  5. 2026-09-07274
  6. 2026-09-08277
  7. 2026-09-09280
  8. 2026-09-10278
  9. 2026-09-13277
  10. 2026-09-15279
  11. 2026-09-16286
  12. 2026-09-20268
  13. 2026-09-22267
  14. 2026-09-25260
  15. 2026-09-26277
  16. 2026-09-28275
  17. 2026-10-04269
  18. 2026-10-08266released 8.1
  19. 2026-10-09262
  20. 2026-10-10261
  21. 2026-10-11262
  22. 2026-10-13258
  23. 2026-10-16267
  24. 2026-10-18269
  25. 2026-10-19268
  26. 2026-10-20265
  27. 2026-10-21269
  28. 2026-10-22276
  29. 2026-10-24277
  30. 2026-10-25278
  31. 2026-10-26279
  32. 2026-10-28278
  33. 2026-11-01281
  34. 2026-11-02280
  35. 2026-11-04266
  36. 2026-11-06259

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.

Versions we have seen

  1. Version 8.1
  2. Version 8.0

Who publishes it

Stigmabase global initiative, who publishes 4 listings we track. This listing has been in the store since 2016-08-29 and was last updated on 2026-10-08.

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 Stigmabase LGBTDiversity access?
No site access is declared in the manifest, so it cannot read the pages you open on its own. It declares no browser permissions.
What data does Stigmabase LGBTDiversity 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 Stigmabase LGBTDiversity asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does Stigmabase LGBTDiversity 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 Stigmabase LGBTDiversity · Alternatives to Stigmabase LGBTDiversity

Where the data comes from: how the catalog is built