See mailshade.org

Email tracker blocker for ProtonMail

After you opt into the ProtonMail web client, Mailshade uses Chrome's declarativeNetRequest to cancel browser requests that match its reviewed tracker-pixel endpoint catalog. A local DOM scan detects pixels and supported tracking-link patterns; recognized links offer a direct-or-original choice. Detected tracker occurrences are recorded in local IndexedDB and charted per sender. Core inbox history is not transmitted to Mailshade servers, and Mailshade source code is published under AGPL-3.0-or-later at mailshade.org/source/. This page describes that browser-side scope.

ProtonMail image handling

ProtonMail may proxy remote images to reduce direct exposure. Mailshade separately evaluates receiver-side browser requests against its reviewed tracker-pixel endpoint catalog.

What Mailshade does in ProtonMail

  • After opt-in, cancels browser requests matching reviewed tracker-pixel endpoints via DNR.
  • Detects supported tracking-link patterns locally and lets you choose direct or original.
  • Shows a red-eye overlay naming the detected tracker endpoint.
  • Records detected tracker occurrences in a per-sender IndexedDB dashboard.

A privacy-first pairing

Mailshade keeps core inbox history in local IndexedDB with tracker URLs reduced to origins and does not transmit that history to Mailshade servers. Settings can use Chrome Sync; paid actions contact Mailshade auth/Polar, and optional privacy-filtered Hawk crash reports are off by default. Mailshade source code is published under AGPL-3.0-or-later at mailshade.org/source/.

Evidence and limits

Mailshade ships an opt-in ProtonMail integration. Comparative claims about other products belong to the dated benchmark, which distinguishes documented scope from behavior exercised in the tested client.

FAQ

How does Mailshade complement ProtonMail's image handling?

ProtonMail may proxy remote images to reduce direct exposure. Mailshade separately uses DNR to cancel opted-in browser requests that match its reviewed tracker-pixel endpoint catalog.

How is Mailshade's ProtonMail coverage scoped?

Mailshade ships an opt-in integration for the ProtonMail web client and evaluates browser requests against reviewed tracker-pixel endpoints. Dated comparative behavior is reported by the benchmark.

Does Mailshade fit ProtonMail's privacy model?

Core inbox history stays in local IndexedDB and is not sent to Mailshade servers. Mailshade source code is published under AGPL-3.0-or-later at mailshade.org/source/. Settings can use Chrome Sync and optional external paths are documented.

Is my ProtonMail data sent anywhere by Mailshade?

Core inbox history is not sent to Mailshade servers. Settings can use Chrome Sync; paid actions contact Mailshade auth/Polar, and optional privacy-filtered Hawk crash reports are off by default. These paths are visible in Mailshade's published AGPL-3.0-or-later source.

How much does the ProtonMail tracker blocker cost?

Core protection remains free after a 14-day Pro trial. Paid Pro starts at $3.99 per month or $19 one-time for Founders Lifetime.