Privacy
This page explains privacy topics for the EFS app, website, support routes and subscription access where available.
This policy covers privacy topics for Edge Football Stats, including app use, website pages, support contact and store-managed subscription access where those features are available.
EFS keeps support requests focused on safe issue context and does not ask users to send receipts, purchase tokens, transaction IDs, order IDs, payment screenshots, passwords, card details or private account details.
EFS uses Firebase Analytics in the EFS app to understand how the app is used and improve the product. EFS does not use Firebase Analytics for advertising or advertising personalisation.
EFS does not set an analytics user ID or user properties. EFS does not describe this analytics information as anonymous because Firebase may use app-instance or device identifiers.
EFS-authored analytics events use closed event-name and parameter allowlists together with a conservative sanitizer. They may include the EFS screen or feature used and internal football-content identifiers such as a fixture, league or team identifier.
EFS-authored analytics events do not include names or email addresses, raw purchase receipts or purchase tokens, transaction or order identifiers, numeric xG values or free-text exception messages.
Separate from EFS-authored events, Firebase may automatically collect app-instance or device identifiers, app interactions and lifecycle information, approximate location derived from a masked IP address and, where supported, purchase or subscription information.
EFS's custom event allowlists and sanitizer do not control Firebase-owned automatic collection.
The Firebase Analytics information above applies to the EFS app. EFS has not added Firebase Analytics, another product-analytics service or advertising-tracking code to this website source.
The service used to host the website may process basic technical request information needed to deliver and protect the pages. This is separate from the app analytics described above.
Product-usage events may include an internal league, season, team, match or fixture identifier together with the EFS screen or feature used. These football-content identifiers help EFS understand which content and features are useful.
EFS does not use these identifiers to build a profile of a person's intended bets, bookmaker accounts, stakes, returns, wins or losses.
Where subscriptions are available, Apple or Google handles payment through the relevant app store. EFS may process the minimum store-provided evidence needed to validate access, support a restore request and prevent misuse.
Raw receipts, purchase tokens, transaction or order identifiers and store-validation payloads are not included in EFS-authored product analytics. Separately, Firebase may automatically collect purchase or subscription information where that collection is supported.
Crash reporting is not currently active in the EFS app. Analytics and crash reporting are separate functions.
EFS-authored analytics events do not include free-text exception messages.
Users can contact EFS through the Support page about privacy, app access, subscriptions or restore issues. EFS may process the contact details, message and other information a user chooses to provide so it can investigate and respond.
Users should not send receipts, purchase tokens, transaction or order identifiers, device or account identifiers, payment screenshots, passwords, card details or private account screenshots through support.
EFS does not use Firebase Analytics for advertising, advertising personalisation or cross-app advertising tracking. EFS does not use Apple's IDFA or Google's advertising ID for advertising, and no advertising or data-broker use is approved.
Firebase Analytics event-data retention is configured for two months. Retention for subscription validation, support requests and website hosting may differ because those systems serve different purposes.
EFS keeps information only for as long as needed for the relevant purpose and any applicable legal, accounting, security or support requirement.
For questions about this policy, privacy rights, data deletion, subscriptions or restore purchases, use the Support route.
Do not include receipts, purchase tokens, transaction or order identifiers, device or account identifiers, payment screenshots, passwords or card details in a support request.