Privacy Policy
Operator: Individual entrepreneur (IP) Nikolai Nikolaevich Kostin,
INN 342601019130, OGRNIP 325470400026949, place of registration: Leningrad Region, town of Kudrovo.
Personal data requests: support@kngames.ru.
1. When processing begins
On first launch, the Game shows a one-time hint: “By continuing to play, you accept the Agreement and the Policy (see ‘Settings’)” (in versions prior to September 2026, a window with links and an “Accept and continue” button). The Game stores the version number of the documents and the time of the first launch; this Policy and the User Agreement can be opened at any time in Settings → “Policy and terms”. Age, permission “to show ads” and permission for crash reports are not requested.
Profile, game and security data are processed in order to provide the features chosen by the user and to perform the User Agreement. The Game does not use Firebase or Crashlytics products or third-party product analytics. Ads are configured as non-personalized: without an advertising ID, geolocation, an advertising profile or the transmission of a personalization consent signal. If the purposes, the scope of the data or the recipients change materially, the notice will be shown again.
2. Age
The Game does not request or store age or date of birth. It contains no content available only to adults; stakes in games are placed only with in-game coins that have no monetary value. Age restrictions of the app store and purchase approval are applied by means of the respective platform. A parent or other legal representative manages the child’s use of the Game where this is required by applicable law.
3. Data, purposes and legal bases
Categories of data subjects: users of the offline and online modes, owners of game profiles, buyers, tournament participants, authors of support requests and visitors of the web version.
| Data | Purpose | Legal basis |
|---|---|---|
| Internal profile ID, a random device “login/password” pair (technical identifiers not linked to the person’s identity), IP, platform, app and device version | Creating and protecting the online profile, authorizing requests, connection security, statistics by platform | Performance of the User Agreement |
| Recovery code (stored in hashed form) | Transferring the profile to another device without signing in via third-party services | Performance of the Agreement; issued upon the user’s action |
| Yandex Games player identifier and signed SDK data; name and photo (if the user has allowed their transfer in the Yandex settings) | Signing in to the Yandex Games version, saving progress, initial population of the public profile; a copy of the name and photo is stored on the Game’s server | Performance of the Agreement; consent expressed in the Yandex settings and upon acceptance of the notice |
| VK/OK identifier, signed launch data; name and photo available via the SDK (VKontakte and Odnoklassniki versions only) | Signing in to the linked game account, saving progress, initial automatic population of the public profile after the notice is accepted; a copy of the name and photo is stored on the Game’s server and is visible to other players | Performance of the Agreement and acceptance of the notice about the public profile |
| Telegram ID / MAX ID and signed Mini App launch data; for purchases in Telegram: bot, order and payment identifiers, the item, the amount of Stars and the status; for purchases in MAX: the YooKassa payment identifier and the email address for the receipt | Signing in to the Mini App, saving progress, verifying the purchase, sending the fiscal receipt, refunds and protection against double crediting | Performance of the User Agreement and the requirements of the law on the use of cash register equipment |
| My World user identifier and signed launch parameters of the canvas app; name and photo available via the JS API | Signing in to the My World version, saving progress, initial population of the public profile; recording payments in mailiki | Performance of the Agreement and acceptance of the notice |
| Version and time of acceptance of the initial notice, platform and app version | Confirming that up-to-date information has been shown | Fulfillment of the Operator’s obligations |
| Game actions, tables, moves and dice rolls, results, rating, coin and chip balances, rewards, tournament results, game logs | Running games, calculating progress, server-side verification of the legality of moves and protection against abuse, reviewing requests | Performance of the User Agreement |
| Chosen name and chosen avatar (from the built-in set or imported from the platform) | Public profile visible to other players; moderation | Performance of the Agreement |
| Product, transaction and entitlement status identifiers; no bank details | Delivering the purchase, restoring the entitlement, refunds and preventing double crediting | Performance of the contract and legal requirements |
| Depersonalized ad impression events (placement, platform, result), without user identifiers | Configuring ad placements and monitoring ad failures | Acknowledgment of the notice |
| IP, app/OS version, device model, table number and technical events of the Game’s own server | Operation of the connection, security, prevention of abuse and fixing errors | Performance of the Agreement and fulfillment of the Operator’s obligations |
| IP, app/device data and impression events; no advertising ID and no geolocation | Showing and measuring non-personalized ads, protection against ad fraud | Providing the free version of the Game; consent or another applicable legal basis where required by the law of the user’s region |
Payment details are processed by the store or the platform’s payment service; the Game’s server does not receive them. The Game does not request the phone number, contacts, friends list, geolocation or biometric data from the platforms.
Processing operations: collection, recording, systematization, accumulation, storage, clarification, retrieval, use, transfer to processors, provision of access to game participants, depersonalization, blocking, deletion and destruction. Other players are shown only the name, avatar, rating, statistics and the game information needed for a game.
4. Who receives the data
| Recipient / processor | Data and purpose | Geography |
|---|---|---|
| Beget | Profile, game data, avatars, game logs — hosting of the server, database and files | Russia |
| Google Play, RuStore, App Store | Store and payment data — app distribution, payment and refunds; RuStore additionally verifies payments via its API | Under the rules of the respective store; for Google Play and the App Store, cross-border processing is possible |
| RevenueCat | Internal client ID, product and transaction identifiers and entitlement statuses — verification, recording and restoration of Google Play and App Store purchases | Cross-border processing |
| Yandex Games, VKontakte, Odnoklassniki, Telegram, MAX, My World | Signed sign-in data and player identifier — signing in to the version for the platform; orders and payments in the platform’s currency — operation of the shop; for MAX — YooKassa as the payment service and fiscal receipts | Under the rules of the respective platform; for Telegram, cross-border transfer is possible |
| Yandex Advertising Network | IP, app/device data and impression events — non-personalized ads, measurement and fraud protection; no advertising ID and no geolocation | Russia; cross-border processing under Yandex’s rules is possible |
The primary recording, systematization, accumulation and storage of the data of citizens of the Russian Federation are carried out in Russia. In the course of purchases and ad requests, certain technical data may be transferred to RevenueCat, Google Play, Apple and Telegram. The specific scope of a transfer is limited to the data required by the respective function.
5. Retention periods
| Category | Period |
|---|---|
| Profile, progress, user content | While the profile exists; after deletion, active data is deleted or the necessary records are depersonalized within 30 days at the latest |
| Network access logs | Up to 30 days |
| Logs of games and of the technical operation of the Game’s own server | Up to 90 days, except for the investigation of a specific incident |
| Record of acceptance of the initial notice | While the profile exists; deleted together with the account |
| Backups | Overwrite cycle of up to 30 days; deleted data is not returned to the production environment |
| Payment and accounting records | For the period required by law; the link to the game profile is removed when it is no longer needed |
6. Public information and moderation
The name, avatar, rating, statistics and the information needed for a game are visible to other participants. The internal ID, technical secrets and support requests are not shown publicly. In the versions for Yandex Games, VKontakte, Odnoklassniki and My World, the name and avatar are taken from the platform account at first sign-in if the platform provides them; they can be changed in the Game profile. Prohibited content can be reported; the Operator is entitled to hide it and restrict the profile.
7. Security
The Operator applies restriction of administrative access, hashing of secrets, backup and logging. Requests to the server are protected by TLS; signatures of platform data and payment notifications are verified on the server.
8. User rights and deletion
The user may request information, correction, restriction, withdrawal of consent or deletion by writing to support@kngames.ru. To locate the profile, state your in-game name, the platform and the substance of the request; do not send the recovery code, password or payment details. The Operator may request a secure confirmation sufficient to protect another person’s profile and responds within the time limits established by applicable law.
Withdrawal of consent does not affect the lawfulness of processing carried out before the withdrawal. Data necessary for the performance of the Agreement, the protection of rights or the fulfillment of legal obligations may be processed on another applicable legal basis to the extent necessary. The Operator’s actions or omissions may be appealed to Roskomnadzor or in court.
The account can be deleted within the Game (Settings → Delete account) or via the public page narde.kngames.ru/legal/delete-account.html. Active game data is deleted; the RevenueCat Customer profile is also deleted. Payment events and the tournament bracket are, where necessary, retained only after being unlinked from the account and after the public name/avatar has been removed. Deleting the game account does not cancel a store subscription: the subscription must be canceled in Google Play, RuStore or the App Store. Restorable purchases can be linked to a new profile using the “Restore purchases” button; coin packs that have been spent are not restored.
9. Changes
In the event of a material change in the purposes, the scope of the data or the recipients, the Game will show a new notice for the relevant version of the document. The current version is permanently available at this address.