Protecting an email address when registering for a conference means giving the registration an address separate from a main inbox. One alias per conference gives that registration its own address, so badge, ticket and sponsor mail all land in one place. The alias stays live until the event has ended and the follow-up mail the registrant still wants has arrived, then it is turned off.
Registration address sharing#
A conference registration address passes to more parties than the organiser. The registration platform collects the address first and passes it to the organiser, whose policy governs its use after registration. Eventbrite's privacy policy, last updated 15 September 2026, states that when a person registers for an event, the organiser receives that information and may then send marketing or other communications under its own separate privacy policy. Integrated Systems Europe's privacy policy for its 2027 event, last updated 27 January 2026, lists the attendee data collected at registration, including name, email address, company name, telephone number, job role and, in some cases, passport number. GDPR Article 13 requires the controller, when personal data is collected, to state the purposes and legal basis, the recipients of the data, the retention period, and the right to withdraw consent. GDPR consent rules require consent to be freely given, specific, informed and unambiguous, and withdrawal to be as easy as giving consent. A GDPR event FAQ adds that registering for a conference does not permit the organiser to hand attendee contact details to sponsors for their own marketing unless there is a separate, specific legal basis.
Attendee lists#
Many conferences publish a participant list of name, title and organisation, normally available to registered attendees only. EDUCAUSE's event policies state that the participant list includes name, title and organisation for those who have opted in. The email address is not on that list, but the name, employer and job title it shows are enough to guess a work email address. The Sports Video Group event registration policy states that attendees opt in to an attendee directory that does not display email addresses, and that the registration email address may be shared with event sponsors, on a private and restricted basis, who are instructed not to use it for mass email distribution. One event's terms, published by the Cardiac Society through EventsAir, state that if a registrant consents to be included in the list of participants, "it is likely that sponsors may add you to their mailing lists and send promotional emails to you".
Sponsor sharing after the event#
The RAK Energy Summit 2026 privacy policy states that participant details such as name, organisation, job title, email ID and mobile number "will be shared after the event to sponsors from relevant sectors as notified during registration". The same policy states that assistant data is kept for 48 months after the summit. Whether a specific conference shares registration data with sponsors depends on that conference's own policy; some share by default, some only with consent, and some not at all. ISE shares name, email address, country, company name and job role with its shareholders AVIXA and CEDIA and with sponsors and partners involved in a conference the attendee has attended, but only with consent given during registration, under GDPR Articles 6(1)(a) and 7. That consent is separate from the consent for event mail, and the webinar registration guide describes the same split on webinar forms.
Once details pass to a sponsor, the sponsor holds them in a separate mailing system under its own retention rules, so an unsubscribe sent to the organiser does not reach the sponsor. How long sponsor mail continues after an event depends on each sponsor's retention rules, which are rarely published. ISE retains personal data only for as long as necessary to fulfil the purposes for which it was collected, while RAK keeps assistant data for 48 months. No public count exists of how many conferences share registration email addresses with sponsors by default versus by opt-in, so no proportion can be stated.
Badge scans#
A badge carries a QR code or an NFC chip, which an exhibitor scans to collect the attendee's contact record. Certain's lead capture documentation states that a scan gives the exhibitor the attendee's name, organisation, job title, phone number and email. Ativ Software's BadgeScanner documentation states that the QR code printed on a badge must include the core contact information, usually first and last name, badge ID and email address, and that scanned contacts export to a CSV file for mail applications or CRM systems. A recent analysis of conference apps and badge scanners, published 31 October 2026, states that a badge scan typically hands the exhibitor the full contact record in seconds and that many attendees do not realise a scan often functions as consent to contact afterwards. The ISE policy treats a scan as consent: its section on Visit Connect states that by allowing an exhibitor to scan a badge, the attendee consents to share the contact information disclosed during registration, including email address and telephone number, and that contact information is not disclosed if the attendee does not allow the badge to be scanned. Some events let attendees choose what a scan shares, and the EDUCAUSE policies treat a badge scan as a separate opt-in from the participant list and vendor mail.
Fake attendee lists#
Scammers sell fake attendee lists, targeting attendees and exhibitors. The Vacation Rental Management Association warning states that fraudulent companies contact members, attendees and exhibitors offering attendee lists, that VRMA does not sell membership or conference attendee email contact information, and that no company is authorised to sell lists for its events. The same warning states that scammers scrape email addresses posted on websites, and that responding to these emails, even to unsubscribe, confirms a valid address. The pattern is the same across associations: NYSAIS does not sell, license or otherwise authorise the distribution of attendee lists, the International Studies Association does not rent or sell any email lists to third parties, and the Society of Petroleum Engineers does not rent, share or sell email addresses to third parties. An offer from a third party to sell an attendee list is therefore not genuine, and replying to it, even to unsubscribe, confirms the address is live.
One alias per conference#
The pattern is one alias per conference. The alias is created before registration and used on the form, in the event app and for any badge-linked account. All mail about that conference arrives on one address: confirmation, badge pickup, session changes, ticket and recording links, and post-event sponsor mail. The alias stays live until the event has ended and the follow-up mail the registrant still wants has arrived. It is then turned off, which stops the sponsor sequence without touching the main inbox or any other conference alias.
The alias forwards to the main inbox while live and is recorded with the conference name and event date. The badge, tickets and recordings all depend on mail arriving, so turning the alias off early can strand a badge pickup notice, a session change, a ticket reissue or a recording link. The event tickets guide states the same rule for ticket purchases: the alias stays live until the event has taken place and any refund window has ended. The travel bookings guide describes the same bounded pattern for booking aliases.
Three checks before submission take a minute. The privacy policy section on sharing is read first, looking for the words sponsor, partner, third party and retention. The consent boxes are checked one at a time, with the sponsor-sharing box left unticked unless the sponsor mail is wanted. The event's opt-out from the participant list is used where the name and organisation need not be visible to other attendees.
An alias changes which address receives conference mail. It does not delete the data a sponsor already holds or stop a sponsor from keeping the copy it received. Turning off an alias stops future delivery to that address, but it does not erase the registration record, the CRM entry, or any list already exported from the event system. Deletion of a copy held by an organiser or a sponsor requires a request to that organiser or sponsor, with GDPR Article 17 as the basis where the GDPR applies. An alias also does not verify a sender: a message claiming to sell an attendee list is not genuine because it arrived on the conference alias. The selling online guide makes the same point for marketplace mail: an alias contains a stream, it does not authenticate it.
AliasFleet conference aliases#
AliasFleet provides email aliases that forward to a verified destination inbox, each of which can be paused or removed on its own. A conference alias is created before registration, used on the form and in the event app, and paused or removed after the event and its follow-up window have ended. The free tier includes 10 active aliases and 1 verified destination inbox. Pro, normally $12 per month, adds more aliases, custom domains and leak detection. The pricing page lists the current tiers.
AliasFleet does not delete data held by an organiser or a sponsor, and it does not stop a conference from publishing a participant list. What it does is keep conference mail on its own address, so the post-event sponsor sequence can be stopped in one place. The docs describe alias creation and management.
