Translation of the published documents. Revision numbers and dates are unchanged. Third-party license texts remain in their original language.

Your people are close

Privacy

What data is processed and how to manage it.

Application policy: 2026-10-12.2 · Website information: October 10, 2026 · English

Revision 2026-10-12.2 dated October 12, 2026.

Operator and contact

The Sniketor service is provided by Sniketor Limited Liability Company, Kyrgyz Republic, taxpayer identification number 01304202610629. Address: Bishkek, Pervomaysky district, Ch. Aitmatov Avenue, 16, 68. The developer name used in Google Play is Sniketor Games. For personal data, security and account deletion enquiries: moderator@qwgames.ru.

This policy applies to chat.qwgames.ru and Sniketor applications connected to it. App stores and external websites set their own rules for their independent processing of data.

Data and purposes of processing

For registration, sign-in and account recovery, we process a username, email address, random account identifier, salted password hash, session information and confirmation of acceptance of the rules revision and age 18+. Plaintext passwords are not stored. Confirming age 18+ does not mean passport verification: we do not request a date of birth or document copy during ordinary registration.

For communication, we store and transmit messages, files and images selected by the user, avatars, profile descriptions, reactions, read markers, settings, friends, community and channel memberships, and assigned roles. Usernames and profile information are visible to users in the relevant interface. Messages and files are available to selected correspondents or channel members within their permissions. Consider the membership and access settings of a community before posting material there.

When voice communication is enabled, your device sends audio to other participants. In supported desktop clients, you can separately start screen sharing. Sniketor does not create server recordings of conversations or streams. Communication data is transmitted through WebRTC directly or via our relay; participants in a direct connection may learn each other's network IP addresses. A recipient may technically record received audio or video on their device; the rules require participants' prior consent.

Push notifications. Notifications on a phone or in a browser work only if the user has turned them on in Sniketor settings and allowed them on the device. To deliver them, we keep the device notification address linked to the session — the Firebase Cloud Messaging token in the Android application or the browser's push subscription address — and a service delivery log: time, device type, event type and result, without message text. Google (Firebase Cloud Messaging) delivers notifications to the Android application; in a browser they are delivered by that browser's push service (for example Google, Mozilla or Apple). By default a notification contains only the sender's name and the name of the chat or community, for example “New message from vovan”; the beginning of the message text is sent only if the user has turned on “Show message text” (a choice saved earlier is kept). Notification content sent to a browser is encrypted for the device; content sent to the Android application is passed to Google as part of a Firebase Cloud Messaging message; Google and push services may process it outside the Kyrgyz Republic. The device address is deleted when the session ends, when the account is deleted or when the push service reports that it is no longer valid; the delivery log keeps no more than the 500 most recent entries and is cleared when the account is deleted.

For security, we process the connection IP address, technical browser or client information, session expiry times, request rate limits, errors and administrative actions. We do not request GPS location, address books or SMS. Content from other applications may be transmitted when you choose to share your screen or system audio. We receive images and files only after you select them; microphone audio when you use the corresponding feature and grant microphone permission; stream audio when sharing with sound is separately enabled.

To handle enquiries, we retain the request text, sender information, participant and object identifiers, a snapshot of content relevant to a report, decisions and dates. A report does not automatically attach your entire private conversation. Deleting the original object does not necessarily delete the separate material of a report already under review.

During screen sharing, participants receive the image of the selected screen. If stream audio is enabled and the client supports capturing it, the computer's system sounds or audio from the selected source are also transmitted; this may include notifications and audio from other applications. Close private windows and disable unnecessary sounds before sharing. Permission to share does not grant permanent screen access: you can stop sharing in the interface.

Your chosen interface language is saved in account settings and locally on the device for future sign-ins. Changing the language does not translate messages, names or other user materials and does not itself change server locations, data recipients or the service's age restriction.

Bots. When you message a bot, press its buttons or send a command in a channel where it is present, the bot receives your identifier, username, the message text, the button pressed and information about the chat (in direct messages, all messages to the bot; in channels, only commands, mentions of the bot and replies to it). A bot receives an audio file from a message only if that message was answered with a command to the bot and the bot can see the channel. A bot in a voice room technically receives participants' audio, like any other participant. When a bot is created via @botfather, its name, description, commands, owner, key hash and review decisions are stored; a minimal log of actions with the bot is kept to investigate abuse.

Third-party bots are created and run by independent developers. They decide what to do with the data they receive and are responsible for it; their terms are not part of this policy. Official Sniketor bots (with a blue check mark) store only the conversation state needed to work and do not record audio.

Legal bases and limits

Core account and messaging operations are necessary to provide the functions requested by the user under the user agreement. Optional features, such as voice or image uploads, need not be used. Abuse prevention, service protection and dispute handling protect legitimate interests to the extent permitted by applicable law. Mandatory processing takes place where a specific legal obligation exists. Where the law requires separate consent, it must be obtained separately and may be withdrawn; acceptance of the rules does not authorise arbitrary data processing.

We do not sell private conversations or other personal data, use them for advertising profiling or display advertising in the current release. No money is charged without a separate payment under the Sniketor+ offer (in Russian); there are no automatic renewals.

Sniketor+ payments

The Sniketor+ subscription is paid by bank card through the payment institution FreedomPay (Kyrgyz Republic), which processes the payment independently under its own rules. The card number, expiry date and security code are entered on FreedomPay's secure page; Sniketor neither receives nor stores them.

To create a payment, we send FreedomPay the order number, amount and currency, the plan name, the random account identifier, the IP address from which the payment is made (for fraud prevention) and, if one is linked to the account, the email address so that FreedomPay can send a receipt. Nicknames, conversations and other account data are not sent. From FreedomPay we receive the payment status, its FreedomPay number, the amount and a test-payment flag.

We keep the order number, plan, amount, status, payment and refund dates, the accepted offer version and the subscription period. The legal basis is performance of the contract under the offer and accounting and tax obligations. When an account is deleted, the subscription is deleted, and payment records are unlinked from the account and kept without the user identifier for the period required by accounting and tax law. Unpaid and cancelled orders are deleted after 180 days.

Recipients and hosting

The main servers, voice relay and server data copies are hosted in Moscow, Russia, on REG.RU / Reg.Cloud infrastructure. This provider's infrastructure is also used for service email and backups. For email delivery, the provider receives the recipient's address and email content, such as a confirmation or recovery link; the entire chat history is not transmitted for this purpose. The recipient's email service also participates in delivery. The operator is located in the Kyrgyz Republic; using the service involves processing data on the specified infrastructure in Russia.

An additional connection point, eu.qwgames.ru, runs on a rented server in Bulgaria (European Union). Connections pass through it for people who open Sniketor at this address or whose application switched to it because the main address was unavailable, and voice passes through it when a call chooses the Bulgarian relay. This server forwards the encrypted website traffic to the main server in Moscow without decrypting it (encryption keys are kept only in Moscow) and passes the user's IP address there for abuse protection; call audio through it stays encrypted (DTLS-SRTP). It can see the IP address, time and volume of a connection; conversations, files and passwords are not available to it and are not stored on it, and no connection logs are kept there.

Authorised staff and technical contractors receive access to data to the extent necessary for support, operation and handling requests. Data may be disclosed to public authorities where an applicable lawful basis exists and to the required extent. Community owners do not receive administrative access to other users' direct conversations.

External websites are opened through user action. In the Android application, YouTube links open in an external application or browser. In the web version, the YouTube player loads only after the play button is pressed: Google/YouTube then receives technical connection information and applies its own policy. Google Play independently processes information about installations and store operation. To deliver push notifications, Google (Firebase Cloud Messaging) or the user's browser push service receives the data listed in the “Push notifications” paragraph. When Sniketor+ is paid for, FreedomPay (Kyrgyz Republic) receives the data listed in the “Sniketor+ payments” section. Future servers in other countries and other payment services are not current recipients under this revision.

Official Sniketor bots run on a separate server in Moscow on the same infrastructure and receive data only through the Bot API, without access to the database. On a participant's command, the music bot fetches audio from the chosen source: a radio or audio file link given in the command, or the Jamendo catalog (Luxembourg) when searching by title. Only the address or the search text is sent to the source — no username or other user data; the source sees the IP address of the bot server, not of participants.

Retention and deletion

Accounts, profiles and communication history are retained while used to provide the service, or until the relevant materials are deleted or an account deletion request is fulfilled. You can delete your own messages in the interface. Account deletion is available through security settings and the webpage chat.qwgames.ru/delete-account. If you cannot sign in, contact moderator@qwgames.ru. Uninstalling the application from your device does not delete the account.

A request in settings is confirmed with the current password and sent to the operator. It does not mean deletion is completed immediately. The operator verifies account ownership, clarifies the request if necessary, performs deletion and communicates the result. We consider requests without undue delay; mandatory statutory time limits apply where established. Deletion is free and does not require acceptance of a new rules revision.

Fulfilment removes the account and sign-in data, active sessions, profile, personal avatar, friend connections and memberships, and the user's own messages and files. Direct conversations are deleted in their entirety for both participants, including the other person's messages and attachments. Other users' messages in shared channels remain. Community owners are advised to transfer ownership in advance; the lack of a successor does not itself negate the right to account deletion.

Expired sessions, registration drafts, single-use tokens and rate-limit counters are cleared by daily maintenance after expiry. An ordinary session lasts up to seven days; confirmation and recovery links last up to 30 minutes. Closed support requests and reports are deleted 180 days after closure; administrative action logs, 180 days after the event. Open requests are retained until a decision; the need for continued review is assessed separately. Minimum information about an active ban is kept for its duration and appeal review.

Cloud backups for both servers are configured to retain 30 daily versions, without separate weekly, monthly, yearly or additionally pinned latest versions. With uninterrupted daily backups, this corresponds to approximately 30 days. The provider does not delete displaced versions instantly; if backups stop, remaining versions may be retained longer. This is not a promise that all backups will be permanently deleted exactly 30 days after a request.

Registered main-server archives are automatically removed from retention after 21 days. The operator reviews migration, manual and local technical copies separately and deletes them within the chosen 30-day period from their creation; this control is not part of the account deletion button. Backups are not used for ordinary access to deleted accounts. After deletion from the live database, residual data may remain in backup versions until removed by the specified retention cycles. When fulfilling a request, the operator checks related copies and explains applicable time limits and restrictions, including where backups have stopped.

Ordinary application and voice-relay technical logs on the service's servers are removed from retention within 30 days when daily maintenance operates normally. Systemd logs are configured for 28-day retention and daily file rotation; system text logs use daily rotation with 28 archives. Separate administrative action records in the database have the 180-day retention period stated above. Residual log copies in backup images are subject to the separate backup retention cycle.

For a specific investigation, dispute or legal obligation, only necessary information may be retained separately until the basis ceases to exist. This exception does not permit indefinite retention of all data. A minimal deletion fulfilment log is needed to reapply deletions after restoring a backup database; it is retained while copies exist from which deleted data could return. A full-server restoration requires a separate check against the current log before access is opened.

Recipients may have saved or forwarded materials outside Sniketor. Such independent copies are not controlled by the operator.

The music bot's temporary audio files are deleted after playback or when the bot leaves the room. When a bot is deleted, its account, key and event queue are deleted.

Security and data on your device

Connections to the service are protected by HTTPS; voice communication uses secure WebRTC transport. Direct messages and server attachments are not end-to-end encrypted. The operator may technically access stored content; access must be limited to operational necessity. Absolute security of any information system cannot be guaranteed.

A necessary session cookie is used for sign-in. Interface settings and drafts may be stored in the browser's or application's local storage. You can remove them using device controls; this does not delete the server account. Microphone permission can be revoked in device or browser settings.

Requests, age and changes

In a request, providing your username or linked email address and describing the request is sufficient. Do not send passwords, one-time codes or full document copies without a separate justified request. A response is provided after proportionate account ownership verification. If a request is denied or some information is retained on a mandatory basis, we explain the reason and the available appeal procedure.

Write to moderator@qwgames.ru to request information about your data, correction, access, export, deletion or restriction of processing, or to withdraw consent where it is the basis. Proportionate verification of account ownership may be required to protect data. We do not ask you to send your password. You may contact a competent supervisory authority and use other legal remedies. This policy does not limit mandatory rights.

The service is intended for people aged 18 and over. If a minor's account is identified, we restrict access and consider deletion of related data, taking safety and applicable obligations into account. Such an account or a threat to a child's safety can be reported through the application or the email address provided.

The revision date and number appear at the top of the page. We notify users of material changes through the service and, where required, request separate confirmation or consent. Relevant information is updated before data processing actually changes. Previous revisions remain archived.

Platform rules · Delete account

Changes in this revision

Added the additional connection point eu.qwgames.ru in Bulgaria: what passes through it and what it can see. User data is still stored only in Moscow; no advertising purposes have been added.

Previous revision 2026-10-12.1 dated October 12, 2026 · Revision dated October 11, 2026 · Revision dated October 10, 2026 · Revision dated September 30, 2026 · Revision dated September 29, 2026

The sniketor.com information website

The website contains project information and links to the application. A manually selected language is saved in the browser's local storage; automatic selection uses the browser language. These settings can be removed through browser controls.

When the website is opened, the server receives technical information necessary for the HTTPS connection, including the IP address. The status page requests only public check results. Conversations, accounts and internal logs are not published there. Data enquiries: moderator@qwgames.ru.