Ext Ops Panel
Open dashboard
Permissions and history

Is Tweet Thread Splitter safe to install?

Tweet Thread Splitter asks for 1 browser permission 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.

Tweet Thread Splitter

Chrome extension · Productivity · Tools

Open in the Chrome Web Store
What the developer says, and 4 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 site access
Data collection
Declares it collects none
Publisher
No store badges
Audience
178 users

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.

Routine for an extension

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 1 browser permission.

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

178 users

Users
+1 since 01.09
166-183 · 32 readings
  1. 2026-09-01177
  2. 2026-09-02180
  3. 2026-09-04183
  4. 2026-09-07179
  5. 2026-09-08175
  6. 2026-09-10173
  7. 2026-09-13174
  8. 2026-09-15176
  9. 2026-09-16179
  10. 2026-09-20177
  11. 2026-09-25175
  12. 2026-09-28168
  13. 2026-10-04179
  14. 2026-10-08174
  15. 2026-10-09171
  16. 2026-10-10170
  17. 2026-10-13166
  18. 2026-10-16171
  19. 2026-10-17172
  20. 2026-10-18176
  21. 2026-10-19176
  22. 2026-10-21177
  23. 2026-10-22179
  24. 2026-10-24175
  25. 2026-10-28183
  26. 2026-10-29177
  27. 2026-11-01170
  28. 2026-11-03173
  29. 2026-11-07174
  30. 2026-11-08177
  31. 2026-11-09178
  32. 2026-11-10178

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

The store lists no publisher name, who publishes 2 listings we track. This listing has been in the store since 2024-07-12 and was last updated on 2024-08-23.

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

Back to Tweet Thread Splitter · Alternatives to Tweet Thread Splitter

Where the data comes from: how the catalog is built