Crystal Bastion TD Privacy Policy

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

This Privacy Policy explains how Crystal Bastion TD (the "game") handles information. Crystal Bastion TD is a mobile tower defense game published by Skyward Atelier and developed by Kirill Shavrin. The game has no sign-in with a name, email address, phone number or social account. If you choose to join the online leaderboards of the endless rifts, the game creates an anonymous account for you (see "Online leaderboards" below).

Developer and contact

Developer: Kirill Shavrin (Skyward Atelier)
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, settings (such as language and sound) and the state of purchases are stored locally in the game's private storage on your device. The game also generates a random installation identifier. It is not linked to your name, email or any account, and it is used to tell installations apart in feedback and diagnostics. If you join the online leaderboards, the name you chose and the anonymous account's sign-in token are also stored on your device.

Information sent over the network

Analytics (Firebase Analytics)

The game uses Google Firebase Analytics to understand how the game is played in aggregate, for example which levels are played, how far players progress, and which screens and features are used. Firebase Analytics records usage events together with a Firebase installation identifier and technical device and app context (such as device model, operating system version, language and app version). On Android it may also read the device's advertising ID. We have turned off Google signals in Google Analytics, and event data is retained for 14 months. Google's own privacy policy and retention rules also apply.

Crash and error reports (Firebase Crashlytics)

When the game crashes or hits a serious error, Firebase Crashlytics may send a crash report with a stack trace, technical device and app information (such as device model, operating system version and app version) and the installation identifier, so we can find and fix the problem.

Closed-beta feedback survey (Firebase Cloud Firestore)

During the closed beta the game may offer a short feedback survey, automatically after you beat the first chapter boss and at any time from a button in the game. Nothing is sent unless you press Send. If you do, the following is stored in Google Cloud Firestore (a database hosted in the europe-west1 region, Belgium): the random installation identifier, the time of submission, app version, platform, device model, operating system version, game language, your ratings (overall, difficulty, gameplay and optional art), your optional comment (up to 500 characters), the mission number, your total stars, whether developer cheats were ever enabled, and whether the survey was opened automatically or manually. Please do not put personal information such as your name, email address or phone number in the comment. We use this information only to improve the game.

Online leaderboards (Firebase Authentication and Cloud Firestore)

The endless rifts have optional public leaderboards. Before your first endless run the game asks whether you want to join them with a name you choose; you can also play without the leaderboard. Nothing is sent unless you save a name. If you do, the game creates an anonymous account with Google Firebase Authentication: a random user identifier, with no name, email address or phone number. The game then stores in Google Cloud Firestore (europe-west1 region, Belgium): your chosen name, your user identifier and, for each rift, your best points, the waves you survived, the battle time of that run and the time of the update. Your name and these results are public: every player of the game can see them in the leaderboard. Please do not use your real full name or other personal information as your leaderboard name; names that are offensive are refused or removed.

If you report another player's name as offensive, the report stores your user identifier, the reported player's user identifier and name, the leaderboard and the time, so we can review it. Results from a game profile in which developer cheats were ever enabled are never sent.

You can change your name or delete your leaderboard data at any time in the game: open a rift leaderboard and choose "Delete my data". This removes your name and results from every leaderboard and deletes the anonymous account. Your local records stay on your device.

Advertising (Google AdMob)

The game shows rewarded ads only. An ad is shown only if you deliberately choose to watch one in exchange for a reward, for example to restore a life or to double a reward. There are no banner, interstitial or app-open ads. When an ad is requested, the Google Mobile Ads SDK collects your device's advertising ID and technical device and request context, and may use them to choose and measure the ad. Where required by law (for example in the European Economic Area and the United Kingdom), the game asks for your consent through Google's consent form before ads are requested. On iOS, the game asks for your permission through Apple's App Tracking Transparency prompt before using the advertising identifier for ads. Google's own advertising policies apply.

Purchases (Google Play and Apple App Store)

The game offers optional in-app purchases: packs of in-game crystals and a one-time "No ads" purchase that removes ads and gives unlimited lives. 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 state needed to deliver what you bought (product identifier and purchase result). Refunds, cancellation and payment history are handled in your Google Play or Apple account. If you reinstall the game or switch devices, use the "Restore purchases" option where it is offered.

Sharing and international transfers

We do not sell your information. Information is processed by the service providers described above (Google LLC for Firebase and AdMob, 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. Leaderboard names and results are shown to other players of the game.

Retention and deletion

Local game data stays on your device until you clear the game's storage or uninstall the game. Firebase Analytics event data is retained for 14 months. Crash reports are retained according to Firebase Crashlytics' retention rules. Beta feedback is kept for as long as it is needed to improve the game. Leaderboard names and results are kept until you delete them in the game or the leaderboards are reset; name reports are kept for as long as they are needed to moderate names.

You can ask us to delete data we hold about you by writing to desvingns@gmail.com. Leaderboard data can be deleted directly in the game (see above). Other data is not linked to an account, so we can identify feedback only from details you can provide, such as the approximate time you sent it, your device model and the text of your comment. To stop analytics and ad personalization on your device, you can reset or opt out of the advertising ID in your device settings.

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.

Security

Game data on your device is stored in the game's private storage. Data is sent to our service providers 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.