Ext Ops Panel
Open dashboard
Permissions and history

Is GEX Levels Indicator safe to install?

GEX Levels Indicator asks for 4 browser permissions and 5 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.

GEX Levels Indicator

Chrome extension by support · Productivity · Tools

Open in the Chrome Web Store
What the developer says, and 1 screenshot

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

Specific sites only: 5 match patterns.

Routine for an extension

Pages it runs its code on

It runs its own code on specific pages only: 2 site patterns.

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

268 users

Users
+195 since 31.08
73-285 · 36 readings
2026-09-02: released 4.1.12026-09-07: released 4.2.02026-09-13: released 4.5.12026-09-15: released 4.6.12026-09-20: released 4.6.42026-09-25: released 4.6.62026-09-29: released 4.6.72026-10-01: gained the good publisher record badge2026-10-01: released 4.6.82026-10-03: released 4.7.12026-10-15: released 5.0.0-rc.1
  1. 2026-08-3173
  2. 2026-09-0274released 4.1.1
  3. 2026-09-0377
  4. 2026-09-0587
  5. 2026-09-0688
  6. 2026-09-0791released 4.2.0
  7. 2026-09-08106
  8. 2026-09-10119
  9. 2026-09-13129released 4.5.1
  10. 2026-09-15139released 4.6.1
  11. 2026-09-17147
  12. 2026-09-20164released 4.6.4
  13. 2026-09-21171
  14. 2026-09-25166released 4.6.6
  15. 2026-09-26162
  16. 2026-09-28161
  17. 2026-10-04219
  18. 2026-10-08226
  19. 2026-10-09222
  20. 2026-10-10215
  21. 2026-10-11225
  22. 2026-10-13235
  23. 2026-10-16246
  24. 2026-10-17252
  25. 2026-10-18260
  26. 2026-10-19263
  27. 2026-10-20271
  28. 2026-10-21279
  29. 2026-10-22285
  30. 2026-10-23279
  31. 2026-10-24281
  32. 2026-10-25276
  33. 2026-10-28275
  34. 2026-10-29278
  35. 2026-10-30272
  36. 2026-11-01268

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.

  1. Asked for more permissions (9, was 8) (changed: browser permissions)
  2. Asked for more permissions (8, was 7)
  3. Swapped which permissions it asks for

Versions we have seen

  1. Version 5.0.0-rc.1 · Asked for more permissions (9, was 8) (changed: browser permissions)
  2. Version 4.7.1
  3. Version 4.6.8
  4. Version 4.6.7
  5. Version 4.6.6
  6. Version 4.6.4
  7. Version 4.6.1 · Asked for more permissions (8, was 7)
  8. Version 4.5.1 · Swapped which permissions it asks for

Who publishes it

support. This listing has been in the store since 2026-06-19 and was last updated on 2026-10-14.

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. Visualizador de Níveis de Trading No site access · 2 permissions 2 users (last published figure)
  2. GEXPluto Auto-Sync Access to specific sites only · 1 permission, 1 site pattern 12 users ★ 5.0
  3. StructMetric for TradingView Access to specific sites only · 1 permission, 3 site patterns 56 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 GEX Levels Indicator access?
Specific sites only: 5 match patterns. It declares 4 browser permissions.
What data does GEX Levels Indicator 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 GEX Levels Indicator asked for more permissions over time?
Its permissions changed 3 times while we watched, most recently on 2026-10-15.
Does GEX Levels Indicator 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 GEX Levels Indicator · Alternatives to GEX Levels Indicator

Where the data comes from: how the catalog is built