Last Updated: September 6, 2026
This Privacy Policy applies to the mobile game RICOX: Ricochet Physics Puzzle ("the App", "Game"), developed and published by Mobover ("we", "our", or "us"). We respect your privacy and are committed to protecting any information collected through your use of the Game.
RICOX processes player nicknames and identifiers, gameplay and online duel records, and technical and advertising data. The Game does not require your real name, email address, phone number, or contacts. Guest identifiers are pseudonymous: they can still be linked to your game activity.
Delete your RICOX account or data: Use Settings → Delete Account when available, or request deletion by emailing info@mobover.com. See account and data deletion instructions for the steps, data covered, and the difference between local progress reset and server data deletion.
When you play RICOX, certain technical and gameplay data is collected automatically to ensure proper game operation:
If you contact us by email, we also receive your email address and the information you include so we can respond to your support or deletion request. Do not send passwords or verification codes.
Our application integrates trusted third-party SDKs that operate under their respective privacy policies:
We use Google AdMob to display banners, interstitial ads, and optional rewarded videos. Its SDK automatically collects and shares IP-derived approximate location, app interactions, diagnostics, and device or other identifiers for advertising, analytics, and fraud prevention.
We use Google Play Games Services for achievements and leaderboards. When you sign in, the Game receives your gamer name and player ID and can submit scores and achievements. Google Play Games also processes SDK usage and diagnostic data. You can manage your Play Games profile visibility and game data through Google's controls.
Google Privacy Policy: https://policies.google.com/privacy
On iOS, we use Apple Game Center for platform sign-in, achievements, and leaderboards. When signed in, the Game can receive your Game Center player identifiers and display name and submit scores and achievements. Apple manages the Game Center profile and its activity-sharing controls separately from your RICOX account. See Game Center & Privacy.
We use Firebase guest authentication and, where supported, verified Google Play Games or Game Center sign-in. Firebase databases support player identities, nickname reservations, available cross-platform leaderboards, and online 1v1 duels. Online services process matchmaking, shot and match records, and connection status. Remote Config provides game and advertising configuration, and App Check helps protect online services against abuse. Communications with Firebase use HTTPS/TLS.
Firebase Privacy Overview: https://firebase.google.com/support/privacy
We use Google Analytics for Firebase to understand level difficulty, duel participation, reward use, and game preferences. Gameplay events contain limited values such as level or arena number, mode, outcome, duration, shot and bounce counts, and selected language. We do not attach your nickname, Firebase account ID, Play Games or Game Center player identifiers, email address, or free-form text to these Analytics events. The SDK uses a separate app-instance identifier and processes device information, sessions, and coarse location derived from a masked IP address. These records are pseudonymous, not anonymous. Advertising ID collection and automatic screen reporting are disabled for Analytics; AdMob has its own data practices described above.
Google's User Messaging Platform (UMP) presents the applicable privacy message. We do not show a separate Analytics permission dialog. The Game starts with Analytics collection disabled and enables it after UMP reports an allowed analytics storage choice or confirms that the choice does not apply in your region. During the Game's initial evaluation, if UMP has not been configured to collect an Analytics choice, the Game also enables gameplay Analytics after your explicit advertising consent for Google is recorded. This temporary rule does not record a separate Analytics consent. An explicit Analytics refusal, missing consent data, or a failed consent refresh leaves collection disabled. Gameplay events occurring while collection is disabled are not sent later. Where UMP requires a privacy options entry, you can revisit your choices using Settings → Privacy options; withdrawing the advertising consent stops collection that depends on this temporary rule. Declining Analytics does not prevent campaign or duel play.
Learn more about data handled by the Google Analytics for Firebase SDK and Google's privacy practices.
Leaderboard submission depends on your platform, game version, sign-in state, and feature availability. Existing Android versions can submit your nickname, player identifier, scores, stars, highest unlocked level, platform, and update time to the public cross-platform leaderboard, including guest play. On iOS, signed-in players can submit scores and achievements to native Game Center. Where the verified cross-platform profile service is available, cross-platform submissions require verified platform sign-in and are publicly accessible. Game Center or Play Games scores and achievements are not a full backup of your local campaign progress. Participants in an online duel can access player identifiers, nicknames, and the gameplay and connection information needed for that match.
The collected information is used strictly for the following purposes:
Where available, open Settings → Delete Account and confirm the request. A platform account may need to be verified again. If deletion is pending, use Resume Account Deletion when prompted. If the feature is unavailable or you need help, request deletion by email using the steps below. You do not need to reinstall the Game or create a new account to submit an email request.
Deletion covers the RICOX Firebase account, player profile and nickname reservations, leaderboard and server-side progress records, and associated matchmaking, connection, shot, and match records that we control. Where a match also contains another player's data, we remove or anonymize your associated information while preserving that player's records. An active shared match or temporary game room may need to finish or expire before deletion can complete; retry the pending request or contact us for help. Older records may require a separate ownership check.
You may also request deletion of specific RICOX data, such as your leaderboard entry, without requesting deletion of your entire account. Specify the data you want removed in your email; we explain any effect on related game features before processing the request.
The Game's progress reset option removes saved campaign progress from your device. It does not delete your Firebase account, nickname reservation, online leaderboard entries, match records, Apple or Google account, or native Game Center or Play Games data. Use account deletion or the email process above for RICOX account or server data deletion.
Private player block lists and associated nickname labels are removed as part of account deletion, including references to your deleted account in other players' block lists. Reports you submitted or that identify your deleted account are also removed.
Deleting your RICOX account does not delete your Apple or Google account or automatically remove native Game Center or Play Games records. Apple’s Game Center data is managed through Apple’s separate profile, privacy, and account controls, described in Game Center & Privacy. You can manage or delete data held in your Google Play Games profile using Google's game data deletion instructions. Data handled independently by Google is also subject to Google's privacy policy and account controls.
Player identity, nickname, and leaderboard records do not have a general 90-day automatic deletion period; they are retained to provide those features until removed through the deletion process. Temporary online records may be removed earlier as part of service operation. We do not promise automatic deletion of all data within 90 days.
Player safety tools let you report an inappropriate nickname or block another player. A block list is private to your account and prevents new matches with that player; you can remove a block in Settings. Reports contain the reporter's and reported player's account identifiers, the nickname captured by our server, any associated match identifier, timestamps, and the review outcome. Authorized operators use these records to investigate abuse and may reset or restrict an inappropriate nickname. Reports are scheduled for deletion 90 days after creation; background cleanup can take additional time. Block lists and active nickname restrictions remain until you remove the block, a restriction is lifted, or the account is deleted. Contact info@mobover.com for safety concerns or to appeal a nickname restriction.
When in-app deletion is used, a minimal request-status record containing hashed identifiers and deletion state is retained while the request is pending so interrupted requests can be resumed. After completion, that record is scheduled to expire after 30 days; background cleanup may take additional time. A completion message confirms deletion of the covered RICOX account data, not removal of these temporary status records or independently managed Apple/Google data.
If particular records must be retained for a legal obligation or a necessary security or fraud-prevention purpose, we restrict their use to that purpose and explain the affected data, reason, and retention period in our response. We retain support correspondence only for as long as needed to handle the request and meet applicable obligations.
In versions with in-app deletion, automatic platform sign-in is suppressed after completion. Choosing to sign in again can create a new RICOX account and new gameplay records. Older versions may create a new guest identity when you continue online play.
RICOX is designed for a general audience (aged 13 and older) and is not targeted towards children under the age of 13. We do not knowingly collect personal information from children under 13. If you believe a child has provided us personal data, please contact us immediately so we can remove it.
We employ industry-standard administrative, physical, and technical safeguards to protect your information against unauthorized access, destruction, or disclosure. All cloud transmissions are encrypted using Transport Layer Security (TLS/HTTPS).
We may update this Privacy Policy from time to time. We encourage you to review this page periodically for any changes. Continued use of the Game after revisions indicates your acceptance of the updated policy.
In accordance with applicable data protection laws (including the EU/UK GDPR and Turkish KVKK Law No. 6698), the data controller responsible for your information is:
