Know what was found
See the type of tracker detected in the message
Detect known trackers in incoming email Choose which ones to block in your browser
Create a free account. Available on Pro.See plansSee the type of tracker detected in the message
Block known trackers while allowing ordinary images
Manage incoming protection separately from the tracking on messages you send
Understand what is being requested before sharing the signal
Block recognized beacons before their remote request tells the sender that the message was displayed
See which known tracker type was detected before deciding whether to load remote content
Use targeted signatures and allow rules instead of disabling every image in every message
No signature list can identify every tracker, especially a new or first-party custom pixel Detection is a best-effort classification, not a guarantee of invisibility
Blocking can reduce sender tracking but cannot undo information already exposed by clicking a link, replying, downloading remote content, or using a provider that prefetches it upstream
Answers about setup, compatibility, privacy, and day-to-day use
No. The design uses known signatures and scoped request rules, with allow rules intended to preserve ordinary images and privacy proxies.
The extension ships separate Chrome, Edge, and Firefox builds with browser-appropriate background and rule behavior.
No. Known services and patterns can be detected, but a new, custom, or first-party beacon may not match the current signature set.
No. The published permission model does not require cookie access for tracker detection and blocking.
Understand what is being requested before sharing the signal