The idea in one sentence

Give each important relationship a labelled, controllable address. The point is not to make email mysterious; it is to stop one routine identifier doing too many jobs.

A useful boundary should make the next decision easier.

The problem it solves

One exposed address becomes a durable link between unrelated accounts. Consider this ordinary moment: a new service asks for an email before explaining how it will use it. Without a boundary, the consequences can spread beyond the relationship that created them.

How to put it into practice

  • Name the relationship
  • Choose a suitable lifetime
  • Store it with the account
  • Review it when the relationship changes

Start with the next account rather than rebuilding your entire digital life in one weekend. Label the choice so future you knows why it exists.

Know the limit

An alias separates the address, not every other identifier a service collects. Treat the address as one layer alongside unique credentials, careful recovery and sensible judgement.

Give the next relationship its own route.

Create an MXDuck alias