Your feed stays
on your device.

01 Scope

This Privacy Policy applies to the FeedFence browser extension and this informational website. FeedFence’s single purpose is to let you filter X posts and account suggestions by account location, country flag, or profile-bio phrase, keep chosen accounts visible, and block an account only when you request it.

FeedFence works only on x.com and twitter.com. X is a separate service with its own terms and privacy practices.

02 Data FeedFence handles

FeedFence handles only the following categories needed for its features:

FeedFence does not ask for your name, email address, password, or payment information. It does not read private messages or use post text for custom bio filters, and it does not record your general browsing history.

03 How data is used and shared

FeedFence uses data only to decide which supported X content to hide or show, remember your choices, carry out a block you request, and keep the extension working reliably.

Extension data is not sold, used for advertising, sent to analytics providers, or sent to the FeedFence developer. The developer cannot read data stored by the extension. This does not include information you choose to send through the website contact form described below.

When a lookup or requested block is needed, the required account and session information is sent directly from your browser to X over HTTPS. X is the only external party that receives data through the extension.

04 Local storage and retention

Settings, allowed accounts, cached lookup results, diagnostics, and extension-made block history are stored in chrome.storage.local in your browser profile.

Lookup-cache retention follows the duration you choose in FeedFence settings. Other extension data remains until you change it, clear the relevant browser or extension data, or uninstall FeedFence.

05 Browser permissions

06 Your controls

• Turn feed filtering on or off from the extension popup.
• Remove selected locations, bio phrases, or allowlisted accounts in settings.
• Disable or clear the local lookup cache from settings.
• Export or import a local settings backup.
• Remove all extension data by uninstalling FeedFence or clearing its extension storage through your browser.

Clearing the lookup cache does not remove your filters, allowlist, or extension-made block history. A settings backup leaves your device only if you move or share the file.

07 Chrome Web Store Limited Use commitment

FeedFence’s use of information received from Google APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.

08 This website

The FeedFence product website is hosted by Netlify, Inc. FeedFence does not set cookies or use analytics, advertising, embedded social widgets, tracking pixels, or user accounts.

If you submit the contact form, the name, email address, and message you enter are processed through Netlify Forms and made available to the FeedFence publisher so your inquiry can be read and answered. Contact submissions are kept only as long as reasonably needed to handle the inquiry or meet applicable legal obligations.

Netlify may also process standard technical request data to deliver and secure the site. The website does not receive data stored by the FeedFence extension. See Netlify’s Privacy Statement.

09 Changes and contact

This policy may be updated when FeedFence’s data practices or legal obligations change. Material changes will be disclosed as required, and the current version date appears at the top of this page.

FeedFence is operated by the publisher identified in its Chrome Web Store listing. Use the form below for privacy questions, support, or feedback.