Privacy Policy

Last updated: April 29, 2026

MailPing is a Chrome extension that injects a small invisible tracking pixel into outgoing Gmail messages so you can see when those emails are opened by recipients. This page explains exactly what we do and do not collect, where the data lives, and what your choices are.

1. What MailPing collects

When you send an email with tracking enabled (green-dot ON), MailPing records:

• A randomly generated tracking ID for that email (e.g. pp_mojx1plg_xnktqwe4).
• The subject line of the email.
• The list of recipient email addresses you typed in the To/Cc/Bcc fields.
• A device ID generated locally on first use (e.g. dev_moihos3e_yex8rvm4mn) , this is a random string, not tied to your name, account or hardware identifiers.
• The timestamp the email was sent.

When the recipient opens the email and the tracking pixel loads, we additionally record:

• The timestamp the pixel loaded.
• The IP address of the device that fetched the pixel (used for proxy/Gmail-prefetch detection).
• The User-Agent string of the device that fetched the pixel.

2. What MailPing does NOT collect

• The body content of your emails.
• Attachments.
• Your Gmail password, OAuth tokens, or any login credentials (MailPing does not use Google sign-in).
• Browsing history outside of mail.google.com.
• Any data from emails sent without tracking (green dot OFF).

3. Where the data lives

• Tracked-email metadata (IDs, subjects, recipients, open timestamps) is stored both locally in chrome.storage.local on your device and on our backend at peakproductivity.online so the popup can show open events that happened while Chrome was closed.
• Pixel hits are logged on a server in Switzerland (operated by Peak Productivity).
• Backend storage is JSON-on-disk, capped at 50,000 most recent events. We do not back it up to third-party services.

4. Permissions justified

• storage , Save your license, settings, daily-quota counter, and open-event cache locally.
• notifications , Show desktop notification when a tracked email is opened.
• scripting , Inject the compose-toolbar tracking indicator and pixel logic into mail.google.com.
• host_permissions: mail.google.com , Detect Gmail compose actions and inject the tracking pixel on Send.
• host_permissions: peakproductivity.online , Verify Pro licenses and log open events to our backend.

5. Your choices

• Click the green dot in any compose window to disable tracking for that one email (no pixel injected, no record kept).
• Open the extension Options page and click "Clear all local data" to wipe everything stored on your device.
• Email support@peakproductivity.online with your device ID to request server-side deletion.
• Uninstall the extension to stop all data collection going forward.

6. Children

MailPing is not directed at children under 13 and we do not knowingly collect data from anyone under 13. If you believe we have, contact us and we will delete it.

7. Changes to this policy

If we make a material change to what we collect or how it is used, we will update the "Last updated" date above and surface a notice in the extension popup. Substantive changes will not apply retroactively to data already collected.

8. Contact

Questions, deletion requests, or concerns , email support@peakproductivity.online.