This policy describes how JMK Mobile Apps (“we”, “us”) handles information in the Bike Fury Android app. It is written so you and Google Play reviewers can see what is collected, why, and who it is shared with.
This app uses advertising (Google AdMob) and this app uses analytics (our own first-party usage analytics). Both are described below. We do not use Firebase Analytics, Google Analytics, or other third-party analytics SDKs.
1. Who this applies to
Bike Fury is a free Android motorcycle combat racing game. It does not create user accounts and does not ask you to sign in. If you do not agree with this policy, do not use the app.
The app is intended for a general audience. It is not directed at children under 13 (or the equivalent age of consent where you live).
2. Information stored only on your device
The following stays on your phone or tablet. We do not receive it:
- Career progress, bikes, upgrades and race records
- Sound, graphics, control and vibration settings
You can delete this local data by starting a new career in Settings, by clearing the app’s storage in Android settings, or by uninstalling the app.
Android backup may copy some of that local data if backup is enabled on your device, under Google’s own terms. The random installation identifier used for our analytics, and queued analytics that have not been sent yet, are ordinary app files. Clearing app data or uninstalling removes them from the device.
3. Advertising (Google AdMob)
This app uses ads so Bike Fury can stay free. Ads are provided by Google AdMob. The app currently shows:
- Interstitial video ads at a break, when you leave the race results screen
- Rewarded video ads, if you choose to watch one to double that race’s purse
The app does not show banner ads. Ads are not shown during a race. Google and its advertising partners may collect and process:
- Advertising ID (Android’s resettable advertising identifier)
- IP address and approximate location derived from it
- Device and app information (model, OS version, app version, language)
- Ad impressions, clicks, and whether a rewarded video was completed
Google uses this to show ads, measure whether they were shown, reduce fraud, and — where allowed — personalise ads. That ad measurement is done by Google, not by our own analytics in section 4. We do not sell your information. Google’s handling of this data is described in the Google Privacy Policy and AdMob & privacy.
In the European Economic Area, the UK, and other regions where Google requires it, the app asks for your consent through Google’s User Messaging Platform before personalised ads are requested. You can also reset or opt out of the Advertising ID in Android settings (often under Privacy or Google > Ads).
4. Analytics (our own usage analytics)
This app uses analytics. We run our own first-party analytics on servers we host at bikefury.jmkmobileapps.com. We do not use Firebase Analytics, Google Analytics, Crashlytics, or other third-party analytics SDKs.
Analytics is used only to understand which routes people race and how much time is spent riding, so we can improve the app. When you race, the app may upload:
- Which route was raced
- How long that race session lasted (active time on the race, not the countdown, pause menu, ads or results screen)
- A random installation identifier and a random session identifier
- Session start and last-update times
The installation identifier is a random value created on your device. It lets us tell one install from another. It is not your name, Google account, Advertising ID, or hardware serial. It resets if you clear the app’s data or uninstall.
Pending session records stay on the device until they are sent over HTTPS, then they are removed from the device. Requests include a short-lived technical signature so only this app can upload. Like other HTTPS requests, our server may also see IP address, date and time, and a generic app user-agent in ordinary server logs, for security and to keep the service running.
We do not include your name, email, Advertising ID, precise location, device model, or race replay in our own analytics. We do not count ads in this analytics, and we do not use these records to personalise ads or to sell data.
5. Permissions
- Internet and network state — to load ads and send our own analytics events
- Advertising ID — added by the AdMob SDK to serve and measure ads. Our own analytics does not use Advertising ID
- Vibration — if you leave vibration turned on, for hits and crashes. This stays on the device
The app does not request location, contacts, microphone, camera, SMS, or storage access.
6. What we do not collect ourselves
- We do not ask for your name, email, phone number, or payment details in the app
- We do not operate an account system
- We do not use the app to collect precise GPS location
- We do not sell personal information
- We do not send Advertising ID to our own analytics
7. Sharing
We share information only as needed to run the app:
- Google AdMob and advertising partners — to show and measure ads, as described in section 3. Our own analytics in section 4 is separate from AdMob
- Our hosting provider (Hostinger) — to serve this website and our own analytics. Server logs may include IP address as described in section 4
- If required by law — if we receive a valid legal request
8. Data retention
- On-device career data remains until you clear it or uninstall
- Our own analytics (route and time-spent records) are retained only as long as needed to understand usage, then aggregated or deleted
- Advertising data held by Google is retained according to Google’s policies
9. Your choices and rights
- Refuse or limit personalised ads through the in-app consent form, and through Android Advertising ID settings
- Delete local data as described in section 2
- Uninstall the app at any time. That stops new analytics events from this device
If you are in a region with privacy rights (for example the EEA, UK, or similar), you may have the right to ask what data we hold, to correct it, or to ask us to delete it. For data held only on your device, use the controls above. For advertising data held by Google, use Google’s tools and policies. For our own analytics, contact us using the developer email on the Bike Fury Google Play listing; because records use a random installation identifier rather than an account, we may not be able to link a request to a specific person.
10. International processing
Google and our hosting provider may process data on servers outside your country. Where consent or another legal basis is required for that, it is obtained through the in-app consent flow or is necessary to provide the features you asked for (ads, and keeping the app running, including our own usage analytics).
11. Changes
If we change how the app collects or shares data, we will update this page and the “Last updated” date. The current version is always at https://bikefury.jmkmobileapps.com/privacy/.
12. Contact
Developer: JMK Mobile Apps
App: Bike Fury
Website: https://bikefury.jmkmobileapps.com/
Contact: the support email shown on the Bike Fury listing on Google Play.