Privacy,
plainly.

Account and local information

Firebase Authentication supports a guest account and optional Apple or Google sign-in. It processes a player identifier, the authentication information needed to sign in and identity information supplied by the selected provider. The game’s Apple sign-in does not request name or email permission scopes.

The game keeps a local profile and cached wallet, club name, selected country and region, league progress, experience, energy, cosmetics, equipped skills and charges. Local settings include audio, vibration, tutorial status and a notification preference. Pending gameplay or purchase operations are stored locally so they can be retried.

Online play and information visible to others

Cloud Firestore, Realtime Database and backend Cloud Functions store and process your profile, wallet and loadout, leagues, match history, friends, friend requests and blocked-player lists. Live match state, player actions and connection state are exchanged to run multiplayer matches.

Your player identifier, club identity, equipped items and relevant match or social information may be visible to other players through public profiles, leaderboards, matches and friend screens. Country and region are selected by you; they are not obtained through precise location access.

Analytics and crash reports

Firebase Analytics and Crashlytics are enabled automatically at startup when the Firebase services are available. They process gameplay or app-use events and technical crash information, including diagnostic reports, device or installation identifiers and failure traces, to help understand use and fix problems. This can also apply during local practice.

In-app purchases

Apple App Store payments are handled through Unity IAP. Product identifiers and signed transaction information are sent to the game’s backend to verify and deliver purchases; pending redemption details can also be kept on your device. The game does not directly collect payment-card details.

Permissions and preferences

Internet access supports accounts, multiplayer, cloud profiles, analytics, crash reporting and purchase verification. The current game does not request camera, microphone, contacts or precise-location access. Its notification switch currently saves a preference without registering push notifications.

Retention and your requests

Local saves remain in the game’s application storage until they are replaced or removed. You can remove them by clearing the application’s stored data where your platform supports it, or removing the app and its data. Device or operating-system backups may retain their own copies. Removing local data loses the associated progress.

Removing the app’s local data does not remove cloud accounts, match records, social records or diagnostic data. The current version has no in-game account-deletion flow or defined automatic retention schedule for its game backend. Contact OREBRON for assistance with access or deletion requests; provider retention and any records that must be retained will be considered when responding.

Service providers

These services have their own information-handling terms:

Firebase privacy and security (opens in a new tab)

Apple App Store privacy (opens in a new tab)

Google privacy policy (opens in a new tab)

Questions and requests

Contact OREBRON about this game’s privacy or to request help accessing or removing information you have shared. Include the game name and enough information to identify your account, if you use one. Please do not send passwords or sign-in tokens.