Last updated: October 21, 2026
This Privacy Policy explains what information the mobile game Unicorn Water Sort - Liquid Sort Puzzle (the “game”) collects on Android and iOS, how it is used and shared, and what choices you have. It applies to version 2.0.0 and later. The game is developed by Grumpy Moose Games (“we”, “us”). You can reach us at nikita.gmgm@gmail.com.
Summary
- The game has no accounts. We never ask for your name, email address, phone number, contacts, photos or precise location.
- Your save file stays on your device. Gameplay and settings events are sent for analytics and crash diagnostics as described below.
- The game uses Google services: AdMob shows ads, Firebase provides analytics, Android crash reports and remote settings, and Google Play Billing or the Apple App Store handle the optional No Ads purchase. These services receive device identifiers and information about how the game is used.
- Every ad request is marked as child-directed and limited to G-rated content, so the ads are not personalized. On iOS the game does not ask for tracking permission and does not access the Apple advertising identifier (IDFA).
- We do not sell your personal information.
Information stored on your device
The game saves your level progress, your settings (day/night theme, sound, vibration, tap timing), whether you own No Ads, the latest remote settings, the Firebase installation ID and the most recently measured banner height in its own storage on your device. We do not upload a copy of your save file; gameplay events and diagnostic information are sent as described below. Local saved data is deleted when you uninstall the game or clear its data. Pending crash reports may also be stored on the device until they can be sent to Firebase.
Information collected automatically
When you play, the following information is collected by the services built into the game:
| Data | What exactly | Collected by | Purposes |
|---|---|---|---|
| Device or other IDs | Android ID on Android or the identifier for vendor (IDFV) on iOS, used as the analytics user ID; Firebase app instance ID and installation ID; Android advertising ID and app set ID; Crashlytics installation UUID and the Android ID used as a pseudonymous crash-report user ID | Firebase Analytics, Firebase Installations/Remote Config, Google Mobile Ads SDK; Firebase Crashlytics on Android | Analytics, app stability, delivering remote settings, advertising, fraud prevention |
| App interactions | Menus opened, tutorial steps and sessions; ads shown and tapped, their format, placement and revenue; day/night, sound, vibration and tap settings; whether the consent form applies to you and whether you have answered it | Firebase Analytics; Google Mobile Ads SDK for ad interactions; recent Analytics events also accompany Android Crashlytics reports | Analytics, app stability, advertising, fraud prevention |
| Gameplay | Levels started, completed and restarted; level difficulty, number and set; moves, undos, extra bottles, restarts and time spent per level; replay status and whether progress was imported from the Unity version | Firebase Analytics; recent Analytics events also accompany Android Crashlytics reports | Analytics, app stability |
| Purchase history | The No Ads purchase: product, price, currency and time; purchase attempts and their outcome | Firebase Analytics (automatic and game-defined purchase events) | Analytics |
| App info and performance | Device model, operating system and app version, language, time zone, app launch time, ad and SDK performance | Firebase, Google Mobile Ads SDK | Analytics, advertising, fraud prevention, delivering remote settings |
| Crash reports (Android) | Crash stack traces, native crash data and relevant app/device state; the current level and level set; recent Analytics events and their parameters; the associated identifiers described above | Firebase Crashlytics, including its native crash reporting component | Finding and fixing crashes, measuring app stability |
| Approximate location | Country or region estimated from your IP address | Firebase Analytics, Google Mobile Ads SDK | Analytics, advertising, fraud prevention |
All of this information is encrypted in transit (TLS). We do not use it to find out who you are and do not combine it with other information about you.
How we use information
- To understand how the game is played, for example which levels are too hard or where players stop, and to improve it.
- To show ads, which keep the game free, and to measure how they perform.
- To understand and fix Android crashes and improve the game’s stability.
- To change some game settings without an app update, for example whether an ad is shown between levels.
- To provide and restore the No Ads purchase.
- To detect and prevent fraud and abuse.
Advertising
The game shows ads through Google AdMob:
- An adaptive banner at the bottom of the game, menu and tutorial screens, enabled by default.
- Rewarded ads that you choose to watch to get more undo actions or an extra bottle.
- Full-screen interstitial ads after some completed levels. These are disabled by default in version 2.0.0 and can be enabled through remote settings.
Buying No Ads turns off all three advertising formats. It does not turn off analytics, Android crash reporting or remote settings.
Every ad request is marked for child-directed treatment and limited to the G content rating. For such requests Google does not show personalized (interest-based) ads or remarketing. Google may still receive your device’s IP address, advertising identifiers and information about the ads shown, to deliver ads, measure them, limit how often you see the same ad and prevent fraud.
On Android you can reset or delete your advertising ID in the device settings (Settings > Privacy > Ads, or Settings > Google > Ads, depending on the device).
On iOS the game does not use App Tracking Transparency and does not access the IDFA.
Consent in the EEA, the UK and Switzerland
If you are in the European Economic Area, the United Kingdom or Switzerland, the game shows Google’s consent form (Google User Messaging Platform, a consent management platform certified under the IAB Transparency and Consent Framework) before it requests any ad. Your choices are stored on your device and passed to Google. You can change them at any time with the Privacy button in the game menu. If you do not give consent, Google may show limited ads that do not use local storage on your device.
The consent form covers advertising. Analytics, Android crash reporting and remote settings work independently of it, on the basis of our legitimate interests described below. Declining ad consent or buying No Ads does not disable these services; the game currently has no in-app switch to turn them off.
Analytics
We use Google Analytics for Firebase to see how the game is played. We have configured it so that analytics data is not used for advertising: the advertising consent signals (ad_storage, ad_user_data, ad_personalization) are set to “denied”, and Google signals and ads personalization are turned off in our Analytics settings.
Event data is kept for 14 months and then deleted automatically. Aggregated reports that no longer relate to an individual device may be kept longer.
Android crash reports
The Android version uses Firebase Crashlytics, including native crash reporting, to find and fix crashes and measure stability. Reports can include crash stack traces and native crash data, app and device information, installation identifiers, a pseudonymous user ID derived from Android ID, the current level and level set, and recent Analytics events and their parameters that help explain what happened before a crash.
Crash reporting is enabled automatically when Firebase starts. A report may be stored locally and sent when you next open the game. Crash reports are used for diagnostics, rather than advertising or personalization. Crashlytics is not enabled in the current iOS build.
Remote settings
Once per launch the game asks Firebase Remote Config for its current settings. The request contains the Firebase installation ID, the app ID, version and package name, your device language and time zone.
In-app purchase
The optional No Ads purchase is processed by Google Play on Android and by the Apple App Store on iOS. We never receive your payment card details, name or billing address. The store only tells the game whether you own No Ads; the game asks it at every launch and when you tap Restore Purchases. The privacy policies of Google and Apple apply to the payment itself.
Third-party services
The game uses the following services. Each has its own privacy policy:
- Google AdMob (Google Mobile Ads SDK) and Google User Messaging Platform: Google Privacy Policy, How Google uses information from apps that use its services
- Google Analytics for Firebase, Firebase Installations, Firebase Remote Config and Firebase Crashlytics (Android): Privacy and Security in Firebase
- Google Play Billing: Google Privacy Policy
- Apple App Store (StoreKit): Apple Privacy Policy
Sharing
We share information only with the services listed above, as described in this policy. Google processes Firebase data on our behalf, and processes advertising data under its own privacy policy. We do not sell your personal information, do not share it for cross-context behavioral advertising and do not give it to data brokers. We may disclose information if the law requires it.
Legal bases (EEA, UK and Switzerland)
- Legitimate interests: analytics, diagnosing crashes and improving stability, remote settings, fraud prevention and security.
- Consent: storing and accessing information on your device for advertising, collected through Google’s consent form.
- Contract: providing the No Ads purchase you made.
International transfers
Google may process information outside your country, including in the United States. For transfers from the EEA, the UK and Switzerland Google relies on safeguards such as the EU-U.S. Data Privacy Framework and the Standard Contractual Clauses of the European Commission.
Data retention
- Data saved on your device: until you uninstall the game or clear its data.
- Analytics event data: 14 months.
- Android crash reports: Firebase states that crash traces, extracted native-crash data and associated identifiers are retained for 90 days before removal from live and backup systems begins. Raw native minidump files are stored temporarily while the crash session is processed and then discarded.
- Data processed by Google for AdMob, Remote Config and Google Play, and by Apple for the App Store: according to their own retention policies.
Your rights and choices
- Change your ad consent at any time with the Privacy button in the game menu (EEA, UK and Switzerland).
- Reset or delete your advertising ID in the Android device settings.
- Buy No Ads to stop all ads.
- Uninstall the game to delete local saved data and stop future collection from that installation. This does not delete reports or events already sent to Google; those are subject to the retention periods above.
- Depending on where you live, you may have the right to access, correct or delete your data, to object to or restrict its processing, and to data portability. To use these rights, email us. The game has no accounts and we do not know who you are, so we can only find data that is linked to your device; we will explain in our reply how to identify it. We answer within 30 days.
- You also have the right to lodge a complaint with your local data protection authority.
If you live in California, you have the right to know what personal information we collect, to request its deletion or correction, and not to be discriminated against for using these rights. We do not sell or share personal information as these terms are defined in California law.
Children
The game is intended for players aged 13 and over and is not directed at children under 13. Because younger players may still like it, every ad request is marked as child-directed, limited to G-rated content and not personalized. We do not knowingly collect personal information from children under 13. If you are a parent or guardian and believe your child is using the game, contact us and we will delete the analytics data linked to their device.
Security
The game does not run its own servers. Information is sent over encrypted connections (TLS) directly to Google and Apple, which store it with their own security measures. No method of transmission or storage is completely secure, so we cannot guarantee absolute security.
Changes to this policy
We may update this policy, for example when the game starts using a new service. The current version is always on this page, with the date of the last change at the top. Earlier versions of the game (1.x, made with the Unity engine) used a different set of libraries, including Unity services. This policy describes version 2.0.0 and later; Android crash reporting in the current version uses Firebase Crashlytics as described above.
Contact us
Grumpy Moose Games, nikita.gmgm@gmail.com