Privacy policy
This policy covers Flock Royale on Apple devices and Android, and the web demo, published by Emre Can Akcan. Contact: emrekcn@gmail.com.
Playing and saving progress
The game stores a guest identifier and sign-in token, chosen display name, settings, and best single-player score on your device. Online Royale stores your player identifier, display name, match results, coin balance, cosmetic ownership and selected outfit on our Google Cloud servers. Other players can see your display name, outfit and match performance. Do not use a real name or other personal information in your display name.
Our server and hosting providers receive network addresses and operational logs to deliver and secure the service. Single-player scores stay on your device. No camera, microphone, contacts or precise-location permission is requested.
Optional account sign-in
When available, Apple or Google sign-in links a provider identifier to your game profile so you can recover it. The game does not receive your provider password. We retain an encrypted provider token so we can revoke access when you delete your game account. Short-lived sign-in challenges expire after ten minutes and are removed by scheduled cleanup.
Optional purchases
Apple or Google processes payments. We receive product and transaction identifiers, store verification records and a game-account identifier to deliver coins, prevent duplicate grants, recover interrupted purchases and handle refunds. We do not receive your payment-card number.
Optional advertising
Rewarded ads, when enabled, appear only when a player chooses to watch one: to double a Royale result, for free coins in the shop, or to continue a single-player run. There are no other ads. The game is intended for players aged 13 and over and is not directed at children.
Google AdMob may process IP addresses (including approximate location), device or account identifiers, ad interactions, diagnostics and performance data to deliver ads, measure their operation and prevent fraud. The app requests non-personalised ads. Non-personalised ads can still use data for these purposes. Where required, Google’s consent form appears before ads are requested. A Privacy Choices button is available when the consent service requires it. You can also choose not to use rewarded ads.
See Google’s privacy policy and how Google uses information from apps. We do not send your chosen display name or provider login token to AdMob; reward verification uses a random offer identifier.
Analytics
The web demo uses Firebase/Google Analytics for gameplay and performance events. The current native builds do not contain a Firebase Analytics bridge. Support pages and the account-deletion page do not load analytics or advertising scripts.
Retention and deletion
Active profiles and gameplay history remain until deleted. You can request deletion online or use Delete Account in the game after signing in again. Deletion removes linked identities, the profile’s name, coins, cosmetics and statistics, revokes provider access and anonymises stored match names. Local single-player scores and settings can be removed by clearing app data or uninstalling.
Limited transaction and reward records, including a pseudonymous player identifier and purchase-verification records, are retained to prevent replay, reconcile payments and handle refunds. An account tombstone prevents old sign-in tokens from restoring a deleted profile. Store providers retain their own records under their policies. Operational backups and logs follow the hosting providers’ retention settings.
You may contact us to request access, correction or deletion of your information. We may need to verify that you control the relevant profile. Where applicable, you may also raise a concern with your local data-protection authority.
Changes
We update this page when the game’s data practices change. Features described as optional may be unavailable while a release is being tested.