Ext Ops Panel
Open dashboard
Permissions and history

Is Header Scraper safe to install?

Header Scraper 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.

Header Scraper

Chrome extension by UnFluffer · Productivity · Workflow

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
Publisher
Featured
Audience
274 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 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.

Worth knowing

Routine for an extension

How usual this is for its category

In Productivity · Workflow, 19% 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

274 users

Users
-6 since 01.09
260-281 · 32 readings
  1. 2026-09-01280
  2. 2026-09-02275
  3. 2026-09-05273
  4. 2026-09-06269
  5. 2026-09-08272
  6. 2026-09-10273
  7. 2026-09-15276
  8. 2026-09-17281
  9. 2026-09-20271
  10. 2026-09-21275
  11. 2026-09-25274
  12. 2026-09-26263
  13. 2026-09-28266
  14. 2026-10-08262
  15. 2026-10-09260
  16. 2026-10-10264
  17. 2026-10-13269
  18. 2026-10-16273
  19. 2026-10-17272
  20. 2026-10-18269
  21. 2026-10-19265
  22. 2026-10-20267
  23. 2026-10-21270
  24. 2026-10-22263
  25. 2026-10-23267
  26. 2026-10-24269
  27. 2026-10-25267
  28. 2026-10-26272
  29. 2026-10-28268
  30. 2026-10-29271
  31. 2026-10-30273
  32. 2026-11-01274

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

UnFluffer, who publishes 3 listings we track. This listing has been in the store since 2023-06-06 and was last updated on 2023-06-06.

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. BOLDering Runs its code on every site · No permissions declared 30 users ★ 5.0
  2. Heading Extractor Runs its code on every site · 1 permission 583 users ★ 3.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 Header Scraper 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 Header Scraper 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 Header Scraper asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does Header Scraper 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-01.

Back to Header Scraper · Alternatives to Header Scraper

Where the data comes from: how the catalog is built