Ground Truth Privacy Policy

Last updated: October 21, 2026 · Русская версия

This Privacy Policy explains how Ground Truth (the "game") handles information. Ground Truth is a mobile tower defense game, a cube of universes in which every universe is its own game made by a different AI model. It is published and developed by Kirill Shavrin. The game does not ask you to sign in and does not ask for your name, email address, phone number or social account.

Developer and contact

Developer: Kirill Shavrin
Email: desvingns@gmail.com
Telegram: @ShavrinK

Who the game is for

The game is intended for players aged 13 and over. It is not directed to children under 13, and we do not knowingly collect information from them. If you believe a child has used the game, contact us and we will delete the related data we can identify.

Information stored on your device

Your game progress, stars, Dust and in-game currencies, settings (such as language and sound), the state of your purchases, the universes you downloaded and, after your first purchase attempt, the encrypted sign-in token of an anonymous account (see "Purchase verification") are stored in the game's private storage on your device. If you export your save, the game writes a file to the place you choose through the system file picker; the game does not upload it. This data stays on your device until you clear the game's storage or uninstall the game.

Information sent over the network

Downloading universes (GitHub)

Some universes are downloaded on demand. When the game starts, and when you tap Download, it requests a small index file and the universe's resource files over HTTPS from a public GitHub release (github.com, which serves files through its own content network). GitHub receives what any web download sends, such as your IP address and a request header, and handles it under its own privacy statement. The game sends no identifier, account or personal data with these requests. Downloaded files are checked against a fingerprint built into the app before they are used.

Advertising (Google AdMob)

The game shows rewarded ads only, and only when you deliberately choose to watch one in exchange for a reward. There are no banner, interstitial or app-open ads. Each time the game starts, Google's consent library (User Messaging Platform) checks whether a consent form is required in your region; this shows nothing unless it is required. Ads are requested only after you tap to watch one. When an ad is requested, the Google Mobile Ads SDK collects your device's advertising ID, app set ID, IP address (from which Google may estimate your approximate location), and information about ad interactions and app performance, and uses them to choose, show, measure and protect against fraud in ads, under Google's own policies. Where required by law (for example in the European Economic Area and the United Kingdom), the game shows Google's consent form the first time you choose to watch an ad, before the ad is requested, and you can change your choice later under Settings > Privacy choices. On iOS, the game asks for your permission through Apple's App Tracking Transparency prompt before the advertising identifier is used for ads; if you decline, ads are not personalised with it. You can reset or delete your advertising ID in your device settings.

Purchases (Google Play and Apple App Store)

The game offers optional in-app purchases of Dust packs (a consumable in-game currency). Payments are processed entirely by Google Play or the Apple App Store. We never see or store your card, bank or payment details. The game receives from the store only the purchase result needed to deliver what you bought (product identifier, state and a signed purchase record), and sends it to our purchase verification service (next section) before the Dust is granted. Because Dust is consumed in the game, the store does not restore it after a reinstall; you can move your progress and Dust to another device with the save export in Settings. Refunds and payment history are handled in your Google Play or Apple account.

Purchase verification (our server)

To protect against fraudulent purchases, the game checks every Dust purchase on a server operated by us before the Dust is granted. The first time you tap a pack, the game creates an anonymous account with our backend provider Supabase: a random user identifier with no name, email address or phone number. Its sign-in token is kept encrypted on your device. The server runs in the European Union (Supabase region eu-west-1, Ireland).

When you buy, the game sends over an encrypted connection (TLS) the purchase token (Google Play) or the signed transaction (App Store) that the store gave your device, plus the product identifier. For a Google Play purchase our verification function sends the token to Google's Play Developer API to confirm that it is a real, paid purchase; for an App Store purchase it checks Apple's signature itself. Then it tells the game to grant the Dust. The function does not store the token or the signed transaction. It stores only: a one-way hash (SHA-256) of the token or transaction identifier, the product and pack identifiers, the store's order reference (the Google Play order ID or the Apple transaction ID), whether it was a store test purchase, the purchase and verification times, whether the purchase was later refunded and why, and your anonymous user identifier. It also keeps counters that limit repeated requests per anonymous user per day, and a bounded log of refused purchase proofs (a hash, the user identifier, the refusal reason and the time, at most 1,000 rows a day). Like any host, Supabase sees technical data such as your IP address in its own request logs, under its terms.

We use these records only to grant what you bought exactly once, to stop repeated or forged purchases, and to handle refunds, support, accounting and security. They are not linked to your name, email address or phone number, because the game does not collect them. We do not use them for advertising and we do not sell them.

Crash and error reports (Sentry)

To find and fix crashes, the game sends a report to our crash-reporting provider Sentry (Functional Software, Inc.) when it crashes or hits a program error. Data is stored in Sentry's European Union region (Germany). A report contains: the technical stack of the crash or error (which part of the game's code, the graphics driver or the system failed), the last lines of the game's technical log, the device model, operating system version, graphics chip and driver, the game version, which screen and which universe were open, and a random identifier that Sentry creates for this installation of the game. It does not contain your name, email address, phone number, advertising ID, purchase records, screenshots or your saves, and we have set Sentry not to store your IP address. Repeated errors are sent only once per session, and at most 25 errors per session. We use these reports only to fix problems in the game. Sentry keeps them for up to 90 days.

What the game does not do

The version covered by this policy has no analytics SDK and no account that you create or sign in to (the anonymous session used for purchase verification is described above). Apart from the purchase verification, it does not contact any server operated by us. (The game's code contains optional online features, such as cloud save, that are switched off in this version. If we turn them on, we will update this policy and the stores' privacy answers before that version is released.) The game does not send your data to any AI model and does not use generative AI while you play. The universes were made by AI models in advance and ship as fixed, checked files. Google Play and the App Store give us aggregated statistics such as install counts and crash rates under their own terms.

Sharing and international transfers

We do not sell your information. Information is processed by the service providers described above (Google LLC for advertising and consent, GitHub for downloads, Supabase for purchase verification, Sentry for crash and error reports, and Google Play or Apple for purchases) under their own terms and privacy policies. These providers may process data in countries other than your own.

Retention and deletion

The only data we hold is the purchase verification record described above, which is keyed by a random identifier and is not linked to your name, email or phone. We keep verified purchase records for as long as we need them for refunds, support, accounting and security; they are financial records, and we have not set a shorter fixed period. We keep the log of refused purchase proofs in the bounded form described above. Local game data is deleted when you clear the game's storage or uninstall the game; clearing it also removes the anonymous sign-in token, after which the game would create a new anonymous account if you buy again. Crash and error reports are kept by Sentry for up to 90 days and are then deleted. Data processed by Google (advertising and consent) and GitHub (downloads) is kept under their retention rules; to limit advertising data on your device, reset or opt out of the advertising ID in your device settings, and use the consent choices in the game.

To ask us about the data we hold, or to ask us to delete or anonymise a purchase record, write to desvingns@gmail.com and include the order number from your Google Play or Apple receipt, because that is how we find a record keyed by a random identifier. We will delete or anonymise it unless we must keep it as a financial record.

Your rights

Depending on where you live (for example in the European Economic Area, the United Kingdom or elsewhere), you may have the right to access, correct or delete your personal data, to object to or restrict its processing, and to withdraw consent. To exercise these rights, contact us at the email above. For data held by Google, GitHub, Supabase or Sentry, you can also use their own privacy controls.

Security

Game data on your device is stored in the game's private storage, and data is sent over encrypted connections. No method of storage or transmission is completely secure, so we cannot guarantee absolute security.

Changes to this Policy

We may update this Policy when the game's data practices or the services it uses change. The date at the top shows the latest revision.