MiraZen Studios

Last Bullet

Privacy Policy

Effective July 1, 2026 · Last updated August 24, 2026

Plain-language summary

Last Bullet is an Android game published by MiraZen Studios. The game stores your settings, progress, currencies, chip inventory, tutorials, and records on your device. It also uses:

  • Google AdMob to show interstitial and rewarded ads;
  • Google User Messaging Platform (UMP) to ask for and manage advertising consent where required;
  • Google Firebase Analytics to understand game use and performance;
  • Google Firebase Crashlytics to find and fix crashes;
  • Google Firebase Remote Config to deliver gameplay-balancing settings and version-support rules;
  • Google Play in-app reviews when you choose to submit a rating or review;
  • Google Play in-app updates to check for and install newer game versions;
  • Microsoft PlayFab for a device-based player account, optional leaderboard nickname, selected avatar, and score/time leaderboards; and
  • Android's share sheet when you choose to share a result.

The game does not provide email/password registration and does not currently include in-app purchases or payment processing. Some identifiers, analytics, advertising, diagnostics, leaderboard information, update-check metadata, and any rating or review you voluntarily submit leave your device. Advertising may be personalized, non-personalized, or limited depending on your region, consent choice, age-related settings, and the ad services available.

You can review advertising privacy choices from the game's settings when UMP makes that option available. You can also request access to or deletion of your supported data using the contact details below. Deleting the local save does not automatically delete information already held by PlayFab, Firebase, AdMob, or another provider.

This summary helps explain the policy but does not replace the full terms below.

1. Who we are

Last Bullet is published by MiraZen Studios.

In this policy, "MiraZen Studios", "we", "us", and "our" refer to the publisher of Last Bullet.

2. Scope

This policy applies to the Android version of Last Bullet, this MiraZen Studios website, and related support and privacy requests. This website hosts the built-in avatar image files used by the game. Those shared image files do not contain per-player information and are not user uploads. The website does not set advertising cookies or run analytics in its current version. The website hosting provider may process standard request and security logs. This policy does not control websites, applications, ad destinations, or sharing services operated by other organizations.

3. Information you provide

Leaderboard nickname and avatar

The game creates a default nickname for the leaderboard. You may replace it with a nickname of your choice and select an avatar from the game's built-in choices. The nickname, selected avatar URL, PlayFab player identifier, high score, and best survival time are sent to PlayFab to provide leaderboard features. The avatar URL points to a shared image hosted on this website; it is not a photo or image uploaded by the player. Do not put sensitive personal information in a nickname.

Google Play ratings and reviews

If the game presents Google Play's in-app review flow, you may choose to submit a rating from one to five stars and an optional written review. The rating and review are sent directly to Google Play. In production, a submitted review may be displayed publicly on the Play Store; during closed testing, it may instead be shared privately with the developer. The game does not receive the rating or review text and cannot determine whether you submitted a review. You can manage or delete a submitted review through your Google Play Store account or Google Account.

Support, access, and deletion requests

If you choose the in-game data-deletion option, the game opens your email application with the PlayFab ID and Firebase App Instance ID shown in the game's Privacy settings included in a draft. If you send that email, we receive the email address and any information you choose to include. We use that information to locate applicable records, verify the request, and respond. The game itself does not read your email account or contacts.

Sharing

If you choose to share a game result, the game creates a share card and text on your device and opens Android's share sheet. You choose the receiving application and recipient. The receiving service processes what you share under its own privacy policy. MiraZen Studios does not receive the share card merely because you open the share sheet.

4. Information collected automatically

Depending on your device, consent choices, region, and enabled services, the game and its service providers may process:

  • a locally generated random player identifier;
  • PlayFab account and player identifiers;
  • Firebase installation identifiers and the Firebase App Instance ID used by Firebase Analytics and related Firebase services;
  • advertising identifiers and other device identifiers used by Google advertising services;
  • IP address and IP-derived approximate location;
  • device model, device type, operating-system version, language, time zone, screen or hardware characteristics, and application version;
  • application identifiers, package name, and Firebase SDK version information used to deliver and maintain Remote Config;
  • update-check information processed by Google Play, including device metadata, the installed application version, and the game modules or asset packs installed on the device;
  • game launches, first shot/run start, run end, score, survival time, rewarded ad results, revives, reward doubling, chip upgrades, screen or focus time, and similar in-game interactions;
  • crash stack traces, crash state, logs, diagnostic information, and app performance information; and
  • consent status and whether privacy options must be shown.

The current Android version does not request permission for precise location, camera, microphone, contacts, calendar, or general file storage.

5. Local game data

The game stores data on your device so it can function. This includes settings, generated identity, selected avatar, tutorial completion, high score, best time, currencies, chip inventory, fragments, levels, loadout, slot unlocks, and related progression.

This local data normally remains until you delete the save, clear the application's storage, or uninstall the game. Android backup, device-transfer, or manufacturer features may affect local copies outside the game's control.

6. PlayFab account and leaderboard data

The game automatically signs in to PlayFab using a locally generated custom identifier and permits PlayFab to create a player account. This is not an email/password registration flow. PlayFab may assign additional service-side identifiers.

PlayFab receives the player identifier needed to sign in, the leaderboard nickname, selected avatar URL, high score, and best survival time. It may also process device and session information according to the PlayFab SDK and the title's dashboard configuration. Last Bullet uses PlayFab for device-based account and leaderboard functionality, not for payments.

Leaderboard nicknames, selected avatars, and scores are intended to be visible to other players through the in-game leaderboard.

7. Advertising

Last Bullet uses Google AdMob for rewarded and interstitial advertising. Rewarded ads are optional gameplay choices: one placement can revive the player and a separate placement can double an eligible game-over reward. Interstitial ads are subject to an application-start and between-ad cooldown.

Google advertising services may process and share IP-derived approximate location, advertising or device identifiers, ad and product interactions, diagnostic information, and app-performance information for advertising, measurement, fraud prevention, security, and compliance. The exact ad served depends on consent, region, device settings, eligibility, and available ad inventory.

Where applicable, ads may be:

  • Personalized: selected using information such as prior activity or inferred interests when legally permitted and consented to;
  • Non-personalized: selected mainly using contextual information, with limited additional processing for measurement, frequency control, and fraud prevention; or
  • Limited or technical-only: served with further restrictions where consent or another required signal is unavailable.

Choosing non-personalized or limited ads does not mean that no data is processed. Some data is still needed to deliver, measure, secure, and prevent fraud in advertising.

The game uses Google's User Messaging Platform to update consent information at startup in regions where this is required. Ads are requested only when UMP reports that ads may be requested. A privacy-options button is available in the game settings when UMP says it is required.

You may change an advertising choice through that privacy-options entry point when available. You can also use Android or Google advertising privacy controls. A changed choice applies prospectively and may not remove information already processed.

Firebase Analytics and Crashlytics start with collection disabled and are enabled only after the game completes its privacy startup process. The current version does not provide a separate in-game switch for Analytics or Crashlytics. We apply additional controls where required by applicable law.

Firebase Remote Config may initialize as part of the game's online service startup to retrieve gameplay-balancing and version-support configuration. It is not used to select advertising or send direct marketing messages.

9. Analytics, diagnostics, configuration, reviews, and updates

Firebase Analytics

Firebase Analytics helps us understand whether the game starts and runs, which gameplay and upgrade actions occur, how advertising features behave, and where important failures happen. It may process app-instance and installation identifiers, app interactions, device/application information, masked IP or IP-derived coarse location, and related measurement data.

Firebase Crashlytics

Firebase Crashlytics helps us diagnose crashes and serious failures. It may process crash stack traces, application state, logs supplied by the game, device and application metadata, installation identifiers, and performance or session information related to the failure.

Firebase Remote Config

Firebase Remote Config allows us to remotely adjust gameplay-balancing values, such as enemy spawn timing, reward and drop rates, combo limits, and chip unlock or upgrade costs, and to deliver version-support values such as the latest available version, the minimum supported version, and whether an optional update prompt is enabled. To fetch and select the applicable configuration, Firebase may process a Firebase installation identifier, country and language codes, time zone, operating-system and platform versions, application identifiers and package name, and Remote Config SDK version. Remote Config is not used to store player progress, currencies, chip inventory, leaderboard information, ratings, reviews, or advertising content.

Google Play in-app reviews

The in-app review feature lets you voluntarily submit a star rating and optional written review without leaving the game. Google Play processes the user-entered rating and review to publish a Play Store review or, for a closed test, to share it privately with the developer. Google states that this information is encrypted. You can delete a submitted review through your Google Play Store account or Google Account. The game is notified only that the Google-controlled review flow has finished; it does not receive the submitted rating, review text, or confirmation that a review was submitted.

Google Play in-app updates

The game uses Google Play's in-app update feature to check for newer compatible versions and to present flexible or immediate update flows where appropriate. Google Play may process device metadata, the installed application version, and the list of installed game modules or asset packs to determine whether an update is available and estimate its size. Google states that this information is encrypted, is not transferred to third parties for this request, and is deleted following a fixed retention period. The game receives the update status information needed to present and manage the update flow.

We do not use Firebase Analytics, Crashlytics, Remote Config, Google Play in-app reviews, or Google Play in-app updates to provide direct marketing messages by email, SMS, or phone.

10. Purposes for processing

We and our providers use information, as applicable, to:

  • run the game and save supported progress;
  • create the device-based PlayFab account;
  • provide leaderboard names, scores, ranks, and best times;
  • deliver rewarded and interstitial ads;
  • grant a rewarded benefit only after a confirmed ad reward;
  • remember and apply privacy choices;
  • understand game use and improve stability and balance;
  • deliver and apply gameplay-balancing and version-support configuration;
  • check update availability and present optional or required update flows;
  • allow you to voluntarily submit a rating or review to Google Play;
  • find, diagnose, and fix crashes and important persistence failures;
  • protect the game, advertising, and services from fraud and abuse;
  • provide support and respond to privacy requests;
  • comply with legal, regulatory, platform, and enforcement obligations; and
  • establish, exercise, or defend legal claims.

Depending on the information and context, we rely on one or more of:

  • Performance of a contract or steps requested by you: providing the game, local save, device-based account, leaderboard, update flow, review submission flow, sharing action, and requested support.
  • Consent: personalized advertising, access to or storage of information on a device where consent is required, and other processing where consent is the appropriate basis.
  • Legitimate interests: maintaining game security, preventing fraud, measuring basic service use, diagnosing crashes, improving stability, and protecting our legal rights, where those interests are not overridden by your rights.
  • Legal obligation: responding to valid legal requests and meeting applicable tax, accounting, consumer, privacy, platform, or regulatory duties.

The legal basis used by a third-party provider for its own processing may differ by service and jurisdiction. This policy does not claim that every provider has the same legal role in every country.

12. How information is disclosed

We disclose information only as described in this policy:

  • to service providers that operate advertising, consent, analytics, diagnostics, gameplay-configuration, update, cloud account, and leaderboard functions;
  • to Google Play when you voluntarily submit a rating or review or when the game requests update information;
  • to another user through the public in-game leaderboard;
  • to a receiving application or recipient when you deliberately use Android's share sheet;
  • to professional advisers, authorities, courts, or other parties when reasonably necessary to comply with law, protect rights, prevent harm, or handle a dispute; and
  • as part of a merger, financing, acquisition, reorganization, or sale of assets, subject to appropriate notice and protections where required.

We do not claim that advertising-related transfers can never be a "sale" or "sharing" under every US state law. Depending on applicable law and the advertising configuration, certain personalized-advertising processing may be treated as targeted advertising, sharing, or sale. See Section 19 for choices.

13. Service providers

Google AdMob and Google User Messaging Platform

Used for advertising, ad measurement, fraud prevention, security, and consent management. See:

Google Firebase

Firebase Analytics, Crashlytics, Remote Config, Firebase Installations, and related session components are used for analytics, diagnostics, crash reporting, installation identification, service operation, and delivery of gameplay-balancing and version-support configuration. See:

Microsoft PlayFab

Used for the device-based player account, identifier, nickname, selected avatar URL, and score/time leaderboards. See:

Google Play and Android

Google Play distributes the game, provides the in-app review and in-app update flows, and processes the information described in Section 9. Android provides operating-system features such as the share sheet. Google processes information under its own terms and privacy policy. See:

User-selected sharing services

If you share a result, the service you select receives the content you chose to send and applies its own privacy policy.

14. International transfers

MiraZen Studios and its providers may process information in countries other than your own. Privacy laws in those countries may differ. Where required, we and our providers rely on recognized safeguards, such as adequacy decisions, contractual protections, or another lawful transfer method. Contact us for information about safeguards applicable to a specific request.

We do not claim that all game data is stored in one country.

15. Retention

We keep information only for as long as reasonably needed for the purposes in this policy, including providing the game, maintaining leaderboards, diagnosing problems, preventing fraud, handling disputes, and meeting legal requirements.

  • Local save information normally remains until the save or app data is deleted or the game is uninstalled.
  • PlayFab leaderboard and account information remains according to the PlayFab title configuration and deletion actions taken by MiraZen Studios.
  • Firebase Analytics, Crashlytics, Remote Config, and Firebase Installations information remains according to the relevant Firebase project settings and provider rules.
  • AdMob and UMP information remains according to Google's product settings and retention rules.
  • Google Play ratings and reviews remain until you edit or delete them through your Google Play Store account or Google Account, subject to Google's rules.
  • Google Play update-check information is deleted by Google following a fixed retention period.
  • Support and privacy-request records may be kept for the time needed to complete the request, prove compliance, prevent abuse, and resolve disputes.

A verified deletion request will be processed across applicable systems, but deletion may not be immediate. Limited copies can remain temporarily in backups, security records, fraud-prevention records, or records that law requires us to keep.

16. Security

We use reasonable technical and organizational measures intended to protect information, including provider transport encryption and access controls. No storage, transmission, or service is completely secure. We cannot guarantee absolute security.

17. Children's privacy

Last Bullet is not directed to children under 13. The game is configured so users are not treated as being under the age of consent for Google's consent process.

If local law sets a higher minimum age for independent consent, a parent or guardian may need to provide consent. If we learn that information from a child was processed in a way that violates applicable law, contact us and we will take appropriate steps.

18. Your choices

Depending on your location and device, you may:

  • change available advertising consent choices through the game's Privacy Options control;
  • change Android or Google advertising privacy settings;
  • decline to watch optional rewarded ads;
  • choose whether to edit the generated leaderboard nickname and which built-in avatar to display;
  • choose whether to submit a Google Play rating or review, and manage or delete a submitted review through Google Play;
  • accept or postpone an optional update; an update may be required before continued use when the installed game version is no longer supported;
  • choose whether and where to share a result;
  • play core local features when network services are unavailable, subject to feature limits and any confirmed minimum-version requirement;
  • delete the local save from the game's supported reset flow;
  • clear app storage or uninstall the game; and
  • contact us to request access to, correction of, or deletion of supported provider data.

Withdrawing consent does not affect processing that was lawful before the withdrawal and does not necessarily stop processing based on another lawful basis.

19. Regional privacy rights

EEA, UK, and Switzerland

Subject to applicable law, you may have rights to:

  • access personal data;
  • correct inaccurate data;
  • delete data;
  • restrict or object to processing;
  • receive portable data;
  • withdraw consent; and
  • complain to your local data-protection authority.

United States

Depending on your state, you may have rights to know, access, correct, delete, or receive a portable copy of personal information, and to opt out of certain sale, sharing, targeted advertising, or profiling. You may also have the right not to receive discriminatory treatment for exercising a privacy right.

Use the available advertising privacy controls and contact us for other requests. If applicable law permits an authorized agent, we may ask for proof of authority and verification of the request. We may deny or limit a request where the law permits and will explain the result when required.

20. Access and deletion requests

Use the in-game privacy/data-deletion option, visit the data deletion request page, or contact support.mirazenstudios@gmail.com.

Last Bullet uses anonymous, device-based identifiers rather than an email/password account. To locate the supported identifiable cloud records covered by the request form, a deletion request must include:

  • the PlayFab ID for the device-based PlayFab account and leaderboard records; and
  • the Firebase App Instance ID for Google Analytics data.

These identifiers are shown in the game's Privacy settings. A leaderboard nickname may help with verification but is optional and is not reliable by itself because nicknames can be changed or duplicated. If either required identifier is unavailable, you may still contact us without reinstalling the game, but we may be unable to identify or delete the corresponding anonymous provider records. Do not send passwords, government identification, payment information, or unrelated sensitive information.

The request process is:

  1. You send the request with the required identifiers.
  2. We verify the PlayFab ID and Firebase App Instance ID and locate the applicable records.
  3. We submit supported deletion actions for identifiable PlayFab, Google Analytics, and support records.
  4. We respond within the period required by applicable law. Provider processing may continue after our initial submission.

Deleting the local save alone does not delete cloud and provider records. PlayFab account deletion and Google Analytics deletion processing may be asynchronous. Advertising data controlled by Google may not be identifiable to MiraZen Studios through the game identifiers; users can also manage advertising choices through the in-game Privacy Options entry point and Android or Google advertising privacy controls. Google Play ratings and reviews are controlled through your Google Play Store account or Google Account and should be edited or deleted there. Google Play update-check information is managed by Google under its retention rules and may not be identifiable to MiraZen Studios. Some information may be retained where required for security, fraud prevention, legal compliance, request records, or dispute handling.

Ads, privacy notices, and shared content may link to third-party applications or websites. We do not control their content or privacy practices. Review their policies before providing information.

22. Changes to this policy

We may update this policy when the game, SDKs, legal requirements, or business practices change. We will update the "Last updated" date and provide any additional notice required by law. Material changes apply prospectively unless law permits otherwise.

23. Contact

MiraZen Studios

Ahmed Alsawalha

Belgium

Email: support.mirazenstudios@gmail.com

Website: MiraZen Studios website