BumuStudios·Türkçe sürüm·ImageToPdf policy·PdfPages policy
Privacy Policy — Mahjong Solitaire
Android game, package com.bumustudios.mahjong
Effective date: 9 October 2026. Last updated: 9 October 2026.
No account, and your progress stays on your phone. There is no sign-in and no server belonging to this game. The game does not read your files, your photos or your contacts — it never asks for a single storage permission. Every board, including the daily challenge, is dealt on your phone, offline.
What does leave your phone is described in full below: Google's advertising and payment services, the advertising partners Google's AdMob may pass an ad request to, and the usage statistics and crash reports that the developer collects through Google Firebase. If you buy the one-time ad removal, the interruptions stop; the only ads left are the optional ones you can choose to watch for a hint or a shuffle.
Who this policy is from
This policy covers the Android game Mahjong Solitaire, distributed through Google Play
under the package name com.bumustudios.mahjong. It is written by the game's
independent developer, BumuStudios. Questions can be sent to the address in
Contact.
What the game is
Mahjong Solitaire is a tile-matching game. Tiles are stacked in layers; you tap two identical free tiles to take them off the board, and you win by clearing it. There are endless numbered levels and a daily challenge, one fixed deal per day with a streak counter. Undo is always free; hints and shuffles are offered in exchange for an optional ad. No account, no subscription, no energy system.
The game runs entirely on your device
This is the most important section, so it is stated plainly:
- Your moves and your progress are not uploaded. The game has no backend of its own. Your stars, your best times, your daily streak and your round in progress are not transmitted anywhere and there is no online leaderboard. The usage statistics described below record when the game is opened, which screens are shown and for how long — never your moves, your times or your progress.
- The daily challenge needs no server. Each day's deal is derived from the date on your device, and every board is dealt on your device from the game's own layouts. No network request is involved.
- The game reads no files. It requests no storage, camera, microphone, contacts or location permission — not on any Android version.
What the game stores locally
The game keeps a small amount of state in its own private storage on the device. None of it is personal information, and none of it is sent anywhere:
- your theme, text size, language, sound, vibration and "Shade blocked tiles" choices;
- your unlocked levels, the stars and best time for each level, your best daily time, your daily streak and the last day you played it, and totals of boards completed and tiles cleared;
- the round in progress, so that a board you have started survives the game being closed in the background and can be resumed;
- whether the one-time "remove ads" purchase is active;
- a counter of how many interstitial ads have been shown, used to keep ad frequency low.
This local state is deliberately excluded from Android cloud backup and from device-to-device transfer, so it is not copied to your Google Drive. Google's advertising and consent components, and the advertising partners' components described below, also keep their own settings on the device, under their own control, and the Google Firebase components described below keep three random identifiers in the game's private storage: a Firebase installation ID, the Analytics app-instance ID and a Crashlytics installation ID. Unlike the list above, these identifiers travel with the usage statistics and crash reports. Uninstalling the game or clearing its data removes everything the game has stored, these identifiers included.
Advertising — Google AdMob
The game is free and is supported by ads served through Google AdMob (Google Ireland Limited / Google LLC, depending on your region). AdMob is embedded in the game as a software development kit, and it does collect data, independently of the developer. When ads are served, AdMob and Google's advertising partners may collect and process:
| Data | Used for |
|---|---|
| Advertising ID (a resettable identifier assigned by Android) | Ad serving, frequency capping, ad measurement, fraud prevention |
| Approximate location — coarse, derived from your IP address, not GPS | Serving ads relevant to your country or region, and legal compliance |
| Device information — model, operating system version, language, screen and network characteristics | Rendering ads correctly, ad measurement, fraud prevention |
| App interaction events — that an ad was requested, shown, clicked or closed | Ad measurement, billing advertisers, fraud prevention |
The game does not request GPS or precise location permission, and it does not send your progress or your play history to AdMob or to any advertising partner. The developer receives no personal data from AdMob — only aggregated, anonymous reporting such as impression and revenue totals.
Because ads require an advertising identifier, the game declares the
com.google.android.gms.permission.AD_ID permission. The ad formats used are:
- a banner at the bottom of the home screen and of the game screen, below the game's buttons and never over the board;
- an interstitial when you leave a finished board (Next level, Play again or Back to home) or start over or leave a board on which no move is left — never during play, never for your first two boards, and never two full-screen ads within 45 seconds;
- an optional rewarded ad that you choose to watch in exchange for a hint or a shuffle. These buttons appear only when an ad is ready. When no move is left and no ad is ready, the shuffle is free;
- an app-open ad when you return to the game after leaving it, at most once every four hours.
No interstitial ever appears in the middle of a board.
How Google handles this data is governed by Google's own policies, not by this one:
- Google Privacy Policy
- How Google uses information from sites or apps that use our services
- AdMob and third-party advertising
Advertising partners — AdMob mediation
To fill ad requests, AdMob uses mediation: for any given ad request it may pass the request to one of the advertising networks below instead of serving a Google ad. The game includes these networks' software development kits for that purpose; AdMob starts them only after the consent step described under "Your advertising choices". Which network, if any, serves a particular ad is decided by AdMob at the time of the request, not by the game.
When a request is passed to one of these partners, that partner receives the same categories of data listed in the table above — the advertising ID, approximate location derived from your IP address, device information and ad interaction events — and processes them as an independent company under its own privacy policy. Your consent choices made in the game are passed on to them together with the request.
| Partner | Privacy policy |
|---|---|
| AppLovin | legal.applovin.com/privacy |
| Unity Ads | unity.com — game player and app user privacy policy |
| Liftoff Monetize (formerly Vungle) | liftoff.ai/privacy-policy |
| Meta Audience Network | facebook.com/privacy/policy |
| Mintegral | mintegral.com/en/privacy |
| Pangle | pangleglobal.com/privacy |
None of these partners receives anything from the game other than what is needed to request, show and measure an ad. They do not receive your progress, your settings or anything you do in the game.
Usage statistics and crash reports — Google Firebase
To see how the game is used and to find and fix crashes, the developer has built two Google Firebase services into it: Google Analytics for Firebase and Firebase Crashlytics. Google provides them as the developer's data processor, and they are active only in the version of the game distributed through Google Play. The game adds nothing of its own to what they collect — no custom events, no user ID or user properties, no custom keys or log messages — so only their automatic collection applies:
| Data | Used for |
|---|---|
| App-instance ID — a random identifier that Analytics creates for this installation | Counting installations and sessions without knowing who you are |
Advertising ID — the resettable identifier described above, available to Analytics
because the game declares the AD_ID permission for AdMob |
Usage statistics; use for advertising only as far as your consent choices allow (below) |
| Approximate location — country or region, derived from your masked IP address, not GPS | Statistics by country and region |
| Device and game information — device model, operating system version, language, game version | Statistics by device, Android version, language and game version |
| Usage events — first open, sessions, screens viewed, engagement time, updates and removal of the game | How many people use the game, how often and for how long, and which screens they open |
| How the game was installed — the Google Play install referrer (for example the store listing or a campaign link) | Counting where installations come from |
| Purchase events reported by Google Play — product, name and price of the one-time "remove ads" purchase | Counting purchases; no card or payment details are included |
| Crash reports, sent only when the game crashes or hits a fatal error — the stack trace, the state of the app at that moment (for example whether it was in the foreground), device details (model, operating system version, orientation, free memory and disk space) and a random Crashlytics installation ID | Finding and fixing crashes, and counting how many installations a crash affects |
Analytics records that a screen was shown and for how long, not what you do on it, and a crash report shows where in the code the crash happened, not your content. Neither service receives your name, your email address or any account details.
In the EEA, the UK and Switzerland, the consent form described below under "Your advertising choices" also covers Analytics: your choices there decide whether Analytics may store its identifiers on your device and whether the data may be used for advertising. Use of the data for advertising ("ad user data") and for ad personalisation stays off there until you consent. You can change your choice at any time from Settings → Privacy options; the entry appears where it is required. The game has no separate switch for the usage statistics or the crash reports; uninstalling it stops both.
Analytics keeps data linked to an installation's identifiers for no longer than 14 months; aggregated reports that contain no identifiers may be kept longer. Crashlytics keeps crash reports for 90 days.
Google processes this data on the developer's behalf, as its data processor, under the Firebase and Google Analytics data processing terms. It may be processed on Google's servers outside your country, including in the United States, and it is encrypted in transit (TLS).
Google describes these services here:
Purchases — Google Play Billing
The game offers one optional, one-time, non-consumable purchase that permanently removes the interrupting ads. There is no subscription and nothing recurring. The rewarded hint and shuffle remain available after the purchase — they only ever play an ad when you ask for one.
The transaction is handled entirely by Google Play Billing. The developer never sees or receives your card number, bank details, billing address or full name. Google Play reports only aggregated sales figures, and Google Analytics for Firebase records that a purchase was made — product, name and price, with no payment details (see above). Inside the game, the purchase is recorded as a single true/false flag on your device, restored from your Google Play account when you reinstall or move to a new device.
Google's handling of payment data is covered by the Google Privacy Policy and Google Play's terms.
Your advertising choices
If you are in the EEA, the UK or Switzerland
Before any ad is requested, the game shows a consent form built with Google's User Messaging Platform, where you choose what you allow — for Google and for the advertising partners it works with. Your choice is stored on your device by Google's component, is respected on later launches, and is passed on with every ad request, including those AdMob passes to a partner.
You can change your decision at any time: open the game, go to Settings → Privacy options, and the same form reappears. You may withdraw consent there. Withdrawing consent does not disable the game; you can keep playing, and ads may still be shown in a non-personalised form. The same choices also apply to Google Analytics for Firebase, as described above.
If you are in a US state with a privacy law
Where a US state privacy law gives you the right to opt out of the "sale" or "sharing" of personal information or of targeted advertising, the game handles that choice through the same Google consent tooling. Where it applies, Settings → Privacy options opens the corresponding Google form, and your choice is applied to the ads the game requests.
Everywhere else
The privacy options entry appears only where a consent choice is legally required, so you may not see it. You can still control advertising at the operating-system level: open Android Settings → Privacy → Ads (the exact path varies by manufacturer and Android version) to reset your advertising ID, or to delete it entirely, which stops apps from receiving a stable advertising identifier.
Removing ads completely
Buying the one-time ad removal stops the banner, interstitial and app-open ads altogether. The only ads left are the rewarded hint and shuffle, which play only when you tap their buttons; the game loads one in advance so that it is ready.
Permissions the game requests
INTERNET— required to fetch ads, to communicate with Google Play Billing and to send the usage statistics and crash reports described above. Nothing else is sent over the network.ACCESS_NETWORK_STATE— lets the ad components check whether a connection is available before trying to load.com.google.android.gms.permission.AD_ID— access to the advertising identifier, used by AdMob, by the advertising partners and by Google Analytics for Firebase as described above.
These are the permissions the game declares itself. The Google and advertising-partner components built into it add a few more that Android grants at installation without asking you, such as Google Play's billing permission and Android's advertising-services permissions; but the game requests no storage, camera, contacts, microphone, location, notification or account permissions on any Android version, and it never shows a permission prompt. To tell you when a newer version is available, the game asks the Google Play Store app on your device (Google Play In-App Updates); that check is made by Google Play and carries no game data.
Children
This is a general-audience game. It is not directed at children under 13 (under 16 in the EEA, or the equivalent minimum age in your country), it is not listed in a children's category, and it is not designed for or marketed to children. The developer does not knowingly collect any personal information from children. If you believe a child has provided personal information through the ad, analytics or crash-reporting services in this game, contact the address below and contact Google, or the advertising partner concerned, whose services would hold it.
Data retention
The developer runs no server and keeps no user data of its own. The usage statistics and crash reports are held by Google on the developer's behalf: Analytics data linked to an installation's identifiers for no longer than 14 months (aggregated reports without identifiers may be kept longer), and crash reports for 90 days. Data held on your device stays there until you clear the game's data or uninstall it. Data collected by Google through AdMob and Google Play is retained according to Google's own retention schedules, described in the Google Privacy Policy, and data collected by an advertising partner according to that partner's privacy policy, linked above.
Security
Everything the game stores sits in its private app storage, which other apps cannot read. Data sent to Google and to the advertising partners travels encrypted (TLS). The developer holds no database of users that could be breached.
Legal bases and your rights
Where the GDPR (EU/UK) applies, the legal basis for personalised advertising is your consent, collected through the form described above and withdrawable at any time. Non-personalised advertising, fraud prevention and the security of the ad services rely on legitimate interests. Processing your purchase is necessary to perform the contract you enter when you buy ad removal. The usage statistics and crash reports rely on the developer's legitimate interest in keeping the game working and understanding, in aggregate, how it is used; storing Analytics identifiers on your device and any advertising use of the data follow your choices in the consent form.
Under the GDPR, and under Turkey's KVKK (Law No. 6698) on equivalent terms, you have the right to ask whether your personal data is processed, to access it, to have it corrected or erased, to restrict or object to its processing, to data portability, and to withdraw consent. You may also lodge a complaint with your national data protection authority — in Turkey, the Kişisel Verileri Koruma Kurumu (KVKK).
The usage statistics and crash reports are pseudonymous: they carry random identifiers, never your name or email address, so the developer cannot tell which records are yours. Where the consent form is shown, you can withdraw consent at any time in Settings → Privacy options, and you can object to this processing, or ask about it, by writing to the address below. Resetting your advertising ID in Android's settings breaks the link to the old one. Uninstalling the game or clearing its data ends the link to the old identifiers, and data already sent then expires on the schedule above. Requests concerning advertising data must be directed to Google, or to the advertising partner concerned, as the party that holds it, using the tools in the Google Privacy Policy or in that partner's policy. For anything else, or for help finding the right route, write to the address below.
Changes to this policy
If the game's data practices change — for example if a new third-party service is added — this page will be updated and the "last updated" date at the top will change. Material changes will also be reflected in the game's Google Play listing. Continuing to play after an update means you accept the revised policy.
This is the first version of this policy, published with the first version of the game.
Contact
For any question about this policy or about privacy in this game, write to:
This is the same address listed on the game's Google Play page. Bug reports, privacy questions and data requests all reach us here.