01Scope
This policy covers City Slash by NikasDev, including Android package com.nikasdev.cityslash and the Windows and macOS versions. It describes the implementation for 1.4.6, not the availability of the update or services for every account. The general NikasDev website policy is on a separate page (Russian).
There is no City Slash account or NikasDev profile-storage server. Persistent progress is saved on your device first. Android cloud features use your Google Play Games account; the game does not request your Google email address or password.
02Progress, settings and backups
Progress includes crystals, campaign completion and permanent upgrades, acquired fighters and arena records, and three open-world slots with character names, inventory, quests, decisions, explored maps and both map markers. These data and backup versions of save files form the save package. Technical ad-reward receipts prevent duplicate rewards; they are not payment details.
A local save is the working data on your device. A cloud copy is a separately uploaded progress package in Google Play Games. An export is a separate file saved to a location you choose; it does not update automatically as you play. Language, sound and age-group settings are local; the age group is excluded from progress exports and cloud packages. The device language is used when no language has been chosen. The game does not request contacts, camera, microphone, SMS or precise GPS location.
03Google Play Games on Android
Saved Games automatically synchronizes saved progress when auto-sync is enabled and the service is available. The backup menu offers manual checking, uploading and a restore prompt. Restoring progress or selecting a conflicting version requires confirmation. Currency, items and quests from different versions are not added together; technical reward receipts are combined to prevent duplicate rewards.
The game uses the Google Play Games player ID, sign-in and synchronization status, modification timestamps and save checksums. The drive.appdata permission covers the application's own data in Google Drive, not all your Drive files. Progress is sent to Google for storage and recovery, not automatically to a NikasDev server. Google Play Games also processes gaming-profile information, analytics and diagnostics as described in its documentation.
Availability depends on the network, account, permissions, Google services and version compatibility. Errors, delays, conflicts and size limits may prevent upload; the current package limit is 3 MiB. Check the status before switching devices or deleting the game. Windows and macOS do not use this integration. Google Play Games data disclosure.
04Advertising and related data
Android uses Google Mobile Ads SDK 25.5.0 (AdMob) and UMP 4.0.0. There are no ads on PC. Optional ads in the campaign and arena award 45 crystals after SDK confirmation and successful saving. Tapping the button or simply closing an ad does not confirm a reward.
Interstitial ads may appear after a campaign or arena victory/defeat, following the ending animation. Tutorials and voluntarily leaving the arena are excluded. There is one attempt per result, without a late interruption of an already available results screen. Opening the open-world inventory may trigger an ad after 15 minutes of active play; menus, pauses, tutorials, background time and ads do not count. A successfully shown interstitial resets the counter. This interval applies to inventory, not battle results.
Inventory ads are excluded early in the world, on death, with a modal open, when switching inventory tabs, during a character action, after recent damage or near danger. If no ad is ready, there is no wait for one. Age settings, UMP, another fullscreen view and unsaved profile or reward data may also block ads. Interstitials do not award 45 crystals.
The advertising SDK collects and shares IP addresses (approximate location), app/ad interactions, diagnostics, Android advertising IDs, App Set IDs and other applicable device/account identifiers for advertising, analytics and fraud prevention. Ads may preload. Declining personalization or optional viewing does not stop all technical processing. SDK data is encrypted in transit using TLS. AdMob data disclosure.
05Age and advertising preferences
The game asks for an age group, not a full birth date. Google Mobile Ads and UMP do not start before an eligible choice, when age is withheld or for under-13s. Changing the category after SDK startup stops new requests but does not erase previously processed data. Personalization is disabled for ages 13–15 and 16–17, with restricted modes and G and PG ad-content limits respectively. Ages 13–15 use UMP's under-age-of-consent setting without a consent prompt. The adult ad-content limit is T.
UMP refreshes consent status and shows regional choices where required for the age group. Advertising preferences are available in game settings when UMP requires that form; age is a separate setting. Changing a choice invalidates loaded ads. Age changes are temporarily unavailable during a fullscreen ad or form. Permission to request ads under UMP is not consent to personalized ads. These advertising age controls do not replace the game's store rating or control Google Play Games account rules. Contact us if a child has sent personal information to support. UMP documentation.
07Your choices and rights
You can turn off auto-sync in the cloud panel. This does not delete an uploaded copy; manual operations are separate actions. Manage ad preferences in the game, the advertising ID in Android, and your Google ad settings.
Depending on applicable law, you may request access, correction, deletion, restriction or portability, object to processing, withdraw consent and complain to a data protection authority. Contact NikasDev for data it receives directly. Withdrawal does not affect the lawfulness of earlier processing. Local progress supports gameplay, cloud processing supports backup and recovery, and correspondence supports assistance. Advertising consent is requested separately where required; this policy is not consent.
08Retention and deletion
Local files remain until removed. Clearing Android app data removes local progress; clearing the cache is not equivalent. Uninstalling does not delete the Google cloud copy. Operating-system backups may remain separately. On Windows/macOS, close the game and delete its user-data files; removing only the executable may leave saves. Delete exported files separately from the chosen folder or service.
To delete City Slash data in Google Play Games, follow Google's current instructions: open your Play Games profile, go to Your Data and game-data deletion, then select City Slash under individual games. On Android, the route is also available through the Play Store profile → Settings → General → Play Games Profile → Privacy & Settings → Delete profile & game data. Labels may change. City Slash has no in-game cloud-delete button.
Before deletion, disable auto-sync on your devices and close the game to avoid uploading remaining local progress again. Cloud deletion does not remove exports, correspondence, local files or separate Google Play History. Support correspondence is retained as needed to resolve requests and meet mandatory requirements; contact us to request deletion. Google applies its own retention rules. We do not promise indefinite storage or automatic deletion of all Google data.
09Security
Google Play Games encrypts data in transit with HTTPS; AdMob uses TLS. This does not promise end-to-end encryption or encrypted local saves/exports. Store exports securely and share them only with intended recipients. Absolute security and guaranteed recovery are not promised. External links are subject to the relevant service's rules.
10Updates and contact
This policy is updated with a new date when features or data practices change; required notices and consent are provided before the relevant processing. For data, support or deletion of voluntarily submitted materials, contact NikasDev, City Slash: nikasdevcom@gmail.com.
NikasDev · City Slash
nikasdevcom@gmail.com