Privacy policy

Last updated 19 August 2026

This document needs review by a qualified lawyer before launch. It accurately describes what the software does — the data flows below were written from the source code — but it has not been reviewed for legal sufficiency in any jurisdiction.

EmailTrackApp tells senders when their email was opened. This page explains exactly what we collect, from whom, and why. Two groups of people are involved and they are treated differently: users, who install the extension, and recipients, who receive a tracked email and never agreed to anything.

What we collect from users

DataWhy
Email address and password hashTo create and secure your account
Subject line and recipient addresses of tracked emailsSo your dashboard can show which email an open belongs to
Hashed IP addresses you connect fromTo recognise and exclude your own opens of your own sent mail
Plan and billing statusPayment is processed by Stripe; we never see your card details

What we never collect

What we collect from recipients

When a recipient's mail client loads the tracking pixel, our server records:

We do not build profiles of recipients. Events belong to the user who created them and are never combined across accounts. We do not sell or share this data.

How a recipient can refuse

Anyone can enter their address on our opt-out page. From that moment no EmailTrackApp user can add a read receipt to mail sent to that address, and existing tracking records for it are deleted. No account is required and it does not expire.

Retention

Detailed open events are deleted after 24 hours for filtered events, and after your plan's history window for counted opens. Aggregate counts are kept with the email record. Deleting your account removes everything associated with it.

Sub-processors

ProviderPurpose
SupabaseDatabase, authentication and serverless functions
Google Firebase HostingServing this website
StripePayment processing

Contact

Questions, access requests or deletion requests: privacy@emailtrackapp.com.