PRIVACY POLICY
BlackHat Tycoon (Android) · by Klipx Limited · last updated 30 October 2026
Short version. You play as a guest with a random Player ID. The game stores your run on Google Firebase servers so it can work. If you link the run, it also stores the email address of that sign-in. If you allow notifications, it stores a push token for your phone. If you buy ◆, it stores a record of each purchase (never your card or payment details: Google Play takes the payment) and whether you said you are 18 or over. Crash reports go to Google by default, without your Player ID, and you can switch them off. Usage stats go to Google Analytics only if you say yes. If you play the Sniffer, it stores the city you choose for your den (so other players within range see a rough distance to you, never your exact spot); it never reads your GPS location. There are no ads and no advertising ID, and nothing is sold. You can delete your account and run in the app at any time.
WHO IS RESPONSIBLE
Klipx Limited, London, United Kingdom, makes the game and is the data controller. Contact: help@klipx.app.
WHAT THE GAME STORES, AND WHY
| Data | What it is | Why |
|---|---|---|
| Player ID | A random ID Firebase Authentication creates when you tap JACK IN (a guest account). The app shows it in Profile & Settings. | To keep your run yours, and to find it when you ask for help or deletion. |
| Sign-in (only if you link) | Your Google account's email address, plus the name and picture Google shares with Firebase Authentication; or the email address you sent a sign-in link to. | So the same run loads on another phone. The game only ever shows the address masked. |
| Your run | Your handle, operator, progress (rig, parts, caches, cash, gems, records, Notoriety, daily and contract progress), your Hacker Rating and season score, the Sniffer's state, your in-game hack log, players you blocked and reports you filed or that name you. | The game runs on the server: every change is checked and saved there. |
| Install marker | A one-way hash of a random ID the app makes when it is installed (the same ID a push registration uses), stored with your run: at most 8, one per phone or reinstall you played it on. | A fair-play rule: a hack between two runs played on the same phone never counts for the Hacker Rating. |
| Public profile | Your handle, operator, rank title, rating and record are shown on the MOST WANTED and SEASON boards, and your handle in other players' scans and hack logs. | The leaderboards and the player-versus-player hacks. |
| Push registration (only if you allow notifications) | A Firebase Cloud Messaging token for your phone, a random install ID, the platform, the time it was last refreshed, and your phone's time offset from UTC rounded to 15 minutes. At most 5 phones per account. | To tell you when someone hacks your rig. The time offset is used only to stay quiet from 22:00 to 08:00 your time. |
| Notification toggles | Which kinds of notification you switched on or off. | So the server and your phones respect them. |
| App integrity | Firebase App Check asks Google Play Integrity whether requests come from the real app on a genuine device. Firebase receives a pass or fail verdict; the game gets no device identifiers from it. | To keep cheats and bots out of a competitive game. |
| Purchases (only if you buy ◆) | For each Google Play purchase: the pack, the ◆ it gave, what Google Play charged (the amount, its currency, the tax and the list price), Google Play's order number, the country Google Play reports, the dates, its state (waiting for payment, added, cancelled or refunded), whether it was a license test or a promo code, and a one-way hash of Google Play's purchase token (never the token). Also your spending summary (this month and in total, per currency, from what Google Play charged), the monthly limit if you set one, and a one-way hash of your Player ID that Google Play's records of your purchases carry. Never your card, bank or other payment details: Google Play processes the payment and keeps its own record of it. | To give you the ◆ you paid for exactly once, finish payments that were pending, take back the ◆ of a refunded or charged-back purchase, show you what you spent and hold you to the limit you set. |
| Age answer (only before a first purchase) | Whether you answered that you are 18 or over. Not your birthday, and not your exact age. | Real-money purchases are only for players 18 or over. |
| Crash reports (on unless you switch them off) | When the game crashes or hits an error, Firebase Crashlytics gets: the stack trace (the part of the game's code that failed), the kind of error, the app version, the device model, the Android version, the device's state at that moment (such as free memory and storage), and two random IDs made for this install (the Crashlytics installation UUID and the Firebase installation ID). While CRASH REPORTS is on, Crashlytics also sends a small session ping each time you open the game after a break, crash or no crash: the app and its version, the device maker and model, the Android version, the time, a random session ID and the Firebase installation ID. The game puts no Player ID, handle, email address, push token or purchases in a report, and it leaves out the text of its own errors wherever that could hold your data. A crash inside Android or another library keeps that error's own message, which the game cannot edit. | To find and fix what breaks, and to count how many players a crash reaches. Switch them off in Profile & Settings › SYSTEM › CRASH REPORTS: this stops the reports and the session pings, and deletes the reports still waiting on your phone. |
| Usage stats (only if you say yes) | The game asks once, after the tutorial. With your yes, Google Analytics gets: five game moments (tutorial finished, a new chapter and its number, first store open, a Patch Tuesday breach, Go Dark; the game adds no gem or money amounts to them); the app events it records by itself (such as first open, app updates, sessions and time in the app); a random app-instance ID made for this install; the device model, Android version, app version and language; and a rough area (country, region, city) Google works out from a masked IP address. Google's SDK can also record a Google Play purchase by itself (the pack, its price and currency): the game has no separate switch for that, so a yes includes it. The game puts no Player ID, handle, email address or push token in usage stats, and does not link them to your run. If you do not answer, they stay off. | To see which parts of the game get played and where players stop, so it can be improved. Change your answer in Profile & Settings › SYSTEM › USAGE STATS: switching off stops them and clears the app-instance ID and what is waiting on your phone. |
| Server logs | Technical logs of the game's server functions. They can contain your Player ID. The game never writes your email address or push token to them. | To keep the service running and secure. Logs are kept for up to 30 days. |
Kept on your phone, never sent to the game's servers: sound and haptics settings, your crash report and usage stats choices, tutorial progress markers, the schedule of the game's own reminders, the hour you usually first open the game each day (to time the Dead Drop reminder), and the email address you typed for a sign-in link until that link is used. If your phone's Android backup is on, Android may include these in its backup of the app and restore them on a new phone, your two choices included.
Collected for the Sniffer: a city you pick by hand for your den (you choose it on a map; the game does not read your location). Other players within range see a distance to your city rounded to the nearest 5 miles, never your city name, your exact spot or your identity.
Not collected: no advertising ID (the game removes that permission and tells Google Analytics not to collect the ID or the Android ID), no ads or ad personalization, no contacts, no GPS or other precise location (your den's city is the one you pick by hand, not where you are), and no payment details (Google Play processes every payment and sends the game only the purchase details listed above).
NOTIFICATIONS
Android asks you before the game can notify you, and you can turn each kind off in Profile & Settings › NOTIFICATIONS, or turn them all off in Android's settings. Reminders about your own run (a full exfil buffer, a finished decrypt bay or contract, the Backdoor, the Dead Drop) are scheduled on your phone and never leave it. The server only sends the hack alerts, at most 3 a day, and your phone keeps its own reminders within the same daily limit as best it can.
WHO PROCESSES IT
Google LLC runs the game's backend on Firebase: Authentication, Cloud Firestore, Cloud Functions, Cloud Messaging, App Check and Hosting, in the United States (us-central1). Google processes the data for Klipx Limited under the Firebase terms. Crash reports (Firebase Crashlytics) and usage stats (Google Analytics) are also processed by Google for Klipx Limited, as its processor under Google's data processing terms, and Google may handle them in any of its data centres, inside or outside the UK and the EEA. Where data leaves the UK or the EEA for a country without an adequacy decision, those terms protect it with a recognised safeguard: Google's Data Privacy Framework certification where that applies, otherwise standard contractual clauses. Klipx Limited does not share them with Google for advertising: the game sends no advertising ID and no ad signals. Purchases are made through Google Play, which processes your payment under its own terms and privacy policy and tells the game the purchase details above. Nothing is shared with anyone else, except where the law requires it.
LEGAL BASES
- Running the game you asked to play: your Player ID, your run, your public profile and linking (contract).
- Purchases: supplying the ◆ you bought, and handling pending payments, refunds and chargebacks (contract).
- The age answer, the spending summary and the monthly limit: keeping real-money purchases to adults and letting you control your spending (legitimate interests: a responsible store).
- Security, anti-cheat, App Check, abuse reports and server logs (legitimate interests: a fair, working game).
- Crash reports and session pings (legitimate interests: a game that works; the game puts no Player ID in them, and the switch in Profile & Settings lets you object at any time).
- Usage stats (your consent, given by answering YES; you can withdraw it at any time with the switch in Profile & Settings).
- Push notifications (your consent, given through Android's permission and the game's toggles; you can withdraw it at any time).
HOW LONG IT IS KEPT
- Crash reports: Google keeps crash traces and the identifiers with them for 90 days, then deletes them. It publishes no separate period for session pings.
- Usage stats: event data is kept for 2 months, the shortest setting Google Analytics offers and the one the game uses. After that only totals remain.
- The Firebase installation ID: Google keeps it until it is deleted, then removes it within 180 days. The game does not delete it today. A reinstall makes a new one.
- Your account and run stay for as long as the account exists. Guest accounts are never deleted automatically, so a run is not lost if you take a break.
- Crash reports and usage stats are pseudonymous: they carry random install IDs, not your Player ID or your name, and we do not link them to your account. Your push token is built on the same Firebase installation ID, so the two could be matched while a push registration exists; the game never does that, and deleting your account deletes the registration. Deleting your account does not reach crash reports or usage stats: they end on the schedules above.
- When you delete your account, everything tied to it is deleted straight away, including your row in the final boards of finished seasons, your purchase records, your spending summary and limit, and your age answer. A few things stay for a short time. Server logs keep the Player ID for up to 30 days. Two markers holding only the Player ID and the time stop the deleted account from starting a new run; they are deleted after about a day (Firestore removes them within a day after that). Google Play keeps its own records of the purchases you made, under Google's privacy policy.
- Your handle can stay as plain text in the short hack logs of players you hacked or who hacked you (each keeps its last few lines), and in other players' own records of a scan or a hack that showed it, which are kept for up to 30 days. Nothing links the handle back to you.
- If you link a sign-in that another of your runs used and choose KEEP THIS RUN, that other run can no longer be signed into. It is deleted within 30 days.
- If you load another run on a phone that had a guest run (TWO RUNS › LOAD THAT RUN), the guest run stays on the server like any guest run nobody plays, because nothing ties it to you any more. To have it deleted, email us its Player ID: copy it in Profile & Settings before you load the other run.
DELETING YOUR ACCOUNT
In the app: Profile & Settings › DANGER ZONE › DELETE ACCOUNT. Without the app, see how to request deletion.
YOUR RIGHTS
You can ask to see, correct, export or delete your data, and you can object to how it is used. Email help@klipx.app with your handle and Player ID. We answer within one month. We do not link crash reports and usage stats to your Player ID, so we cannot look yours up from it: the two switches in Profile & Settings are how you stop them. You can also complain to your data protection authority (in the UK, the Information Commissioner's Office).
CHILDREN
BlackHat Tycoon is not meant for children under 16. If you think a child has an account, email us and we will delete it. The age question before a first purchase keeps only whether the answer is 18 or over, and real-money purchases stay off for anyone who answers under 18.
SECURITY
All traffic is encrypted (HTTPS). The server owns every change to your run. Security rules let each player read only their own private data, and no other player ever sees your Player ID, email or push token.
CHANGES
If this policy changes, this page shows the new version and its date. If a change matters, the game says so too.