What we store (and what we never do).
Subject, recipients, send time, open events. Zero message content: not the body, not attachments, not even a preview.
For every tracked email, MailViewed keeps the subject, the recipients, and the send time, plus the open/click events that happen afterwards. A few housekeeping fields sit alongside them: the web addresses of any links you chose to track, and when a reply was seen. To see the full record for any email, open it in the dashboard and expand What we store about this email.
On your account we also keep a few setup dates: when the extension first linked, the last day it was active, when your first email was tracked, and when you hid the setup guide if you did. They are listed in the Privacy Policy.
We never store
- The body of your email, not even a preview or first line
- Attachments: during a Compose send they exist in memory only for the seconds it takes Gmail to accept the email
- Your inbox, drafts, or any email you didn't choose to track
- Reader locations: we don't geolocate opens
During a Compose send, your message transits our server encrypted (AES-256-GCM) purely to be handed to Gmail, then is hard-deleted. A group email sent as individual copies (Pro, on by default once you connect Gmail; you can turn it off in Settings) also passes through our server: it's held in memory only while each person's copy is handed to Gmail, and none of it is kept. More on how we handle your data is in the Privacy Policy and Security page.
Skeptical? Good. In Chrome, open chrome://extensions, turn on Developer mode, and click service worker under MailViewed to open the extension's own DevTools. Send a tracked email from Gmail and its Network tab shows the request: subject, recipients, and links. No body field exists in the payload. The one exception is a Pro group email sent as individual copies: that request carries the message, with any images and attachments, so each person's copy can be sent through your Gmail. It passes through and is never stored.