The ordinary moment

A genuine collaboration sits beside hundreds of automated pitches. Nothing looks dangerous. That is why the decision is useful: privacy habits work best before a message becomes urgent.

The small choice

Treat public contact as infrastructure designed to absorb exposure. Record the route with the account and continue normally. There is no disguise, dramatic tool or complicated ritual.

What happens later

Months later, the address may receive a strange promotion, a security warning or a recovery message. Because the route has context, you know where to investigate and what can be replaced without disturbing everything else.

Context turns a surprising message into a smaller question.

The lesson

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

Reply behaviour can expose an underlying address if the service does not preserve the alias. The boundary provides evidence and control; judgement still decides what to do.

Give the next relationship its own route.

Create an MXDuck alias