Privacy Policy

Dirt Bike Racing: Motocross Game · Last updated 10 October 2026

This policy explains what happens to information when you play Dirt Bike Racing: Motocross Game (“the game”), published by Bogdan Veres (“we”).

The short version. The game has no account of its own and no sign-up. We never ask for your email address or phone number. The only name the game handles is the rider name you type, and it leaves your phone only for a multiplayer race on your Wi-Fi or when you share or race a friend's challenge. Your progress is stored on your own device and in your own iCloud or Google account. Signing in to Game Center or Google Play Games is optional and adds achievements, weekly leaderboards and, on Android, a cloud save. The game shows ads, sells in-app purchases, and counts anonymous gameplay events, and those things involve third parties described below.

1. Information the game handles

WhatWhyWho sees it
Game progress — races completed, times, coins, garage, purchases owned So you can keep playing where you left off, and not lose progress if you reinstall Stored on your device and in your own iCloud or Google account (see section 3). We have no access to it
Achievements you unlock, your daily challenge results, and on Android a copy of your saved game — only if you sign in to Google Play Games or Game Center So your trophies and progress follow you to a new device, and so you can compare daily results on the weekly leaderboards Google (Play Games) or Apple (Game Center). Other players can see your Play Games or Game Center name and your score on the leaderboards (see section 4)
Purchase records — which in-app product was bought, and when To deliver what you paid for and to restore it after a reinstall RevenueCat, and Apple or Google. Identified by a randomly generated ID, not by your name. Where analytics consent allows it, RevenueCat is also given the app instance ID that Google Analytics for Firebase uses, and reports each purchase — the product, its price and currency — to Google Analytics, so purchases are counted with the rest of the game’s analytics (see section 7)
Advertising identifier, IP address, ad interactions, coarse device and app information To show ads, limit repeats, measure whether an ad worked, and prevent fraud Google AdMob
Gameplay events — which race or mode was played, how it ended, stars, coins earned and spent, which store items were viewed or bought — with a randomly generated app instance ID and coarse device and app information To understand where the game is too hard or unclear, and which features are used Google Analytics for Firebase. Sent only where consent allows it (see section 7)
A randomly generated Firebase installation ID, the app version, platform and language, when the game asks for its current settings To fetch game settings that can change without an update — race rewards, how often ads and offers appear, multiplayer rules and whether challenges are on (the keys dbr_economy, dbr_ads, dbr_offers, dbr_mp and dbr_challenges). Nothing about you or your play is sent Google Firebase Remote Config
Your rider name, machine and position on track, during a local multiplayer race So the friends you are racing see you on their screens Only the phones in that race, on the same Wi-Fi network. It never leaves that network and is not sent to us
When you challenge a friend: your recorded run on that race (the bike's path and timing, not your inputs), your rider name, machine, race and finish time, under a seven-character code. When you race a friend's challenge: your rider name, machine and best time on it, under a random identifier made for that one challenge, which links to nothing else on your phone So the friends you share the code with can race your ghost, and so you can see how they did Google Cloud Firestore, in the developer's Firebase project. Anyone holding the code can read the challenge and its results. A challenge can no longer be opened 30 days after it was shared; the challenge and the friends' results stay stored and readable with the code until removed on request (see section 13). Not used for advertising or tracking
Purchase and usage information for a refund request So Apple can make an informed decision when you ask it for a refund Apple, through RevenueCat, only when a refund is requested (see section 6)

2. What we do not do

3. Your saved game

Your progress is written to your device. On iOS a copy is also written to your own iCloud account using Apple’s key-value storage, so that deleting and reinstalling the game does not lose your campaign, your coins, or a purchase you made. On Android the equivalent copy is made by the system’s own backup service, and if you are signed in to Google Play Games, the game also keeps a copy as a Play Games saved game, which brings your campaign back after a reinstall or on a new phone.

Those copies live in your Apple or Google account, under your control. We cannot read them, and they are removed when you remove them from your account, or when you delete the game and its backups and, on Android, its Play Games data (see section 4).

4. Google Play Games and Game Center

Signing in is optional, and the game plays the same without it. Signing in adds the platform’s own achievements, the weekly leaderboards and, on Android, the cloud save described in section 3.

When you are signed in:

These services are run by Google and Apple under their own privacy policies (Google, Apple Game Center). Google Play Games also collects your gamer name and profile picture, and analytics and diagnostic information about its own software, as it does for every game that uses it.

On Android you can delete your Play Games data, including this game’s saved game, from the Google Play Games app or your Google Account. On iOS you can sign out of Game Center in Settings → Game Center; Apple’s Game Center page linked above explains how to manage the data it holds.

5. Purchases

In-app purchases are processed by Apple’s App Store or Google Play. We use RevenueCat to confirm that a purchase completed and to restore purchases on a new installation.

RevenueCat identifies your purchases with a randomly generated identifier. It is not linked to your name or email address, and we do not connect it to any other information.

6. Refund requests

Refunds for purchases made through the App Store are decided by Apple. When you ask Apple for a refund, Apple may ask us how the purchase was used. RevenueCat answers on our behalf.

Consent to share consumption data with Apple. By using the game and making in-app purchases, you consent to our sharing information about your usage and consumption of purchased content with Apple when resolving refund requests. This information may include how you accessed and interacted with the purchased content — for example, whether purchased coins were spent and how long you have played. We share this information only as needed to help Apple make an informed refund decision and in accordance with Apple’s policies. It is identified by the same randomly generated ID described above, not by your name.

If you do not want this information shared, write to the address at the bottom of this page before requesting a refund, including the order ID from your App Store receipt, and we will turn it off for your purchases.

7. Analytics

The game uses Google Analytics for Firebase to count gameplay events, such as a race finishing or a store item being viewed. These events are tied to a randomly generated app instance ID, not to your name, and are used only to improve the game. They are not used to show you ads.

Analytics follows the same consent choice as advertising. Where consent is required and you refuse it, analytics collection is turned off and nothing is sent.

8. Advertising

The game shows ads supplied by Google AdMob. Two kinds appear: short full-screen ads between races, and optional ads you choose to watch in exchange for in-game coins. Watching the optional kind is always your decision.

To do this, Google receives your device’s advertising identifier, IP address, and information about how you interacted with an ad. Google’s use of this information is governed by its own privacy policy.

Personalised ads and your choice

If you are in the European Economic Area, the United Kingdom, or Switzerland, the game asks for your consent before any personalised advertising, using Google’s consent form. You may refuse, in which case you will still see ads, but they will not be personalised. You can change your answer at any time from the game’s Options screen.

On iOS, Apple additionally asks whether the game may track you across other companies’ apps and websites. If you decline, advertising remains non-personalised. You can change this in Settings → Privacy & Security → Tracking.

On Android you can reset or delete your advertising ID in Settings → Google → Ads.

Buying ads out

The game sells a one-off purchase that stops the full-screen ads. The optional coin-paying ads remain available, because they pay you and removing them would be a downgrade.

9. Children

The game is a general-audience racing game. It is not directed at children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child has provided us with personal information, contact us and we will delete it.

10. Your rights

Because the game has no account of its own, we hold almost nothing that identifies you. Even so:

To exercise any of these, write to the address at the bottom of this page. We answer within 30 days.

11. Data outside your country

Our service providers — Apple, Google, and RevenueCat — operate internationally and may process information in countries other than yours, including the United States, under the safeguards described in their own policies.

12. Changes

If this policy changes, the date at the top of the page changes with it. Material changes will be announced in the game before they take effect.

13. Contact

Questions, requests, or complaints: bogdan.veres@pedalcare.io