Privacy Policy
Rocket Blast — Temir Game Studio
Last updated: 8 October 2026
Android package: com.temirgamestudio.rocket
This Privacy Policy explains how Temir Game Studio handles information when you use Rocket Blast. Contact us at info@temirgamestudio.com. Website: Temir Game Studio.
Information We Collect
- Player account information: your required nickname, an automatically assigned account identifier, a player identifier, and account creation information. Your nickname must be unique across the game. Please avoid including your real name or other personal information in it.
- Leaderboard information: your nickname, highest altitude, total coins earned, total flights, the flight count at which you reached your altitude record, and record update information. A country code may be obtained from the country information supplied by our network infrastructure or, as a fallback, your device's regional settings. This does not use GPS or precise location access.
- Local game information: progress, virtual currency balances, items, upgrades, Market activity, Daily Login rewards, and device preferences are stored on your device. This does not mean that every local save field is uploaded to our servers.
- Gameplay diagnostics in diagnostic-enabled versions: versions distributed with gameplay diagnostics enabled also send installation and gameplay identifiers; session and flight times and durations; flight results, fuel use, rocket configuration, obstacles, controls, continues, collected coins and experience; and virtual currency earnings, spending, balances, and related gameplay events. They also send app/build and game configuration versions, platform, device model, operating system version, screen dimensions, graphics quality settings, target frame rate, measured frame rates, and frame times. Detailed gameplay diagnostics are disabled in the current standard Android release configuration.
- Service error information: our backend functions record service failures, such as failed database requests, to help diagnose operational problems. The current app does not include a dedicated remote crash-reporting integration.
Online requests transmit an IP address to service infrastructure. Providers may process network/request information for service operation, security, and abuse prevention. We do not store raw IP addresses in the leaderboard's application records; this does not mean that infrastructure logs do not process IP addresses.
How We Use Information
We use information to operate the game and its online features; manage player accounts and unique nicknames; maintain and display leaderboards; support progress, virtual currency, Market, and Daily Login features; and protect account ownership and prevent unauthorized activity. Where gameplay diagnostics are enabled, we use gameplay and performance information to understand play patterns, balance the game, and investigate technical issues.
Authentication and Player Accounts
Rocket Blast uses Supabase anonymous authentication to create a player account automatically. You do not need to register with an email address or password. Your account identifier is used to associate online player data with your account. Your nickname is a display name and is not a login credential.
“Anonymous authentication” does not mean that your gameplay records are fully anonymized: records can be associated with your player account. The current game does not use an advertising identifier as your Supabase player identity. Gameplay diagnostics use the existing player account rather than creating a separate authentication account.
Gameplay Analytics
Leaderboard records contain gameplay statistics. Diagnostic-enabled versions additionally collect the gameplay and technical information described above for analysis and balancing. The current standard Android release configuration does not upload those detailed diagnostic sessions, runs, or economy events. We do not use our own gameplay diagnostic records to create advertising profiles. Disabling gameplay diagnostics does not disable the advertising SDK's own measurement or diagnostic processing.
Third-Party Services
We use Supabase for anonymous authentication, backend hosting, database storage, leaderboards, remote Market and Daily Login configuration, account deletion, and gameplay ingestion where enabled. Supabase processes information needed to provide these services. Its privacy information is available at Supabase Privacy Policy.
Google Mobile Ads (AdMob) and Google UMP have been integrated into the Android app. There is no active app integration with Google Play Billing, Google Play Games, or Play Integrity. Virtual currency transactions inside the game should not be confused with real-money payments.
Data Sharing
Our backend service provider processes information to provide the game services described here. Leaderboards make your nickname, country indicator where available, rank, highest altitude, flight count at the altitude record, and total coins earned visible to other players. The leaderboard response does not display your authentication or internal player identifiers.
We may disclose information where required by law or necessary to address a lawful request. When advertising operates, Google and applicable advertising partners may process the advertising data described below.
Advertising, Advertising Partners, and Consent Choices
The Android app includes Google Mobile Ads (AdMob) for rewarded ads and Google User Messaging Platform (UMP) for privacy messages and consent choices. Live advertising is disabled in the currently audited configuration; development versions use Google's official test ads. Test ads can still send network requests to Google services. If live advertising is enabled, personalized, non-personalized, or limited ads may be served according to regional requirements and your choices.
When the advertising service operates, Google may process IP addresses and the general location estimated from them; Android advertising ID, app set ID, and other device/account identifiers where applicable; interactions such as app launches, taps, and video views; and app/SDK performance and technical diagnostic information. Purposes include ad delivery and measurement, analytics, and fraud prevention. Use of some identifiers depends on device, region, and choices. We do not deliberately pass your Supabase account identifier, nickname, or local save file to the advertising service; the advertising SDK may use its own identifiers.
UMP displays privacy messages where required and processes relevant choice and request information to manage your preferences. UMP allowing ad requests does not mean that you consented to personalization for every use. When UMP requires it, you can reopen your choices through Ad Privacy in Settings. Changing an advertising preference does not delete your game account.
You can choose whether to watch a rewarded ad. However, ads may be preloaded when the advertising service is eligible; choosing not to watch an ad does not by itself stop all advertising data processing. Non-personalized ads may still involve network, measurement, security, and diagnostic processing. Android advertising ID controls let you reset or delete the ID; options vary by Android version. This does not delete other identifiers or all historical records.
Advertising technology partners involved in Google's ad delivery and measurement may process information according to applicable consent and service configuration. The relevant privacy message/partner list identifies applicable partners and their privacy links. Google's general partner list does not mean that the game uses every listed partner.
Google Privacy Policy, How Google uses information from partner apps, Google advertising technology partners. Providers apply their own retention practices; in-game account deletion does not directly manage those systems.
Data Retention
Player information may be retained for as long as needed to provide the service or until you request deletion. We do not specify a fixed number of days for general account or gameplay retention.
Account deletion removes the account-linked player records from the active game database as described below. A limited technical confirmation record containing a session token hash, expiry, and completion status remains to safely handle repeated deletion requests. An account identifier hash may also exist until completion; it is removed upon completion. Validity ends when the associated session token expires; physical cleanup occurs during a later deletion request or confirmation check, rather than by a guaranteed scheduled cleanup. This record does not contain your nickname or gameplay history.
The in-game deletion operation does not directly purge infrastructure logs or backup copies. Any applicable provider retention and legally required retention are separate from deletion of the active player account. Contact us for questions about these records.
Account and Data Deletion
You can request deletion through the delete option in the game's Settings section and confirm the request. An internet connection is required. If the server cannot confirm deletion, the game does not treat the request as successfully completed.
Once completed, the server deletes the current player's authentication account and associated player account, nickname registration, leaderboard record, and any linked gameplay sessions, runs, feedback, economy events, and server-side Market claim records. The app clears local account data and game progress, then returns to a fresh-player state with a new anonymous account and a new nickname setup. Device preferences such as language, audio, and controls are preserved. Deleting your account is irreversible.
Deletion without access to the app: Email deletion request
You can also contact info@temirgamestudio.com to request deletion or help identifying your account. Include the game name and your nickname if available. We may ask for information needed to verify ownership; never send passwords or authentication tokens. Because the game does not use an email-based login, an email address alone does not identify your player account.
Advertising provider data: deleting the game account does not automatically delete advertising ID, IP, interaction, measurement, consent, or diagnostic records held by Google/AdMob or advertising partners. Use the relevant provider's privacy channels and Google Privacy Help; you can also contact us for help. Resetting/deleting an advertising ID or changing consent is different from deleting all historical provider records.
Security
The configured online game endpoints use HTTPS/TLS to protect information during transmission. Account access and deletion requests are checked against the requesting player's authenticated session. No method of transmission or storage can guarantee absolute security.
Children and Teen Privacy
Rocket Blast is intended for players aged 13 and older, including teenagers. This does not mean teenagers can consent to personalized advertising in every country; applicable age and consent rules must be considered. Please avoid putting personal information in a public nickname. We do not claim that anonymous authentication technically prevents a younger person from using the game. If you are a parent or guardian concerned about information associated with a child's use of Rocket Blast, contact us so we can help identify the relevant account and address the request.
Changes to This Privacy Policy
We may update this policy when the game's data practices change. We will publish the updated policy and revise the date above. Where required, we will provide additional notice.
Policy URL: Privacy Policy.
Contact Us
Temir Game Studio
Game: Rocket Blast
Email: info@temirgamestudio.com
Website: Temir Game Studio
Data deletion: Email deletion request
