Check it yourself

Do not take our word for it. These checks take about a minute and work for any extension.

1. Open your extensions page

   Copy this address, open a new tab and paste it in. Then find MailAfter and choose Details.

   chrome://extensionsCopy

   Chrome does not let websites open this page, so it needs a copy and paste.

2. Site access

   You should seeOnly mail.google.com and mailafter.app. That is how it adds the tracking pixel to the emails you send. No other sites.

3. Permissions

   You should seeChrome may list “Block content on any page”. MailAfter uses it only so your own browser does not load its pixel, which keeps your own views out of the count. Nothing about your browsing history.

4. Your Google account

   Open the list of apps and services connected to your Google account.

   Open Google permissions ↗

   You should seeMailAfter is not on the list. It never asks you to sign in with Google, so there is nothing to revoke.

5. The manifest (for developers)

   On the Details page, copy the extension ID. Then open this address in a new tab, with your ID in place of <ID>:

   chrome-extension://<ID>/manifest.json

   You should seeTwo permissions (storage and declarativeNetRequest), one host (mailafter.app), and content scripts only on Gmail and the connect page. No oauth2 and no identity.

   "permissions": ["storage", "declarativeNetRequest"],
   "host_permissions": ["https://mailafter.app/*"],
   "content_scripts": mail.google.com/*, mailafter.app/connect*
   // no "oauth2", no "identity"

6. What it does read

   While you write an email, the extension reads its recipients and subject in your browser. It sends MailAfter the To, Cc and subject, so your dashboard can show which email was opened. Bcc and the message text are never sent. Your never-track list stays in your browser.

Questions? Write to support@mailafter.app.