Protecting an email address when signing up for food delivery means giving each delivery app a separate email alias instead of a primary address. DoorDash, Uber Eats and Deliveroo each collect a name, email address, phone number, delivery address and payment information at signup, and the alias keeps order mail, marketing and breach exposure contained to one app while the account is in use.
What delivery apps hold after signup#
A food delivery account links an email address to a physical front door. The courier receives the name and drop-off address for every order. The account also holds a payment method and a full order history. The email address is the account identifier, password reset route, receipt channel and marketing channel, all attached to that home address and payment method.
The three largest services collect the same core details, according to their own privacy policies, and differ only in the extras each policy lists.
| Detail collected | DoorDash | Uber Eats | Deliveroo |
|---|---|---|---|
| Name, email address and phone number | Yes | Yes | Yes |
| Home or delivery address | Yes | Yes | Yes |
| Payment information | Card details processed by payment providers, last four digits stored | Payment or banking information | Card numbers collected by payment providers |
| Order history and items ordered | Yes, with transaction amounts and merchants | Yes | Yes, with order notes |
| Location data | Precise geolocation if the user consents | Precise or approximate location from order request to completion | Longitude and latitude on ordering |
| Extra sources | Activity and special instructions | Guest checkout covered | Date of birth for age-restricted items; data from fraud detection providers, advertising platforms and data brokers |
DoorDash's consumer privacy policy, last updated 15 September 2025, lists the contact details above. Uber's privacy notice covers order recipients on Uber Eats at account creation or guest checkout. Deliveroo's privacy policy lists the same details on account creation. Deliveroo is now part of the DoorDash, Inc. group of companies.
DoorDash's policy also states that personal information is used to advertise its services on third-party websites and platforms. Deliveroo's policy states that it collects information from third parties, including fraud detection providers, online advertising platforms and data brokers. DoorDash offers an opt-out of sale or sharing.
Two breaches of delivery data#
Two confirmed breaches exposed the same combination: an email address next to a home delivery address and an order history.
In September 2019, DoorDash confirmed an unauthorised access to user data that had happened on 4 May 2019, through a third-party service provider. About 4.9 million consumers, Dashers and merchants who joined on or before 5 April 2018 were affected. The data accessed included names, email addresses, delivery addresses, order history, phone numbers and hashed and salted passwords, plus the last four digits of some consumers' payment cards and driver's licence numbers for about 100,000 Dashers, while full card numbers and CVV codes were not accessed. TechCrunch and The Register reported the disclosure, both quoting DoorDash's own statement.
In June 2020, Delivery Hero confirmed that its Foodora brand had been breached. The exposed data had been found online on 19 May 2020. Delivery Hero's security teams validated a database of about 480,000 email addresses, containing unique email addresses, encrypted password hashes, name, delivery address and phone number. Customers in 14 countries were affected. The data dated back to 2016. No financial data, clear-text passwords or geolocation data was exposed. The confirmation was reported by Infosecurity Magazine.
A message that names a real restaurant, a real order and a real street address is harder to spot as fake than a generic phishing email. Order history records what a person eats, when they order and where they live.
Why the address outlasts the password#
A breached password can be changed. A breached email address cannot be withdrawn from breach data once exposed. Password resets, order confirmations, receipts, refund notices and marketing all go to it, and it stays in circulation in breach data and marketing lists after the password has been replaced.
The risk spreads when the same address is used elsewhere. If the delivery address is also the bank account address, a breach of the delivery app hands an attacker the exact address to target with phishing for the bank. A separate address for the delivery account breaks that link.
Separate aliases for separate apps#
An email alias is a dedicated forwarding address given to one service instead of a primary email address. Mail sent to the alias arrives in the real inbox, and replies go back through the alias so the real address stays hidden. What an email alias is explains the mechanism in full.
Setup follows the same pattern as any other account: the user creates one alias for the app and enters it as the email address at signup. Order confirmations, receipts and password resets arrive at the alias. They forward to the real inbox. If the app is breached, the exposed address is the alias, not the primary inbox. If the alias starts receiving spam, the source is known: that alias was given to one app only.
Separate aliases make the source visible. One shared alias for DoorDash, Uber Eats and Deliveroo tells the user nothing when spam arrives. Three aliases, one per app, name the source. The same principle applies to shopping accounts, as described in the guide to a separate email for online shopping.
The alias also limits the damage after a breach. The account password still needs changing, and the exposed address should still be checked on Have I Been Pwned, which lists 1,053 pwned websites and more than 17.8 billion pwned addresses. The primary email address was never in the breached database, so it does not join the lists that circulate afterwards. The steps for disabling a spammed alias are covered in what to do when an alias starts getting spam.
AliasFleet provision for delivery accounts#
AliasFleet provides managed email aliases that forward to a verified destination inbox. The Free tier includes 10 active forwarding aliases, 3 personal subdomains, 1 verified destination inbox and 50 MB of monthly forwarding bandwidth, with two-way reply forwarding included. The Pro plan is $7 per month under the Founder's Club, with a $12 list price, and adds unlimited aliases, vendor leak detection and tracker pixel and UTM stripping. The current pricing is published at AliasFleet pricing.
AliasFleet is not a disposable email service. Aliases are persistent forwarding addresses under the user's control, staying active until the user disables them. That matters for a delivery account, because the alias is the account recovery address. How email aliases actually work describes the forwarding and reply mechanism, and whether email aliases are safe covers what an alias does and does not protect. Ten free aliases cover several delivery apps with room left over, and each app gets its own.
An alias does not hide the home address or the payment method from the app, and it does not fix the app's security. It protects the email address only.
Alias lifetime and account recovery#
The alias for a delivery app must stay active for as long as the account is in use. A short-lived address is the wrong tool for an account holding a payment method and a home address, because the email address is how the account is recovered and order problems are resolved.
If the alias is disabled while the account is still active, password resets and refund notices stop arriving, and the user cannot prove ownership of the account by email. The app still holds the home address and the payment method. The alias is disabled only when the account behind it is closed or no longer used.
Two-factor authentication codes arrive at the alias too, since it is the account email address. Receiving two-factor authentication codes at an email alias explains how the codes arrive and what to check if one is delayed. Whether an alias can be used for account recovery covers recovery in more detail.
Signup timing and address changes#
The alias is set up before the first order, at signup, when the app asks for an email address. The user creates the alias first, then enters it on the signup form, and the confirmation email arrives at the alias and forwards to the real inbox. How to set up an email alias walks through the creation steps.
For an existing account, the email address can usually be changed in the account settings to the new alias. Order history and the payment method stay attached to the account, because only the email address changes. The old address remains in the company's past records and in any breach data already taken, so the change limits future exposure rather than erasing past exposure.
Some apps reject alias addresses at signup, usually because the alias domain appears on a blocklist. When a service will not accept an alias email covers the workarounds, including using a subdomain or a custom domain.
Order mail and the primary inbox#
A delivery account generates more mail than the account itself. Order confirmations, courier updates, receipts and marketing arrive in a steady stream, and the retailer and carrier emails that follow an order form a separate stream. How to protect email for delivery notifications covers that notification stream and how to keep it out of the primary inbox.
A primary email address is a single point of failure. AliasFleet states it directly: banking, shopping and personal accounts all share the same address, and a single third-party breach exposes it everywhere. One alias per app limits what a breach of the app can take from the user, and it names the source when the mail that follows is unwanted.
