Ext Ops Panel
Open dashboard
Permissions and history

Is X/Twitter Spam Filter safe to install?

X/Twitter Spam Filter asks for 2 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.

X/Twitter Spam Filter

Chrome extension by mohcine · 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
No site access
Data collection
Declares it collects none
Audience
153 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

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.

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

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

153 users

Users
-38 since 01.09
153-278 · 33 readings
  1. 2026-09-01191
  2. 2026-09-02206
  3. 2026-09-04200
  4. 2026-09-06198
  5. 2026-09-07193
  6. 2026-09-08180
  7. 2026-09-10181
  8. 2026-09-13194
  9. 2026-09-15204
  10. 2026-09-17217
  11. 2026-09-20199
  12. 2026-09-21189
  13. 2026-09-25179
  14. 2026-09-26189
  15. 2026-09-28190
  16. 2026-10-04242
  17. 2026-10-08262
  18. 2026-10-09261
  19. 2026-10-10256
  20. 2026-10-13240
  21. 2026-10-16241
  22. 2026-10-17254
  23. 2026-10-19260
  24. 2026-10-20270
  25. 2026-10-21278
  26. 2026-10-22272
  27. 2026-10-23271
  28. 2026-10-24258
  29. 2026-10-25236
  30. 2026-10-28193
  31. 2026-10-29170
  32. 2026-10-30153
  33. 2026-10-31153

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.

Who publishes it

mohcine. This listing has been in the store since 2024-11-25 and was last updated on 2024-11-25.

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 X/Twitter Spam Filter access?
No site access is declared in the manifest, so it cannot read the pages you open on its own. It declares 2 browser permissions.
What data does X/Twitter Spam Filter 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 X/Twitter Spam Filter asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does X/Twitter Spam Filter 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-10-31.

Back to X/Twitter Spam Filter · Alternatives to X/Twitter Spam Filter

Where the data comes from: how the catalog is built