Public layer
Plain-text addresses on personal pages, forums, and documents are easy for automated collectors to harvest. Replace them with a contact form or dedicated alias.
Tiered self-check
Email privacy audit: Where is your real address exposed?
Select what applies to you to see your exposure level and priority actions. Results are calculated in your browser; you never need to enter your real email address.
Six signals: select what applies now
Current recommendation
Low exposure: Keep one-time interactions separate from long-term accounts, and review old subscriptions regularly.
Layer by source
Exposure is not a switch—it is a relationship map
Public listings, transactions, identity accounts, and one-time sign-ups carry different risks and require different priorities.
Transaction layer
Stores need to send ongoing updates, but they do not need your primary email. A unique alias for each store can pinpoint the source of a leak.
Identity layer
Banking, government, and work accounts are responsible for account recovery. Use a long-term, controlled address and enable multi-factor authentication.
Trial layer
Unfamiliar tools and one-time downloads only need short-term access to your inbox. A disposable email helps limit the spread of marketing lists.
Social layer
Communities and events often last for a while. A forwarding alias is easier to retire and trace than an address that expires.
Legacy layer
Accounts you have not used for years may still expose an old address. Close them or update recovery details to reduce dormant risk.
Repair order
Protect identity first, then reduce noise
Do not migrate every account at once. Handle them in batches based on potential impact and how difficult each one is to replace.
Protect core accounts
Verify recovery email addresses, strong passwords, and multi-factor authentication to avoid losing access when an old address is compromised.
Remove public addresses
Replace plain-text addresses on webpages and address the entry points most likely to be harvested in bulk.
Separate high-noise sources
Use different aliases for shopping, subscriptions, and communities so you can pause and trace them easily.
Make one-time interactions temporary
Use short-term addresses for trials and downloads instead of adding new exposure to your primary email.
Audit scope
What this self-check reviews—and what it does not decide for you
Review public entry points
Check whether public pages, order contacts, and subscription sign-ups share an address, and note which relationships a leak could affect.
Consider the cost of revocation
Assess whether an entry point can be disabled on its own without changing your banking, work, and family contacts at the same time.
No email access
Your selections are calculated on this page only. You do not need to upload email content, contacts, or historical addresses.
Not a security checkup
Address separation cannot replace strong passwords, one-time codes, and device security. Harden important accounts independently.
| Relationship type | Recommended retention | Boundary action after exposure |
|---|---|---|
| One-time download | Keep briefly after verification | Stop using the temporary entry point |
| Regular subscription | For as long as the relationship lasts | Pause the corresponding alias |
| Order support | Reassess after the warranty ends | Keep proof, then change the entry point |
| Core account | Long term | Switch to a dedicated address and review login activity |
The audit reflects only the exposure signals you select. It does not scan other websites or change any email automatically. If the same address serves both core accounts and public listings, moving public relationships first is usually safer than immediately changing every important account.
After layering your addresses, record each purpose in a trusted password manager or personal list and regularly review relationships that are still active. If you receive a reset email from an unknown source, access the account independently through its official website to verify it.