DEV Community

Ahsan Luqman
Ahsan Luqman

Posted on Originally published at aliasfleet.com on

A separate email alias per booking keeps each trip organised

An email alias for a travel booking is a separate forwarding address used for one trip or one booking provider. Mail to the alias forwards to the main inbox, and the alias stays live until the trip and any refund, compensation or dispute window close, then it is paused. Confirmations, boarding passes, itinerary changes, receipts and refund messages arrive through the alias, together with later marketing from each company on the booking. A booking therefore forms a bounded episode with a definite end, and the alias for that booking ends at the same point as the follow-up for the episode.

Booking message types

A booking produces confirmation mail recording the booking and the price, itinerary mail recording changes to times, gates, rooms or dates, check-in mail carrying boarding passes or check-in links, receipt and refund mail recording payment, partial refunds and compensation claims, and marketing mail promoting future trips, similar routes, partner hotels, car hire, insurance or loyalty offers. Transactional mail and marketing mail fall under different rules, and that split explains why stopping one kind does not stop the other. The Federal Trade Commission states that a commercial message must include a clear way to opt out of future marketing mail and that opt-out requests must be honoured within 10 business days, while transactional or relationship messages, such as messages confirming a transaction already agreed to, are treated differently. Marriott states the same split for its guests: opting out of marketing mail does not stop transactional messages about reservations, stays and account security, and marketing preferences can be changed through the unsubscribe link in a promotional message or through account profile settings. Booking messages continue while the reservation exists, even after marketing stops.

Alias patterns for trips and providers

Two patterns cover most bookings, and the pattern chosen decides what the alias represents. One alias per trip uses a single address for every booking on one journey, so the flight, hotel and car hire for the same holiday share one alias. One alias per provider uses a separate address for each company, so the airline, hotel and booking platform each receive a different alias. Both patterns forward to the same main inbox, so mail is still read in one place, and the difference appears later, when a message arrives and the source company and the booking it belongs to must be identified. One alias per trip is simpler to set up and simpler to pause, because only one address is switched off when the trip is over, but marketing from every company on the trip then arrives on the same address and the source of a later message is less clear. One alias per provider takes more work at booking time, because each checkout form needs a different address, but it gives a precise record, so marketing on the airline alias comes from the airline. A middle pattern also works, with one alias per platform for bookings made through that platform and direct airline or hotel bookings on their own aliases. Each pattern trades setup effort against tracking precision, and in every case the alias represents a bounded relationship that ends when the trip and its follow-up end.

Airline messages

Airlines send booking messages to the address given at checkout, and those messages carry the details needed to travel. ITA Airways states that online check-in, ticket change, refund, upgrade and price blocking services send notifications, including messages containing boarding passes, information on requested changes and refunds, to the address provided, and that those messages may include the booking code and ticket identification number. A changed flight, refund or upgrade notice has no value if it goes to an address already switched off, which is why the booking code in those messages sets the minimum life of the alias. Airlines also use the booking address for marketing, under rules that differ by airline. Lufthansa states that, without separate consent for marketing, it may contact a customer who has already booked by mail about similar offers and services, but only where the address was received in connection with a sale, the marketing is for its own similar goods or services, and the customer has not objected. Consent for promotional notifications can be withdrawn at any time, and Lufthansa also states that an objection to marketing does not automatically delete booking data or a Travel ID, so stopping marketing and keeping the booking record are separate actions. Flysair states a narrower version of the same pattern: marketing communications are sent intermittently if the traveller agreed to special offers and product mail during booking, offers may include money off future bookings, ticket sales, airline news or promotional material with payment partners, and marketing can be stopped by leaving the relevant box unchecked at booking or by using the unsubscribe link in a marketing message. Flysair also states that it does not share personal information and contact details with other companies for marketing purposes without consent. Partner offers are a further category of airline mail: a booking address can receive offers mentioning a partner even when the traveller booked with one airline only.

Hotel and platform messages

Hotels and booking platforms add a second layer, because a booking made through a platform involves both the platform and the property. Booking.com states that trip reservation communications include confirmations, modifications and reminders, and that it sends personalised marketing messages, including promotions and travel experiences, by mail and other channels. A traveller can unsubscribe from mail marketing at any time through the unsubscribe link in each communication or through account settings, so the platform sends both kinds of mail to the same address and the alias is what separates later platform marketing from the main address. Platforms also run masked addresses for guests, which is a related mechanism under different control. A guide to Booking.com guest messaging states that Booking.com uses a guest.booking.com alias for guests instead of the personal address and forwards mail sent to that alias to the guest, and the same guide states that a Booking.com alias stops forwarding once the stay is over, so post-stay messages sent to it may not reach the guest. That guide is a third-party account of Booking.com practice, not Booking.com's own privacy notice wording. Control differs between the two kinds of alias: the traveller does not control the platform alias in the same way as an alias created by the traveller. Airbnb policy adds a further limit on the host side: for reservations booked before 20 November 2026, the policy prohibits selling, sharing or using guest contact information for marketing communications or signing guests up for a contact list, and it prohibits soliciting a guest's email through the Airbnb messaging system or mail alias after a booking.

Operational notices and refund windows

Booking addresses also carry operational notices that have nothing to do with marketing. IATA Resolution 830d required travel agents from 1 June 2019 to actively ask each passenger whether contact details, including mail, should be provided to airlines on the itinerary, so that airlines could advise passengers of irregular flight operations and disruptions. Reporting on the rule states that IATA said none of the information obtained would be used for marketing or sales purposes, and that it would only be used for operational notifications like flight cancellations and schedule changes. The Travel Market Report account of the rule is the source for that statement. The address on the booking is the address that receives the cancellation or delay notice, and a traveller who changes address after booking needs to update the booking, not only the inbox filter.

The pause point is set by the trip and by the follow-up window, not by the return date alone, because a flight delay or cancellation can produce a refund or compensation claim after the traveller is home. SWISS states the EU Regulation 261/2004 compensation bands as 250 euros for flights up to 1,500 km, 400 euros for flights between 1,500 and 3,500 km and flights within Europe, and 600 euros for flights of more than 3,500 km, with halved amounts where a rerouted arrival is only slightly late, and that for delays of more than 5 hours, a refund is due within seven days for the parts of the journey not completed. The European Consumer Centres Network states the same choice for cancelled flights in the EU, Norway or Iceland: rerouting or reimbursement, plus a possible right to compensation, with 14-day and 7-day notice thresholds deciding whether compensation applies. Hotel refunds follow no single window, because the window depends on the rate, the property and the platform terms, so no single hotel refund number is stated here. The rule that transfers across cases is the order of operations: the alias stays live until the refund has arrived, the compensation claim has been answered and any charge dispute has closed, and only then is it paused.

Retention policies show why the pause point is not only about the inbox. FlyDirect states that if a traveller has opted out of marketing, data is automatically removed from its booking systems and marketing databases 180 days after travel completes, provided there are no outstanding balances, while opted-in data and booking history are retained for up to ten years or until preferences change or deletion is requested. That contrast is a company retention rule, not a rule the traveller controls. Pausing an alias still leaves the company retention rule in place, and traveller control covers the inbox channel, not the company database.


A travel booking alias stays live until the refund has arrived, the compensation claim has been answered and any charge dispute has closed, and only then is it paused.

Marketing volume and unsubscribe rules

Bulk sender rules set a floor for how marketing mail must behave, but they do not cap how much marketing a traveller receives from a company that holds a booking address. A summary of the Google and Yahoo bulk sender requirements states that senders of 5,000 or more messages a day to personal Gmail accounts must authenticate with SPF and DKIM, publish a DMARC record, offer one-click unsubscribe and keep the spam complaint rate below 0.3 percent. Those requirements make unsubscribing easier and make unauthenticated marketing harder to deliver, but they do not stop a company from sending marketing to a booking address that has not unsubscribed. Unsubscribing stops one company's marketing, while pausing the alias stops every message sent to that alias, including marketing from partners the traveller never contacted directly.

Booking aliases and loyalty accounts

Bookings end, and loyalty accounts persist, and that difference decides the alias pattern for each case. A loyalty account keeps earning points, keeps a tier and keeps sending account messages across many trips, so its alias needs to stay live across trips and is paused only if the account itself is closed. A booking alias covers one journey, or one provider's bookings for one journey, and it is paused when that journey and its follow-up are done. Mixing the two patterns creates the two common errors: a loyalty alias paused after one trip breaks the next trip's account messages, and a booking alias left live indefinitely collects marketing for years from a trip that ended long ago. Labelling each alias by what it covers at creation time turns the later pause decision into a lookup, not a guess.

AliasFleet travel booking aliases

AliasFleet provides mail aliases that forward to a destination inbox chosen by the account holder. An alias created for a travel booking forwards confirmations, boarding passes, itinerary changes and refund messages to that inbox, and the account holder can pause the alias when the trip and its follow-up window have closed. The live homepage lists the free plan as 10 active forwarding privacy aliases, 3 auto-provisioned personal subdomains, 1 verified destination inbox and 100 MB monthly forwarding bandwidth. AliasFleet does not control the airline, hotel or platform database, and pausing an alias does not delete the booking record held by the company. AliasFleet also does not change the booking itself, so a traveller who needs to change the contact address on an existing booking still needs to update that booking with the provider. A separate AliasFleet explainer describes the general pattern as one alias per website, with mail forwarded to the chosen inbox and the alias shut down when a site leaks the address, and the travel version of that pattern is one alias per trip or per provider, paused at the end of the booking episode rather than at the first sign of marketing.

Limits of booking aliases

An alias does not hide the booking from the company that received it, and it does not hide the name, payment details or travel dates from that company. It separates the contact channel, not the booking record. An alias also does not fix a booking made with the wrong address, because the provider sends operational messages to the address on the booking, and a traveller who discovers the error after booking needs to contact the provider and update the booking. A further limit is that some providers and platforms use their own masked addresses, as in the Booking.com guest alias case, and a traveller-controlled alias does not replace that system for messages the platform routes through its own channel. The method also depends on the traveller keeping a record of which alias covers which trip, because an unlabelled alias paused at the wrong time has the same cost as no alias at all. A breach check on the booking alias, for example through Have I Been Pwned, can show whether that address has appeared in a known breach, but a clean result does not prove that the address was never shared, and a breach result does not prove that the booking itself was exposed.

Top comments (0)