Mutant Survivor Privacy Policy

Effective 8 October 2026

This policy explains how Mutant Survivor, an Android game published by MutantLab, handles game progress and data used by Google Play Games Services, Google Mobile Ads and Google Analytics for Firebase. Features and privacy controls described here depend on your installed version.

Game progress stored on your device

The game saves permanent progress and preferences on your device. This includes earned DNA, kills and completed runs, upgrades, unlocked abilities and skins, gameplay milestones, and settings such as sound and ability opacity. The save lets you continue playing and keep your unlocks. MutantLab does not require a separate account to play.

Google Play Games sign-in and cloud saves

If you sign in through Google Play Games, the game uses Play Games Services to store a copy of your permanent progress and preferences as a Saved Games snapshot in your Google account and sync it across your devices. If the device and cloud saves differ, the game asks which one to keep. Google handles sign-in; MutantLab does not ask for or store your Google password. Google may process account and device identifiers needed to provide Play Games Services. See Google's Privacy Policy.

Test ads and privacy choices

During testing, the game uses Google's sample test ad-unit IDs. Optional rewarded ads are offered on the results screen; watching one is your choice and declining does not remove your normal run rewards. Newer builds also support occasional interstitial test ads after a run has ended, before the results screen. These are never shown during an active run, on app launch or exit, or during a menu action. Break ads require at least two completed runs lasting one minute or more, are limited to six per device per UTC day, and wait at least five minutes after the previous full-screen ad. Rewarded ads are limited to eight per device per UTC day, with five minutes between reward bonuses and one bonus per run. An automatic break ad does not consume the reward-bonus cooldown. Ad counters and timestamps are stored locally, separately from cloud progress. Verified Ad-Free Lab owners receive no ad requests and can claim the capped bonus without viewing an ad.

The Google Mobile Ads and User Messaging Platform SDKs may process an IP address, app and ad interactions (such as launches, taps and video views), diagnostic information, and device or account identifiers. Google uses this information for ad delivery, measurement, analytics and fraud prevention.

Version 1.0.12 and later do not ask for your age. New installations provide no publisher-supplied age signal to the ad SDK and are not recorded as adults. Personalized ads may be served when applicable privacy choices and Google's ad-serving rules permit them; consenting does not establish or verify your age. Google applies additional ad protections to Google accounts it identifies as belonging to younger users. The game does not obtain a date of birth from Google Play Games. Version 1.0.11 asked for a locally stored age group, separately from cloud saves. When updating from that version, previously declared Under-16 and undisclosed choices retain child-protected treatment and a PG content limit; declared ages 16–17 retain teen-protected treatment. Both disable personalized ads and remarketing. Earlier builds use teen protection for everyone. Other ad requests have a teen content-rating limit.

Google's consent message offers Consent, Do not consent and Manage options. Where consent is required, ads wait for the applicable choices. You can revisit those choices using Settings → Google Services → Privacy Options when Google requires that control. Changing consent clears cached ads. The Age Group control exists only in version 1.0.11. Google describes its SDK's data handling in its Google Play data disclosure. MutantLab does not sell your game-save data.

Gameplay analytics

Newer builds use Google Analytics for Firebase automatically when applicable privacy requirements permit collection; there is no separate Game Analytics switch. Collection waits for the current privacy check. Where consent is collected, the game requires permission for device storage and service improvement for MutantLab's own use, together with the relevant Google permission. Ad-partner consent alone does not enable our gameplay analytics. Previously declared Under-16 and undisclosed age choices keep analytics disabled after updating. In version 1.0.11, unknown age also kept analytics disabled; version 1.0.12 and later use the privacy flow for new installations without asking for age. Older testing builds, including version 1.0.10, have a separate Game Analytics switch that is off by default. You can play, save progress and sign in to Play Games without granting analytics consent.

When permitted, the game sends events about run starts and results, selected mutations and codices, boss defeats, kills, player levels, run duration, earned DNA and permanent upgrade totals. These reports help MutantLab understand difficulty and improve the game. Google Analytics also processes app-instance identifiers, app interactions, device and app information, and approximate location derived from IP addresses. Its SDK may automatically measure sessions, app updates and in-app purchases. Custom gameplay events do not contain your email, Play Games player ID, Google credentials, full save file or precise location.

The game's Firebase configuration disables Advertising ID collection and advertising personalization for analytics. Its custom analytics are not used to build advertising audiences. This setting is separate from the Google Mobile Ads SDK described above. See Google Analytics SDK data collection and Google's Privacy Policy.

Withdrawing the applicable permission in Privacy Options stops further analytics collection, discards unsent custom events in the game, clears analytics stored on this device and resets its analytics app-instance identifier. In version 1.0.11, changing to a protected age group has the same effect. In older builds, turning Game Analytics off also stops collection. These actions do not automatically delete information already received by Google or erase aggregate reports. For questions or requests about previously collected data, contact MutantLab at [email protected]. Google Analytics retention settings and policies govern data held by that service; see data retention.

Who receives data

Google receives data when you use Play Games sign-in or cloud saves, when its ad and privacy SDKs operate, and when permitted gameplay analytics are active. MutantLab can view analytics reports to understand game usage and improve balance. The game does not upload its local save to a MutantLab-operated server.

Storage, retention and deletion

Your device save remains in the game's app storage until you clear the app's data or uninstall it, subject to Android backup settings. A Play Games cloud save remains in your Google account until you delete that game's Play Games data or Google deletes it under its policies. You can remove a game's Play Games data through your Play Games profile; Google explains the steps here. Clearing only the device save does not automatically delete the cloud copy. If you delete the cloud copy but continue playing with a local save while signed in, the game may sync that progress again. For questions about your game data or a deletion request, contact MutantLab at [email protected].

Security

The local save is kept in the game's Android app storage. Google says the Mobile Ads SDK sends collected data using encrypted connections. Google Play Games handles transmission and storage of its cloud save. No method of storage or transmission can be guaranteed completely secure.

Age and changes

Mutant Survivor is intended for teens and adults aged 13 or older, not for children under 13. If the game or its data practices change, MutantLab will update this page and its effective date.

Contact

MutantLab — [email protected]