Last updated · May 2026

Privacy

BuzzerCue is built for families. Most of what the app needs lives on your device. Anything that doesn't is opt-in. 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.)

What stays on your device (the default)

Open the app and don't sign in: everything you add stays in your browser on this device. That's:

• Your kids' first names, optional grade and school, and the avatar you pick.
• The events you tap to register them for.
• Per-event details: rooms, blocks, placements, notes.
• App preferences like theme and reminder lead time.

We don't run a server that holds any of this. Clearing your browser data clears it.

What's in the cloud, only if you sign in

There's an optional Google sign-in. Choose it and the same 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.

By default that information stays on the parent's device. If the parent signs in to sync across devices, a mirror sits in their cloud account, 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:

• Pull competitor names from organizers' lists to pre-populate them.
• Match kids to public results sheets.
• Link kids across families or events.
• Build behavioural profiles.

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

What we don't do

• Run analytics or tracking on buzzercue.com or any per-event app.
• Sell, share, or rent data.
• Set marketing cookies. There's a sign-in cookie to keep you signed in if you choose to sign in. That's it.
• Build a coach- or organizer-facing dashboard. The app is one-way: the organizer's schedule flows in, the family's personalization stays with the family.

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.

Contact

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