PRIVACY POLICY
Mosaiva: Falling Blocks
Last updated:
1. Scope
This policy covers the Android game Mosaiva: Falling Blocks, package com.pantevia.games.mosaiva, operated by Burhan Kuzucu (Pantevia Games) in Türkiye. It supplements the main website policy and takes precedence for this game.
2. Local game data
Progress, scores, virtual coins, cosmetics, language, settings, age group and unfinished games are stored on your device. The game has no player account, cloud save, online leaderboard, developer-operated game server, real-money purchases, Firebase Analytics or Crashlytics.
3. Advertising
The Google Play and Huawei Android configurations use different advertising services. The Huawei disclosure below covers the prepared 3.6.22 production APK and distinguishes it from earlier test builds. Preparing this APK does not confirm an AppGallery public release, store approval or guaranteed ad availability.
Google Mobile Ads provides banner ads and, for users aged 18 or older, interstitials on eligible returns to the menu and optional rewarded ads for continuing or earning coins. Rewarded ads are not loaded or shown to users under 18 or users of unknown age, and their reward offers are hidden. Virtual coins cannot be exchanged for cash or transferred to other players.
Google may process IP-derived approximate location, device identifiers, ad interactions and diagnostics for advertising, measurement and fraud prevention. Non-personalised ads still involve technical data. Google governs its own retention and processing, which may occur outside Türkiye. The game does not request precise-location permission.
Google Privacy Policy · Google advertising SDK data disclosure
4. Age and privacy choices
The Google-specific controls in this section apply to the Google Play configuration. The Huawei configuration follows the separate adult-only controls described below.
The intended audience includes school-age children, teenagers and adults. A neutral age-selection screen is shown before advertising is enabled. Your exact age is used temporarily to determine an age group; only the group, not the exact age or date of birth, is saved on the device. Advertising stays off while the age group is unknown.
Under-13 users receive child-directed treatment; ages 13–17 receive under-age-of-consent treatment. For both groups, child/privacy targeting and disabled ad personalisation are configured before advertising SDK initialization. Google Mobile Ads’ publisher first-party ID disabling API is then applied after initialization, as required by the SDK, and before any ad request. If this setting cannot be applied, ad requests remain blocked. Neither group receives interstitial or rewarded ads. All age groups use a maximum ad content rating of G. Adult personalisation depends on applicable privacy choices. These safeguards are not a claim that non-personalised advertising processes no data.
Google UMP updates privacy information on each launch once an age group is available and shows forms where required. Ad loading requires the native UMP canRequestAds result and successful application of the publisher first-party ID setting. Settings provides age selection and a Privacy options entry when Google UMP reports that it is required. Changing preferences does not delete data already processed by Google.
Huawei / Petal Ads — production configuration, 3.6.22
The separate Huawei Android build uses Petal Ads Lite SDK 13.4.91.301 and Huawei Ads Consent SDK 3.4.91.301, instead of Google Mobile Ads and Google UMP. Version 3.6.22 uses production ad-unit identifiers. Banner ads, interstitials on eligible menu returns and optional rewarded ads for continuing or earning virtual coins require the 18-or-older age group and explicit permission. No Huawei ad requests are enabled for users under 18 or of unknown age. Requests are non-personalised and use the maximum content classification W. W is an ad content filter, not an app age rating or a promise of data-free processing. An unavailable ad does not prevent normal gameplay.
Petal Ads and the advertising providers reported by its Consent SDK may process device/advertising identifiers, IP-derived approximate location, device and network information, advertising interactions and technical diagnostics for ad delivery, measurement, fraud prevention and service operation. Before its explicit advertising SDK initialization, the app disables optional Wi-Fi, Bluetooth, Android ID and memory-size information use through the SDK settings. The APK does not request location, Wi-Fi-state, Bluetooth-scan or broad installed-app-list permissions. Disabling Android ID does not disable every advertising identifier, such as OAID. Huawei’s SDK guide also describes other configuration-dependent information; not every SDK category has been observed in this game. These settings do not control Huawei services used by other apps, establish zero background processing, or make non-personalised ads data-free.
After an adult allows advertising, the game requests updated Huawei consent information before explicitly initializing the advertising SDK. Where required, or when the reported provider list changes, a separate screen displays provider names and HTTPS privacy links for your choice. Invalid required provider information or a failed consent update blocks new ad requests. The SDK supplies the provider list; it does not prove that every provider receives data in every request. Huawei/HMS Core or AppGallery services may participate under their own terms. Providers control their processing and retention, which can occur outside Türkiye. We have not established one retention period for all providers.
You may decline and play without ads, or change your choice in Settings → Privacy options. The local choice, notice version, timestamp and a fingerprint of the reported provider list are stored on your device. Production notice version 3 requires a new choice instead of reusing an accepted test-build choice; a saved refusal remains effective. Acceptance is rechecked after a notice change or 180 days; this is a technical renewal interval, not a provider-data retention period. A minor or unknown-age profile invalidates previous acceptance. Each accepted launch refreshes SDK consent information. Withdrawal stops the app’s new ad requests and pending retries but does not erase provider-held data or undo already-started SDK processing.
Earlier test builds use Huawei test ad-unit identifiers, and the separate ads-disabled release candidate does not enable the app’s advertising or consent requests. This does not change the production configuration described here. Use each provider’s displayed privacy policy and privacy/request controls for provider-held data. Use our support and deletion links below for data held by Pantevia Games. This disclosure is not a certification of full regional legal compliance, completed store review or public Huawei release.
Huawei Ads SDK compliance guide · Huawei Privacy Policy · Advertising providers
5. Deletion and support
Local game data is retained on the device until you clear app storage or uninstall the game. Android application backup is disabled in the game’s configuration; operating-system or manufacturer-specific device-transfer behavior is outside the game’s control. Google controls provider-held data separately; consult Google’s privacy controls and retention information for that data. Email support involves your address, message and attachments under our main privacy policy; these are separate from local saves.
support@panteviagames.com · Data deletion · Main privacy policy
