Ext Ops Panel
Open dashboard
Permissions and history

Is LinkedIn Feed Blocker safe to install?

LinkedIn Feed Blocker asks for 1 browser permission 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.

LinkedIn Feed Blocker

Chrome extension by aedigitalroad · Productivity · Tools

Open in the Chrome Web Store
What the developer says, and 2 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
Declares it collects none
Upkeep
Updated 306 days ago
Publisher
No store badges
Audience
191 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

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 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

191 users

Users
+23 since 01.09
167-191 · 31 readings
  1. 2026-09-01168
  2. 2026-09-03167
  3. 2026-09-04169
  4. 2026-09-06170
  5. 2026-09-07172
  6. 2026-09-09170
  7. 2026-09-10172
  8. 2026-09-13176
  9. 2026-09-15173
  10. 2026-09-17171
  11. 2026-09-20170
  12. 2026-09-21174
  13. 2026-09-25171
  14. 2026-09-26169
  15. 2026-10-04168
  16. 2026-10-08172
  17. 2026-10-10172
  18. 2026-10-13174
  19. 2026-10-16175
  20. 2026-10-18178
  21. 2026-10-19177
  22. 2026-10-20180
  23. 2026-10-21182
  24. 2026-10-22186
  25. 2026-10-23185
  26. 2026-10-24190
  27. 2026-10-26189
  28. 2026-10-28188
  29. 2026-10-29187
  30. 2026-10-30191
  31. 2026-10-31191

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

aedigitalroad, who publishes 8 listings we track. This listing has been in the store since 2025-12-30 and was last updated on 2025-12-30.

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. Feed Hider for LinkedIn No permissions at all · No permissions declared 6 users ★ 5.0
  2. LinkedIn Feed Blocker No site access · 1 permission 13 users
  3. Simple LinkedIn Newsfeed Blocker No site access · 1 permission 14 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 LinkedIn Feed Blocker access?
Specific sites only: 1 match pattern. It declares 1 browser permission.
What data does LinkedIn Feed Blocker 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 LinkedIn Feed Blocker asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does LinkedIn Feed Blocker 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 LinkedIn Feed Blocker · Alternatives to LinkedIn Feed Blocker

Where the data comes from: how the catalog is built