Choose one trigger

Use the moment a new relationship asks for an address as the trigger. Decide its category, recovery need and likely lifetime before typing the familiar address from muscle memory.

Make the routine small

Pair a per-service alias with a unique password or passkey. Then label it and store it with the account. Those two steps turn separation into a repeatable habit rather than a collection of unexplained aliases.

  • Generate unique passwords
  • Store the matching alias
  • Enable strong MFA
  • Update both after a breach

Review when something changes

A breach, a new subscription, the end of a trip or a change of employer is a natural review point. You do not need a daily dashboard for quiet addresses.

Keep the system humane

Aliases complement strong authentication; they do not replace it.

A privacy habit should return attention, not consume it.

Give the next relationship its own route.

Create an MXDuck alias