MailSignals

Features

Everything it does, and what it refuses to claim.

Eight capabilities, each written up from the code with its limits stated. The differentiator is not a longer list. It is that every number on screen can be defended in one sentence.

The vocabulary

Six glyphs in Gmail, one per status. Hover any of them and the tooltip says what is known and, when the answer is uncertain, why.

Sent, nothing yet
✓✓Delivered to Apple Mail; read unconfirmed
✓✓Opened by a person
A link was clicked
A reply arrived
Delivery failed

Replies outrank clicks, clicks outrank opens, and a bounce is shown only when nothing was read, clicked or replied to and every recipient hard-bounced. One bad address among several never hides what the others did.

What it deliberately does not do

A tracker earns trust by the claims it declines to make. These are the ones MailSignals declines.

It will not tell you

  • That someone read your email when all it saw was a proxy prefetch. Apple Mail Privacy Protection downloads are reported as delivery, never as a read.
  • Which recipient of a group email opened it. One message carries one pixel, so an open means someone did.
  • Whether a recipient deleted, archived or reported your email. Nothing leaves their mailbox when they do, so no tracker can see it.
  • That an unrecognised client was a person. An unrecognised fetch is recorded in the timeline and counted nowhere.
  • A read count that a mail proxy hid. A proxied open is labelled a lower bound.

It does not include

  • Mass mailing, campaigns or mail merge. This is for the email you write one at a time.
  • A CRM pipeline, e-signatures, document tracking or video messages.
  • A mobile app or an Outlook add-in. The extension runs in Chrome and Edge on Gmail in the browser.
  • Per-recipient tracking of group emails, which commercial trackers do by re-creating one message per recipient through the Gmail API.
  • Any access to your mailbox. Sign-in requests openid, email and profile, and nothing else.

Every setting

The dashboard and the extension's options page expose the same settings; a change in one reaches an open compose window within a minute, without a reload.

Settings sections and what they control
SectionWhat it controls
Tracking defaultsTrack new emails by default; track links by default; rewrite links whose visible text is a bare URL (on); an optional one-line disclosure footer with editable text; a do-not-track domain list.
What counts as an openStrict counts only direct fetches. Normal, the default, adds proxied opens from Gmail, Outlook and Yahoo. Lenient also counts Apple Mail delivery prefetches.
NotificationsDesktop notifications, in-Gmail toasts, every open or first open only, clicks, replies, and quiet hours that may wrap midnight.
AlertsThe hot-conversation threshold (3 opens in 10 minutes), the revival gap (7 days) and the follow-up reminder (3 days). Zero disables one.
Summary emailDaily or weekly, at an hour you choose, in your timezone, only when something was sent.
PrivacyEvent retention in days, where 0 keeps everything. Sender view signals and unmatched hits are always pruned after seven days.
Gmail accountsEvery Gmail address the extension has seen, with Tracked, Needs a decision or Ignored, and the number of sends refused.
Agent keysMint, name and revoke keys for programs that send through the Gmail API; copy a ready-made MCP configuration.
Export and deleteMessages, events, contacts and links as CSV or JSON. Delete everything, confirmed by typing the phrase, keeps only the account and its settings.

Defaults are read from DEFAULT_USER_SETTINGS in the shared package. Changing a default never changes a stored account: an explicit value survives.

Run it in your own project.

One Firebase project, two subdomains, one deploy script. About an hour the first time, and no subscription afterwards.