Privacy Policy

Effective date: June 18, 2026

Labmaster is a mobile idle network-building game developed by pungpungstudi. This Privacy Policy explains how Labmaster handles information when you play the game, view ads, or make in-app purchases.

Contact: Labmaster Support

Summary

Labmaster does not require an account and does not ask for your name, email address, phone number, contacts, photos, microphone, camera, or precise location.

The game stores gameplay progress on your device. If ads or in-app purchases are enabled in a release build, platform providers and advertising SDKs may process additional data as described below.

Information We Handle

Gameplay and Save Data

The game stores local gameplay data, including:

• credits, research, gems, energy, lab level, and protocol cores
• node graph layout, node ownership, upgrades, research unlocks, contracts, dailies, weekly sprint state, and tutorial state
• offline reward timing, cooldowns, and local settings
• privacy choices such as non-personalized ads and analytics preference

This data is used to run the game and restore progress on the same device. The current build does not use a player account or cloud save.

Advertising Data

Labmaster may show optional rewarded ads and, in future release builds, limited interstitial ads at natural breaks. The current internal build uses Google AdMob test IDs. Production builds may use Google AdMob.

Ads default to non-personalized. Personalized ads are locked in the current app flow until native Google User Messaging Platform consent and iOS App Tracking Transparency handling are integrated and reviewed.

Advertising SDKs may process data such as:

• IP address, which may be used to estimate general location
• device or advertising identifiers, such as Android Advertising ID or Apple IDFA when available and permitted
• ad interactions, app launches, taps, video views, and other product interaction events
• diagnostics such as SDK performance, app launch time, hang rate, or error information

This data may be used for advertising, ad measurement, analytics, fraud prevention, security, frequency capping, and measuring ad performance.

Purchase Data

In-app purchases are processed by the official platform stores: Google Play Billing on Android and Apple StoreKit In-App Purchase on iOS.

The game may store product IDs, purchase tokens or transaction identifiers, ownership flags, restore state, and entitlement status so it can grant purchases and avoid duplicate consumable grants. We do not receive your full payment card details.

Analytics and Crash Reporting

Separate analytics and crash reporting SDKs are not enabled in the current app design. Analytics defaults to off in the in-game Privacy Bay. If analytics or crash reporting is added later, this policy and store disclosures must be updated before release.

User Choices

On first launch, Labmaster opens Privacy Bay before tutorial, ad, analytics, or store-service choices. Players can later review or reset choices in Shop -> Privacy Choices.

Current defaults:

• non-personalized ads
• analytics off
• personalized ads locked until native consent is integrated

Children

The game is not designed to collect personal information from children. Final age-rating, family-policy, and child-directed service decisions must be completed in each store console before release.

Changes To This Policy

If the policy version changes, the app should ask players to review Privacy Bay again. Store listings and public policy URLs must be updated before submitting a build that changes data collection or sharing.

Contact

For privacy questions, contact Labmaster Support.