Privacy
Public analytics, kept narrow.
This note covers Musa's optional Google Analytics and PostHog measurement. It does not change the processing that is necessary when you choose to sign in, organize an event, or buy a ticket.
Optionally help improve checkout: allow Google Analytics to count booking steps, general error categories, and page speed. No names, contact details, answers, payment information, error messages or private links are included. This is separate from booking and stays off unless you choose it. “Accept all” on the cookie question turns it on together with analytics; “Essential only” leaves both off. You can change this separate choice in Analytics settings. Declining analytics stops these measurements too.
Campaign links and an optional booking reminder
When you use an operator’s Musa campaign link, its campaign identifier can be recorded with your checkout and booking. The operator can see attributed checkout starts, paid bookings and linked refunds. This does not add advertising pixels or send your contact details to an analytics service.
Where offered, you can separately choose one email reminder if you leave before starting payment. This choice does not subscribe you to newsletters. The reminder contains a private link to review your ticket selections and a link to stop booking reminders. Availability and prices are checked again; the reminder holds no seats.
Optional public-site analytics
Google Analytics is denied by default and the Google tag does not load until you choose “Accept all” on the cookie question, or “Allow public-page analytics” behind its Review button. If allowed, Musa sends manual page views only for the public discovery page and public event-detail pages, plus two booking signals: that an online checkout started, and that an online booking was completed. With this updated choice, measured steps also include the public event code when available and an external or test traffic label. Each count sends the order total, currency, ticket type names and codes, prices and quantities; a completed booking also sends the tax amount and a one-way code in place of the order number. Those signals are sent only after you have allowed analytics under this wording. If you allowed page analytics before these booking signals were added, that earlier choice keeps covering page views only; the booking signals stay off until you allow them again. Like any request to Google Analytics, every page view and booking signal also reaches Google with the technical details a browser shares with a website, such as its IP address and browser type. The privacy page itself is not measured. Earlier choices do not gain the public event code or traffic label until you allow the updated wording. You can exclude this browser in Analytics settings; that stops Musa analytics on this device. Explicitly marked test browsers are labelled as tests and send no server booking signal.
Product analytics with PostHog
PostHog is a product analytics service, with data hosted in the United States. Musa uses it only if you allowed analytics in the choice panel that names PostHog. If you allowed analytics earlier, before PostHog was added, that choice keeps covering Google Analytics exactly as it described and PostHog stays off; you will be asked again on the public discovery and event pages, never during checkout, and PostHog starts only after you allow it there.
Once you have allowed it, PostHog helps Musa understand how people move from discovery to booking. It loads only on the public discovery page, public event pages, and the checkout and confirmation steps, and records a discovery page view, an event page view with the public event and organizer identifiers, an online checkout entry before details are submitted, that an online checkout started, and that an online booking was completed. The last two also carry the amount, currency, ticket count, and each ticket type's identifier, price and quantity, plus a one-way code in place of the order identifier. Page addresses are cut to the site and path, and referrers to the site name. PostHog stores a random browser identifier on your device to tell visits apart; it is not linked to a name, email address, phone number, or account.
Checkout entry counts opening a valid online cart; checkout starts count its first quoted reservation. Entry adds the public event code and traffic label, without cart contents or form entries. The updated choice also adds a measurement version to these funnel events so reports compare steps with the same coverage. Earlier choices keep their existing events and heatmaps; checkout entry and the measurement version stay off until you allow again.
Like any request to PostHog, each event also carries the technical details a browser shares with a website: browser and operating system type and version, language, time zone, screen and window size, and random session and window codes. PostHog receives your IP address with each request; the project is set not to keep it.
If you allow analytics under the wording that includes heatmaps, PostHog also receives click and pointer coordinates on the discovery and public event pages. These show where visitors interact, without collecting page text, form entries, screenshots or recordings. Forms, dialogs, checkout, confirmation, guest-trip and private pages are excluded. Earlier choices keep their original scope: heatmaps stay off until you allow again. We do not enable automatic element clickmaps or additional page-view or page-leave events for heatmaps.
We do not use session replay, screen recording, surveys, feature flags, experiments, or automatic DOM-content capture, and we do not build personal profiles. PostHog is never used to decide prices, payment, or ticket delivery.
This version of checkout no longer sends an analytics identifier with new reservations. Earlier reservations may already have submitted an anonymous booking confirmation to PostHog with amount, currency and ticket count tied to a random browser code. Those legacy signals may still be processed and are separate from this browser funnel.
To withdraw, choose Keep analytics off from the Analytics settings control on a public event page. That turns off PostHog together with Google Analytics: PostHog makes no further requests from this browser, this version sends no analytics identifier with new reservations, and the PostHog identifier stored on your device is removed. A booking started in an older version may still produce a legacy server signal. PostHog stays off for that page until it is reloaded.
What stays out
We strip query strings and do not send checkout form entries, buyer or attendee details, email addresses, order numbers, payment references, authentication pages, embedded storefront or box-office activity, or organizer dashboards to Google Analytics or PostHog. Checkout and confirmation do not send automatic page views. The separately described checkout entry count contains no form entries. Google advertising storage, advertising user data, advertising personalization, and Google signals remain disabled.
Error reports
If a page breaks, Musa may receive a technical error report, such as the error message, your browser type and the page path without any query string, with personal details like email addresses, phone numbers and ticket links removed and with no screen or session recordings.
Your choice
You can decline without affecting event discovery or ticketing. Use the persistent Analytics settings control on a public event or privacy page to allow or revoke analytics at any time.