Privacy

Privacy Policy.

What we collect, what we don't, and how spectator and admin data is handled across Eggbeater. We do not sell or share personal data.

No data sold or sharedHTTPS / TLS encryptedSign-in optional
Effective March 28, 2026Last updated April 5, 2026

1About this policy

Eggbeater is a tournament-tracking tool for water polo teams and clubs. It does not sell or share personal data. This Privacy Policy describes how the Eggbeater Water Polo app ("the App") handles information when you use it — in any browser, or via our native applications for iOS, Android, and Apple TV. By using the App you agree to this policy. The Apple TV app is a read-only companion that displays public tournament information; it requires no account or sign-in and collects no personal data.

2Information we collect

Information you provide

  • Player roster entries, game scores, live-scoring statistics, and bracket data you create.

Information from Google (if you sign in with Google)

  • Your Google account display name, email address, and profile photo — used only to identify your session and draw your first name in the App header.
  • A Firebase Authentication UID, used to associate your saved preferences with your account in Firestore.
  • A Google OAuth access token for Google Calendar (requested at sign-in time and held in memory only).

Information from Apple (if you sign in with Apple)

  • Your Apple user identifier and the name/email you choose to share — Apple’s Hide My Email may give us a private relay address instead of your real one, and that is the only email we ever see.
  • A Firebase Authentication UID, used the same way as with Google sign-in: to associate your saved preferences with your account.
  • We never receive your Apple ID password or account details.

Admin authentication

  • Admin sign-in uses Firebase Authentication and a Firebase ID token with each API request for verification.
  • Your Firebase UID is stored to a club-specific authentication list to determine admin access.
  • Admin ID tokens are refreshed automatically and never stored server-side persistently.