Ext Ops Panel
Open dashboard
Permissions and history

Is FeedFilter – LinkedIn AI Detector safe to install?

FeedFilter – LinkedIn AI Detector asks for 2 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.

FeedFilter – LinkedIn AI Detector

Chrome extension · 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
Declares it collects none
Upkeep
Updated 207 days ago
Publisher
No store badges
Audience
5 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

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: 2 site patterns.

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

5 users

Users
+5 since 01.09
0-6 · 18 readings
  1. 2026-09-010
  2. 2026-09-054
  3. 2026-09-065
  4. 2026-09-073
  5. 2026-09-084
  6. 2026-09-095
  7. 2026-09-215
  8. 2026-09-266
  9. 2026-09-285
  10. 2026-10-096
  11. 2026-10-105
  12. 2026-10-185
  13. 2026-10-216
  14. 2026-10-225
  15. 2026-10-236
  16. 2026-10-245
  17. 2026-10-296
  18. 2026-11-015

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. This listing has been in the store since 2026-04-08 and was last updated on 2026-04-08.

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. LinkedIn AI Post Detector No permissions at all · No permissions declared 10 users ★ 1.0
  2. AI Slop Filter for LinkedIn — Hide AI Posts No site access · 1 permission 10 users
  3. LinkedIn AI Content Detector No site access · 1 permission 20 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 FeedFilter – LinkedIn AI Detector access?
Specific sites only: 1 match pattern. It declares 2 browser permissions.
What data does FeedFilter – LinkedIn AI Detector 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 FeedFilter – LinkedIn AI Detector asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does FeedFilter – LinkedIn AI Detector 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-01.

Back to FeedFilter – LinkedIn AI Detector · Alternatives to FeedFilter – LinkedIn AI Detector

Where the data comes from: how the catalog is built