Privacy Policy

@Filter and the community map

@Filter is a browser extension that hides content matching keywords you choose. When you enable community participation, the extension sends filtering activity to @Map so people can see which keywords are being filtered in different places. You can turn participation off in the extension settings. In the current extension, turning it off also stops content filtering.

What the extension sends

With community participation enabled, @Filter may send:

• The keywords you add, remove, or use to filter content.
• The site domain where filtering happened, such as a news site's domain, but not the full page URL.
• The number of items hidden, the time of the event, and technical information such as browser type and extension version.
• A random installation ID and session ID. The server stores a hash of the installation ID to count installations and help detect abuse.
• Approximate country, region, or city derived from the request IP address. The IP address is used for this lookup and is not saved in the analytics database.

The extension does not send page text, passwords, form contents, or full browsing history as filtering events. Your keyword list is also stored locally in your browser so the extension can filter pages.

What other people can see

@Map and its API display grouped filtering statistics, including keywords, site domains, approximate geography, time periods, and counts. An uncommon keyword or a small group can be revealing even when a name or account is not attached. Please avoid entering private information as a filter keyword if you participate in the community map.

We do not currently add statistical noise to every public count or require 100 users for every public result. Some fine-grained geographic views have additional minimum-count checks.

How long data is kept

Raw keyword-change and filtering-event records are used to make summary counts and are scheduled for deletion within 24 hours of receipt. The summary counts are kept for historical map views. A hashed installation ID and its approximate location may remain longer so the service can count observed installations and detect abuse. Your local keyword settings remain in your browser until you change them or uninstall the extension.

Backups and older records created before this retention change are being reviewed separately. We will not describe them as deleted until that cleanup is verified.

Your choices

You can turn community participation off in @Filter settings. Pending unsent events on that installation are cleared, and new filtering events are not sent while participation is off. Turning participation off currently disables the filtering feature as well. You can uninstall the extension to remove its local settings.

Because public summary counts combine activity from multiple installations, we may not be able to isolate and remove one installation's contribution after aggregation. For questions about the data linked to your installation, contact legal@atfilter.com.

Where data is processed

@Filter uses service providers for website hosting, database storage, and security. Data may be processed in the United States. Public map data and API results may be accessed by visitors and API customers.

Changes and contact

We will post changes to this page with an updated date. For privacy questions or requests, email legal@atfilter.com.