METEORITE CRISIS · PLAYER RESOURCES
Meteorite Crisis: City Smash
Privacy policy
This policy applies specifically to Meteorite Crisis (石不可挡), Android package com.vicyang.meteorite. The developer responsible for the practices described here is Vic Yang, an individual based in Hebei, China. Contact: tigerywy@gmail.com
1. Your choices at a glance
- Settings → Data Sharing offers independent gameplay-analytics and crash-diagnostics switches. Both are off initially. You can decline both and still play, or change either choice later. Choices are saved locally.
- Advertising consent is separate from Firebase. Where required, Google UMP presents advertising privacy messages; Settings → Ad privacy opens the privacy options when UMP requires this entry point. Available options depend on your region and the configured message.
- Turning off reporting or changing advertising choices does not automatically erase data already sent. For requests, contact the developer using the deletion page below.
2. Local progress and settings
Progress, currencies, upgrades, reward status, purchase-fulfilment records and preferences are stored on your device. The game has no developer-operated sign-in or cloud-save account. Your operating system may back up app data according to your device settings. Clearing app storage or uninstalling may remove local progress permanently; it does not remove records held by Google or email support.
3. Optional Firebase analytics and crash diagnostics
When gameplay analytics is enabled, Google Analytics for Firebase processes app-instance identifiers, app and device information, usage/session information and gameplay events to help understand and improve the game. Events include city and level entry, run results and duration, distance, upgrades, rewards, shop/settings use, purchase-flow outcomes, and rewarded-ad loading, viewing and reward outcomes. SDK-generated events may also be included. City names in these events describe game locations, not your real-world location.
When crash diagnostics is enabled, Firebase Crashlytics processes crash/error details, stack traces, app/OS/device information, installation identifiers and limited diagnostic context to investigate faults. If both switches are enabled, event names and game-level context can accompany reports. The game does not attach a developer-assigned player identity, raw purchase receipts, purchase tokens or complete saves to its custom telemetry events. Installation identifiers are pseudonymous, not a guarantee of anonymity.
The Firebase integration denies advertising-storage, advertising-user-data and advertising-personalization consent. These settings apply to Firebase; they do not switch off AdMob or billing. Disabling Analytics stops new custom analytics delivery and resets local Analytics data and its app-instance identifier; it does not delete previously uploaded records. Crashlytics changes may require restarting the app, and reports stored on the device may be sent if reporting is enabled later.
4. AdMob rewarded videos and advertising privacy
The game uses Google AdMob only for rewarded videos that you choose to watch: one diamond from the shop, or doubling the coin reward on an eligible ordinary-run result screen. It does not integrate banner, interstitial or app-open ad placements. Reward availability and completion conditions are shown in the game.
UMP requests updated consent information and shows a required consent form when configured. AdMob is initialized and ads are requested only when UMP allows requests. Ads may then be preloaded before you press a watch button. Not watching a video therefore does not necessarily prevent advertising-service requests. Declining personalization may still allow other ads and associated processing.
Google and applicable advertising partners may process IP addresses and inferred approximate location, advertising/app/device identifiers and applicable device-account identifiers, ad interactions and diagnostics for delivery, measurement and fraud prevention. Consent status and choices are also processed. Android advertising-ID controls and Google’s privacy controls provide additional choices. Firebase switches do not control this processing. Some applicable US state laws may treat advertising disclosures as sale or sharing; where applicable, use the advertising privacy options or contact me about opting out.
5. Google Play purchases
Where available, Android purchases use Google Play Billing through Unity IAP. Product identifiers, signed receipts or purchase tokens, order status and fulfilment records are processed to verify and deliver items and prevent duplicate grants. The current game validates store receipts on the device and stores fulfilment state locally. Google Play handles payment details; I do not receive your full payment-card details. The billing SDK can contact the store to load products and recover pending orders independently of Firebase choices. Google and Unity service records follow their own policies.
6. Email support and this website
If you contact me, Gmail processes your email address, message, attachments and email metadata. I use them to answer questions, investigate issues and handle requests, not to enroll you in marketing. Only provide relevant information; never send passwords or verification codes. Email links open drafts and do not send messages automatically.
This policy is hosted on the developer’s static Cloudflare website. The site code has no analytics trackers, advertising SDKs, account registration or request-submission backend. Cloudflare processes connection information to deliver and protect pages. Website and support privacy details
7. Purposes, recipients and processing locations
Information is used to provide requested game features and purchases, deliver and measure ads, investigate faults, prevent fraud, answer support requests and meet legal obligations. Where applicable, legal grounds include necessary service delivery, proportionate legitimate interests in support and security, legal obligations, and consent for optional reporting or advertising where required. Reading this policy or accepting terms is not consent to optional collection.
Relevant recipients include Google (Firebase, AdMob/UMP, Google Play and Gmail), applicable advertising partners, Unity for its purchase services, and Cloudflare for this website. Necessary information may also be disclosed for a legal requirement or specific dispute. I operate from China; providers may process information in other countries. Applicable transfer safeguards or other lawful mechanisms are required where relevant. Contact me about arrangements applicable to your data.
- Google Privacy Policy · Firebase privacy information
- AdMob data disclosure · Google services on partner apps · Google privacy controls
- Unity player privacy policy
- Cloudflare privacy policy
8. Retention and security
Local data remains until cleared, overwritten or removed, subject to device backups. Analytics retention depends on the active property settings and Google’s controls; this game’s configured retention period has not yet been verified, so no specific period is claimed here. Crashlytics, advertising and store records follow the relevant provider’s retention and deletion rules. Their periods differ by data type, purpose and legal obligations; changing a game setting does not erase all provider records. Contact me to ask about a record’s applicable retention or deletion.
Support correspondence is ordinarily kept while a request is open and for up to 12 months after closure for follow-up. Unnecessary attachments and verification information are removed when no longer needed. Minimal records may be kept for a legal obligation or a specific unresolved dispute; provider backups follow their applicable rules.
Reasonable access controls and proportionate handling help protect information, but no system guarantees absolute security.
9. Your rights and deletion requests
You can contact me to request applicable access, correction, deletion, portability, restriction, objection, consent withdrawal or an appeal. You may complain to the competent data-protection authority. Proportionate verification may be needed. Requests can cover all identifiable personal data held by the developer or specified records. Local saves, Analytics, Crashlytics, advertising and store records have different identifiers and deletion limits; I will explain what can be located and removed and any required retention. I aim to respond within one month, follow any shorter applicable deadline, and explain any permitted extension.
10. Younger players and updates
A store age rating or target-audience classification is not asserted by this development-build notice. Follow the eligibility and age information provided with your version. A parent or guardian may contact me about a child’s information without sending unnecessary details. Advertising and consent configuration must match the audience before release.
Updates will carry a revised date. Material changes will be communicated where required, with new consent when necessary. This policy does not certify a completed Google Play Data safety declaration or production-release review.