1. Introduction and Distribution Scope
This Privacy Policy ("Policy") applies to the JoyNB9 Blast Android application ("the App"), package name com.match.game.rpg.app.
Distribution scope (fixed): the App is not distributed or offered in Mainland China, the EU or the UK; other territories are those actually selected in the app-store console. We process your information in accordance with the data-protection laws applicable in your jurisdiction.
When collection starts: the App starts collecting as described in this Policy on first launch. There is no separate consent prompt. Section 6 lists how you can stop or limit collection.
By installing and using the App you confirm that you have read, understood and agreed to this Policy. If you do not agree, please stop using the App and uninstall it.
2. Information We Collect
2.1 Device and installation identifiers
Information Source Purpose
Advertising ID (GAID) System AdvertisingIdClient Device attribution, install-source measurement
ANDROID_ID System Settings.Secure Fallback device identifier when the advertising ID is unavailable
Firebase Installation ID (FID) Firebase Installations SDK Distinguish installs, analytics, anti-fraud
Firebase app instance ID Firebase Analytics SDK Session analytics
Facebook anonymous device ID Facebook SDK Ad attribution
When the advertising ID is unavailable (you have limited ad personalisation, or the read failed) we fall back to ANDROID_ID; the two are never used together. The Firebase identifiers above are sent to Google directly by the Firebase SDK (see 4.1).
2.2 Device and system information
The App itself reads: app package name, OS version, system build number and API level, and device manufacturer — used for compatibility and analytics.
In addition, Firebase Analytics collects device model, OS version, app version and language/region through its own mechanisms (see 4.1) — these are not fields the App reads itself.
2.3 In-app behaviour and game data
Game progress: best score, best floor, number of runs, total damage, daily-challenge results. This is stored locally on your device; when online features are available it may be sent to our servers with network requests.
Analytics events: page opened, external link opened (host only — never the full URL), boot completed or degraded, load failure and retry.
We never write complete URLs (which contain device identifiers in their query string) to logs or analytics.
2.4 Network and log data
To keep the service available and secure we process: IP address, request time, request path, HTTP status code, error type and stack trace. This is used for troubleshooting and anti-fraud and is not linked to your real-world identity.
2.5 Information we do not collect
The App does not request or collect:
Precise or coarse location (no location permission)
Contacts, call logs, SMS, calendar
Photos, videos, microphone (no camera or recording permission)
The list of other apps installed on your device
IMEI, IMSI, phone number or SIM details (no READ_PHONE_STATE)
Biometrics, health data or financial account information
The only permissions the App declares are:
Permission Purpose
INTERNET Network access (Firebase and our servers)
ACCESS_NETWORK_STATE Detect connectivity so we show an offline notice instead of firing doomed requests
com.google.android.gms.permission.AD_ID Advertising-ID attribution
Integrating the Firebase and Facebook SDKs additionally pulls in manifest entries such as ACCESS_ADSERVICES_* and BIND_GET_INSTALL_REFERRER_SERVICE for install-source attribution. The App does not request a wake lock (WAKE_LOCK); keeping the screen on uses a window flag that is released as soon as you leave the game screen.
2.6 Changes to the scope of collection
The App is updated continuously and the categories of information we process may change with it. Any such change stays within the purposes already described in this Policy; if an expansion is genuinely needed, we will update this Policy first and notify you prominently in-app.
2.7 On-device storage
The following stays on your device and does not leave it except as described in 2.6:
Storage Contents
Encrypted storage (Android Keystore) Third-party SDK initialisation config
App preferences Game progress (best score / floor / runs / total damage / daily result), language, sound, vibration
WebView localStorage Local mini-game save and language preference
Uninstalling the App removes all of the above.
2.8 When collection starts, and how to stop it
The App starts collecting on first launch and provides no separate consent prompt. You can stop or limit collection at any time:
Action Effect
Uninstall the App Stops all collection and erases every piece of on-device data
Reset or turn off the advertising ID (Settings → Privacy → Ads) Invalidates the identifier already collected, so later analytics can no longer be attributed to the same device
Settings → Apps → Storage → Clear data Erases progress, preferences and the local game save
Restrict background data / run offline The game remains fully playable offline; network reporting stops
3. How We Use Information
Provide and operate the game: save progress, load content, grant rewards.
Compatibility and quality: adapt to devices and OS versions, fix crashes and stutter.
Analytics: understand feature usage and retention to improve the game. Results are reported in aggregate.
Attribution and anti-fraud: identify install sources and prevent fake traffic and inflation.
Security and compliance: investigate anomalous requests and meet legal obligations.
We do not use your personal information to sell it to third parties, to make automated decisions that produce legal effects for you, or for any purpose unrelated to this Policy.
4. Third-Party SDKs and Sharing
4.0 Recipients at a glance
Recipient Receives
Our servers The device identifiers and device information described in section 2
Google (Firebase Analytics / Installations) See 4.1
Meta (Facebook SDK) See 4.3
4.1 Google Analytics for Firebase
Collected: app instance ID, installation identifier, device model, OS version, app version, language/region, sessions and the analytics events listed above; an approximate geographic area derived from IP; and, given the declared AD_ID permission, potentially the advertising ID.
In addition, the install-source attribution capability the App integrates (BIND_GET_INSTALL_REFERRER_SERVICE / Play Install Referrer) lets Google receive install-referrer information used to determine which channel you installed from.
Purpose: analytics, crash/performance monitoring, ad attribution.
Privacy: https://firebase.google.com/support/privacy · https://policies.google.com/privacy
4.2 Firebase Installations
Generates and manages the Firebase Installation ID (FID). Same privacy policy as above.
4.3 Meta (Facebook) SDK
Purpose: ad attribution, anonymous device-ID lookup, app-event reporting.
⚠️ Initialising the SDK turns on automatic app-event logging — install and launch events are sent to Meta by the SDK itself, with no further action from you; the advertising ID may also be used for attribution.
The SDK is only initialised once we hold a valid configuration; without one it does not start and none of the above reporting happens.
We may also receive ad-delivery-related data according to your Facebook settings.
Privacy: https://www.facebook.com/privacy/policy
4.4 Other sharing
We do not share your personal information except:
With your explicit consent;
When required by law or by a competent judicial or administrative authority following due process;
With service providers (cloud and network providers) only to the extent needed to serve us, under confidentiality obligations;
In a business transfer: in a merger, acquisition or asset sale we will require the successor to honour this Policy, or we will seek your consent again.
5. Storage and Retention
Location: where our service providers operate (which may be outside your country).
Retention:
On-device data: until you uninstall the App or clear its data;
Server-side network logs and analytics: generally 6 months, or longer where the law requires;
Attribution and install statistics: 13 months.
Cross-border transfers: where data must move outside your country, we apply the safeguards required by law and require recipients to handle your information to the standard set out in this Policy.
6. Your Rights
To the extent permitted by applicable law, you may:
Access and obtain a copy of your personal information;
Correct inaccurate information;
Delete your personal information or ask us to delete it;
Require us to stop processing your personal information;
Restrict or object to certain processing;
Receive your information in a portable format;
Lodge a complaint with a supervisory authority.
Things you can do immediately yourself:
Reset or turn off the advertising ID: Android Settings → Privacy → Ads (or Google → Ads);
Opt out of analytics: uninstall the App, or restrict background data in system settings;
Clear local data: in-app Settings → Clear local data, or Settings → Apps → Storage → Clear data.
To exercise these rights, contact us using the details below. We respond within 15 business days.
7. Children's Privacy
The App is not directed to children under 13 (or the lower age set by your jurisdiction), and we do not knowingly collect their personal information. If you are a parent or guardian and believe a child has provided us with personal information, please contact us and we will delete it promptly.
8. Security
We use measures including HTTPS in transit, Android Keystore encryption for sensitive configuration, least-privilege access, and log redaction (we do not log device identifiers or full URLs).
However, no internet transmission or electronic storage can be guaranteed to be perfectly secure. If a security incident occurs, we will notify you of the circumstances and our remediation as required by law.
9. Changes to This Policy
We may update this Policy. For material changes (for example, a new category of data, a broader purpose, or a new recipient) we will notify you prominently in-app and obtain fresh consent where the law requires it, before you continue using the App.
Prior versions and the "last updated" date are published alongside this Policy. Continued use means you accept the updated Policy.
10. Contact Us
Email: conwaybryant963@gmail.com
We have a designated data-protection contact who handles your requests and complaints.