Missive Read Receipts: Does Missive Track Your Email?

If a reply just landed from an accounting firm, a law office or a logistics team running a shared inbox, it may have come through Missive, a collaborative email client built for teams. So are there Missive read receipts watching when you open it? No. Missive email tracking does not exist as a feature: the company removed read receipts six years ago and has refused every request to bring them back. That makes Missive the rare entry in our series of email client investigations where the answer is a clean no. The more interesting question runs the other way. Missive now blocks trackers in the email its own users receive, and how that blocking works tells you a lot about what Gmail's protection does and doesn't do for you.

Key Takeaways

• Missive's own documentation answers "Do you offer read tracking?" with "No, we used to offer read tracking, but we stopped," so emails sent from Missive carry no Missive open pixel.
• Missive's Philippe Lehoux announced the removal in a September 14, 2020 blog post that calls read tracking "a predatory feature, privacy wise" and says it works only about 70% of the time.
• Missive blocks read trackers and 1x1 tracking pixels by default in mail its users receive, and it lets teams build rules on a "contains read trackers" condition.
• Missive's internal read receipts show teammates who read a shared conversation; they are never sent to the outside person who wrote the email.
• An image proxy like Missive's or Gmail's hides your IP address, but any tracking image it fails to catch still gets fetched, so a sender can still learn that someone opened the message.

Does Missive Track Your Email?

No, Missive does not track when you open email sent from its app. Its help center is blunt about it. Under the question "Do you offer read tracking?" the Missive FAQ answers: "No, we used to offer read tracking, but we stopped." Missive's security and privacy FAQ, updated on September 23, 2026, repeats the position from the receiving side: "Missive blocks read trackers and 1x1 tracking pixels by default, so senders can't tell whether you opened their message."

We checked the obvious places a tracking host would hide and found nothing (details in the probe section below). That result is consistent with the documentation, and it contrasts sharply with Missive's closest competitor. Front's Seen receipts embed a one pixel image in outgoing mail and show a whole support or sales team when you opened it. Two products built for the same job, shared team email, took opposite positions on watching the people they write to.

Why Did Missive Remove Read Receipts?

Missive removed read receipts because it concluded the feature was unreliable and open to abuse, and that offering it was a legal risk a small company couldn't afford. The reasoning is laid out in "The life and death of email read tracking," a post by Philippe Lehoux dated September 14, 2020. Missive launched in 2015, requests for read tracking "quickly started to pile up," and the team built it. Five years after launch, they pulled it.

The post gives three reasons:

• It doesn't work reliably. Blocked images cause missed opens, and servers that download images in advance cause fake ones. "A technology that works 70% of the time is a bad one," Lehoux wrote.
• It gets abused. The team said it "saw first hand how it was misused and weaponized to abuse people," and said it didn't need to imagine abuse scenarios because customers wrote in with them.
• It sits on the wrong side of privacy law. The post quotes European regulators, who in Article 29 Working Party Opinion 2/2006, adopted on 21 February 2006, expressed "the strongest opposition" to secretly recording whether recipients open email.

Lehoux's verdict: "read tracking is a predatory feature, privacy wise." The post also takes a swipe at Superhuman, which made its tracking opt in after a public backlash. A competitor funded with "hundreds of millions of dollars from Silicon Valley can certainly foot the legal bills," Lehoux wrote, "not us."

It cost them customers. On Missive's public "Bring back read receipts" request, one user wrote on September 10, 2020, "We're leaving missive." Lehoux closed the request on September 14, saying the odds of a return "are pretty much zero," and on October 5, 2020 replied to another user: "To us it would be hypocritical to fight this practice and still offer it in our product."

Compare that with Spark Mail. Readdle also pulled an early read receipt feature, in 2015, but today sells open tracking as Read Statuses on its Pro and Enterprise plans. Polymail still serves its open pixel from share.polymail.io. Missive is the one in this series that removed tracking and kept it removed.

What Does Missive Do With Trackers in Email Its Users Receive?

Missive strips known read trackers and 1x1 images out of incoming mail before its users see it. The help center puts it in one line: "Missive auto blocks read trackers and 1x1 images to prevent senders from spying on what you do with their email." The privacy FAQ adds that teams can build rules on the "contains read trackers" condition, which it suggests for routing marketing email automatically. A marketing newsletter that shows up with a pixel can be filed away automatically.

Images that aren't treated as trackers still need to load, and Missive appears to fetch those through its own proxy. The hostname camo.missiveusercontent.com resolves today to an Amazon CloudFront distribution. A September 17, 2026 issue filed on the bitwire-it/ipblocklist project on GitHub identifies it as the outbound address of the Missive client's image proxy and says it downloads images from email signatures. "Camo" is the name of a well known open source image proxy that GitHub itself uses to hide viewers' details, as GitHub's documentation on anonymized URLs explains.

Does an Image Proxy Stop Every Open From Registering?

No, a proxy hides who opened an email, not whether it was opened. This is the most important distinction in this article, and it applies to every image proxy, Missive's included.

Missive's own 2020 post explains the mechanism: "Each recipient receives a different version of the email with a unique transparent image. Each time one of those images is requested, the server matches it to a recipient and notifies the sender." Nothing about that requires the image to be transparent or 1x1. A sender can give every recipient a uniquely named copy of a company logo instead. When a proxy fetches that logo, the sender's server logs a hit on a URL that belongs to one person. It sees a cloud server's IP address instead of yours, but the open still registers.

So Missive's protection has two layers, and they do different things:

• Blocking removes a detected tracker, so no request is ever made. The sender learns nothing.
• Proxying fetches everything else from Missive's servers. The sender loses your IP address and location but can still see that a request happened.

Gmail only has the second layer. Google's help page on images says senders "can't use image loading to get information about your computer or location," then concedes: "Sometimes, senders may know whether you've opened an email that has an image." We covered how trackers work around that proxy in the tracking pixel that learned to dodge Gmail. Proton Mail is another client with both layers, and we ran its open source link cleaner ourselves in our Proton Mail read receipts investigation.

What Can a Missive Team See About You?

A Missive team can see which of its own members have read your email, but you are never part of that signal. Missive's collaboration docs describe "internal read receipts" that "show who in your team has read messages or comments within a shared conversation." They are on by default, and each user can switch them off under Settings, Preferences, Appearance by toggling "Show internal read receipts."

Teammate avatars also carry status markers. A blue dot means that teammate hasn't read every email in the thread, and a glowing border means they are looking at it right now. All of that describes the team's own activity inside Missive. None of it depends on an image loading in your inbox, so none of it tells the team when you read anything.

That is the line between collaboration and surveillance. Front's Seen receipts, by contrast, show the whole team when the customer opened a reply, which makes your reading habits visible to everyone on the account. Missive keeps its read receipts pointed inward.

What Did Our DNS and HTTP Probes Find?

We found no Missive tracking host. On September 28, 2026 we queried candidate hostnames with a nonsense subdomain as a control for each zone, so a wildcard DNS record couldn't produce a false hit. The method follows the approach in our guide to detecting email tracking pixels in Gmail.

The only live Missive host we found works in the recipient's favor. It fetches images for people reading mail in Missive; it doesn't report anyone's opens back to a Missive sender.

How Does Missive Compare to Gmail, HEY, Proton and Gblock?

Missive belongs to a small group of mail apps that fight trackers by default. Here is how their approaches line up, based on each vendor's own documentation.

HEY says it strips known spy pixel patterns and "everything that even smells like a spy pixel," is "confident we'll catch 98% of all the tracking," and "routes all images through our own servers first." Proton's support page on email tracker protection says it removes known trackers and preloads other remote images on your behalf through a proxy with "a generic IP address and geolocation." Preloading at delivery helps because the fetch no longer lines up with the moment you read. Apple says Mail Privacy Protection hides your IP address and "prevents senders from seeing if you've opened the email message," a side effect of which is fake opens in senders' dashboards.

Every one of these tools shares one blind spot: a tracking image nobody has identified yet. Blocklists and size heuristics catch the common cases; a uniquely named logo still gets fetched somewhere.

What This Means for Your Gmail Inbox

If people email you from Missive, relax: Missive isn't telling them when you read it. The risk sits with everyone else who writes to you. Newsletters and sales sequences routinely carry pixels, and if you read that mail in Gmail, Missive's blocker does nothing for you. Missive's protection only applies "when viewing emails in Missive," in the privacy FAQ's own words. A team that connects a Gmail account to Missive but also reads on the Gmail app gets Gmail's behavior there, not Missive's.

By default, Google says, Gmail shows images automatically, loading them through Google's proxy. That hides your location, but a sender can still see the open, which is exactly the half of the problem Missive's blocking layer solves. For the full picture of how senders get read receipts inside Gmail, see how Gmail read receipts work. Regulators are moving on this too: France's CNIL has told marketers that tracking pixels generally need consent, the same concern Missive cited when it quit.

How Do You Get Missive Style Tracker Blocking in Gmail?

You need to add the blocking layer that Gmail lacks. Our guide on how to block email tracking in Gmail covers every option in depth. The short version:

1. Stop images from loading automatically. In Gmail on the web, open Settings, See all settings, scroll to Images, choose "Ask before displaying external images" and click Save Changes, per Google's instructions. It works, but every legitimate image then needs a click.
2. Treat links as trackers too. Hover before you click. A link whose real destination is buried inside a parameter on someone else's domain is a click tracking redirect, and no image proxy touches it.
3. Add a pixel blocker that runs inside Gmail. Gblock blocks requests to known tracking hosts using a blocklist that updates automatically, and it flags unknown pixel sized images so the list keeps growing. Links go through its own proxy, which strips tracking parameters. Like Missive, it can't block a tracking image nobody has identified yet; that image still loads through Google's proxy.
4. Check a suspicious message yourself. Use Gmail's "Show original" and look for tiny images or long, unique image URLs.

What We Could Not Verify

We did not send tracked test email into a Missive account, so we can't say how Missive's detector decides what counts as a tracker beyond the 1x1 rule it documents. We also couldn't confirm whether its proxy fetches images when mail arrives or when someone opens it, which decides how much timing a sender can infer. Finally, we didn't test whether a third party pixel pasted into a Missive draft survives sending. Missive documents no built in way to add one, and its FAQ says it stopped offering read tracking.