Travel means handing your address to airlines, hotels, aggregators and third-party booking systems in quick succession — and unlike most signups, every confirmation genuinely matters. A missed booking reference or gate-change notice is a real problem, so this is the wrong place for a disposable address. Give each provider its own permanent alias, keep them all live through the trip, and prune afterwards.
Why travel is unusually leaky
- Aggregators sit in the middle. Book through a comparison site and your details may reach the aggregator, the airline or hotel, and the payment processor — three holders from one transaction.
- Loyalty programmes are data businesses. The points are payment for a durable marketing relationship.
- Volume is compressed. A single trip can mean eight or ten signups in an evening.
- Wifi portals everywhere. Airport, hotel, café — each wanting an address before it lets you online.
- Marketing outlives the trip by years. One hotel booking produces mail long after you've forgotten the city.
The setup
- One alias per provider, named for them:
ba@yourdomain.com,booking@yourdomain.com,hilton@yourdomain.com. - Never a disposable address. You need the booking reference, the schedule change, the check-in link and any refund correspondence. A throwaway address loses all of it. Why
- A separate burnable alias for wifi portals. These get sold reliably and you never need mail from them.
- Keep everything live until you're home and any refunds have settled.
- Then disable the ones you're done with, keeping loyalty programmes you'll use again.
The one way this setup hurts you. A cancelled flight, a rebooking, an overbooked hotel — all reach you by email at the address on the booking. Switch that off while travelling and you're finding out at the airport.
Rule: prune after the trip, never during. The general version
Practical wrinkles
- You may need to read the address aloud at a check-in desk. An argument for short, readable addresses on your own domain rather than random strings.
- Some airline systems reject unusual addresses. Rare with your own domain, more common with well-known masking domains. Keep your real address as a fallback for a booking you can't complete. How often this happens
- Group bookings. If someone else books for you, their address is on the reservation — the alias only helps for bookings you make.
- Check the address before you fly. Confirm the booking email actually arrived rather than discovering a typo at the gate.
What it buys you
Beyond the marketing control, attribution. Book a hotel through an aggregator, then start receiving mail from three unrelated travel companies at that alias, and you know exactly which link in the chain sold you on. That's genuinely difficult to determine any other way, because a travel booking touches so many parties at once.
What it doesn't do
Nothing here is anonymity — you gave them your passport details. This controls which inbox their mail reaches and tells you who passed you on. For travel specifically, that's the realistic goal. The boundary