Last updated: November 4, 2026

Privacy

What the extension reads

Before filtering starts, the extension shows an in-product notice describing the data it uses and asks you to agree. After you agree, it examines recognized feed entries and member-list details already rendered in your FetLife tab. When a selected filter needs details that are not shown in a list, it may request that member's own FetLife profile or activity page. Those requests go to FetLife over HTTPS, using your existing signed-in browser session. The extension does not send this information to its developer.

What is stored on your device

What is sent to the developer

The extension does not include analytics, error-reporting services such as Sentry, an account system, or cloud sync. It does not transmit your settings, FetLife page content, or usage events to the developer. The extension's Chrome Web Store listing may provide aggregate installation statistics to the developer under Google's own services and policies; those statistics are provided by Google, not collected by this extension.

We follow the Chrome Web Store User Data Policy's Limited Use requirements: user data is used only for the disclosed filtering purpose, is not sold or used for advertising, and is not shared with third parties.

Permissions and access

The extension requests Chrome's storage permission and runs on FetLife HTTPS pages. It does not request broad access to all websites, cookies, downloads, or your full tab list. Filtering is done in the browser and is reversible: the extension does not delete posts, send messages, change friendships, or alter account settings.

This website

These pages are static and do not use analytics, advertising pixels, cookies, or externally hosted fonts. The open-source fonts and icons are bundled with the site. The web host may process standard technical request information, such as an IP address and requested URL, to deliver and protect the site. The site is hosted on Railway, which may keep standard request logs under its own policies.

Contact form

If you use the contact form (or the “Report a bug” and “Request a feature” links in the extension, which open that page), the site receives what you type: the type of message, a summary, your details, an optional email address, and the extension version if you came from the extension. It also sees your browser's user-agent string. The message is sent by email to the developer through Resend and is not published or stored in a database on this site. To limit spam, the form uses Cloudflare Turnstile, which runs a security check in your browser and may process technical information such as your IP address under Cloudflare's privacy policy. The server keeps recent IP addresses in memory only, to limit how many messages one connection can send, and discards them within an hour. Opening the contact page from the extension sends nothing from the extension itself. Do not include passwords or private FetLife content in a message.

Third-party services

FetLife Filter interacts with FetLife only in your own browser to provide filtering features. FetLife's handling of your account and data is governed by its own terms and privacy practices. Installing through the Chrome Web Store is also subject to Google's services and privacy policy.

Your choices

You can edit or reset filter preferences in the extension, turn off the optional seen-member feature, clear its stored data through Chrome's extension settings, or remove the extension. Clearing the extension's stored data also clears your consent choice; filtering stays off until you agree to the notice again. Chrome clears the extension's local storage when the extension is removed.

Changes to this page

If the extension's data practices change, this page will be updated to describe them. New collection or transmission would require corresponding product disclosures and any consent required by applicable law and Chrome Web Store policy.

Privacy questions

Use the contact form and choose “Question.” Do not send private FetLife content or account credentials in a support request.