BumuStudios·Türkçe sürüm

Privacy Policy — Knight Fist

Android game, package com.bumustudios.knightfist

Effective date: 31 October 2026. Last updated: 4 November 2026.

Controller: Burak Gökgöz (BumuStudios), Türkiye — bumustudios@gmail.com

No account, and the game plays offline. There is no account and no server belonging to this game; the only sign-in is Google Play Games, which is Google's and optional. The game does not read your files, your photos or your contacts, and it asks for no storage, camera, microphone or location permission. Every stage, fight and story scene runs on your phone.

What does leave your phone is described in full below: Google's ads, Google Play Games, and the usage statistics and crash reports that the developer collects through Google Firebase. There are no purchases in the game.

Who this policy is from

This policy covers the Android game Knight Fist, distributed through Google Play under the package name com.bumustudios.knightfist. It is written by the game's independent developer. Questions can be sent to the address in Contact.

The controller of the personal data described in this policy — the party responsible for it under data protection law, including the GDPR and Türkiye's KVKK — is Burak Gökgöz, who publishes the game as BumuStudios, in Türkiye. Contact: bumustudios@gmail.com.

What the game is

Knight Fist is a medieval side-scrolling beat 'em up. You choose one of three heroes and fight through ten stages, from a village street to a castle's throne hall, against outlaws, soldiers and ten bosses, with a short story told between them. No account, no subscription, no energy system.

The game runs on your device

What the game stores locally

The game keeps one small save file in its own private storage. None of it is personal information:

This save file, and nothing else the game or its components store, is included in Android's backup and in device-to-device transfer, so your progress can follow you to a new phone. Google's advertising and consent components keep their own settings on the device, under Google's control, and the Google Firebase components described below keep random identifiers in the game's private storage (a Firebase installation ID, the Analytics app-instance ID and a Crashlytics installation ID); these travel with the usage statistics and crash reports but are never backed up. Uninstalling the game or clearing its data removes everything it has stored.

Advertising — Google AdMob and its mediation partners

The game is free and is supported by ads served by 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 GPSServing ads relevant to your country or region, and legal compliance
Device information — model, operating system version, language, screen and network characteristicsRendering ads correctly, ad measurement, fraud prevention
App interaction events — that an ad was requested, shown, clicked or closedAd measurement, billing advertisers, fraud prevention

The game does not request GPS or precise location, and it does not send your progress or your play to AdMob or to any of its mediation partners (below). The developer receives no personal data from AdMob, only aggregated 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.

Two ad formats are used, both only at a pause in play: an interstitial when you leave a stage's results screen (to the next stage, to play again or to the title), at most once every three minutes; and, after a defeat, an optional rewarded ad you can choose to watch to fight on where you fell. There is no banner and no ad ever appears during a fight.

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

Mediation partners

Since version 1.0.1 the game also contains the software of two other ad networks, which AdMob can call on through its mediation feature. When the game requests an ad, AdMob may pass that request to one of these partners, and the partner that serves the ad then receives the same categories of data listed in the table above (advertising ID, approximate location derived from your IP address, device information and ad interaction events) and processes it under its own privacy policy:

In the answers they publish for Google Play's data safety section, Unity Ads says its software may also collect purchase history, user IDs, app interactions (such as taps inside its ads), app usage times (only when Unity's optimisation features are turned on) and diagnostics, for advertising, analytics, fraud prevention and app functionality; Liftoff Monetize says it collects approximate location, for analytics, app functionality and advertising. The game's data safety section on Google Play includes these answers.

Which partner, if any, serves a given ad is decided by AdMob. Your choices in the consent form described under "Your advertising choices" are passed to these partners through the standard consent signal that Google's consent tool stores on the device.

Usage statistics and crash reports — Google Firebase

To see how hard the stages are for real players and to find and fix crashes, the developer has built two Google Firebase services into the game: 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. No user ID or user properties are set.

DataUsed for
App-instance ID — a random identifier that Analytics creates for this installationCounting 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 AdMobUsage 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 GPSStatistics by country and region
Device and game information — device model, operating system version, language, game versionStatistics by device, Android version, language and game version
Usage events collected automatically — first open, sessions, engagement time, updates and removal of the gameHow many people play, how often and for how long
Stage events sent by the game — a stage started, resumed, cleared or lost, with the stage number, the hero, the difficulty, and on a clear the time, rank, lives lost and score, on a defeat how far you got and the boss's remaining health; and that you chose to fight on after an adSeeing where players struggle, to tune the difficulty of each stage and boss
How the game was installed — the Google Play install referrerCounting where installations come from
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 IDFinding and fixing crashes, and counting how many installations a crash affects

Neither service receives your name, your email address or any account details. Both services start on the first launch, in every region, before any consent form has been answered; outside the EEA, the UK and Switzerland, Analytics runs by default. In the EEA, the UK and Switzerland, once you answer the consent form described below under "Your advertising choices", Analytics follows your answer, both for storing its identifier on your device and for using the data for advertising, which stays off there until you agree. You can change your answer at any time from Settings → Privacy options; the entry appears where it is required. Crash reports are sent whatever you answer, on the developer's legitimate interest in finding and fixing crashes. The game has no separate switch for either service: to object, write to the address below; uninstalling the game stops both. Analytics keeps data linked to an installation's identifiers for no longer than 14 months; Crashlytics keeps crash reports for 90 days. Google processes this data on the developer's behalf 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.

Achievements and leaderboards — Google Play Games

Knight Fist works with Google Play Games, a Google service. If Play Games is on your phone, the game signs you in to it automatically with the Play Games profile Google already holds for you; nothing in the game depends on it.

When you are signed in, the game sends Google Play Games the achievements you unlock and two scores: your best score on a stage and your longest chain of hits. Google keeps them with your Play Games profile and shows the leaderboards, with your Play Games name and picture, to other players according to your profile's visibility settings. Nothing else about your play is sent, and the developer receives no personal data from it. Your Play Games profile and its data are managed in the Google Play Games app and your Google Account, under the Google Privacy Policy.

Purchases

There are none. The game sells nothing and asks for no payment details.

Your advertising choices

If you are in the EEA, the UK or Switzerland

When the game starts, it asks Google's User Messaging Platform whether a consent choice is needed and, where it is, shows a consent form before ads are requested, where you choose what you allow. If Google's consent service cannot be reached at that moment (for example without a connection), the game still starts its ad component, so an ad can be requested before you have answered; the form then appears on a later launch. Your choice is stored on your device by Google's component and respected on later launches. You can change it at any time from Settings → Privacy options. Withdrawing consent does not stop the game; you keep playing, and ads may still be shown in a non-personalised form.

If you are in a US state with a privacy law

Where a US state privacy law applies (for example in California), the same Google consent tool can show a notice about the use of your information for targeted advertising and let you opt out of its sale or sharing. Where it applies, the Settings → Privacy options entry appears and opens your choices again. Your rights there are described under Privacy rights in US states below.

Everywhere else

The privacy options entry appears only where a consent choice is legally required. You can still reset or delete your advertising ID in Android's Settings → Privacy → Ads (the path varies by manufacturer and Android version).

Permissions the game requests

The Google components built into the game add a few more that Android grants at installation without asking you, such as the install-referrer and Android's advertising-services permissions; the game requests no storage, camera, contacts, microphone, location or account permission.

Children

Knight Fist is a fighting game for a general, teenage and adult audience. It is not directed at children under 13 (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 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, for the periods given above. Data on your device stays there until you clear the game's data or uninstall it. Data collected by Google through AdMob and Google Play Games is kept according to Google's own schedules, described in the Google Privacy Policy; data a mediation partner receives is kept according to that partner's policy, 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. The usage statistics and crash reports rely on the developer's legitimate interest in keeping the game working and balanced; in the EEA, the UK and Switzerland, Analytics' storage of its identifier on your device and any advertising use of the data rely on your consent (GDPR Art. 6(1)(a)) once you answer the consent form; until you answer, Analytics already runs from the first launch.

Under the GDPR 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 at any time, and you may lodge a complaint with the data protection authority of your country. Users in Türkiye have the rights described under Users in Türkiye (KVKK) below. 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. Uninstalling the game or clearing its data ends the link to the old identifiers. Requests concerning advertising or Play Games data must go to Google, using the tools in the Google Privacy Policy, or, for an ad a mediation partner served, to that partner; for anything else, write to the address below.

Transfers outside Türkiye and the EEA

The developer works from Türkiye and has no server. The data described in this policy goes from your device directly to the providers below, which process it outside Türkiye and outside the European Economic Area, notably in the United States. The developer reads the usage statistics and crash reports in the Firebase console from Türkiye.

These providers state in their policies that, for transfers from the EEA, the UK and Switzerland, they rely on safeguards such as the European Commission's Standard Contractual Clauses and, where they are certified, the EU–US Data Privacy Framework. The details are in their policies linked above.

Users in Türkiye (KVKK)

The controller is Burak Gökgöz (BumuStudios), Türkiye. Under Law No. 6698 on the Protection of Personal Data (KVKK) you may apply to the controller to learn whether your personal data is processed and to request information about it; to learn the purpose of the processing and whether the data is used for that purpose; to know the third parties in Türkiye or abroad to whom it is transferred; to have it corrected if it is incomplete or inaccurate, and erased or destroyed under the conditions of KVKK Article 7; to have those corrections and erasures notified to the third parties it was transferred to; to object to a result against you that arises solely from automated analysis of the data; and to claim compensation for damage caused by unlawful processing (KVKK Article 11). You may also withdraw your explicit consent at any time.

Apply first to the controller, by email to bumustudios@gmail.com. Your application is concluded within 30 days at the latest and, as a rule, free of charge (KVKK Article 13). If it is refused, if you find the answer insufficient or if no answer comes in time, you may complain to the Personal Data Protection Board (Kişisel Verileri Koruma Kurulu) within 30 days of learning the answer, and in any case within 60 days of your application (KVKK Article 14). The full information notice in Turkish (KVKK Aydınlatma Metni) is in the Turkish version of this page.

Privacy rights in US states

This section is for residents of California and of the other US states with a consumer privacy law, to the extent those laws apply to the developer.

Security

What the game keeps is stored in its private storage on your device, which Android isolates from other apps. The game has no account and no server; the only copies elsewhere are your save file in your own Android backup, if you use backup, and what the game sends to Google Play Games. Data sent to Google and to the ad partners travels encrypted (TLS). No method of storage or transmission is perfectly secure; keep your device locked and up to date.

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.

A second update on 4 November 2026 names the controller; describes more precisely when the usage statistics and crash reports run (from the first launch, in every region; in the EEA, the UK and Switzerland, Analytics follows your answer in the consent form once you give it); adds the transfers outside Türkiye and the EEA, the rights of users in Türkiye (KVKK) and in US states and a security section; and removes the sentence that treated continued use as acceptance of a revised policy. It also describes what happens when the consent service cannot be reached at launch.

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.