MergeMate Privacy Policy

Updated September 6, 2026. This policy describes MergeMate version 1.3 for Android and iOS, its website and its friend-match service. The app identifier is games.mickey.mergemate.

Local play and optional platform services

The solo campaign works offline and does not require a MergeMate account. Progress, earned stars, daily challenge records, the current position and settings are saved on your device.

On Android, the game attempts Google Play Games sign-in using your platform account and sign-in choices. Playing the solo campaign does not depend on successful sign-in. Once signed in, the game synchronizes unlocked levels, stars and daily challenge records with Google cloud saves and submits progress and total-star leaderboard scores. Google also processes the game-account identifiers, gamer name and avatar used for these features. Your Play Games profile settings determine who can see your profile and game data. Play Games services may also process device identifiers, IP addresses and approximate country or region to provide game services. The SDK has its own analytics and diagnostics processing for SDK stability and product improvements. You can manage sign-in, profile visibility and related game data through your Google Play Games account settings. These services are separate from the gameplay-diagnostics choice below. The current iOS version stores progress locally and does not provide Game Center cloud saves or leaderboards.

Optional gameplay analytics and crash reports

Gameplay analytics and crash-report collection are off by default. If you allow “Share gameplay data,” we enable the relevant Google Firebase Analytics and Crashlytics collection to improve difficulty, controls and stability. Declining does not restrict game content.

This can include level starts and results, move and merge counts, star objectives, hint and undo use, session duration, app version and timing, crash traces, and device and operating-system state. After you enable Analytics, the service also derives an approximate country or city from your network IP address to analyze regional usage; this is not precise GPS location. Firebase may also process app-instance or installation identifiers to count sessions, distinguish installations and diagnose failures. These events do not ask for your name, email address or chat messages. Technical identifiers can connect activity from the same installation, so this data is not completely anonymous.

You can turn collection off in Settings → Share gameplay data. This stops future gameplay-diagnostics delivery and resets local Analytics data; it does not automatically delete records already sent to a server. The switch does not control the processing needed for Google Play Games, online matches or website access. Service initialization and network communication may also involve necessary device and connection information.

Friend matches and website access

Friend matches require the internet. Room codes, game mode, position seed, assigned seat and move, merge and deployment actions pass through a Cloudflare-hosted service to the other player in the room. The game has no open text chat and does not require you to disclose your real name or email address to your opponent.

The room service currently does not write a persistent match-history database and removes a connection's room session when that connection closes. The website and match service may still process IP addresses, request times, connection status and error logs to operate the service and investigate failures. Ending a match does not mean every service log is immediately deleted. The website has no gameplay-analytics script; hosting-related technical processing is separate from your in-game diagnostics choice.

Advertising, sharing and notifications

This version 1.3 release offers no ads, ad rewards or in-app purchase products. Advertising SDKs remain in the package as inactive dependencies, while the game's ad controls and active ad-service initialization are disabled. Gameplay-diagnostics consent does not enable ad personalization. Firebase consent for advertising storage, advertising user data and ad personalization remains denied.

Victory cards are generated locally and passed to the system share sheet only when you choose to share. You choose the receiving app, whose privacy practices then apply. Card generation does not read your photo library or contacts. Android daily reminders are local device notifications; you can decline notification permission or disable them in system settings. The current iOS version does not provide these reminders.

Service providers and retention

We use Google Firebase for optional diagnostics, Google Play Games for Android platform game services, and Cloudflare for website hosting and match connections. These services may process data outside your country or region. See the Firebase privacy information, Google Privacy Policy Play Games data information, and Cloudflare Privacy Policy.

Local data normally remains until you clear app data or uninstall. Operating-system backups or Google Play Games cloud saves may restore progress after reinstallation. Cloud saves, previously sent diagnostics and service logs are handled under the relevant services' retention rules and storage settings. Uninstalling or withdrawing diagnostics consent does not automatically delete all cloud data.

Children and privacy requests

This game is not directed at children under 13, and we do not knowingly collect children's personal information. Please contact us if you believe a child has supplied personal information to us.

You may contact us about data handling or to request access, correction or deletion. Include your platform, app version and the type of request; do not send passwords or full payment information. We will review what relevant data can be identified and what action is available. Google account and Play Games data can also be managed using Google's account tools. We will update this page and relevant in-app choices when future features change how data is used.