Light bulb Limited Spots Available: Secure Your Lifetime Subscription on Gumroad!

Nov 08, 2026 · 10 min read

Disroot Read Receipts: Does Disroot Track Your Email?

Disroot, the volunteer run Amsterdam collective founded in 2015, runs no ads and keeps its logs for a day. It also stores your mail unencrypted, and on November 8, 2026 its webmail was still one security release behind.

Does Disroot track your email? Not in any way we could find: no analytics, no advertisers, and server logs deleted after 24 hours, according to its privacy statement. Disroot read receipts are a smaller question, because no receipt leaves your account unless your mail program sends it. The bigger gaps are elsewhere. We read Disroot's privacy statement, terms, email page and webmail guide, inspected the code of its webmail sign in page, checked its DNS records and followed its status page on November 8, 2026. One complication: disroot.org itself is down. A storage server failure that began on October 26 has replaced the site with a maintenance notice, so we read its policies from Internet Archive copies.

Key Takeaways

  • Disroot's privacy statement, version 1.5 from February 2024, says email server logs with your username and IP address are deleted after 24 hours and that "No backup of log files is created."
  • Disroot's privacy statement also says "All emails, unless encrypted by the user (with GnuPG/PGP, for example) are stored unencrypted on our servers," protected only by disk encryption.
  • Disroot's webmail reports Roundcube 1.7.4, released September 6, 2026, which predates the October 19 release that fixed two remote content blocking bypasses.
  • Disroot documents neither its remote image default nor its read receipt default; stock Roundcube blocks remote images and asks before answering a receipt request.
  • A storage failure reported on October 26, 2026 cut Disroot users off from their mailboxes, and a November 2 update warned of disk regions that "may lead to unrecoverable data."
Volunteer administrator replacing a hard drive in a server rack beside a laptop showing webmail, illustrating whether Disroot email and Disroot read receipts track users

Does Disroot Track You?

No evidence says it does, and its written policy rules most tracking out. The privacy statement says Disroot does not "process, analyze your behavior or personal characteristics to create profiles about you," and adds: "We have no advertisements or business relationships with advertisers." For email specifically, it keeps:

  • Server logs for 24 hours: your username and IP address, the from and to addresses, and the IP addresses of the servers mail passes through, kept "to prevent brute-force attacks on accounts and to provide quick insight when debugging issues."
  • Your IP address while a device is connected over IMAP or POP3, "as long as the device is logged in."
  • A signup email address, deleted once your account is approved or denied unless you keep it for password resets.

The code we could see agrees. The webmail sign in page at webmail.disroot.org loads only Roundcube's own scripts and a Disroot skin, sends referrer-policy: no-referrer, and sets one session cookie. The maintenance page now at disroot.org loads no scripts at all. One DNS record looks alarming and isn't: a google-site-verification TXT entry proves domain ownership to Google Search Console and collects nothing from users. Disroot's mail records are strict, too: SPF ends in -all and DMARC is set to p=reject, so receivers that enforce DMARC should reject mail that fakes a disroot.org sender.

What we could not check: whether Disroot ever adds anything to outgoing mail. That needs a live account, which we did not create. Nothing in Roundcube or the policy suggests it does.

Which Webmail Does Disroot Use, and Does It Block Remote Images?

Disroot runs Roundcube, and its remote image default is not documented. The sign in page reports "rcversion":10704, which is Roundcube 1.7.4, released on GitHub on September 6, 2026. The emergency archive at archives.disroot.org reports the same number.

That version matters for tracking. Roundcube 1.7.5 shipped on October 19, 2026, and its release notes list two fixes that go straight at spy pixels: "Fix remote content blocking bypass via SVG SMIL by attribute" and "Fix remote content blocking bypass via CSS escapes in FuncIRI attributes (again)." A remote content bypass lets a crafted message load a sender's image even when you chose to block images. Twenty days later, Disroot's webmail still reported 1.7.4. Disroot may have backported the patches without changing the version number, but it doesn't say so.

Riseup, which we reviewed two days ago, was on the newest 1.6 patch within 18 days. That gap is the clearest technical difference between the two collectives for anyone worried about pixels. The timing also deserves fairness: the 1.7.5 release landed one week before Disroot's storage server failed, and its small volunteer team has spent the weeks since rebuilding disks.

If Disroot kept Roundcube's defaults, you start protected. The 1.7 defaults file sets show_images to 0, "Never, always ask." Disroot's webmail preferences guide warns that loading remote content by default "can represent a serious risk to privacy," but never states the setting it ships. Our Roundcube tracking review found that Roundcube has no image proxy and does not clean tracked links, so once you allow images, the sender sees your IP address.

Does Disroot Send Read Receipts?

Disroot sends a read receipt only when your mail program agrees to. A receipt is a message disposition notification under RFC 8098, and the recipient's client decides whether to answer. Stock Roundcube sets mdn_requests to 0, which the defaults file defines as "ask the user." Disroot's guide lists the option as "On request for return receipt," which it says "Sets out what the client should do if the sender of a message requests for a read receipt," but not which choice is preselected.

Disroot read receipts work the other way too. The guide documents "Always request a return receipt" for mail you send, and Roundcube leaves that checkbox off by default. Recipients can ignore your request, so it proves little either way.

Is Disroot Email Encrypted at Rest?

Only at the disk level. The privacy statement says Disroot uses "disk encryption on all servers to prevent data leak in case the servers are stolen, confiscated or in any way physically tampered with." It is equally plain about mailboxes: "All emails, unless encrypted by the user (with GnuPG/PGP, for example) are stored unencrypted on our servers."

This is where Disroot and Riseup differ most. Our Riseup review found that every Riseup account created since March 2017 gets personally encrypted storage unlocked by your password. Disk encryption protects a Disroot server that has been switched off and carried away. It does not protect a running server, and a running server is what a Dutch court order or an intruder would meet. Disroot's email page points users to Mailvelope for PGP in webmail; for sensitive correspondence, that is the encryption that counts.

Which Laws Apply to Disroot?

Dutch law and the GDPR. Disroot's terms of service say it "is hosted in the Netherlands and therefore is subject to Dutch laws and jurisdiction." The operator is Stichting Disroot.org, a Dutch foundation with Chamber of Commerce number 69988099, and the privacy statement names the Dutch Data Protection Authority, the Autoriteit Persoonsgegevens, as the place to complain. All data sits on Disroot's own servers in a Dutch data center.

Neither the privacy statement nor the terms mention a warrant canary or a public report on law enforcement requests. That proves nothing either way, but readers coming from Riseup, whose canary statement disclosed two sealed FBI warrants, should not expect the same signal here. The 24 hour log window does limit what any order could collect after the fact.

What Happened to Disroot Email in October 2026?

A storage server failed and took mailbox access with it. Disroot's status page posted on October 26 that "Access to mailboxes is not possible," with temporary storage catching new mail. On October 28 it reported that two drives in the array had failed. On November 2 it said the file system was mounted read only but "some unreadable region does exist on the disk which may lead to unrecoverable data." By November 4, archives.disroot.org offered "an read-only archive of the email storage," and the team asked users to "try to back things up yourself."

The privacy statement promises daily backups to a remote server, kept "for period of 4 days." None of the updates through November 4 explains how those backups figure in the recovery. That is a resilience story, not a tracking one, but it belongs in any honest review: a provider that keeps little about you can still lose the mail you trusted it with. Activist providers carry this risk in different forms, as the Autistici/Inventati shutdown showed. Keep your own copy over IMAP or POP3.

The Real Risk: Senders Tracking Disroot Users

Disroot's own terms ban the activity that produces most tracking pixels: "Sending bulk emails, including but not limited to marketing and advertising, for business purposes." So the pixels Disroot users meet come from outside, in newsletters, receipts and targeted mail. When your mail program fetches one, the request goes to the sender's server, which logs your IP address and the time. Disroot's 24 hour log limit has no effect on what the sender keeps.

Tracked links do the same on click, and Roundcube does not clean them. For journalists and activists, the stakes are concrete: an open pixel can confirm that a burner address is read, and when.

How to Block Tracking in Disroot Email

These steps use the labels from Disroot's Roundcube preferences guide:

  1. Block remote images. Go to Settings, Preferences, Displaying Messages and set Allow remote resources (images, styles) to never.
  2. Turn off Display HTML for high risk accounts. In the same section, disabling it converts formatted mail to plain text, which should also neutralize image blocking bypasses like the two fixed in Roundcube 1.7.5.
  3. Refuse receipts. Disroot's guide places "On request for return receipt" under Settings, Preferences, Mailbox View; set it to ignore, or to ask and always decline.
  4. Lock down your desktop client. Disroot suggests Thunderbird, K9Mail and FairEmail among others; keep remote content blocked in whichever you use.
  5. Hover before clicking links from unknown senders, and retype addresses you need.
  6. Use the onion address if your connection to Disroot is sensitive; the webmail advertises one in its onion-location header.
  7. Export your mailbox regularly over IMAP so an outage can't take your archive with it.

Gmail vs Disroot Webmail vs Gblock: An Honest Comparison

Many Disroot users also keep a Gmail account, and some forward one into the other. Once Disroot mail lands in Gmail, Gmail's rules apply. Google's image settings page shows images automatically by default and warns that "senders may know whether you've opened an email that has an image." Our guide to blocking email tracking in Gmail covers the settings in detail.

  • Gmail's image proxy: since a December 2013 change, Gmail serves images "through Google's own secure proxy servers," which hides your IP address from senders. The open itself still registers. The setting Ask before displaying external images stops that, but hides wanted images too.
  • Disroot webmail: stock Roundcube blocks remote images until you allow them, with no proxy and no link cleaning, and Disroot's copy is a release behind on two blocking bypass fixes.
  • 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 Disroot's webmail or in Thunderbird.
  • Ugly Email, PixelBlock and Trocker: other Gmail extensions that flag or block the same pixels, with different trade offs in coverage, link handling and upkeep.

The Quick Answer

Does Disroot track your email? By its privacy statement and the code we could inspect, no: no analytics, no ads, logs gone after 24 hours. Disroot read receipts go out only if you send them. The weak points are unencrypted mailbox storage, a webmail one patch behind on image blocking fixes, and an outage that put mailboxes at risk. Block remote content, use PGP for anything sensitive, and keep your own backup.

Stop Email Tracking in Gmail

Disroot keeps its logs for just 24 hours, but the Gmail inbox where many Disroot users also read mail loads tracking images the moment a message opens. Gblock blocks known spy pixels and strips tracking links in Gmail on your desktop browser, so senders can't tell when you read their email.

Try Gblock Free for 30 Days

No credit card required. Works with Chrome, Edge, Brave, and Arc.