Reviewed 18 August 2026

How email tracking pixels work

An HTML email can reference an image hosted on a remote server. When a mail reader downloads that image, the server can observe a request. A unique image URL may let the sender infer that a message was opened, along with request metadata such as time, network address, and user-agent details.

A pixel does not need to look like an image

Tracking resources are often tiny or invisible, but ordinary logos and product images can be individualized too. Blocking only one-pixel images is therefore incomplete. Links can also contain identifiers, so opening a detected link remains an intentional user action.

What gettemp.email does

Incoming HTML is treated as untrusted. Scripts, forms, frames, SVG, active styles, event handlers, and remote images are removed before rendering. The interface also provides a plain text view and labels external links. Message bodies, links, sender data, addresses, and codes are excluded from analytics and advertising contexts.

Limits of tracker-safe rendering

Removing remote content reduces passive loading from the message view, but it cannot make an external destination private. Following a link takes you to another service with its own logs, cookies, and privacy policy. Review the hostname and use the original service directly when a message is unexpected.

For appropriate use cases, see when to use a temporary address.