Ext Ops Panel
Open dashboard
Permissions and history

Is Feed Cleaner for LinkedIn safe to install?

Feed Cleaner for LinkedIn asks for 3 browser permissions and 1 site pattern. 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.

Feed Cleaner for LinkedIn

Chrome extension by simohberto · Productivity · Tools

Open in the Chrome Web Store
What the developer says, and 3 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
Access to specific sites only
Data collection
2 kinds of data declared
Upkeep
Updated 103 days ago
Publisher
No store badges
Audience
19 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: 1 match pattern.

Routine for an extension

Pages it runs its code on

It runs its own code on specific pages only: 1 site pattern.

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: Access to specific sites only.

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

19 users

Users
unchanged since 01.09
17-21 · 28 readings
  1. 2026-09-0119
  2. 2026-09-0320
  3. 2026-09-0421
  4. 2026-09-0620
  5. 2026-09-0719
  6. 2026-09-0818
  7. 2026-09-0919
  8. 2026-09-1018
  9. 2026-09-1319
  10. 2026-09-1520
  11. 2026-09-1718
  12. 2026-09-2020
  13. 2026-09-2119
  14. 2026-09-2520
  15. 2026-09-2819
  16. 2026-10-0517
  17. 2026-10-0818
  18. 2026-10-0919
  19. 2026-10-1018
  20. 2026-10-1619
  21. 2026-10-2120
  22. 2026-10-2219
  23. 2026-10-2318
  24. 2026-10-2418
  25. 2026-10-2919
  26. 2026-11-0120
  27. 2026-11-0319
  28. 2026-11-0419

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

simohberto. This listing has been in the store since 2026-07-13 and was last updated on 2026-07-24.

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. FeedHacker No site access · 1 permission 19 users ★ 5.0
  2. Feed Filter for LinkedIn No site access · 1 permission 9 users
  3. LinkedIn Feed Cleaner No site access · 1 permission 7 users

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 Feed Cleaner for LinkedIn access?
Specific sites only: 1 match pattern. It declares 3 browser permissions.
What data does Feed Cleaner for LinkedIn collect?
The developer declares that it collects these kinds of data: Web history, Website content. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.
Has Feed Cleaner for LinkedIn asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does Feed Cleaner for LinkedIn 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-04.

Back to Feed Cleaner for LinkedIn · Alternatives to Feed Cleaner for LinkedIn

Where the data comes from: how the catalog is built