How do I hide the event location until people register?

Public addresses and start times are not always safe to publish. Common reasons:

• Security in wartime. In Ukraine, announcing in public where and when a crowd will gather can create risk. Many organizers share the venue only with registered guests and only shortly before the start.
• Private venues. Apartments, studios and offices whose owners do not want the address online.
• Sensitive audiences. Support groups, LGBTQ+ events, activist meetings, events for vulnerable people.
• Capacity control. Secret-location parties and pop-ups where only ticket holders should turn up.

Hiding the address is not a guarantee of secrecy — any registered guest can forward it — but it removes the details from search engines, link previews and casual browsing, and lets you decide who receives them.

Registration with QR tickets must be on. In the Registration and paid participation section open Ticket contents and choose what to keep out of the public page:

• Venue — ticket only (also available as a checkbox in the Place section);
• Exact time — ticket only — the date stays public, the time does not;
• Date and time — in the ticket only.

Visitors see a banner saying the organizer will share details only with registered participants. You set the reveal moment; until then a registered guest sees when their ticket will become available. At that moment the details appear in the ticket automatically (AET checks every 5 minutes), or you press Open now and notify to reveal immediately. Every registrant receives an email when details are revealed.

You can also add a message shown only in the ticket — for example "entrance from the courtyard, ring 12" — and a link to the event's chat or group that only registered guests see.

Give people enough time to plan the trip: if the venue may be far, reveal at least the district or metro station in the public description.

For sensitive events, add Participant selection to the registration form. People then apply instead of registering instantly; you review their answers and approve or decline. Only approved participants receive tickets, so only they get the venue at reveal time. For paid events, approved people receive a payment link by email and you set how many hours they have to pay.

• Keep the venue out of the poster and description. An AI poster writes the place onto the image when the place is part of the public event data. If you generated the poster before hiding the venue, regenerate it; also remove the address from the description, gallery captions and custom sections.
• Brief co-admins. Everyone with access to the event sees the hidden details.
• Check tickets at the door. Scanning QR codes at aet.events/qr confirms that only registered guests enter.
• Plan for air-raid alerts. In Ukraine, tell guests in the ticket message where the nearest shelter is and what happens if an alert starts.
• Do not overshare in chats. Ask guests not to repost the address publicly.

Some do in a simpler form. Luma, for example, lets organizers keep the address hidden until a guest registers (check Luma's help center for current behavior). What AET adds is scheduled reveal at a chosen moment, separate control of date and exact time, an email to all registrants at reveal, and a ticket-only message and group link. If you only need "address visible after registration", several tools can do it; if you need timed reveal for safety, check that your tool supports it.