Feed Filter

Privacy policy

Last updated October 4, 2026

This policy covers the Feed Filter Chrome extension. In short: it reads the text of the posts in your YouTube, X and LinkedIn feeds, sends that text and your goals to an AI model to judge them, and blurs the ones it flags. There are no accounts, no ads and no analytics, and your data is never sold.

What the extension reads

Only on youtube.com, x.com (and twitter.com) and linkedin.com, and only the items in your feed: each video's or post's title or text, the channel or author name, and the metadata shown with it, such as views, duration or the post's reaction counts.

It does not read page addresses, your browsing history, your messages, your account details, or anything on any other website.

Where that text goes

To judge each item, the extension sends batches of up to 20 items, together with the goals you wrote, to TypeSafe's Jev model. Which way it goes depends on your setup:

  • With your own API key: straight from your browser to the provider you picked, OpenRouter or TypeSafe, along with your key. It does not pass through our server.
  • Without a key (the free tier): to our server at feed-filter-two.vercel.app, which forwards it to Jev through OpenRouter using our own key and returns the answers.

The model returns a score for each item. The extension uses those scores only to decide what to blur.

What our free-tier server keeps

The free-tier server does not store or log the posts, titles or goals you send. To enforce the daily limit it keeps only counters of how many items were judged, keyed by:

  • a one-way hash of a random install ID the extension creates when you install it, and
  • a one-way hash of your IP address. The IP address itself is never stored.

These counters expire on their own: the per-minute ones after two minutes and the daily ones at midnight UTC. They can't be used to identify you. The server runs on Vercel, and the counters live in Upstash Redis. As hosting providers, they may keep standard request logs for a short time.

What stays on your device

In Chrome's local extension storage, never synced to an account: your settings, your goals, your API key if you add one, recent verdicts (kept for up to 7 days so the same post isn't judged twice), the random install ID, and where you placed the on-page switch. Uninstalling the extension deletes all of it. You can also clear the verdict cache from the options page at any time.

What we don't do

  • We don't sell or rent your data, or hand it to anyone except the providers named above for judging posts.
  • We don't use it for advertising, profiling, or anything unrelated to filtering your feed.
  • We don't use it to decide creditworthiness or for lending.
  • The extension has no analytics, tracking or accounts, and it runs no code from outside its own package.

Our use of information received through the extension complies with the Chrome Web Store User Data Policy, including its Limited Use requirements.

Changes and contact

If the extension starts handling data differently, this page will change first, with a new date at the top. For questions or requests, open an issue on GitHub.

Buy Me a Coffee