1. Who operates GridRush
This policy describes the Android game GridRush (com.cyberloft.gridrush). The responsible publisher is Victor Saliba, based in Malta. For questions about privacy and personal data, contact victorsaliba@gmail.com.
2. Information stored on the device
GridRush saves gameplay progress, high scores, resumable runs, Daily activity, settings, earned coins and gems, and cosmetic ownership locally. These records support gameplay and may be lost if you clear app data or remove the game without an available recovery method. Local game progress should not be confused with information independently held by Google services. The current Android package also declares a notification permission. Whether and when notifications are shown depends on the game features and the permissions you allow in Android settings.
3. Google Play Games
GridRush integrates Google Play Games sign-in, supported leaderboards and achievements. When authenticated, supported gameplay data can be sent to Google Play Games, including leaderboard scores, achievements, progression and Google Play Games event statistics such as game mode, completed runs, cleared floors and Daily attempt activity. Google may associate these records with your Play Games account. These features are separate from the optional Firebase Analytics choice, and declining Analytics does not disable Google Play Games processing.
4. Purchases
Optional in-app purchases use Google Play Billing through Unity Purchasing. Purchase processing can involve product identifiers, order status, purchase tokens, verification and recovery information. The game may check for previously purchased items when it starts, even if you do not start a new purchase. Payment card details are handled by Google Play rather than entered into GridRush. Billing, fulfillment and purchase restoration operate independently of the optional Firebase Analytics choice.
5. Optional Firebase Analytics
The current GridRush implementation starts Firebase Analytics collection disabled. Players can choose whether to allow optional gameplay Analytics through Settings → Privacy. If allowed, Firebase may process app usage, app-instance identifiers, technical device information and automatic activity events, together with limited in-game events such as selected game mode, run starts and outcomes, campaign milestones, store interactions and claimed rewards. Custom game events do not intentionally include names, email addresses, purchase tokens or Google Play Games account identifiers.
Declining Analytics does not restrict gameplay or purchases. Switching it off stops future Analytics collection; it does not automatically erase events previously received by Google. A single combined consent experience for Analytics and any future advertising is being prepared but is not yet active.
6. Firebase and connected features
GridRush includes Firebase SDKs for Analytics, Authentication and App Check-related functions. Some Firebase Authentication and Play Integrity App Check workflows are currently restricted to development diagnostics or separately gated testing features. The inspected normal release path does not intentionally create a Firebase anonymous account automatically on launch. Depending on the enabled build and features, Firebase-related services may process technical identifiers, integrity attestations or authentication information. Public Daily ranked participation and online Daily score submissions are not currently active; a future release enabling them would require an updated disclosure and the relevant player choice.
7. Advertising
Third-party mobile advertisements are planned for a future GridRush version and are not currently part of the active gameplay experience. The inspected Android build declares advertising-identifier and attribution-related Android permissions through its packaged components, although Firebase Analytics advertising-ID collection is configured disabled and no Google Mobile Ads SDK was detected in that build. A permission declaration alone does not establish that the identifier is accessed. We will verify actual use and update this policy and consent choices before any advertising is activated. A future one-time Remove Ads purchase would control advertising display, not automatically withdraw Analytics consent.
8. Service providers, protection and international processing
Google Play, Google Play Games and Firebase are service providers relevant to the functions described above. Their processing may involve infrastructure in multiple countries. GridRush aims to limit optional telemetry and avoid including direct personal identifiers in its custom gameplay events. Details of the relevant Google services can be found in Google's published privacy documentation.
9. Retention and deletion
Local game information remains on the device until changed or removed, subject to Android storage and backup behavior. For optional Firebase Analytics, the publisher has configured both event data and user data retention to 2 months, with reset on new user activity disabled. These Google Analytics retention controls apply to the relevant user-level and event-level data, not to every standard aggregated report or records managed by other Google services. Removing the app does not necessarily delete information held by Google or Firebase. For applicable access, deletion or other privacy requests, contact victorsaliba@gmail.com. Requests concerning Google-managed account records may also require action through Google's services.
10. Your choices and rights
You can change the optional Analytics choice in GridRush Settings → Privacy. Where applicable, data protection law may also give you rights to request access, correction, deletion or restriction, or to object to processing. Some Google account-related preferences and requests must be managed directly through Google.
11. Children and regional requirements
GridRush's declared Google Play target groups are ages 13-15, 16-17, 18+. GridRush does not target under-13 age groups. Younger users within the declared audience may be considered children under applicable local laws. Before introducing third-party advertising, we will review the relevant child and teen protections, including data processing, consent, ad targeting and age-appropriate advertising. No third-party advertisements are currently active in GridRush.
12. Policy updates
This policy will be updated as GridRush changes, especially before introducing third-party advertising, additional online competitions or materially different data use. The effective date shown above identifies the approved version.
