MARTILAR · PRIVACY
Privacy Policy
Scope and accounts
This policy describes the handling of game data and app services in the Martılar Android app. The inspected app contains no Martılar account creation, sign-in, developer-hosted profile, server synchronization of game progress, or purchase-verification server. A Google Play account is not a Martılar account; Google Play processes purchases through its service.
Game and preference data stored on your device
The game profile is stored in the device's WebView localStorage under the martilar.save.v1 key. The save can include route and mission progress, career score and hit statistics, spendable points, unlocked items and flags, reward inventory and reward-processing markers, selected item/flag, language, sound/music, and other game preferences. No flow uploading this game save to a Martılar developer or game server was found in the inspected source.
The app may choose its initial language from device language preferences; a language later selected by the player is stored on the device. The native language bridge passes Android language tags to the app.
Age and advertising privacy
The date entered on the ad-safety screen is used only in the app to calculate an age band. The save stores the coarse band (child, teen, adult, or unknown), not the date of birth. The inspected code does not persist the birth date or send it to UMP or the advertising SDK.
The age band remains in the on-device game save. The app maps it to separate advertising-safety signals: a Boolean under-age-of-consent tag in the UMP consent-information request, and a CHILD, TEEN, or UNSPECIFIED age-treatment setting in the Android Google Mobile Ads configuration. These are age/treatment signals passed to the SDKs, not the birth date. Google's Android GMA documentation says its age-treatment setting applies to ad requests. The app source does not establish the complete signal payload or Google's retention period.
The app updates consent information with Google User Messaging Platform (UMP) each session, presents a required message/form when applicable, and does not request ads unless canRequestAds permits them. UMP privacy options are available from Settings when required. UMP's own storage and Google-side retention cannot be verified from app source; Google's current UMP and AdMob disclosures apply.
On Android, the app initializes Google Mobile Ads only when the saved age band is adult and UMP permits ad requests. Full-screen rewarded and interstitial ads are available only under those conditions; they are blocked for child, teen, and unknown age bands. This describes inspected source behavior and is not a claim that protected-profile SDK network traffic has been measured on a real device.
When Google Mobile Ads is used, Google's Android GMA 25.5.0 data disclosure says the SDK may automatically collect and share IP address (which may be used to estimate general location), app interactions, diagnostics, and device/account identifiers (the advertising ID, App Set ID, and, where applicable, other identifiers associated with accounts). The disclosure lists advertising, analytics, and fraud-prevention purposes and TLS encryption in transit. This SDK data is separate from the game save and is not uploaded to a Martılar game server.
If Android system backup restores the saved age band to another device, the app can reuse that band without detecting the transfer or requesting age confirmation again. A transfer-specific age reconfirmation has not been implemented. UMP consent information is still refreshed each session.
Internet connectivity check
The app checks internet reachability by making a bodyless HTTPS request to connectivitycheck.gstatic.com/generate_204; it also reads Android's validated network state locally. The network request may expose the connection's IP address to Google. Martılar does not control or independently verify logging and retention by that Google endpoint.
Purchases
“Remove Ads” (remove_ads) is a one-time Google Play purchase. The app gets the product name and localized price from Google Play Billing. The inspected app code does not read payment-card details, billing address, or payment credentials; Google Play processes the payment. The Android Billing bridge passes the product ID, purchase state, acknowledgement state, and purchase token to the app for ownership checks. Ownership is rechecked through Google Play Billing queries; Martılar has no purchase server. Google Play's own terms and privacy disclosures apply to purchase data.
Google Play purchase ownership is separate from game progress: progress is in the on-device save, while remove_ads entitlement comes from a Google Play Billing ownership query. Clearing game data does not cancel a purchase. Google Play manages its payment and transaction records under its own terms and disclosures.
Sharing and third-party services
The inspected app does not upload the game save to advertisers or a Martılar server. Google Mobile Ads, UMP, and Google Play Billing communicate with Google to provide their respective services. The connectivity check also contacts Google's network-check endpoint. SDK transmission is separate from direct sharing of the game save and must be assessed separately in the Google Play Data Safety declaration.
Security
The game save is stored in Android app/WebView storage. No separate encryption layer for this save was found in the inspected app code. Android's app sandbox and device storage protections are provided by the platform; this review does not verify disk or backup encryption on any particular device. Google states that TLS is used in transit for data covered by its Google Mobile Ads disclosure. Current UMP and Billing security details are subject to Google's relevant documentation.
Retention, backup, and deletion
The game save remains on the device until the user clears app data or removes the app. The inspected Settings screen has no game-save deletion or account-deletion feature. A user can clear Martılar storage/data in Android app settings; that removes local progress and preferences. Uninstalling may remove app data, but Android backup may restore data.
The source Android manifest sets android:allowBackup="true" and defines no custom dataExtractionRules or fullBackupContent rule. Android system backup may back up eligible app data to cloud backup or transfer it directly between devices, depending on user/device settings and transfer type. This is separate from an upload to a Martılar game server. Whether this app's WebView localStorage is actually restored in cloud or device-to-device transfers has not been verified on an Android device. We therefore do not claim that game data is never backed up or that clearing app data removes every system backup copy.
The age band is part of that same local save. A valid restored band may currently be reused without a transfer-specific confirmation; no migration-specific age reconfirmation has been implemented.
There is no Martılar account and therefore no app account-deletion service. Clearing local game data does not cancel a Google Play purchase. Google Play purchase history is subject to the Google Play account and Google's retention rules. UMP choices can be changed through the privacy options provided by UMP; storage and deletion of UMP data follow Google's UMP behavior.
Privacy questions and contact
For questions about privacy, data access, or clearing local game data from your device, contact CronicFamily at gurcaykaan@gmail.com. The inspected app has no Martılar developer account or server profile containing a hosted player account record.
Changes to this policy
If the app, its SDKs, or its data practices change, this policy and its last-updated date will also be updated.