Legal · Privacy

Privacy Policy

How Fast Mail Tracker handles the Google data it needs to send your tracked email, and nothing it doesn't. Last updated September 2026.

Last updatedSeptember 2026Plain-language summary below; nothing here overrides the full text.
Google data we accessSend, and keep Sent honestThe full mail.google.com scope. We send your tracked copy as you and touch only the messages we sent for you, the draft you're sending, and the headers of a message you reply to - never the body of anything else in your inbox.
Your rightsExport, erase, disconnectRevoke Gmail access from Google or right in your Fast Mail Tracker account, any time.

What Google data we access, and why

Fast Mail Tracker connects to your Gmail with two scopes: the restricted https://mail.google.com/ scope, and the standard openid email profile scope for sign-in. We hold the full mail scope because two things the product does to guarantee accurate tracking - sending each copy as you over SMTP, and permanently removing a stray tracked copy from your own Sent folder - are authorized by no narrower scope. Everything we do inside your Gmail is listed below, in full.

Each operation is confined to a message you chose to involve: the copies we sent on your behalf (found by the exact Message-ID we generated for them), the specific draft you chose to send (by its own id), and, only when you send a reply, the Message-ID and References headers of the message you're replying to (headers only, so the reply threads correctly). We do not list, browse, or search your mailbox, and we never read the body of any message we did not send for you.

What we do in your GmailWhyGmail mechanismNarrowest scope that allows it
Send each copy as youDeliver one copy per recipient so each carries only that recipient's tracking, while everyone still sees the full To/Cc group.SMTP submission (XOAUTH2) - envelope set to one recipient, visible headers left as the full group.mail.google.com (full scope required)
Write one clean copy to your SentPlace a copy carrying only your own tracking into your Sent before recipient copies go out, so opening your own Sent copy never registers a false 'open'.messages.insertgmail.insert
Verify and clean your Sent copiesConfirm no copy of this message in your own mailbox carries recipient tracking, and repair any that does.messages.list + messages.get (find by Message-ID, read bytes), messages.modify (labels), messages.delete (permanently remove a stray tracked copy).mail.google.com (full scope required)
Read the draft you're sendingWhen your tracked send has attachments, read that one draft's contents so the files ride on every copy.drafts.get (that specific draft, by its id; we do not list or search your drafts).gmail.readonly
Thread your replies correctlyWhen you send a reply, read only the Message-ID and References headers of the message you're replying to, so your reply threads into the right conversation. No body or subject is read.messages.get (format=metadata; Message-ID + References headers only).gmail.metadata

How the access works, end to end

Two views of the same flow. The first traces the product's promise down to the only scope that satisfies it: every narrower route dead-ends before it reaches accurate tracking. The second shows the exact Gmail calls, in order, each tagged with the narrowest scope that grants it.

Loading diagram...

Why the full scope is the only route to 100% accurate tracking

Loading diagram...

Every Gmail call in the send path, tagged with its narrowest scope

Why not a narrower scope? Two of the operations above can be performed with the full https://mail.google.com/ scope and no other: submitting mail over SMTP as you - the narrower gmail.send uses the Gmail API, which derives recipients from the message headers and cannot split the SMTP envelope from the visible To/Cc line, the exact mechanism per-recipient tracking depends on - and permanently deleting a stray tracked copy, which the narrower modify scope cannot do (it can only move the copy to Trash, where its tracking pixel survives). Because the full scope is already required for those two, it also covers the read, insert, and label operations. So mail.google.com is the minimum single scope that supports the product - not a convenience.

How we protect this data

  • Encrypted in transit. All traffic - between your browser, our servers, Google, and your recipients' opens - travels over TLS.
  • Encrypted at rest. Your Google OAuth refresh token is sealed with AES-256-GCM and cryptographically bound to your account (the key is derived over your user, organization, and email), so a copied token blob is useless anywhere else. All other data, including your tracking metadata, is encrypted at rest by our managed cloud database.
  • Least access. The sealed token can be opened only by the sending service that needs it to deliver your mail; each organization's data is isolated from every other tenant's.
  • Minimal retention. We do not store your mailbox contents. For a message you choose to track, we keep the message you send through us (its subject and body) and the tracking metadata your dashboard shows (recipients, opens, clicks, timestamps), plus an encrypted refresh token so we can keep sending for you without repeated reconnects - nothing more.
  • Deletion on your command. Disconnecting Gmail revokes our access at Google and deletes the stored token immediately. Deleting your account (Settings → Delete account) revokes that Google access too and permanently removes your account, organization, and tracking data (see "Revoking access" below).

Sharing & disclosure

Google user data obtained through the Gmail send-as scope is used solely to deliver the email you compose and to insert the delivery notification into your own inbox. It is not shared with, sold to, or used by any advertiser, data broker, or third party, outside the subprocessors below required to run the service. The same list is published and kept current on our subprocessor registry.

RecipientWhyWhat they receiveGoogle data?
Google (Gmail API & OAuth)Sign-in, and sending your tracked copy as you, with your explicit consent.Your Google account identity and the message you choose to send. It's the source of your mail, not a party we hand data to.Yes
Amazon Web ServicesApplication hosting and the Postgres database the tracking API runs on.Account details and tracking data (recipients, opens, clicks, timestamps), including data derived from your Gmail connection, encrypted at rest.Yes
CloudflareNetwork edge in front of this site, the dashboard, and the tracking API.Encrypted traffic in transit between your browser, your recipients' opens, and our servers.Yes
Dodo PaymentsBilling - processes paid-plan checkout and subscriptions.Your name, email, and payment details when you buy a plan. Never any mail or tracking data.No

Limited Use

As required by Google

Fast Mail Tracker's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

AI & your data

Fast Mail Tracker does not use Gmail data, or any other data obtained through Google APIs, to train artificial intelligence or machine learning models - generalized or otherwise. No part of the product runs your messages through an AI model today.

What we don't do

We don't sell your data, and we don't build advertising profiles from it. Tracking data is engagement information tied to your account, for your follow-up, not a product we resell.

Your recipients

Tracking records that an email was opened or a link was clicked. It's designed as a signal for your own follow-up, not surveillance. You can turn tracking off for any individual message.

What this looks like in practice

01

We ask for the minimum

We hold the full mail.google.com scope because sending as you over SMTP and permanently cleaning a stray tracked copy from your Sent both need it - and it then covers everything else we do. We add no scope for features we haven't built, so access never exceeds what the product actually uses.

02

We don't store what we don't need

Beyond an encrypted OAuth refresh token (AES-256-GCM), the messages you send through us, and the tracking metadata your dashboard shows you, we don't keep a copy of the rest of your mailbox.

03

You hold the switch

Disconnect Gmail from Settings at any time. Disconnecting revokes access at Google and deletes the stored token immediately - not just at the app level.

Revoking access

You can disconnect Fast Mail Tracker's access to your Gmail account two ways:

  • In your Fast Mail Tracker account: open Settings → Gmail connection → Disconnect. This revokes the grant at Google and deletes the stored refresh token right away.
  • In your Google Account: visit myaccount.google.com/permissions and remove Fast Mail Tracker's access directly from Google.

You can delete your account and all its data at any time from Settings → Delete account. Deletion cancels any active subscription, revokes our access at Google, and permanently removes your account, organization, and tracking data. You can also write to privacy@fastmailtracker.com and we'll do it for you.

Your rights

You can access, export, or delete your data from your account, or by contacting us. Where the GDPR applies, you have additional rights described in our GDPR compliance guide.

Privacy, answered

Google data

Does Fast Mail Tracker read my inbox?+
No. We read our own sent copies back (matched by the exact Message-ID we generated) to confirm your Sent copy carries no recipient tracking, we read the one draft you chose to send so we can carry its attachments onto every copy, and when you send a reply we read only the Message-ID and References headers of the message you're replying to so the reply threads correctly. We never list, browse, or search your mailbox, and we never read the body of any message we didn't send for you.
Why does Fast Mail Tracker need the full mail.google.com scope instead of gmail.send?+
Two reasons, each of which requires the full scope on its own. Per-recipient group tracking needs one delivery per recipient with the SMTP envelope split from the visible To/Cc line, which only SMTP submission (XOAUTH2) supports - the narrower Gmail API scope derives recipients from the headers and can't split them. And we permanently remove any stray recipient-tracked copy from your own Sent folder, which the narrower modify scope can't do: it can only move the copy to Trash, where its tracking pixel survives.
Is my Gmail data used to train any AI model?+
No. Fast Mail Tracker doesn't use Gmail data, or any Google user data, to train AI or machine learning models of any kind.

Your data

What do you store, exactly?+
An encrypted OAuth refresh token (AES-256-GCM) so we can keep sending on your behalf, the messages you send through us (subject and body), and the tracking metadata your dashboard shows you (recipients, opens, clicks, timestamps). We don't store the rest of your mailbox.
How do I disconnect Gmail?+
Settings → Gmail connection → Disconnect, inside your Fast Mail Tracker account. It revokes the grant at Google and deletes the stored token immediately. You can also remove access directly from Google at myaccount.google.com/permissions.
Can I delete my account and data?+
Yes - open Settings → Delete account to permanently remove your account and all its data yourself; deletion also revokes our access at Google. You can also write to privacy@fastmailtracker.com and we'll do it for you.

Questions about this page? Write to privacy@fastmailtracker.com or contact us.

More of the fine print