An address is also an identifier
Email addresses are stable, easy to store and commonly collected. Two records with the same address are likely to describe the same person, even when the names, devices or contexts differ. That makes the address useful for account login—and for data matching.
The UK Information Commissioner describes data broking services that combine sources, enrich profiles and match one kind of contact detail to another. A reused address gives those systems a convenient joining key.
What the joined picture can reveal
One database may know what you bought. Another knows which newsletter you read. A public page may connect the address to a job or real name. A breach can add old passwords, phone numbers or delivery history.
No single record needs to be dramatic. The privacy change happens when ordinary fragments become one confident profile.
Correlation turns breadcrumbs into a map.
How aliases break the easy join
A unique alias gives each relationship a different key. The shop and forum can still know what you tell them, but they cannot match records merely because the email field is identical. An alias also reveals which relationship received an unexpected message.
This is compartmentalisation, not invisibility. Payment details, phone numbers, devices, cookies and delivery addresses may still connect activity. Aliases remove one of the cheapest and most reliable links.
A proportionate strategy
- Keep recovery and high-consequence addresses private.
- Use durable per-service aliases for accounts you expect to keep.
- Use a public contact alias where discoverability is the point.
- Avoid repeating identifying words in every alias when correlation is a serious concern.
- Pair separation with tracker controls and sensible browser privacy.
You do not need to create a maze no human can maintain. Start with new accounts, separate the most revealing categories, and let the map become less obvious one relationship at a time.
Give the next relationship its own route.
Create an MXDuck alias
