Free for personal use Nothing to install to check a mail We cannot see who mails whom
WhoSealed

Privacy policy

WhoSealed is built so that we do not learn who mails whom. This page lists everything we do store, where it is kept, and how to have it deleted.

Last updated 21 November 2026

If you check a seal

You need no account. Your browser turns the seal code and the address the mail was sent to into a lookup number and a key, asks us for the record with that lookup number, and opens the record on your device. We receive neither the code nor the address.

Your browser keeps two things on your device so the page can remember them: the address you entered, and the time you first checked each seal. Clearing the site data in your browser removes both.

Like any website, our server sees the internet address a request comes from. We use it to limit how many codes can be tried per minute.

If you seal your mail

We storeWhy
The e-mail addresses you verifyTo sign you in and to state which address sealed a mail.
For each sealed mail: your From address, the time, and one encrypted record per recipientSo a recipient can check the seal. We cannot open the records, but we can count them.
A fingerprint of each sign-in tokenTo keep you signed in on the website and in the add-in.
Sign-in codes, as fingerprints, for ten minutesTo check the code we mailed you.

What we never receive

The subject, text and attachments of your mail. The seal code. The addresses of your recipients: the add-in stores one encrypted record per recipient under a fingerprint that can only be computed from the seal code together with that recipient’s address.

What a seal reveals to someone who has the code

A code alone reveals nothing. Someone who has the code and knows an address the mail was sent to can see the sealing address, the time of sealing and how many recipients the mail had. They cannot list the other recipients.

Who else handles data

ProviderWhat it handles
Amazon Web ServicesHosts the server and the database, in the United States.
Amazon SESDelivers the sign-in codes, so it handles the address a code is sent to.
CloudflareSits in front of the website and passes requests on to the server, so it sees the internet address of each visitor and the requests they make.

We do not sell or share data with anyone else, show advertising, or use analytics or tracking cookies. The site sets no cookies of its own.

Licensing

We count how many senders use addresses at the same domain, and we may write to those senders about a licence when a company is using WhoSealed (see pricing).

How long we keep it

Sign-in codes expire after ten minutes. Verified addresses and sign-in tokens are kept until you remove them or ask for your account to be deleted. Seal records are kept so that old mail can still be checked; deleting an account deletes its seals, after which they can no longer be checked.

Your choices

You can remove a secondary address and sign out on the account page. To see what we hold about you, to correct it, or to have your account and all of its seals deleted, write to us from an address on the account.

Contact details will be published here.

Changes

If this policy changes, the date at the top changes with it. If a change affects people who already seal their mail, we will tell them by e-mail first.