Privacy, without getting in the way.

The short version

The public merchant website uses a limited Meta Pixel setup to measure public-page visits and ticket-link activity. It runs automatically for United States visitors unless they opt out. Visitors in the EEA, United Kingdom, Switzerland and Québec are asked first. Everywhere else—and whenever location is unavailable—it stays off unless the visitor turns it on. The unlisted /press route is excluded completely.

We do not use Google Analytics 4 or Meta Conversions API, and we do not deliberately send names, email addresses, phone numbers or booking-form contents to Meta.

Merchant does not sell personal information for money. Some United States privacy laws may nevertheless treat advertising-measurement data sent to Meta as sharing or targeted advertising. Privacy choices and supported browser privacy signals stop that transmission.

Your analytics choice

You can allow or decline Meta measurement at any time. An explicit choice is stored only in this browser for 180 days. A Global Privacy Control or Do Not Track signal keeps Meta analytics off and overrides a previously saved allowance.

Declining after previously allowing stops future site events. It does not erase information Meta may already have processed; browser controls can also be used to remove existing cookies or local site data.

The hosting edge uses a coarse country or region signal only to select the appropriate default. Merchant does not save that location signal in its own database.

What may be measured

• PageView: one event for each public route view.
• ViewContent: one event when a show-detail page is viewed.
• TicketLinkClick: one event when a ticket link is intentionally activated.

Show and ticket events are limited to the show ID, venue, city, ticket vendor and, for a ticket activation, the button location. The site does not attach form entries or contact information to these events.

Necessary site security

The hosting network may set a short-lived Cloudflare security cookie, including __cf_bm, to distinguish legitimate traffic from automated abuse and keep the site available. It is necessary hosting infrastructure, not Merchant marketing analytics, and may operate before you make a Meta analytics choice.

Cloudflare explains these cookies in its cookie documentation.

What Meta may receive

When enabled, Meta Pixel can receive the event information above along with ordinary browser and device information involved in a web request, such as the page address, referrer, IP address, browser details and cookie or device identifiers. Meta controls its own processing and retention of that information.

Read Meta's Privacy Policy and Cookies Policy.

Questions

For privacy questions about this website, email romario@merchantsound.com.