A waitlist is an opt-in list of people who want notice when a product, or a specific feature, becomes available. Protection for a waitlist signup rests on one method: the subscriber creates a separate alias for each waitlist, which stays live until the launch invite arrives and is closed after that point. The address given at signup remains on the list for the whole interval between signup and launch. A separate alias keeps that address apart from the main inbox for the full interval.
What a waitlist collects
Loops defines a product waitlist as an opt-in email list of people who want to be told when a product, or a specific feature, is available. Most waitlists collect an email address. Some also ask for a name, a company, a role, or an intended use. The list gives the product a launch-day audience before there is anything to sell. That audience is the purpose of the list. A waitlist marketing guide notes that a waitlist validates interest in a pitch, not demand for a product. A long signup list therefore shows interest in the pitch. It does not by itself show demand for the finished product.
Length of the wait
The wait is long by design. LaunchList puts the optimal start window at 2 to 6 months before launch. Earlier signups go cold before shipping. Later signups miss the chance to build a launch audience. The mail sequence after signup follows a set pattern: a welcome message arrives immediately, progress updates follow every 2 to 4 weeks, a launch-week teaser comes next, and the launch-day invite closes the sequence. Waitlister sets out the same lifecycle in nine steps, from the signup page and welcome message to keeping the list warm until launch and deciding when the waitlist ends. Loops names months of silence followed by a launch message as the common failure. Subscribers forget the signup by then.
Exposure of a waitlist address
A waitlist address carries three risks, and each one follows from the length of the wait. The first risk is volume. One signup can produce a welcome message, regular updates, a teaser, a launch invite, and then ongoing product mail. The waitlist often converts into the customer list at launch. The second risk is memory. After months of silence, a launch message from a forgotten signup reads as mail from a stranger. The third risk is exposure. The address sits in the operator database for the whole wait. Every database that holds an address can leak it. The list can also pass to a new owner if the product is acquired.
The scale of breach exposure is large. Have I Been Pwned reported 1,048 pwned websites and 17,846,896,404 pwned addresses on its homepage as crawled on 2026-10-30. An address unique to one waitlist changes the result of a leak. The leak names the source, because no other product holds the same address. Closing the alias stops mail to the leaked address. No other signup is touched. List sharing is a separate risk. An operator can move the list into a general marketing list at launch. A closed alias still stops later mail, even if the address remains on that marketing list.
One alias for each waitlist
One alias for each waitlist means one forwarding address for each product on the waitlist. The alias carries a label naming the product. Mail sent to the alias arrives in the main inbox while the alias stays active. When the wait ends, the alias is deactivated or deleted. Mail to it then stops. The main inbox address never appears in the waitlist database. A leak of that database exposes the alias. It does not expose the main address.
The timing of closure matters because the launch invite is the reason for the signup. An alias that stays live until the invite arrives receives the invite. An alias that is closed early loses the invite. No second copy exists. The sequence is fixed: the alias is created at signup, stays active through the wait, receives the invite and serves account setup, and is closed only after the account exists or after the wait ends without a launch.
Other address options
Plus addressing is the cheapest version of the same idea. RFC 5233 defines subaddressing as augmenting the local part of an address with detail information, commonly with a "+" separator, for example ken+sieve@example.org. Cloudflare describes the same mechanism in its Email Routing product, where mail to user+detail@example.com is captured by the user@example.com address. Plus addressing has two limits for waitlists. The first limit is exposure. The base address sits inside every plus address in plain view. Anyone who strips the detail part reaches the main address directly. The second limit is acceptance. Some mail systems refuse addresses with a "+" sign. Some waitlist forms strip the detail part or reject the address outright. A full alias is stronger on both counts. The main address is not visible in the alias. The alias can be closed without affecting the main address.
Apple Hide My Email generates unique, random email addresses that forward to a personal email account. Addresses no longer needed can be deactivated or deleted. With Sign in with Apple, the address uses @private.icloud.com or @privaterelay.appleid.com, and that address is tied to the app or website the account was created with. It follows the same pattern as a per-waitlist alias, with each signup given its own address that can be closed when the wait ends.
Domain filtering at signup
Some waitlists block alias domains, and that limit has to be stated plainly. A signup form can reject an address based on its domain before any mail is sent. Auth0 documents a pre-user registration action that parses the email address, checks the domain against an allowed list, and returns an invalid-domain error when the domain is not allowed. Any site can filter domains at signup. The effect depends on the kind of alias. A shared alias domain is visible as a domain used by many people for many signups. A blocklist can name it directly. An alias on a domain the subscriber owns is harder to list. That domain is not shared with other subscribers.
No primary study measuring rejection at waitlist forms was found in this research pass. No rejection rate is claimed here. A rejected signup leaves two options. The subscriber can use the main address with a filter. The subscriber can skip the waitlist. An address that stops working before launch is not a safe option. A launch invite sent to an address that no longer works never arrives.
Opt-out rules
Opt-out rights exist, but the rights work slowly, and that slowness is part of the case for an alias. The FTC states that a sender must honour an opt-out request within 10 business days. The opt-out mechanism must be able to process requests for at least 30 days after the message is sent. Once a person has opted out, the sender cannot sell or transfer the address, even as part of a mailing list. The FTC guide also states that each separate email in violation can carry a penalty of up to $53,088. Ten business days is a long time when the mail is unwanted. The opt-out covers future marketing mail, not the launch invite itself. A subscriber who opts out during the wait may miss the launch invite. The opt-out stops mail from that sender.
An alias avoids that trade-off: the alias stays live through the wait, receives the invite, and is closed after the account exists, with no request to the sender and no 10-business-day delay. The ICO states that PECR sets the rules for sending electronic mail marketing, and that a person who exercises the right to object must stop receiving direct marketing, with no grounds to refuse. Closing an alias does not depend on the sender at all. Mail to a closed alias has nowhere to go.
AliasFleet and waitlists
AliasFleet provides managed, persistent email aliases that forward to a verified destination inbox, with one alias per signup and a control to disable any alias. The AliasFleet homepage describes the model as one alias per website, with the moment spam arrives naming the source, and the alias disabled in one click while the main address stays clean. For waitlists, a subscriber creates one alias per waitlist and labels it with the product name. The alias stays live until the launch invite arrives. After the account is set up, or after the wait ends without a launch, the alias is disabled. Later mail from that list then stops.
The free tier covers the waitlist case without a payment. The AliasFleet pricing page states that the free tier includes 10 active aliases, 1 verified destination inbox, 3 managed subdomains, and 100 MB monthly forwarding bandwidth, with two-way reply routing. Ten aliases cover ten concurrent waitlists. Paid tiers add custom domains and unlimited aliases. A custom domain matters when a subscriber wants aliases on a domain that is less likely to be blocklisted at signup. The AliasFleet documentation covers alias creation and custom domain setup for subscribers who want to move from a shared alias domain to a domain of their own.
AliasFleet does not do two things that matter for waitlists. It does not control the waitlist operator database. It cannot stop an operator from storing the alias or sharing it. It also does not receive a launch invite sent to a closed alias. The alias must stay live until the invite arrives. An alias limits what is exposed and where later mail can go. No claim is made here that an alias blocks tracking.
Closure at the end of the wait
The end of a waitlist arrives in one of three forms. The first form is a launch invite followed by account setup. The second form is a launch without an invite, where the product opens to everyone. The third form is silence, where the product never ships. In each form, the closing step is the same: the alias is deactivated or deleted, mail to it stops, and every other signup stays intact because no other alias was touched. A waitlist signup made with the main address leaves no such record. The only exit is an opt-out request to each sender, honoured within 10 business days. The alternative is a filter rule that hides the mail without stopping it. One alias per waitlist gives the subscriber an exit that works even when the sender does not cooperate. That exit covers a signup that may last months and may never lead to a product at all.
Top comments (0)