Privacy, in plain language
Useful by design. Quiet with your data.
This guide minimizes collection, keeps commerce on the official destination, and does not use fingerprinting or advertising trackers.
What happens here
A small, purpose-built data footprint.
Night Plans
Your selected performance, reminder, and checklist are saved in this browser so the Night Card can return. Clear the plan to remove it from this browser.
Assisted reservation requests
If the approved request desk is active and you choose to use it, the site collects only the published performance, requested ticket count, your name, your chosen email or phone contact, an optional request to discuss access arrangements, and your consent to transactional follow-up. Contact details are encrypted before storage and sent only to the configured reservation specialist. No payment is collected, no seat is held, and no availability is promised.
Reservation-request records are kept only for operational follow-up, audit, and any legally required reconciliation period. They are not joined to audience-location reports, and public analytics never includes your name, email, phone number, or precise location. The final retention and deletion schedule must be approved before the request desk is activated.
Haygoods Concierge
Questions are sent to the site’s protected server and then to OpenAI to generate a grounded response. Do not include private, financial, health, or ticket-account information. Questions are not placed in the client bundle or used here to create a public profile.
Optional audience insights and official-ticket handoffs
Only after you allow audience insights, the site can record pseudonymous first-party page views using random visitor and session IDs, source and campaign labels, and approximate country, region, and city supplied with the network request. It does not request GPS or a precise address. Small location groups are suppressed in reporting. Global Privacy Control and Do Not Track force measurement off.
These random browser identifiers are directional audience signals, not verified unique people. Source and campaign labels can also be supplied by a visitor’s link, so reports label them as observed rather than provider-verified.
With that same permission, an official-ticket handoff can record a random event ID, time, page, button placement, and the clean official destination. It stores no name, email, payment details, raw device signature, or cross-site advertising identifier. The official ticket site may also receive this site’s origin through the browser’s standard referral header.
A handoff is not a purchase. Unconverted handoffs become eligible for deletion after 30 days and are purged when a later handoff runs the cleanup. This guide cannot verify a conversion or revenue share until an approved provider returns a signed purchase or refund event tied to that handoff.
Your choice
Audience events become eligible for deletion after 400 days and are purged opportunistically when a later consented event runs cleanup, so 400 days is not a guaranteed hard maximum. The annual report shows the trailing 12 months and does not provide a prior-year comparison. You can decline before any audience event or identifier is created, and you can withdraw later. Withdrawing removes the audience visitor and session identifiers from this browser and stops new measurement; it does not retroactively identify and erase prior pseudonymous events. Transactional contact consent for a reservation request is separate from audience measurement.
What is not used
No fingerprinting, advertising SDK, social-media tracking pixel, cross-site cookie, GPS or precise location, contact access, or raw payment collection is part of this app.
When you leave this guide
External services use their own terms.
The official ticket destination, maps, OpenAI, and official social or music platforms operate under their own privacy practices. This guide does not add an affiliate or campaign parameter to the approved ticket URL.