BumuStudios·Türkçe sürüm·ImageToPdf policy·PdfPages policy

Privacy Policy — 2048 Zen

Android game, package com.bumustudios.zen2048

Effective date: 9 October 2026. Last updated: 9 October 2026.

No account, and your games stay with you. There is no sign-in and no server belonging to this game. The game does not read your files, your photos or your contacts, and it never shows a permission prompt. Every board, score and statistic is computed and kept on your phone, offline.

What does leave your phone is described in full below: Google's advertising service and the ad networks it works with, Google Play's payment service, 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 ad left is the optional video you can choose to watch for more undos.

Who this policy is from

This policy covers the Android game 2048 Zen (listed on Google Play as 2048 Zen – Calm Number Puzzle), distributed through Google Play under the package name com.bumustudios.zen2048. It is written by the game's independent developer, BumuStudios. Questions can be sent to the address in Contact.

What the game is

2048 Zen is the classic sliding-tile number puzzle: you swipe, every tile slides as far as it can, two equal tiles merge into their sum, and a new tile appears after every move. There are four board sizes — 3×3, 4×4, 5×5 and 6×6 — each with its own goal tile and its own saved game, plus an undo, statistics, and light and dark themes. 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:

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 the game itself sends none of it anywhere:

Android backup. The game lets your games in progress, statistics and settings be included in Android's own backup and device-to-device transfer, so that your saved games, best scores and statistics can follow you to a new phone. That backup is made by Android in your Google account if you have backup switched on; it is handled by Android and Google, not by the developer, who has no access to it, and you can switch it off in Android's settings. The game's backup rules exclude its shared-preferences and database storage, which is where Google's consent component keeps your consent choices, so you are asked for consent again on a new device. The purchase flag and the counter of full-screen ad opportunities are excluded from that backup as well and stay on this device; the purchase itself is checked again with Google Play every time the game starts.

Google's advertising and consent components also keep their own settings on the device, under Google's 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 on the device, these identifiers included. You can also reset your statistics at any time from the Statistics screen.

Advertising — Google AdMob and its mediation partners

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:

DataUsed 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

Mediation partners

The game also contains the software of six other advertising networks, which AdMob can use to fill an ad request ("mediation"). When AdMob routes a request to one of them, that network serves the ad and receives the same categories of data listed above — advertising ID, approximate location derived from your IP address, device information and ad interaction events — and processes it under its own privacy policy:

Which network serves which request is decided by AdMob, not by the game. In the EEA, the UK and Switzerland, your choices in the consent form described below reach these networks through the industry-standard consent signal (IAB TCF) that Google's form stores on your device.

The game does not request GPS or precise location permission, and it does not send your games, your scores or your play history to AdMob or to any of these networks. The developer receives no personal data from them — 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. No ad is requested before the consent step at launch has finished. The ad formats used are exactly these:

How Google handles this data is governed by Google's own policies, not by this one:

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:

DataUsed 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
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, 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 the game was used and for how long, not what you do in it, and a crash report shows where in the code the crash happened, not your games. 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. In the EEA and the UK, Analytics stores no identifiers on your device until you have answered the form, and 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, in Settings, that permanently removes the interrupting ads. There is no subscription and nothing recurring. The optional undo video remains available after the purchase — it only ever plays when you ask it to.

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, and it is checked again with your Google Play account every time the game starts, so it is restored 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

When the game starts, and before any ad is requested, it shows a consent form built with Google's User Messaging Platform where one is required, and you choose what you allow. Your choice is stored on your device by Google's component and is respected on later launches.

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 the mediation partners and to Google Analytics for Firebase, as described above.

In US states with their own privacy laws

Where Google's consent tooling applies to your state, the same Settings → Privacy options entry lets you review your choices and opt out of the use of your information for targeted advertising.

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 ad left is the optional undo video, which plays only when you choose to watch it; the game loads one in advance so that it is ready.

Permissions the game requests

These are the permissions the game declares itself, and none of them shows a prompt. The components built into it add a few more that Android grants at installation without asking you: Google Play's billing and install-referrer permissions, Android's advertising-services permissions (advertising ID, attribution and topics), wake-lock and foreground-service permissions used for background work by Google's components, and, from the AppLovin and Liftoff ad SDKs, Wi-Fi state, vibration, Google Play licence check and a device-attestation permission. The game requests no storage, camera, contacts, microphone, location, notification or account permission on any Android version.

Children

This is a general-audience game. It is not directed at children under 13 (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, 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; a copy in your Android backup is kept and deleted according to Android's and Google's backup settings. Data collected by Google through AdMob and Google Play, and by the mediation partners, is retained according to their own retention schedules, described in their privacy policies linked above.

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. 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 mediation partner concerned, as the party that holds it, using the tools in their privacy policies linked above. 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 game's first release.

Contact

For any question about this policy or about privacy in this game, write to:

bumustudios@gmail.com

This is the same address listed on the game's Google Play page. Bug reports, privacy questions and data requests all reach us here.