Before you share the address

Pause at the point where a convincing security warning arrives at the address printed on your profile. Ask whether the relationship is temporary, whether recovery matters and what would happen if the address became public.

The checklist

  • Hide recovery routes
  • Use unique credentials
  • Review discoverability settings
  • Keep public contact replaceable

Write down the purpose beside the credential. A label is small operational memory: it prevents a random-looking address becoming another mystery.

After the first message arrives

Confirm that the route works, that replies behave as expected and that important mail is not being forwarded somewhere unsafe. If the relationship grows, extend the lifetime before it becomes urgent.

Review without over-managing

Separate public contact from the address that unlocks the account. Review on change—not every day. Platforms may still correlate activity using phone numbers, devices or payment details.

Give the next relationship its own route.

Create an MXDuck alias