What stays the same

Both choices can receive legitimate mail. Neither guarantees anonymity, trustworthy senders or secure accounts. You still need unique authentication and a dependable recovery plan.

What changes

With a public contact alias, you can apply this principle: treat public contact as infrastructure designed to absorb exposure. With a private account address, a visible address is scraped, copied and retained far beyond its original page. The value is containment rather than invisibility.

A separate route changes the size of the clean-up.

How to choose

Use the simpler option when the consequence is small and the relationship is short. Choose stronger separation when recovery, public exposure or cross-context matching would matter.

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

The honest caveat

Reply behaviour can expose an underlying address if the service does not preserve the alias. Make the decision for the risk you actually have, not the most dramatic risk you can imagine.

Give the next relationship its own route.

Create an MXDuck alias