Privacy
This local prototype page explains privacy topics that must be covered before EFS public billing. It is not final legal advice and must be reviewed and approved before production use.
No. This is draft website-prototype wording for privacy readiness. The final Privacy Policy must match the live app, backend, support process, billing setup, analytics choices and crash-reporting choices before public billing.
Mark approval is required before this wording or route is used in Google Play Console, App Store Connect, the Flutter app or production subscription flows.
EFS is a football statistics and research product. The final privacy wording should explain what information is used to run the app, website and support routes, and how subscription access is validated when billing goes live.
The final policy should cover app usage, website pages, support requests, fixture and football statistics data, account or saved-item behavior if used, and any analytics or crash tooling that is actually present.
Once subscriptions are live, Apple or Google process store payments. EFS access should only change after store purchase or restore evidence is validated by the EFS backend.
Support requests should ask only for safe context such as app version, platform, device model and an issue summary. Users should not send receipts, purchase tokens, transaction IDs, order IDs, payment details or private account screenshots.
The final wording must be checked against the actual providers and SDKs in use. This prototype does not add analytics, crash monitoring, payment collection or support forms.
Final privacy wording, support contact details and public URL use remain Mark-owned release gates. Public billing remains blocked until the page is live, mobile-readable and approved.
The public support route or support email is still pending Mark confirmation. Until it is approved, this page should be treated as a local prototype rather than a production privacy contact route.
Use Support for the provisional website support page.