Privacy Policy

ScoreBit has no user accounts and no sign-up flow. We don't collect names, email addresses, passwords, precise location, contacts, photos, health/fitness data, or payment information — none of that exists anywhere in the app.

We do use Firebase Analytics to automatically collect limited, non-identifying usage data whenever you use the app, including:

• App interactions — screens viewed, features used, session length and frequency
• Device and app info — device model, OS version, app version, language, and general (country/region-level) location inferred from IP address
• A randomly generated app instance identifier, used to distinguish installs — not tied to your name or any account
• Basic diagnostic signals such as app crashes or errors

Anything you configure locally in the app — favorite teams, notification settings — stays on your device and is never sent to us or to Firebase.

Opening ScoreBit or pulling a refresh sends a request straight from your device to the ESPN API for live scores, schedules, and stats. ScoreBit just renders what ESPN sends back; we never log or retain that data ourselves.

Separately, the app sends analytics events to Firebase Analytics so we can understand usage patterns and app stability. This runs in the background and is unrelated to the scores you see — it doesn't affect what data ESPN receives.

Since ESPN and Google (Firebase) each process their own request independently, their privacy policies govern that handling on their end: ESPN's Privacy Policy and Google's Privacy Policy.

We don't sell data, and we don't share anything with advertisers or data brokers. The only places data flows are the two third-party services this app depends on to function: the ESPN API (for scores) and Google's Firebase Analytics (for aggregated usage stats). Neither receives anything beyond what's described in the sections above.

ScoreBit doesn't operate its own database, so there's nothing stored on our end to retain. Local preferences live on your device and disappear the moment you uninstall the app.

Analytics data collected via Firebase is retained by Google according to Firebase's standard analytics data retention settings, and is periodically aggregated or deleted per Google's policies.

• Notifications: manage or disable alerts in App Settings or your device's system settings
• Local preferences: reset favorite teams and settings anytime in-app, or by uninstalling
• Analytics: you can limit ad tracking and analytics data collection through your device's privacy settings (e.g. Android Settings → Privacy → Ads), or contact us to request deletion of analytics data tied to your device's app instance
• No account to delete: since there's no account or server-side database, there's no profile for us to access, correct, or erase beyond the analytics data described above

ScoreBit is intended for a general sports audience and doesn't knowingly collect personal information from children under 13 (or the applicable minimum age in your region). Firebase Analytics is configured for general audiences; if you believe a child has used the app in a way that raises a concern, contact us and we'll address it.

All traffic between the app and the ESPN API, and between the app and Firebase, runs over standard encrypted HTTPS connections. With no ScoreBit-controlled database of personal data, there's no user data store on our end to secure or breach — analytics data is held and secured by Google under their own infrastructure.

ScoreBit uses Firebase Analytics, provided by Google, to understand how the app is used and to help us fix bugs and improve performance. Firebase may collect device information, app usage events, and general location (derived from IP, at the city/region level, not precise GPS). This data is processed under Google's privacy practices — see Firebase's Privacy and Security page and Google's Privacy Policy.

ScoreBit relies on the ESPN API for scores, schedules, and statistics. We don't control — and aren't responsible for — ESPN's own data practices. See ESPN's Privacy Policy and Terms of Use for how they handle API requests.

We may update this policy if the app's functionality or data practices change. Material changes will show up in the "Last updated" date above and, where it matters, get flagged in-app.