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

Treat public contact as infrastructure designed to absorb exposure. 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.

  • Publish a dedicated route
  • State useful contact boundaries
  • Check reply identity
  • Replace it when abuse wins

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

Reply behaviour can expose an underlying address if the service does not preserve the alias.

A privacy habit should return attention, not consume it.

Give the next relationship its own route.

Create an MXDuck alias