Ext Ops Panel
Open dashboard
Permissions and history

Is Twitter DM SaaS - Token Extractor safe to install?

Twitter DM SaaS - Token Extractor 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.

Twitter DM SaaS - Token Extractor

Chrome extension by domenico.grasso · Productivity · Developer

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
2 kinds of data declared
Upkeep
Updated 184 days ago
Publisher
No store badges
Audience
6 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.

Reaches your browsing data or every site

Worth knowing

Routine for an extension

Sites that can connect to it

Web pages matching these patterns can open a messaging channel to it: 2 site patterns.

Declared as externally connectable in the manifest: a page on these sites can exchange messages with the extension, for example to tell it you have signed in. It does not give the page access to your browser.

How usual this is for its category

In Productivity · Developer, 30% 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

6 users

Users
+1 since 01.09
4-7 · 31 readings
  1. 2026-09-015
  2. 2026-09-026
  3. 2026-09-055
  4. 2026-09-066
  5. 2026-09-075
  6. 2026-09-086
  7. 2026-09-105
  8. 2026-09-156
  9. 2026-09-175
  10. 2026-09-206
  11. 2026-09-214
  12. 2026-09-275
  13. 2026-09-284
  14. 2026-10-046
  15. 2026-10-097
  16. 2026-10-106
  17. 2026-10-135
  18. 2026-10-164
  19. 2026-10-185
  20. 2026-10-194
  21. 2026-10-215
  22. 2026-10-236
  23. 2026-10-247
  24. 2026-10-256
  25. 2026-10-285
  26. 2026-10-306
  27. 2026-11-016
  28. 2026-11-045
  29. 2026-11-077
  30. 2026-11-086
  31. 2026-11-166

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

domenico.grasso. This listing has been in the store since 2026-05-16 and was last updated on 2026-05-16.

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. xtwittermarket.com | auth token login No site access · 1 permission 101 users ★ 5.0
  2. ReplyOn - Twitter Growth Tool Access to specific sites only · 1 permission, 2 site patterns 15 users ★ 5.0
  3. Twitter Token Login Access to specific sites only · 1 permission, 1 site pattern 8k users ★ 5.0

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 Twitter DM SaaS - Token Extractor access?
Specific sites only: 5 match patterns. It declares 4 browser permissions.
What data does Twitter DM SaaS - Token Extractor collect?
The developer declares that it collects these kinds of data: Authentication information, User activity. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.
Has Twitter DM SaaS - Token Extractor asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does Twitter DM SaaS - Token Extractor 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-16.

Back to Twitter DM SaaS - Token Extractor · Alternatives to Twitter DM SaaS - Token Extractor

Where the data comes from: how the catalog is built