FeedFilter

Your information

Privacy policy

Last updated:

FeedFilter is a browser extension for X, selected Google Search pages, and news listing pages you configure. It processes most information locally and uses remote services for public account-location lookups, Fresh News rules, and actions you explicitly initiate.

1. Information stored locally

FeedFilter stores extension settings and feature data in browser storage or IndexedDB. This can include your country, account, and display-name filters; the optional comment-author X fallback setting; a hidden-post count; cached public usernames and location results; and temporary request coordination data.

For Fresh News, FeedFilter stores configured listing pages, freshness settings, headline URLs, titles and timestamps, verified rule releases, and related local state. Headline history remains local unless you explicitly configure a private history sync group. A device-local pseudonymous contributor key and compact rating or submission identifiers may be stored after you choose to rate or submit a rule.

2. Network requests

Depending on the features you use, FeedFilter may communicate with:

  • X-Posed: a read-only lookup endpoint may receive public usernames that are missing from local or passively observed data. FeedFilter does not contribute records to X-Posed.
  • X: FeedFilter may use location data already present in X responses and, when allowed, request public account-location data through your existing X session.
  • Twemoji: flag images may be loaded from X's static asset host.
  • Fresh News catalog: configured pages may request signed declarative rules using the normalized host and path. Health checks run locally.
  • Ratings and submissions: when you explicitly rate or submit a rule, FeedFilter sends the rating or validated rule data and sanitized fixtures. It does not send live page content for these actions.
  • Google Maps: the Maps enhancement reads the current Google search query locally to construct a link. Google receives that query if you follow an inserted Maps link.

These requests expose standard connection information, such as your IP address, to the receiving service and its infrastructure provider.

3. Information not collected

FeedFilter does not collect passwords, email addresses, direct messages, private X content, general browsing history, or the contents of posts hidden by local filters. Fresh News scanning, preview, health, and rating paths do not upload page HTML or live page content.

If you explicitly enable private history sync, bounded encrypted history snapshots and clear markers are sent to the HTTPS service you choose. The encryption key remains in extension local storage and is shared through your pairing code. The service receives a group identifier, IP address, request timing, payload sizes, and a digest of the bearer secret, but not the encrypted headline contents. Anyone holding a pairing code can read, change, or delete that group's history. Access to your browser profile may expose locally stored secrets.

4. How information is used

Public account-location data is used to display flags, apply country filters, and reduce direct X requests. Headline URLs, titles, and first- and last-seen times are used to identify previously seen headlines. Remote rules are signed declarative data interpreted by a bounded local engine; downloaded rules cannot execute code.

FeedFilter does not use filters for advertising or profiling. It is not affiliated with X Corp. or X-Posed.

5. Third-party services

X-Posed independently operates its lookup service. X provides account data and Twemoji assets. Google receives requests when you follow a Maps link. FeedFilter's Fresh News API host receives rule-resolution requests and any ratings or submissions you choose to send. Your selected history sync host receives encrypted snapshots only after you set up sync. These providers handle requests under their own privacy policies.

6. Your controls

X-Posed lookups are always enabled. You can change the optional direct-X fallback for comment authors in settings. You can remove filters, configured news pages, and headline history. History sync is off by default; settings let you disconnect, share a clear with the group, or delete the remote group.

Disconnecting sync removes local sync credentials while retaining a non-secret group identifier to prevent stale history from being reseeded on rejoin. A service provider's backups may retain encrypted data after group deletion. Removing a configured page also removes its host access when no other configured page uses that origin. You can disable or uninstall FeedFilter through your browser's extension manager.

7. This website

These pages use no cookies, analytics scripts, third-party fonts, or embedded tracking. Visiting the website does not connect to X or any account. The hosting provider may process standard request information, such as your IP address, browser information, and requested URL, to deliver and secure the website. External links are governed by the destination's privacy practices.

8. Changes and contact

This policy will be updated when FeedFilter's data practices change. The date above identifies the latest revision.

For questions, contact the developer through the FeedFilter issue tracker.