Nov 08, 2026 · 9 min read
Migadu Read Receipts: Does Migadu Track Your Email?
Migadu's webmail asks before it sends a read receipt, hides remote images until you click, and quietly drops many tracking pixels. Its image loads still go straight to the sender, and its servers sit in France, not Switzerland.
Migadu read receipts exist, but only when you choose to send one: the webmail shows a banner and waits for your click. So does Migadu track email you receive, or let senders do it? Mostly no, with gaps worth knowing. Migadu-Mail GmbH, which its about page calls a "small bootstrapped, independent Swiss company," runs its webmail on the open source SnappyMail client. On November 8, 2026 we read Migadu's privacy policy, terms and guides, downloaded the SnappyMail 2.38.2 code its webmail serves, compared it with the SnappyMail source on GitHub, and checked migadu.com's website and DNS records ourselves. We did not open a paid account, so settings visible only after login are marked as unverified.
Key Takeaways
- Migadu Webmail runs SnappyMail 2.38.2, which never answers a read receipt request on its own; it shows the banner "The sender has asked to be notified when you read this message." and sends a receipt only if you click it.
- SnappyMail's shipped default for external images is "ask," and its code hides tiny images and known open tracking addresses such as github.com/notifications/beacon/ even after you load images.
- Migadu's webmail appears to run without SnappyMail's image proxy, so an image you load reaches the sender's server with your own IP address.
- The Migadu privacy policy, updated December 5, 2024, says "No tracking or analytics cookies are employed" but states no log retention periods.
- Migadu is a Swiss company under the law of the Canton of Appenzell Ausserrhoden, yet it says "Current data centers are located in France."
Does Migadu Support Read Receipts?
Yes, but you control both directions. A read receipt request travels in the Disposition-Notification-To header defined in RFC 8098, and SnappyMail handles it in two places:
- Receiving. When a message carries a request, the webmail shows a clickable line: "The sender has asked to be notified when you read this message." Nothing goes out unless you click it. If you do, SnappyMail sends a message titled "Return Receipt (displayed)" which states that it "only acknowledges that the message was displayed on the recipient's computer."
- Sending. The compose window has a "Request a read receipt" option. In the SnappyMail source, the user setting behind it starts at 0, meaning off.
That puts Migadu between Runbox, which our Runbox review found has no receipt support at all, and providers that answer automatically. Over IMAP, your desktop app's own receipt setting applies instead. Read receipts are polite tracking, though; the pixel never asks.
Does Migadu Block Remote Images and Tracking Pixels?
By default, yes, and better than most webmail. Migadu documents none of this itself; the evidence comes from the SnappyMail 2.38.2 code that webmail.migadu.com serves.
- Images wait for you. SnappyMail's configuration ships
view_imagesset to "ask," with two other choices: "match," described as "whitelist or ask," and "always." The interface labels them Always ask, Whitelist or ask and Show always, and offers a Display external images button per message. Whether Migadu changed this default for new mailboxes is unverified, since it only shows after login. - Pixels stay hidden even after you click. SnappyMail's HTML cleaner hides any image narrower than 2 pixels or capped below 3 pixels, plus any image whose address contains one of four known open trackers:
email.microsoftemail.com/open,github.com/notifications/beacon/,/track/openandgoogle-analytics.com. The/track/openpattern is labelled in the code as covering Mandrill and list-manage.com, Mailchimp's domain. Hidden images are left out when you press Display external images.
The size check is the clever part. A tracking pixel has to be tiny to stay invisible, so a rule based on size catches pixels from email platforms that aren't on any list. It misses a tracker disguised as a normal sized logo, and that is where a maintained blocklist does better. Our guide on how to block email tracking in Gmail explains how pixels report an open.
Does Migadu Proxy Images or Clean Tracking Links?
Images: apparently not. Links: partly. SnappyMail can route images through the webmail server, which hides your IP address from the sender, and its stock configuration turns that proxy on. Migadu's webmail seems to have it off. When we requested an image through its /?/ProxyExternal/ address, the server returned an empty 404 without the X-Content-Location header that SnappyMail's proxy code sets whenever the proxy is enabled. The webmail's content security policy also lets the browser load images from any https address. Migadu doesn't document the setting either way, so treat this as our finding, not Migadu's statement: a loaded image tells the sender your IP address and the moment you opened.
Link cleaning is real but uneven. SnappyMail rewrites redirect links from a named set of services, including Mailchimp, Mandrill, Amazon SES's awstrack.me, GoDaddy and Outlook Safe Links, back to the real destination. It also tries to delete tracking parameters, and here we found a gap. The pattern in the 2.38.2 code Migadu serves is anchored at both ends, so it removes exact names such as fbclid, mc_eid, mkt_tok and _hsenc, but a test of the same expression showed utm_source and utm_campaign survive. Links from platforms outside the named set keep their full redirect.
Does Migadu Add Tracking to Mail You Send?
We found no sign of it. Migadu documents no open or click tracking feature, and its pros and cons page says "We do not approve of or accept bulk mailing, even if it is not spam." A provider that bans bulk senders has little reason to build campaign analytics. Migadu's own mail follows the same pattern: its SPF record, v=spf1 include:spf.migadu.com -all, points only to Migadu's own spf.migadu.com record, which lists Migadu hosts and IP ranges and no outside marketing platform. The about page adds: "We do not advertise, do not run "social media" accounts."
What Does Migadu Log About You?
Migadu doesn't say. The Migadu privacy policy, dated "Updated Thursday, December 5, 2024," never mentions server logs or IP addresses. Its only retention rule is that "Personal data is stored only as long as necessary to fulfill the purposes outlined in this policy." Here is what it does commit to:
- "We use cookies only to establish working sessions on our website and webmail."
- "No tracking or analytics cookies are employed," and "We do not collect data for user behavior analytics or integrate any website analytics."
- Payment data "is directly sent to our payment processors Stripe and PayPal," which the policy says includes transfers to the USA.
The website matches the analytics promise. The migadu.com homepage we downloaded contains a single inline script that expands a features list, with no analytics code. The gap is logging. Runbox, by comparison, publishes 10 day delivery logs and 1 month webmail logs. For compliance officers, an undocumented retention period is a question to put to Migadu in writing, not an answer.
Which Law Protects Migadu Mail: Swiss or EU?
Both, and the servers sit in the EU. The privacy policy says processing complies with the GDPR and "the local Swiss Federal Data Protection Act (DPA)." Migadu's terms of service are "governed in all respects by the laws of the Canton of Appenzell Ausserrhoden, Swiss Confederation." But the pros and cons page is blunt: "Current data centers are located in France," and "we do not host our servers in Switzerland." The webmail and inbound mail addresses we resolved sit in address blocks registered to the hosting company OVH.
Anyone choosing Migadu for "Swiss privacy" should note that. Migadu even writes, "We find EU privacy laws much more elaborate and restrictive than the Swiss ones." It also rules out encryption at rest, because "we would have to keep the encryption keys ourselves." Migadu publishes no transparency report, so how often authorities ask for data is unknown. The terms mention only that it may terminate accounts "In response to abuse reports, complaints or court orders."
How to Limit Email Tracking in Migadu
These steps follow the SnappyMail settings above and Migadu's client setup guides:
- Check the external images setting and keep it on Always ask or Whitelist or ask, never Show always.
- Whitelist only senders you trust, since Migadu doesn't appear to proxy the images you allow.
- Ignore the receipt banner unless you want the sender to know you read the message.
- Hover before you click. utm parameters and unlisted redirect services pass through untouched.
- Check your IMAP app. Thunderbird, Apple Mail and Outlook apply their own image and receipt settings, not SnappyMail's.
Why Email Users Should Care: Migadu Mail Read in Gmail
Migadu's protections stop at its webmail. Migadu publishes a Gmail setup guide that has Gmail pull mail over POP3 from pop.migadu.com, and its forwarding feature can redirect a mailbox to outside addresses. Once a newsletter lands in Gmail, Google's rules apply. Google's image settings page says "By default, when you get an email with an image, you'll see the image automatically," and that "Sometimes, senders may know whether you've opened an email that has an image."
Here is how the options compare for that mail:
- Gmail's image proxy: Gmail fetches images through Google's servers, which hides your IP address but still tells the sender when you opened. Settings, See all settings, Images, then Ask before displaying external images blocks everything, wanted images included.
- Migadu webmail: asks before loading images and hides tiny pixels, but sends allowed images without a proxy and cleans links only partly.
- Gblock in Gmail: a paid Chrome extension for Gmail on desktop browsers, with a 30 day trial. It blocks known tracking pixels using a blocklist that updates automatically, strips tracking from links and leaves other images alone, all inside Gmail. It does nothing in Migadu webmail or on Gmail's mobile apps.
- Ugly Email, PixelBlock and Trocker: other Gmail extensions that detect or block the same pixels, with their own lists and trade offs.
For other European options, see our mailbox.org review and the best private email providers comparison.
The Quick Answer
Do Migadu read receipts exist? Yes, but its webmail sends one only when you click the banner. Does Migadu track email? Its privacy policy rules out analytics and tracking cookies, and its SnappyMail webmail asks before loading images and hides most tiny pixels. The weak spots: no apparent image proxy, link cleaning that misses utm parameters, no published log retention, and servers in France rather than Switzerland.
For a privacy email provider whose servers actually sit in Switzerland, see our Kolab Now read receipts review.