Ext Ops Panel
Open dashboard
Permissions and history

Is qwertySeq() safe to install?

qwertySeq() 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.

qwertySeq()

Chrome extension by wgc · Lifestyle · Art

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 permissions at all
Data collection
Declares it collects none
Publisher
No store badges
Audience
606 users · 4.5/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

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 · Art, 13% of extensions ask for access to every site. This one: No permissions at all.

The typical extension there declares 1 browser permission; 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

606 users

Users
+28 since 31.08
561-616 · 39 readings
  1. 2026-08-31578
  2. 2026-09-03563
  3. 2026-09-04561
  4. 2026-09-05562
  5. 2026-09-07568
  6. 2026-09-08577
  7. 2026-09-10612
  8. 2026-09-13610
  9. 2026-09-15597
  10. 2026-09-17584
  11. 2026-09-20576
  12. 2026-09-22580
  13. 2026-09-25584
  14. 2026-09-26597
  15. 2026-09-28607
  16. 2026-10-04600
  17. 2026-10-08601
  18. 2026-10-09602
  19. 2026-10-10599
  20. 2026-10-11597
  21. 2026-10-13584
  22. 2026-10-16601
  23. 2026-10-17600
  24. 2026-10-18601
  25. 2026-10-19611
  26. 2026-10-20616
  27. 2026-10-21611
  28. 2026-10-22605
  29. 2026-10-23598
  30. 2026-10-24591
  31. 2026-10-25590
  32. 2026-10-26586
  33. 2026-10-28594
  34. 2026-10-29586
  35. 2026-10-30585
  36. 2026-11-01590
  37. 2026-11-02587
  38. 2026-11-04606
  39. 2026-11-05606

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

wgc. This listing has been in the store since 2018-08-28 and was last updated on 2025-06-12.

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 qwertySeq() 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 qwertySeq() 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 qwertySeq() asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does qwertySeq() 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-05.

Back to qwertySeq() · Alternatives to qwertySeq()

Where the data comes from: how the catalog is built