The idea in one sentence

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

A visible address is scraped, copied and retained far beyond its original page. Consider this ordinary moment: a genuine collaboration sits beside hundreds of automated pitches. Without a boundary, the consequences can spread beyond the relationship that created them.

How to put it into practice

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

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

Reply behaviour can expose an underlying address if the service does not preserve the alias. 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