Drift Versus

Drift Versus — Privacy Policy & Credits

Effective date: 13 October 2026

This policy explains what happens to information when you play Drift Versus (“the game”), a mobile racing game published by Muhammad Hazki Hariowibowo, trading as MHz Games (“we”, “us”).

The short version

1. Information the game collects

Nothing that identifies you. The game has no accounts and never asks for your name, email address, contacts, location or anything similar.

Usage data

To understand how the game is played, it sends us a small number of anonymous usage events: the app was opened, how far through the game you have got, the tutorial was finished, skipped or left partway, a race was started, a race finished, a Endless Drift run was started or finished, in-game currency was earned or spent, a reward ad was watched or skipped, an interruption ad was shown (and whether on the way home or into the next stage), the store page was opened, and a purchase was made (which product, where it was started from, and whether it went through).

The race events describe the driving and nothing else: which course, which stage of the career it was and whether that stage was a King’s fight, which mode, win or loss, how long the run took, the drift score and how it was made up, how many times the car touched a wall, which stars the run earned, and the pips it paid. The tutorial event records how it ended, how far along its road you got, how long it took, and how many presses and drifts you made. The Endless Drift events describe a run the same way: whether it was the day’s road, how far the car got and for how long, how many rivals it overtook, how much damage it took and had repaired, how it ended, your best distance before it, and the stars it paid. The currency events record that in-game pips or car tokens moved — how many, why (a race, a King’s first fall, a solo medal, a rewarded ad, a purchase, or buying a car) and the balance afterwards. None of this is money; pips and tokens cannot be cashed out and exist only inside the game.

When the store page is opened, the game records that it was opened and what your counters read at that moment — how many tokens and pips you hold, how far off the next free car is, and which stage you are on. It is how we tell a store nobody opens from a store people open and leave, and it carries nothing about you that the rest of this list does not already carry.

Performance data

Once a race has been run, the game also sends how smoothly it ran: how many frames it drew and how long they took (the typical frame, the slowest, and how many were late), how much of that time the processor and the graphics chip were busy, which graphics settings were in use, and whether the device reported itself as running hot.

That measurement is only meaningful next to the hardware that produced it, so the same event carries what kind of device the game is running on: the device model name, the graphics chip name, the operating system version, how much memory and graphics memory it has, how many processor cores, and the size and refresh rate of the screen. This is a description of a phone model — the same for every copy of that phone — and not an identifier: it contains no serial number, no advertising ID and nothing that singles out your device among others of its kind.

We collect it for one reason. The game aims to run at 60 frames per second on mid-range hardware, and Android phones vary enormously; without knowing which models struggle, the only alternative is to make every phone run the lowest settings. This data is what lets better-looking graphics be turned on for the devices that can hold the frame rate.

Once each time you open the game, it also sends how far you have got: how many stages you have cleared, how many Kings and rematches you have beaten, how many stars you hold, whether you have finished the career, how many cars you own, how many races you have run, and your pip and token balances. This is the same progress the game already shows you on its own screens — it tells us where players get to and where they stop, which is how we know which parts of the game are too hard.

Each event also carries which country the game is being played in, as a two-letter code such as “US” or “DE”. It is the country that issued the phone’s SIM card, or, where there is none, the country chosen in the device’s own region setting. It is never finer than a country, it is not worked out from your IP address or GPS, and the game asks for no location permission to read it. It tells us which countries the game is reaching, and so which languages its store page should be written in.

Each event carries the app version, the operating system, a random installation ID that the game generates the first time it runs, the date that ID was created, and a second random ID that identifies the current run of the app. The installation ID is not derived from your device, your advertising identifier or anything about you, and we cannot connect it to you. Uninstalling the game deletes it, unless your device later restores the game’s data from your own backup (see below).

This data is received and stored for us by PostHog, a product-analytics service, on servers in the United States. Like any web service, PostHog sees the IP address the events arrive from; we do not use it to identify anyone. PostHog processes this data only on our behalf, under its own privacy policy: https://posthog.com/privacy.

If you are in the EEA, the UK or Switzerland, no usage data is sent. The game asks Google’s consent platform which region it is in, and in those regions the usage reporting stays off. It also stays off for anyone who has told the game they are under the age gate.

Data kept on your device

The game also writes files to your device’s private app storage, so that it can remember your progress between sessions:

What Why
Race progress, cars owned and in-game currency So you keep what you earned
Sound and display preferences So the game opens the way you left it
Your recorded consent choices So you are not asked the same question repeatedly
The random installation ID described above So the usage data from one install is counted once

These files are stored in the app’s private storage area and are readable only by the game. We never receive them and have no way to access them — the game does not upload them anywhere.

They may, however, be included in your device’s own cloud backup. If you have iCloud Backup switched on (iOS) or Android’s automatic backup (Android), your device may copy this app’s saved data into your personal cloud account, in the same way it does for other apps you have installed. That backup belongs to you and is handled by Apple or Google under their own policies, not by us; it is not somewhere we can read. You can turn it off in your device’s settings.

Uninstalling the game deletes these files from your device. A copy may remain in your own backup until that backup is replaced or you delete it.

2. Information collected by advertising

Drift Versus shows advertisements supplied by Google AdMob. To do this, the Google Mobile Ads SDK is included in the game, and it communicates directly with Google’s servers.

Google may receive and process information including your device’s advertising identifier, IP address, device type and operating system, general location derived from your IP address, and how you interacted with an ad. We do not receive this information. We see only aggregate, anonymous reports — for example, how many ads were shown in total. The usage data described in section 1 is never shared with Google, and the random installation ID is never sent to it.

How Google uses this data is governed by Google’s own policies:

Whether the ads you see are personalised depends on the choice you make in the consent prompt described in section 4, and on your device’s own settings.

3. Purchases

If you buy in-game currency or the ad-free upgrade, the purchase is handled entirely by Apple’s App Store or Google Play. Your payment details go to them, never to us — we never see or store your card number, billing address, or any other payment information. We receive only a confirmation that a purchase completed, which the game uses to grant what you bought.

Apple and Google’s handling of that transaction is covered by their own privacy policies.

4. Your choices

If you are in the EEA, the UK or Switzerland, the game shows a consent form the first time you play, provided by Google’s User Messaging Platform. Your answer determines whether the ads you see are personalised.

You can change your answer at any time from Settings → About & Privacy → Privacy Options inside the game. This option appears wherever a consent choice applies to you.

On any device, you can also limit ad tracking through your device’s own settings:

To remove ads entirely, you can buy the ad-free upgrade in the game’s store. Note that this removes interruptive ads; the optional “watch to double your reward” ads remain available, because they are a way to earn in-game currency rather than an interruption, and removing them would take something away from you rather than give something back.

To stop usage data being sent, uninstall the game. There is no separate switch for it inside the game; the data is anonymous, and in the regions where the law requires an explicit choice it is not collected at all.

To delete everything the game has stored, uninstall it. All local data goes with it, including the installation ID, so nothing sent after a reinstall can be connected to what came before.

5. Children

Drift Versus is not directed to children under 13, and we do not knowingly collect personal information from children under 13. Our declared target audience with both app stores reflects this.

If you believe a child has provided personal information through the game, please contact us at the address below and we will act on it.

6. Data retention

Usage data (section 1) is kept for as long as it is useful to us, and for at least twelve months — the minimum our analytics provider holds it for on the plan we use. We have not set a fixed expiry date on it: we remove it when we no longer need it, and all of it goes when we close the PostHog project. It is held only in aggregate-ready form — events under a random ID — and we never build profiles of individual players from it. Section 7 explains why that also means we cannot find and remove one player’s events on request. Data stored on your device stays there until you uninstall the game or clear its data. Data held by Google as an advertising partner is retained according to Google’s own policies, linked in section 2.

7. Your rights

Depending on where you live, you may have rights to access, correct, delete, or restrict the processing of your personal data, or to object to it.

The usage data we hold is not linked to you. It sits under a random installation ID that the game keeps in its own private storage and never displays, so there is nothing you could send us that would identify your events, and nothing we could use to find them. That is one fact seen from both sides: it is why the data cannot be traced back to you, and it is why we cannot pick your events out of it to delete them on request. Uninstalling the game discards the ID (unless your own device backup restores it), and nothing further is ever recorded against that install. Everything else — the advertising data — is held by Google, and those rights are exercised against Google as the party that holds it; Google’s privacy policy, linked in section 2, explains how. For anything relating to this game specifically, contact us and we will help.

8. Security

We hold no database of player identities that could be breached: the usage data we keep is anonymous events under random IDs, sent over an encrypted connection and stored by PostHog under its own security programme. Data on your device is protected by your device’s own app sandboxing and whatever passcode or biometric lock you have set.

9. Changes to this policy

If the game changes in a way that affects this policy — for example if crash reporting were ever added, or usage data were ever collected in more regions — we will update this page and change the effective date at the top. Material changes will also be surfaced in the game itself.

10. Contact

Questions about this policy or about privacy in Drift Versus:

hello@mhzgames.com

Credits

Drift Versus is built on some work by other people. Thank you to all of them.