BuzzerCue

Last updated · July 2026

Privacy

BuzzerCue is built for families. Your family's data lives in your account, is cached on your device so the app works offline, and is never used for anything beyond what this page lists. This page exists to spell that out clearly, in case you're the kind of parent who reads privacy pages before tapping Add to Home Screen. (We are too.)

On your device

Everything you add is written to a local database in your browser first, which is why the app opens instantly and keeps working on hallway Wi-Fi. That's:

On a shared computer, each account keeps its own separate local copy. Clearing your browser data clears the local copy; your account's cloud copy restores it the next time you sign in. (Earlier versions offered a no-sign-in guest mode; current versions require an account so your data can follow you across devices.)

In the cloud, with your account

You sign in with Google or with an email and password, and the data above gets a mirror in the cloud, scoped to your account, so you can pick it up on another phone or browser.

The cloud is Google Firebase, the only third-party service we use to store your data. Their terms cover the storage. We don't add a layer of our own analytics, identifiers, or cross-device joins on top.

If you sign out, the cloud copy stays under your account so the next sign-in restores it, and the local copy on your device is untouched. If you want it gone, the "Delete account" action in Settings removes the cloud copy.

Push reminders (only if you opt in)

If you allow push notifications, your browser hands the app a token so we can send the next-event ping. The token doesn't reveal who you are. Revoking notifications, or signing out, retires it.

What we serve from the network

The schedule is fetched when you open the app. The hosting provider sees your device's address briefly in standard access logs, the same way any website request does. We don't mine those logs to identify families.

The marketing site (buzzercue.com) loads one typeface from Google Fonts. The per-event apps don't.

Calendar export

The calendar export is built entirely on your device and downloaded directly. Apple Calendar or Google Calendar then has it, under their own privacy terms. We never see what you exported.

Children

The app processes a small amount of information about competitors: a first name (or initial), an optional grade, an optional school, and the events the parent has tagged. The parent is the user. The child is not.

That information lives in the parent's account, with a working copy on the parent's device, accessible only to that account. Coaches, organizers, and BuzzerCue itself don't have a way to look a kid up. We don't have one to give.

We don't:

The parent can delete it at any time, from the device and (if signed in) from the cloud.

What we don't do

Changes

If we add a privacy-respecting analytics tool, a feature that requires a new server-side process, or a new third-party processor, we will update this page first and call it out plainly in the FAQ on the home page. We won't add anything that turns this page into a long one.

Competition data from the organizer

When you use BuzzerCue during an IAC event (like IGC 2026), the app shows competition information that IAC has already published publicly on its own websites: participant names, player IDs, affiliations, room assignments, schedules, scores, and placements. We didn't create this data and we don't control it. We sync it from IAC's public postings so you don't have to refresh twenty spreadsheets, and we cache a copy in our database to make the app fast and to keep history (for example, a room assignment the organizer later overwrites with a score).

If you want competition data about your family corrected or removed, the source is IAC, and corrections there flow into the app automatically. If you want it gone from our cache specifically, email hello@buzzercue.com and we'll remove it.

Linking a participant

If you link a participant's Player ID to your account, we store that link (the ID, and which kid profile in your account it belongs to) so the app can show you that participant's schedule and results automatically. Linking doesn't give us any new data about the participant. It just connects your account to the public competition record described above. You can unlink at any time in the kid's profile; that deletes the link immediately. It doesn't (and can't) delete the organizer's public data.

Please only link participants from your own family. The link asks for the participant's last name as a simple check, not as a security measure. The underlying data is already public.

Signing in

You can sign in with Google or with an email address and password. Either way, authentication is handled by Google Firebase; if you use a password, it is stored by Firebase's authentication service and is never visible to us. What we store with your account: your email address, the kid profiles and registrations you create, participant links, notification preferences, and the date/version of the terms you accepted. You can delete your account in Settings; that removes your account data from our systems.

Notifications

If you turn on notifications, we store a push token for each device you enable so we can deliver alerts (room changes, results) for the participants you've linked. Turning notifications off in Settings, or revoking the permission in your phone's settings, stops delivery; tokens for disabled devices are cleaned up. We don't use notifications for marketing.

Contact

Questions, concerns, or a privacy-related request? We're small and we read every note. Email us at hello@buzzercue.com.