What the app needs
The app may request network access, timezone context, and lightweight diagnostics needed to fetch football data, render scores correctly, and understand cache failures.
Scorebar is built around football data retrieval, local caching, and product analytics needed to operate the service. The current direction is to keep collection narrow and push stable sports data into the backend instead of pushing user state into third-party systems.
The app may request network access, timezone context, and lightweight diagnostics needed to fetch football data, render scores correctly, and understand cache failures.
Stable football data such as fixtures, standings snapshots, teams, provider payloads, and media references can be cached or persisted on the server. This exists to reduce third-party API cost and improve reliability.
Scorebar is not designed as an ad-tech profile builder. The product direction is a football workspace, not an engagement trap.
If you need clarification on product telemetry, cached sports data, or account-related handling, contact the project owner through the public app channels before release.