Privacy Policy
Operator: Individual Entrepreneur Nikolai Nikolaevich Kostin,
INN 342601019130, OGRNIP 325470400026949, registered in Kudrovo, Leningrad Region, Russia.
Personal data requests: support@kngames.ru.
1. When processing starts
Processing starts when the Game is launched for the first time. The Game creates a game profile, stores the number of the current edition of the documents and the time of the first launch, and shows a one-time hint: “By continuing to play you accept the Agreement and Policy (see Settings)”. This Policy and the Terms of Use can be opened in the Game at any time: Settings → “Policy and terms”. The Game does not ask for age, for permission “to show ads” or for permission to send crash reports. Data is processed on the grounds listed in section 3; the Game’s own usage statistics can be switched off in Settings at any time.
Profile, game and security data are processed to provide the features the user chooses and to perform the Terms of Use. The Game does not use Firebase, Crashlytics or third-party product analytics. Limited usage statistics are first stored on the device and sent in batches only to the Game’s own server. Ads are configured as non-personalized: no advertising ID, no geolocation, no advertising profile and no signal of consent to personalization. If the purposes, the data or the recipients change materially, the Game will show a one-time hint about the new edition.
2. Age
The Game does not ask for or store age or date of birth. It has no content available only to adults. Age restrictions of the app store and purchase approval are applied by the respective platform. A parent or other legal guardian manages a child’s use of the Game where applicable law requires it.
3. Data, purposes and legal grounds
Data subjects: users of the offline and online modes, owners of game profiles, buyers and authors of support requests.
| Data | Purpose | Legal ground |
|---|---|---|
| Internal ID, public tag, hashes of the installation key and session, IP, app and device version | Creating and protecting the online profile, authorization, connection security | Performance of the Terms of Use |
| Version and time of the initial notice, platform and app version | Proof that up-to-date information was shown | Performance of the Operator’s obligations |
| Random installation identifier in hashed form, random session identifier, screen transitions, opened windows, chosen game modes and settings, type of chosen design and the summary result of a game; no nickname, message text, cards in hand, advertising ID, geolocation or device model | Understanding how features are used, finding broken scenarios and improving the Game | Acknowledgement of the notice and the Terms of Use; collection can be switched off in Settings |
| Game actions, tables, results, rating, coin balance and rewards | Running games, calculating progress and preventing abuse | Performance of the Terms of Use |
| Chosen nickname and uploaded avatar | Public profile visible to other players; moderation | Performance of the Terms of Use; for a photo, a separate voluntary action after a notice that it will be public |
| Product, transaction and entitlement status identifiers; no bank details | Delivering a purchase, restoring an entitlement, refunds and preventing double crediting | Performance of the contract and legal requirements |
| Text of a support request; optional email and image; public tag and nickname; platform, device model, OS, Game and build versions, locale, screen size and source screen | Delivering and answering the request, diagnosing and fixing the described problem | The user’s request and performance of the Terms of Use; a separate voluntary action for the email and the attachment |
| IP, app/OS version, device model, roomId and technical events of the Game’s own server | Keeping the connection working, security, preventing abuse and fixing errors | Performance of the Terms of Use and of the Operator’s obligations |
| IP, app/device data and ad 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 ground where the law of the user’s region requires it |
Payment details are processed by the app store; the Game’s server does not receive them. A regular image is not used for face recognition or identification. Do not upload documents, bank cards, addresses, medical information or images of other people.
Processing operations: collection, recording, systematization, accumulation, storage, clarification, retrieval, use, transfer to processors, granting access to game participants, depersonalization, blocking, deletion and destruction. Other players see only the public tag, nickname, avatar, rating and the game information needed for a game.
4. Who receives the data
| Recipient / processor | Data and purpose | Location |
|---|---|---|
| Domain Name Registrar REG.RU LLC (INN 7733568767; 72 Leningradsky Prospekt, bldg. 3, Moscow 125315) | Profile, game data, public avatars, support requests and logs — hosting of the server, database and files (cloud server in Moscow) | Russia |
| RuSender | Text of a support request, email, attachment and technical context — delivery to the service mailbox | Under the service’s terms; the main record of the request is stored in Russia |
| Apple (App Store) | Store and payment data — app distribution, payment and refunds | Cross-border processing under Apple’s rules is possible |
| RevenueCat | Internal client ID, product and transaction identifiers and entitlement statuses — verifying, recording and restoring purchases | Cross-border processing; the Customer profile is deleted server-to-server when the account is deleted |
| Yandex Advertising Network and its current mediation partners | IP, app/device data and impression events — non-personalized ads, measurement and fraud protection; no advertising ID and no geolocation | Cross-border processing is possible depending on the partner chosen by Yandex |
The initial recording, systematization, accumulation and storage of data of citizens of the Russian Federation take place in Russia.
For purchases and ad requests, some technical data may be transferred to RevenueCat, Apple and foreign advertising partners. The Operator filed a notice of intent
to carry out cross-border transfers with Roskomnadzor on 2 September 2026, number
100407329. Each transfer is limited to the data needed by the respective feature.
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 |
| Network access logs | Up to 30 days |
| Raw depersonalized usage events on the server | Up to 30 days; when the storage limit is reached, the oldest records are deleted earlier |
| Local event queue on the device | Until a successful batch upload; at most 500 events and 192 KB, the oldest are dropped on overflow |
| Security and technical logs of the Game’s own server | Up to 90 days, except for the investigation of a specific incident |
| Image attached to a support request | Up to 90 days after successful delivery or until the profile is deleted |
| Text of a support request, email and technical context | As long as needed to handle and answer the request, but no longer than the profile exists; deleted together with the account |
| Record that the initial notice was shown | While the profile exists; deleted together with the account |
| Backups | Overwrite cycle of up to 30 days; deleted data is not restored to the working system |
| 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 public tag, nickname, chosen avatar, rating and the information needed for a game are visible to other participants. The internal ID, email, technical secrets and support requests are never shown publicly. Before a photo from the device is chosen, the Game says explicitly that other players will see it. Uploading is optional; public display can be stopped by choosing a built-in avatar or by deleting the account. Prohibited content can be reported; the Operator may hide it and restrict the profile.
7. Security
The Operator restricts administrative access, hashes secrets, makes backups and keeps logs. The game’s realtime channel and server requests are protected by TLS; the client verifies the certificate and the server name.
8. User rights and deletion
The user may request information, correction, restriction, withdrawal of consent or deletion by writing to support@kngames.ru. To find an anonymous profile, give the public tag, the request and an email for the reply; do not send the installation key or the session secret. The Operator may ask for a safe confirmation sufficient to protect another person’s profile and replies within the time limits set by applicable law.
Withdrawal of consent does not affect the lawfulness of processing carried out before it. Data needed to perform the Terms of Use, protect rights or meet legal obligations may be processed on another applicable ground to the necessary extent. Actions or omissions of the Operator can be appealed to Roskomnadzor or to a court.
The account can be deleted in the Game or through the public page durak.kngames.ru/legal/app_store/delete-account-en. Active game data is deleted; the RevenueCat Customer profile is also deleted. Payment events, if needed, are kept only after being unlinked from the account and after the public name/avatar is removed. If a subscription is active, deleting the game account does not cancel it: the subscription must be cancelled through the App Store. An active subscription and restorable purchases can be linked to a new profile with the “Restore purchases” button; coin packs that were already spent are not restored.
Collection of usage statistics can be switched off separately in Settings. When it is switched off, the local queue is cleared and the Game keeps requesting deletion of the data of the current random identifier from its own server until this is confirmed. If collection is switched on again, a new identifier is created.
9. Changes
If the purposes, the data or the recipients change materially, the Game will show a new notice for the respective version of the document. The current edition is always available at this address.