Privacy

What we collect. When you submit a form on this site we store what you typed: your email address and, if provided, your name, organization, and message. We also measure how the site is used, as described under Analytics below. There are no advertising identifiers.

Purchases. Payments are processed by Stripe. Your card details go to Stripe and are never stored by Ballyhoo. Stripe also collects the billing and tax information needed to complete the payment. We keep a record of each purchase: the email address you bought with, the show, the ticket type, the amounts charged (price, service fee, tax, total), and the date. The show’s creator or partner can see the email address, ticket type, amount, and date of purchases for their show.

How we use it. To reply to partnership inquiries and, if you opted in on the fan list, to announce shows. We don’t sell or share your information with third parties for their marketing.

Retention & removal. We keep inquiries while they’re active. Playback logs are kept as long as the show needs them for reporting; your IP address and full browser user-agent string are cleared after 180 days. Want your info corrected or deleted? Email hello@ballyhoo.show and we’ll take care of it.

Playback & anti-abuse data. When you watch a show, we log your IP address, approximate country, a device/browser identifier and label, the general kind of device you watched on (phone, tablet, desktop, TV), your session’s start and end times, viewing progress, which camera angles you watched and for roughly how long, and periodic heartbeat activity confirming playback is still running.

How you found us. If you allow analytics (below), then on your first visit we record the campaign parameters in the link you arrived through, the referring site, and the page you landed on. This tells us which channels bring people to a show. It is stored against an anonymous browser id, never sold, and never used to build an advertising profile.

Analytics (your choice). Analytics are off unless you allow them: the banner asks on your first visit, and rejecting is as easy as accepting. If you allow them, we store an anonymous visitor id (bh_sid) and your first-touch attribution (bh_attr: campaign parameters, referrer, and landing page) in your browser. We use the id to connect your page views to purchases and viewing, and Mux Data uses it to measure playback quality (startup time, buffering, errors). If you decline, we store neither and Mux Data does not run. Two things continue either way because they identify no one: Vercel Analytics, which is cookieless and counts page views in aggregate, and counts of actions such as button clicks and checkout steps, recorded without any visitor id or attribution. Change your choice at any time with Privacy settings in the page footer; withdrawing deletes bh_sid and bh_attr and reloads the page.

Storage we always use. A few items are needed for the site to work and are not optional: sign-in cookies that keep you logged in; a device identifier (bh_device) used to enforce stream and device limits; player settings you choose; admin-interface preferences; and c15t, which records your privacy choice itself.

Why we log it. To enforce concurrent-stream and device limits (so a ticket can’t be shared past what you purchased), to troubleshoot playback issues when you contact support, and to build aggregate audience reports for the show’s creator.

What creators see. Partner-facing playback reports only ever include coarse data — country, an anonymized device identifier, and session timings. (Purchase records, described above, are separate.) Creators never receive your raw IP address, device label, or full browser details.

Stream limits. Each account can play up to 2 streams at the same time. Starting a third is blocked unless you choose to take over, which ends your oldest stream.

Lifecycle emails. We send a small number of emails tied to your tickets — a reminder before a show, a notice when access opens, and a warning before access expires.

Processors. Payments are handled by Stripe. Form submissions are stored with our database provider (Supabase) and notifications are delivered via our email provider (Resend). Analytics are provided by Vercel Analytics. Video is hosted and streamed by Mux, which observes the same playback data described above.

This policy also covers ticket purchases and show playback, and will continue to expand as Ballyhoo adds new features.