Idle Datacenter Tycoon ("the Game", "we", "us") is an idle building game with optional online features (leaderboard, clans, events), developed by Jonathan Pietsch. This policy covers the Android app, the iPhone/iPad app and the browser game, and explains what data the Game handles and why.
Your game progress (money, buildings, upgrades, settings) is saved locally on your device using
standard browser/app storage (localStorage). This data never leaves your device unless
the cloud sync described below is used, and it is deleted automatically if you uninstall the app or
clear the app's storage.
The Game automatically attempts to back up your progress to a database hosted on Supabase and retrieve it using a randomly generated identifier stored on your device. This identifier is pseudonymous, not an account or a guarantee of anonymity. We do not ask for a name or email to play. The backup contains game progress and timestamps. If you lose the device identifier, for example when clearing storage, the Game cannot automatically recover that backup on another installation.
Data sent to the cloud is transmitted securely over HTTPS. It is used to provide save/sync and the global progress leaderboard, and is not sold, shared with advertisers, or used for tracking across other apps or websites.
After seven minutes of active play, the leaderboard displays a generated pseudonymous name, global rank, highest unlocked location, build percentage and stars. You can replace the pseudonym with a player name of your choice in the leaderboard; it is stored with your cloud save and shown to other players. Please do not use your real name. The leaderboard does not display your device identifier, full save or email. Other players can see these leaderboard fields.
The developer may send a private message to an individual player to ask for feedback. Such a message appears only on that player's device (messages icon in the Game); other players cannot see it or any reply. If you reply, your text is stored in the same Supabase database, linked to your device identifier, and read only by the developer. Replying is optional. Please do not include personal details such as your real name, address or phone number in a reply. Messages are kept until deleted on request (see "Deleting your data").
Clans (from October 1, 2026). Joining or founding a clan is optional. The Game shows a short notice before your first clan. Clan data is stored in the same Supabase database, linked to your device identifier: the clan you are in, your role, your player name (or generated pseudonym), the days you played (for the clan's daily Clan Bits) and your clan chat messages. Other members of your clan see your player name, role, whether you played today and your chat messages; all players can see clan names, descriptions, member counts and Clan Bits in the clan list and leaderboard. Your device identifier is never shown to other players. If you report a chat message, the developer receives the message text, its author's player name and the clan to review it. Chat messages and clan membership are kept while the clan exists or until deleted on request. You can leave a clan at any time; please do not share personal details in the chat.
Community votes. The Game occasionally asks which feature to build next. Your vote is stored once per device identifier; only the totals are shown to other players.
Network providers necessarily receive connection information, including your IP address. Supabase processes the backup to provide storage and retrieval. See Supabase's privacy policy.
The mobile app integrates Google AdMob (Google Mobile Ads SDK) and Google's User Messaging Platform. You can choose to watch an investor's rewarded ad for in-game currency. Skipping an ad does not prevent normal play. The browser game does not integrate AdMob; its optional ad demo does not show a real ad or award saved currency.
Google's advertising SDK processes IP addresses (which may indicate approximate location), app/ad interactions, diagnostic information, and device or account identifiers such as the Android advertising ID or, on iPhone and iPad, Apple's advertising identifier (IDFA) – the latter only if you allow tracking in Apple's App Tracking Transparency prompt – depending on configuration and privacy choices. These are used for advertising, measurement and fraud prevention. SDK data is encrypted in transit. See Google's privacy policy and how Google uses information from partner apps.
Before requesting ads, the app checks Google's consent system. Where required, it presents privacy choices. Where Google requires a privacy-options entry point, you can reopen it through Settings → Ad privacy choices. Choices can affect personalization and ad availability. An ad may be requested in the background before you choose to watch it, once the consent system permits requests. Declining personalization is not a promise of no data processing.
The Game does not request access to contacts, camera, microphone or precise GPS location. We do not send the cloud-save identifier or the contents of your save to AdMob in our integration.
Campaign measurement (Android app). To learn whether our Google Ads campaigns reach players who actually enjoy the Game, the Android app uses Google Analytics for Firebase. It records an app-instance identifier, basic device and app information, approximate location derived from the IP address, standard app events such as the first app open, and one in-game milestone: reaching the second location (together with the rounded minutes of play until then). We do not send your save, your player name or purchase details to Google Analytics. The same privacy choices you make in Google's consent system (see above) control this measurement: where consent is required, analytics and advertising storage stay disabled until you agree, and you can change your choice later under Settings → Ad privacy choices. Aggregated results may be shared with our linked Google Ads account to measure campaign performance. See how Google uses information from partner apps. The browser game does not use Google Analytics.
The apps can offer optional cosmetic worker skins, tap animations and permanent unlocks (such as an additional location or the Clan HQ villa): on Android through Google Play Billing, on iPhone and iPad through Apple's In-App Purchase. The store processes the payment and may process account, payment, device, tax and fraud-prevention information, Google under Google's privacy policy and Apple under Apple's privacy policy. We do not receive or store your full card or bank details, your Apple ID or your Google account.
To verify and prevent reuse of a purchase, the Game sends the product ID, the store's purchase proof (on Android the Google Play purchase token, on iPhone/iPad the transaction signed by Apple, which contains the transaction ID, product, purchase date, storefront country and environment), the selected cosmetic ID and the Game's pseudonymous device identifier to our verification service. We store a one-way hash of the purchase token or Apple transaction ID together with the product, cosmetic, device identifier, store order or transaction identifier and timestamp in Supabase. The cosmetic entitlement is also included in your local and cloud save. Permanent unlocks can be restored on a new device through the store account that bought them.
You can wipe your progress at any time from Settings → Delete save inside the Game. This resets local progress and attempts to replace the cloud backup with a fresh game state. It does not delete the cloud database record. Network failures can prevent the remote reset.
If you would like your cloud entry removed entirely rather than reset, contact us at the email below. We may need your game's device identifier to locate the record; a date alone may not identify it. Cloud backups remain until replaced or removed; no automatic expiry is implemented by the game client. Deleting your game save does not delete information independently held by Google. Use Google's privacy controls for that information, including advertising-ID controls in Android settings. On iPhone and iPad you can change tracking permission at any time under Settings → Privacy & Security → Tracking.
Verified-purchase ledger records may be retained to prevent duplicate redemption and to document transactions. Contact us if you want the game data linked to your device identifier removed. Google Play and App Store purchase records must be managed through your Google account or Apple ID and may be retained by Google or Apple independently.
The data processing described above can include personal data. If you are a parent or guardian and have a concern about a child's data, contact us below. Do not include unnecessary information about the child in your message.
If this policy changes, the "Last updated" date above will be revised. Where required, updated consent will be requested separately; continued play is not treated as consent to advertising.
Questions about this policy or a data deletion request can be sent to:
jonathan01.pietsch@gmail.com