Summary
Mahjong for Seniors: Big Tiles is a single-player puzzle game. No game account is required and core gameplay works offline. iOS version 1.5.0 offers optional coin purchases through Apple and does not include an active advertising SDK. On a new installation of iOS 1.5.0, accepting the displayed Terms and Privacy Policy enables Firebase Analytics and Crashlytics as disclosed on the welcome screen. You can turn Analytics & crash reports off under Privacy & Data; gameplay and purchases remain available. Existing players retain their saved preference. Earlier versions may provide separate enable/continue-without-sharing choices. Analytics is not used for advertising or cross-app tracking.
Data Stored on Your Device
The app stores game progress, the active puzzle, preferences including your Analytics & crash reports choice, and your acceptance of the Terms of Use and Privacy Policy locally on your device. You can change this choice at any time in Privacy & Data. Local copies remain on the device until you clear the app data or uninstall the app. Game progress and economy records may also be stored in your private iCloud database as described below; Analytics and notification preferences remain local to this installation.
Your Choices
In version 1.5.0 on iOS and Android, the first-launch Start action accepts the Terms and Privacy Policy and enables Analytics & crash reports as disclosed on that screen. This is not a separate analytics opt-in. You may turn the setting off at any time under Privacy & Data without losing access to gameplay or purchases. Earlier versions with separate enable/continue-without-sharing buttons follow the choice shown in those versions. Turning the setting off stops future optional uploads, resets Analytics data for this installation, and deletes unsent crash reports. If you do not agree to these documents, do not use the app.
Analytics and Crash Diagnostics
While Analytics & crash reports are enabled, Firebase Analytics may receive basic app, device, and session information, such as app version, operating system, device model, language, an approximate region derived from the network address, session activity, and a randomly generated app-instance identifier. We also send gameplay events and measurements used to understand level funnels, player retention, feature use, and difficulty, including game mode, level number and difficulty category, level start and outcome, moves, matched pairs, remaining tiles, holder count, active play time, and use of hint, shuffle, undo, rescue, share, or review-prompt actions.
While the same setting is enabled, Firebase Crashlytics may receive crash logs, stack traces, thread and process state, app version and state, device model, operating-system information, memory and storage state, and installation identifiers needed to associate crash events. We use these diagnostics to investigate crashes and improve stability. Analytics events and crash reports do not intentionally include tile faces or tile identifiers, board seeds, shared-link contents, free-form text, names, email addresses, or account identifiers.
In Android versions before 1.3.0, Firebase Installations may automatically generate and process a per-installation Firebase installation ID and Firebase user-agent information about the SDK, app, and device needed to provide Firebase services, independently of optional Analytics and crash reports. In version 1.3.0, Firebase Installations is initialized only after the same opt-in as Analytics and crash reports. This identifier is not an advertising identifier and is not used for advertising or cross-app tracking.
Purchases in iOS 1.5.0
Optional consumable coin packs are processed by Apple through StoreKit. Apple handles your payment and App Store account information under its privacy policy; we do not receive payment-card details. The app verifies Apple transactions locally and stores the coin balance, product identifier and completed transaction identifiers on your device and in your private iCloud save to deliver coins and prevent duplicate grants. Coin purchases and spending coins on boosters require an internet connection and available iCloud sync. Paid deliveries and coin spending are confirmed in the cloud and saved locally before becoming available. There is no developer-operated iOS receipt server or separate game account. Restoring a saved balance does not regrant coins that have already been spent.
While Analytics & crash reports are enabled, coin-economy events sent to Google Firebase include whether coins came from an in-app purchase, the coin amount and balance, associated with the app-instance identifier. We use these purchase-related events for product analytics, not advertising. Transaction identifiers are not included in these custom analytics events. Turning analytics off does not prevent a purchase or delivery of purchased coins.
Purchases in Android 1.5.0
Optional coin packs are processed by Google Play Billing. We do not receive payment-card details or your Google account email. To verify a purchase and prevent fraud, the app sends the product identifier, Google Play purchase token and a randomly generated installation account identifier to our verification service hosted on Google Cloud Run. The service checks the order with Google Play before the app delivers coins. Purchase tokens and account identifiers are processed in memory and are not intentionally written to application logs or a server-side wallet. Operational logs may retain request timing, status and network metadata for service security and reliability.
The Android app saves coin balances, progress and hashed transaction identifiers locally and consumes the purchase only after saving delivery. Verification and purchases require internet access; spending owned coins and normal gameplay do not require iCloud. Android does not provide the iCloud backup described below. Completed consumable purchases cannot restore a lost local balance after app data is deleted. While Analytics & crash reports are enabled, purchase-related coin amounts and balances may be sent to Firebase for analytics; purchase tokens are not included in these events.
iCloud Game Saves
iOS 1.5.0 uses Apple CloudKit to save progress in the signed-in user’s private iCloud database. The save includes campaign progress, the current board, coin balance, booster inventory, reward state, completed purchase identifiers and coin-spend identifiers used to prevent duplicate deliveries or spending. The app uses an opaque CloudKit account identifier locally to detect account changes. We do not receive your Apple ID email address, password or payment-card details, and there is no public player database or developer-operated save server.
Cloud saves support restoring progress for the same iCloud account. When local and cloud progress conflict, the app asks you to choose cloud restoration from Home and creates a local backup before replacing progress. Uninstalling the app removes local information but does not necessarily delete the private iCloud save. You can manage the app’s iCloud data through Apple’s iCloud storage settings. Switching iCloud accounts, deleting cloud data or disabling iCloud may prevent syncing, restoration and coin transactions; regular gameplay and already-owned boosters remain available. Analytics and notification choices are not transferred to another installation through the cloud save.
Apple provides and secures iCloud under its privacy policy. Turning Analytics & crash reports off does not turn off iCloud saves, which are used for app functionality rather than advertising or analytics.
Advertising in Ad-Enabled Versions
Version 1.5.0 on iOS and Android does not display ads or initialize an advertising SDK. The following applies only to separately identified ad-enabled versions: versions that display ads use Google AdMob for optional rewarded ads and occasional interstitial ads between completed games. Older ad-free versions do not initialize an advertising SDK. Google may process your IP address and approximate region, app or device identifiers, ad views and interactions, and performance or crash diagnostics for advertising, measurement, and fraud prevention. Advertising involves network requests; core gameplay remains available offline.
Advertising consent is separate from the Analytics & crash reports setting. Where required, Google’s consent form appears before ads are requested. You can review or withdraw applicable choices through Ad privacy choices in Settings. If consent information does not permit ad requests, ads are not loaded. Rewards require completing the optional ad; unavailable or cancelled ads do not consume coins.
For details, see Google advertising technologies and Google Privacy Policy.
Data We Do Not Collect
We do not ask you to provide your name, email address, contacts, photos, precise location, payment details, health information, or other personal profile information through the app. Ad-enabled versions include Google AdMob. The app does not request precise location or Apple’s App Tracking Transparency permission. Android advertising ID permission is removed from the app manifest. We do not sell personal data or use Analytics for advertising.
Data Retention and Deletion
Turning Analytics & crash reports off stops future optional collection, resets this installation’s Analytics state and identifier on the device, and deletes crash reports that have not yet been sent; it cannot recall uploads already in progress or delete information already retained by Google. At the date of this policy, the production Analytics property is configured for two months of event-data retention and 14 months of user-data retention. Crash diagnostics are retained according to the Firebase service’s applicable settings and terms. Because the app has no account and does not attach your name, email address, or another account identifier to these records, we generally cannot locate a particular person’s previously submitted records. Clearing app data or uninstalling the app removes locally stored game information and stops optional collection from that installation. Private iCloud saves may remain until removed through iCloud storage settings, as explained above.
Service Provider and Security
Google provides Firebase Analytics, Firebase Crashlytics, and Firebase Installations. Google processes optional Analytics and crash-diagnostic information on our behalf after you enable Analytics & crash reports; in Android versions before 1.3.0, the Firebase Installations service data described above may be processed independently. Data is encrypted in transit. Google describes its Firebase privacy and security practices in Privacy and Security in Firebase and its broader practices in the Google Privacy Policy.
Permissions and Network Access
Core gameplay works offline and does not require access to your contacts, camera, microphone, photos, or location. Coin purchases use network access on both platforms. On iOS, iCloud saves and spending coins on boosters also use network access. When Analytics & crash reports are enabled, optional Analytics information and crash diagnostics may be sent to Firebase when a network connection is available. In Android versions before 1.3.0, the Firebase Installations service data described above may be transmitted independently of that optional choice. Your device platform or an authorized app store may independently process download, diagnostic, or support information under its own privacy policy.
Children's Privacy
The app is not designed to ask children for personal details. A parent or guardian should review the Terms of Use and this Privacy Policy before allowing a child to continue. If you believe a child has provided personal information through the app, please contact us so we can review the concern.
Changes to This Policy
If a future version adds online services or changes its data practices, we will update this policy and its effective date before those practices apply.
Contact
Questions about this policy can be sent to Mala Tech LLC at ruskyluo@gmail.com.