Product story

Privacy-first email tracking for Gmail

Most “privacy” claims in this category mean “we also have a policy.” SentCue’s design is narrower: optional pixels for messages you choose, history on this Chrome install, and a processor that stores a random token plus timestamps — not your subject line and not a map of the recipient.

This page is a human rewrite of the differentiators. The Privacy Policy is the legal text. If they ever disagree, the policy wins.

What this version still does not do

No link-click tracking, no map showing the recipient’s location, no IP profiles, no reading the rest of the mailbox, no Gmail API. Cloudflare may still process the HTTP request that fetches the pixel. Origin access logs redact tokens. If a future paid feature needed Google OAuth or a cloud copy of history, that would require a new disclosure — it is not how 1.2 works.

What stays on your device vs SentCue servers

Never collectedMessage body, attachments, and passwords do not go to either local history or the SentCue backend.

On this device

Your context stays local

Recipient, subject, and Gmail IDsUsed for local history and to connect a Sent row to its status.
History, reminders, and labelsStored in this browser, not in a SentCue account.
Random tracking IDUsed only to ask the server for signal status.

SentCue server

Only what is needed for a signal

Random tracking ID and send timeUsed to count activity signals.
Signal timestampsReturned to the extension when it checks status.
Recipient IP address and browser detailsNot persisted in the application database. Cloudflare still processes the HTTP request to serve the image.
Not sent to the backendRecipient address, subject, Gmail IDs, reminders, and follow-up labels.

You are the controller for recipient tracking

If you turn tracking On, you decide whom you email and why. Under frameworks that split controller and processor, you are the controller for personal data relating to those recipients. SentCue provides the technical feature and, for token and timestamps created when the image is requested, acts as a processor on your instructions. This page is not a claim of “100% GDPR compliance,” and it is not legal advice. Jurisdictions differ; ePrivacy-style rules may apply to pixels in email.

No account, no Google OAuth

You do not create a SentCue user. This version does not call Google Workspace APIs and does not use Gmail OAuth. The extension uses a content script on mail.google.com, chrome.storage for settings and history, alarms for reminders, optional notifications you grant separately, and host access to the pixel origin.

What recipients may still see

SentCue does not append a product line to your messages. That is not the same as hiding tracking. A mail client may still load a remote image, warn about images, or show the image URL in the HTML. A blue circle means that an activity signal was detected. It does not guarantee that the recipient read the message.

Not for bulk

There are no lists, sequences, or campaign analytics. If you need those, pick a sales suite. SentCue is for individual mail you already write in Gmail.

How to turn tracking off

Global Off in the popup stops new pixels. Per-message Off in compose skips that send. Delete tracking data for this install clears local history and asks the origin to drop install-scoped rows. Removing the extension also clears local storage.

Get the extension