Privacy Policy

Draft for owner review — not approved for publication

This draft must be checked against the released app before publication. The legal publisher, support email, applicable country and any required address remain to be supplied by the owner.

Match data and service providers

The app requests football information from its configured backend, including selected dates, match or team IDs and search queries. API-Football is the intended football-data provider; the owner must confirm the actual production backend and provider before publication. Their request logging, retention, processing locations and applicable provider terms remain unconfirmed.

The app can load sports images from image hosts using URLs returned in match data. Those hosts receive the image requests. The website uses only local artwork and does not load those images.

Followed teams and widget information

Favorites and settings, including language, appearance and alert choices, are stored on the device using SharedPreferences. Local storage does not mean the selections always stay on the device: team IDs are used in match requests and may be shared for notifications as described below.

The Android widget stores cached match information and display settings locally. When background refresh is configured, it sends followed team IDs to the backend to request live, recently finished and upcoming matches. It can also download and cache sports images. Release configuration and retention of these caches must be confirmed before publication.

Notifications, analytics and advertising

Firebase Messaging is included. When push is enabled and configured and notification permission is allowed, the app registers with the backend using an installation ID stored on the device, a push token, platform, language, timezone, app version, alert preferences and followed team and competition IDs. Firebase handles notification delivery. The owner must verify which flows are enabled in the released app and document the providers, purposes, retention and user choices.

Analytics collection is explicitly disabled in the Android manifest reviewed. No dedicated analytics or crash-reporting integration was found in the reviewed app source; the shipped app and SDK behavior still require verification.

The Google Mobile Ads SDK is present. The internal-testing flag disables ad requests; local-live and staging modes can request Google sample ads. Production ads require deliberate activation and valid configuration, and remain deferred for this project. Disabling ad requests does not establish that the embedded SDK processes no data. The owner must verify shipped SDK behavior and, before enabling ads, update this policy with providers, data use and applicable consent.

Retention, choices and contact

Retention periods, deletion procedures, data requests and a verified contact route have not been confirmed. The owner must supply and review these details; this draft does not promise a retention period or a deletion process.

This website

This static website has no account system, football API requests, analytics SDK, advertising SDK or cookies. Hosting-provider request handling must be checked separately before publication.