Privacy Policy — Monster Lab
Effective Date: September 9, 2026
Developer / Publisher: NgDinhNha
Contact: https://ngdinhnha.blogspot.com/p/contact.html
1. Developer-Operated Services Not Used
Monster Lab has no account/login, developer-operated gameplay or cloud-save backend, real-money billing, standalone Firebase Analytics/product analytics SDK, standalone crash-reporting SDK, location feature, camera/microphone feature, contacts/messages integration, or user-to-user social feature.
2. Google Mobile Ads and Third-Party Data Processing
Monster Lab uses the Google Mobile Ads Next-Gen SDK to request and display advertisements. According to Google's current Android SDK disclosure, the SDK automatically collects and shares certain information for advertising, analytics/measurement, and fraud-prevention purposes. Depending on device, configuration, consent, and applicable law, this can include:
- IP address, which may be used to estimate general device location;
- user product interactions such as app launches, taps, and video views;
- diagnostic information such as app/SDK performance, launch time, hang rate, and energy usage;
- device/account identifiers such as Android advertising ID, app set ID, and where applicable other identifiers related to accounts signed in on the device.
Google states that Mobile Ads SDK data is encrypted in transit using TLS. Google and participating ad providers handle data under their own policies, consent choices, applicable law, and the advertising configuration used for the release. See Google's Privacy Policy.
Monster Lab does not add Firebase Analytics or a developer-operated analytics backend. References to analytics/measurement here include processing performed by the advertising SDK itself.
3. Consent and Privacy Choices
Monster Lab uses Google's User Messaging Platform (UMP) to update consent information and display a consent form when required. Ads are requested only when UMP reports that ad requests are permitted.
When UMP reports that a publisher-provided privacy-options entry point is required, Monster Lab shows Privacy Choices in the in-app About & Privacy screen. The exact messages and choices depend on the publisher's AdMob Privacy & messaging configuration, geography, applicable law, and Google services.
4. How Advertising Affects Gameplay
- A successful Expedition grants its normal result before any ad offer.
- An optional rewarded ad may add a bounded Coin/Research Point Expedition bonus.
- The free Emergency Reserve remains available without an ad when Energy is below 10, at most once per UTC day.
- After that free reserve was used and Energy later falls below 10 again, one optional rewarded ad may restore up to +5 Energy that UTC day.
- Rewarded bonuses are granted only when the ad SDK reports that the reward was earned. Ad dismissal, failure, or no-fill does not grant the extra bonus and does not remove normal gameplay rewards.
- Interstitial ads are frequency-capped and limited to natural breaks after onboarding.
Core Fusion, Care, Expedition, Research, collection, timers, and local save/load remain usable without watching an advertisement.
5. Local App Data
Monster Lab stores gameplay state in private local app storage. Primary structured progress uses a Room/SQLite database. Narrow private preferences preserve the free Emergency Reserve/rewarded-Energy daily gates and restrained interstitial frequency/timestamps.
Local state can include owned/discovered monsters; traits, mutations, favorites, mood and bond; Coin, Gene, Energy, Research Points and care samples; Encyclopedia/research/facility progress; quests/contracts/Boss Samples; expedition history; incubation/anomaly/Perfect Project state; care needs/streaks/observations/mastery; habitats; care items; Living Lab Journal and season state; and the local state needed to enforce the documented daily/ad-frequency rules.
Monster Lab does not upload the Room gameplay database to a developer-operated server.
6. Android Backup and Device Transfer
Monster Lab enables standard Android backup support (android:allowBackup="true"). Depending on Android/Google settings and effective backup rules, the operating system may copy or restore eligible app data/preferences through platform backup or device-transfer services. NgDinhNha does not operate those services and does not receive or access those backup files.
7. Network and External Links
The app requests Android INTERNET and ACCESS_NETWORK_STATE permissions for advertising/consent network behavior. Core gameplay remains offline-first. If ads are unavailable or there is no network connection, ordinary gameplay remains available.
The About & Privacy screen includes an optional support/contact action that opens the user's external browser. That browser is governed by its own privacy practices.
8. Purchases
The current candidate has no real-money billing or purchase integration. Rewarded ads provide only the bounded optional bonuses described above and do not unlock an ad-exclusive species or power path.
9. Children's Privacy / Target Audience
The repository does not make the developer's final legal/store target-audience decision. Because the candidate contains advertising, the developer must select intended age groups and configure any required child-directed/family/ad-treatment settings in Google Play and AdMob before release. This policy does not claim a particular child-directed treatment until that final configuration is selected and verified.
10. Data Retention and Deletion
You can remove Monster Lab's locally stored app data by clearing app storage in Android Settings or uninstalling the app. Platform backup copies, if any, are managed through Android/Google backup settings. Monster Lab has no developer-hosted player account database requiring a separate server-side account deletion request. Data handled by Google or advertising providers is subject to those providers' retention/deletion controls and policies.
11. Security
Local app data is stored in Android private app storage subject to the device/platform security model. Google states that Mobile Ads SDK data is encrypted in transit using TLS. The exact release configuration and dependencies are reviewed before publication.
12. Changes to This Policy
This policy may be updated when game features, advertising/consent configuration, technical integrations, or applicable requirements change. The published copy will identify its effective date.
13. Contact
For questions or privacy concerns, use the official support/contact page: https://ngdinhnha.blogspot.com/p/contact.html.
Comments
Post a Comment