Ideally, I want something that:
- Works reliably in Gmail’s web interface - Blocks tracking pixels and redirects - Doesn’t leak any data to third parties
I’ve been experimenting with this problem myself and I built a small extension called gblock (https://gblock.app ) that hides tracking pixels and neutralizes tracking links. I’m the developer, so I want to be up-front about that. I’m not here to promote it, I’m genuinely curious about what others use, what actually works, and what issues you’ve run into (false positives, performance, Gmail UI breakage, etc.).
If you’ve tested different approaches or have insights into how modern trackers evade detection, I’d love to hear your thoughts. Thanks!
_wire_•4mo ago
Since early days of Gmail Google has claimed several features to mitigate tracking:
1) the option to not automatically load images
2) proxying of message referents so that views don't imply unique loads.
3) render only a subset of markup avoiding active and risky elements by default
If you google, gemini will provide a rundown of native tracking mitigation features.