Privacy Policy

We process personal data in accordance with Russian Federal Law 152-FZ on Personal Data. The policy explains what data we collect, the purposes, your rights, and retention periods.

This document is a translation from Russian. In the event of any discrepancy between the versions, the Russian text prevails.

SPORTPOKER PRIVACY POLICY

Revision of 12 October 2026. Effective date: 12 October 2026.

This Privacy Policy (the "Policy") defines the procedure for the processing and protection of the personal data of individuals (the "Data Subjects", "Users") carried out by the Operator in connection with the use of the SPORTPOKER service, located on the Internet at sportpoker.app, as well as within mobile applications and other client interfaces of the Service (collectively, the "Service").

The Policy is developed in fulfilment of the requirements of Federal Law No. 152-FZ of 27 July 2006 "On Personal Data" (the "152-FZ"), in particular Article 18.1 (publication of a document defining the policy regarding the processing of personal data), and defines the Operator's policy regarding the processing of personal data.

The Policy explains data processing and is not consent to every purpose. Registration and sign-in do not by themselves constitute consent to optional processing or public disclosure. Core Service functions rely on contractual and other grounds provided by law; a separate choice is requested where consent is required.

Important clarification about the nature of the Service. SPORTPOKER is a software-and-information service for organizing, recording and informationally supporting sporting (non-gambling) poker events. The Service does not organize and does not conduct gambling within the meaning of Federal Law No. 244-FZ of 29 December 2006, is not a gambling establishment, does not accept monetary stakes and does not pay out winnings. Sporting results, points, finishing places, the number of knockouts and the rating are of an accounting-and-sporting nature, are not winnings and have no monetary equivalent. Payments on the platform are related solely to subscriptions of organizing clubs to the Service's functionality. The relationship of the parties is regulated in detail in the Terms of Use (/terms) and the Public Offer (/offer).


1. Personal-data Operator and contact details

Operator (also the Provider under the Terms of Use):

  • Individual entrepreneur Balayan Gurgen Aleksandrovich, INN 263606960022, OGRNIP 326774600691392, registered 23.09.2026.
  • INN: 263606960022.
  • Phone: +7 977 607-65-47.
  • E-mail for enquiries from Data Subjects on personal-data matters: privacy@sportpoker.app.
  • Service website: https://sportpoker.app.

The Operator is an individual and independently determines the purposes and composition of the personal data processed, as well as the actions performed with it. The functions of the person responsible for organizing the processing of personal data (clause 1, part 1, Article 18.1 of 152-FZ) are performed by the Operator itself. All enquiries related to the processing of personal data (including requests for access, rectification, deletion, withdrawal of consent, data export and complaints) are sent to the contacts indicated above.

The Operator processes personal data in compliance with the requirements of 152-FZ. Information about the Operator is entered into the register of operators processing personal data on the basis of a notification sent by the Operator to the authorized body for the protection of the rights of personal-data subjects (Roskomnadzor) in the manner of Article 22 of 152-FZ.

1.1. The role of organizing clubs as independent operators

The Service is of a platform nature. In addition to the Operator, organizing clubs of sports poker events operate on the Service (the "Clubs").

With respect to personal data that Clubs independently collect, generate and use to hold their own events, maintain their own client base, register player participation, record their own results and for other of their own purposes, the Club acts as an independent personal-data operator and bears independent responsibility for compliance with the personal-data legislation, including obtaining the necessary consents, informing subjects and implementing their rights.

Provision of a player's data to a Club within the Service. To ensure a player's participation in a particular Club's event and to maintain sporting records, the Operator provides such a Club with the player's data to the extent necessary for these purposes: display name (nickname) and avatar, the status and timestamps of registration and arrival at the event, sporting results (finishing place, number of knockouts, points), "who knocked out whom" links for the Club's events, as well as the review of that Club (with the author's nickname and avatar). Such provision is carried out within the framework of performing the contract (the Terms of Use) and/or on the basis of the User's consent. Within these purposes, the Club processes the obtained data as an independent operator and is responsible for its further processing; for questions about such processing, the Data Subject should contact the relevant Club directly.

The Operator does not control and is not responsible for the processing of personal data carried out by Clubs outside the Service (e.g. in the Club's own accounting systems, during offline registration, or when arranging fees or prizes outside the Service).

Unless otherwise expressly stated, within the provision and functioning of the Service itself (registration, authentication, maintaining the player profile, the platform rating, delivery of notifications, ensuring security, etc.), the operator of the relevant personal data is the Operator indicated in clause 1 of this Policy.

1.2. Responsibility for personal-data processing

The Operator is responsible for its processing and for processing entrusted to processors to the extent required by law. Engaging a processor, a User posting data, or withdrawal of consent does not remove the Operator’s duties to protect data and uphold the Data Subject’s rights. Independent controllers, including Clubs, are responsible according to their actual purposes and activities; the Service terms do not restrict mandatory rights.


2. Terms and definitions

  • Personal data (PD) — any information relating to a directly or indirectly identified or identifiable individual (a personal-data Subject).
  • Processing of personal data — any action (operation) or set of actions with personal data performed with or without the use of automation tools (collection, recording, systematization, accumulation, storage, rectification, extraction, use, transfer, anonymization, blocking, deletion, destruction).
  • Anonymization — actions as a result of which it becomes impossible, without the use of additional information, to determine the belonging of personal data to a specific Subject (clause 9, Article 3 of 152-FZ).
  • Pseudonymization — the replacement of direct identifiers with technical ones (e.g. replacing a name with a numeric identifier) while preserving the possibility of correlating the data with the Subject given additional information. Pseudonymized data remains personal data.
  • Data Subject / User — an individual whose personal data is processed: a player, a Club representative, a website visitor.
  • Operator — the person indicated in clause 1 of the Policy.
  • Processor (sub-processor) — a person to whom the Operator entrusts the processing of personal data on the basis of a contract (part 3, Article 6 of 152-FZ).
  • Website — the Service website at sportpoker.app.
  • Club — an organizing club of sports poker events using the Service.

3. Categories of personal-data subjects

The Operator processes the personal data of the following categories of subjects:

  • Players — individuals registered with the Service to participate in sporting events, maintain a profile and receive related services;
  • Club representatives — individuals acting on behalf of organizing Clubs and using the relevant functionality of the Service;
  • Website visitors — persons using the Website without registration.

The Service is intended for persons who have reached the age of 18. The Operator does not deliberately collect the personal data of minors. See also Section 13 "Age restriction".


4. List (categories) of personal data processed

The Operator processes only the personal data necessary for the stated purposes, guided by the principle of minimization (Article 5 of 152-FZ). The list of data processed is provided below by category.

4.1. Registration, identification and authentication data

  • a unique account identifier;
  • e-mail address;
  • phone number;
  • a protected (hashed) representation of the password — the password in clear form is not stored by the Operator; the hashed representation of the password is stored as part of the account;
  • date of birth (used to verify that the age of 18 has been reached);
  • account status and preferred interface language;
  • information about the enabling of two-factor authentication and related technical parameters (the two-factor-authentication secret is stored in a protected (encrypted) form and is masked in service logs);
  • one-time confirmation codes (for e-mail confirmation and phone sign-in) — processed temporarily (see Section 4.10).

4.2. Player profile data

  • nickname (display name);
  • profile image (avatar) uploaded by the User as a file;
  • city;
  • profile privacy settings;
  • aggregated game statistics displayed in the profile.

Public visibility of profiles and sports information, as well as publication of reviews and resumes, is governed by Section 6 and existing restrictions. Access to one’s own profile does not make it accessible to others.

4.3. Game (sporting) data

  • information about registration for events (tournaments): the fact of registration, status, the method of marking arrival (a text value), timestamps of registration, arrival, elimination, cancellation;
  • sporting results and rating data: finishing place, number of knockouts, points awarded, field size, association with a Club and an event;
  • data generated to ensure the fairness of competitions and to counter unfair practices (including "who knocked out whom" links).

The said sporting results are of an accounting-and-sporting nature, are not winnings and have no monetary equivalent. The player's geolocation (location coordinates) is not stored on the server; the method of marking arrival is stored as a text value and does not contain GPS coordinates (see also Section 4.9).

4.4. Reviews and user-generated content (UGC)

  • the content of a review about a Club (rating and text);
  • information about the verification and moderation status of the review, as well as service notes from automated moderation.

Publishing a review’s text and score requires separate permission for both the “Nickname” and “Reviews” categories. An avatar appears only if separately allowed. Users must not include another person’s personal data without a lawful basis; this does not remove the Operator’s duty to examine complaints and restrict unlawful processing.

4.5. Chat messages

  • the content of messages and information about participation in chat rooms. The text of messages is generated by the User in free form and may contain personal data that the User decides to indicate; the author bears responsibility for such content.

4.6. Payment and subscription data

The Operator's own information system processes payment metadata for Club subscriptions: amount, currency, status, the payment identifier at the payment provider, the tariff name, as well as service information about the payment provider's webhooks (to ensure the correctness and single-time nature of processing).

Full bank-card details are not collected or stored by the Operator. The entry of payment details is carried out on the side of the payment provider (see Section 8). See also Section 4.6.1 on the composition of the data transferred to the provider.

4.6.1. Composition of data transferred during payment and fiscalization

When a payment is formed for the connected payment provider, the following are transferred: the shop identifier, amount, invoice number, service description ("SportPoker Subscription"), the receipt composition (service name, quantity, amount and applicable tax indicator) and the request signature. The full bank-card number (PAN), the CVV/CVC code and the card expiry date are not transferred to, and are not stored by, the Operator — entry of card details takes place on the side of the payment provider (Section 8). The payer's e-mail address and phone are likewise not transferred to the Operator as part of this information.

Auto-renewal (recurring payments). If the Club gives separate consent to automatic charges at payment (opt-in), the connected payment provider stores on its side a recurring-payment binding (a payment token / binding identifier) that allows charging for subsequent periods without re-entering the card details. The Operator in this case obtains and stores only a reference (identifier) to such a binding held at the provider and a flag that auto-renewal is enabled; the card number (PAN), the CVV/CVC code and other full card details themselves are not available to, and are not stored by, the Operator. The auto-renewal consent and the binding may be revoked by the Club at any time by disabling auto-renewal in the club cabinet.

An electronic receipt is generated through the connected fiscalization system in accordance with the laws of the Russian Federation. If a fiscal-data operator (OFD) is engaged, the receipt may include the purchaser's e-mail address and receipt line items solely to the extent necessary to meet the applicable requirements.

4.7. Notification (push) subscription data

  • Web push: the address of the browser's push-service endpoint, cryptographic subscription keys, information about the client application (user-agent), selected notification categories, marks of last activity and of subscription withdrawal;
  • Mobile push: device platform, push-notification token, application version, language, marks of last activity.

4.8. Technical data, audit and security log data

  • Security and audit data include IP address, client application information (user-agent), action, object, time and technical identifiers. They remain personal data where events can be linked to a person; a technical identifier alone does not make data anonymous. Retention grounds and periods are described in clause 10.3.
  • Internal product events help analyse Service operation; account-linked identifiers remain personal data. Third-party Yandex Metrika web analytics is described separately in clause 12.2.
  • Firebase Analytics is not used in the mobile applications. In release builds, Firebase Crashlytics automatically collects diagnostic reports from app startup, including before sign-in: errors and stack traces, event times, app and OS versions, device model and manufacturer, technical memory, disk and battery state, Crashlytics installation UUID and Firebase Installation ID. The current version has no separate consent or separate switch for diagnostics. The SportPoker account identifier is not deliberately set in Crashlytics, but installation identifiers can link reports from one installation, so the data is not fully anonymous. The network diagnostic handler excludes original URLs, headers and request content; the general JavaScript error handler sends the error message and stack, so personal data cannot be guaranteed absent from every error message. Deleting a SportPoker account does not automatically delete reports already sent to Firebase.

4.8.1. CVs, contact requests and Club CRM

  • desired position, experience, skills, CV text, job-search status, CV photo and the record/date of separate publication consent;
  • contact-disclosure requests, requester, message, the CV owner's decision and timestamps;
  • for a Club in which the User actually participated: phone, e-mail, avatar, favorite-Club flag, visit dates, organizational-fee/product totals, debt composition and settlements.

The public CV feed contains no direct contacts. Contacts are disclosed to a specific authenticated requester only after the CV owner explicitly accepts the request. CRM data is available only to authorized staff of the relevant Club, which acts as an independent PD operator under clause 1.1.

4.9. Geodata

  • Venue addresses and coordinates are used in the Club directory.
  • When location access is permitted, device location is used for the map and local selection of the nearest city. The mobile exact-coordinate cache exists only in process memory for no more than 15 minutes and is cleared on sign-out, account change and detected permission withdrawal. The former persistent cache is deleted when the updated application starts. The live position on an open map is handled on the device.
  • The profile receives the selected city’s name and centre. Exact device GPS coordinates are not sent in Club directory requests or used for system reverse geocoding to select a phone prefix. Map tile requests reveal the IP address and viewed map area to the map provider (section 8). Location permission can be withdrawn in device settings; the city can be selected manually.

4.10. Data used for sign-in and authentication

Signing in to the Service is performed using a one-time code sent to the specified e-mail address, Yandex ID, or, where the corresponding method is enabled, a phone number with ownership confirmed by an incoming call placed by the User. In the phone flow, the provider issues a service toll-free number, the User calls it, and the call is not answered; no SMS code, voice code, or outbound call to the User is used. The Operator processes the e-mail address, phone number, one-time e-mail code, and technical verification identifier solely for registration, sign-in, and account security.

4.11. Special categories of personal data and biometrics

The Operator does not collect special categories of personal data (on racial or ethnic origin, political, religious and other beliefs, state of health, etc.).

The profile images (avatars) and other photographs uploaded by the User are not used by the Operator to establish identity and are not biometric personal data within the meaning of Article 11 of 152-FZ.


5. Purposes of processing and legal grounds

The Operator processes personal data for specific, predefined and lawful purposes. The legal ground is indicated for each purpose below.

No.Purpose of processingCategories of dataLegal ground
5.1Registration, identification and authentication of the User, ensuring access to the account, access recovery, two-factor authentication4.1, 4.10Performance of the contract (the Terms of Use), to which the Subject is a party (clause 5, part 1, Article 6 of 152-FZ)
5.2Maintaining the profile and giving the User access to their own data4.2Performance of the contract
5.2.1Public display of the nickname, avatar, city, sporting results and reviews within the selected scope4.2, 4.3, 4.4Separate dissemination consent under Section 6 (Article 10.1 of 152-FZ)
5.3Participation in sporting events, internal sporting records and the User’s own statistics; necessary operational access for the organizing Club (clause 1.1)4.3Performance of the contract
5.3.1Creating and publishing CVs, staff recruitment, mediated contact requests and consent-based disclosure of contacts4.2, 4.8.1Performance of the contract; separate consent for public dissemination of the CV and disclosure of contacts (Articles 9 and 10.1 of 152-FZ)
5.3.2A Club maintaining the history of its own clients, visits, settlements and debts for event operations and reconciliation4.3, 4.6, 4.8.1Performance of the contract; the Club's legitimate interest subject to a balance of interests; the Club is an independent operator under clause 1.1
5.4Ensuring the fairness of competitions, countering collusion, multi-accounts and other unfair practices4.3, 4.8The legitimate interest of the Operator and other users with a balance of interests observed (clause 7, part 1, Article 6 of 152-FZ); fulfilment of the Operator's data-security obligations (Article 19 of 152-FZ)
5.5Publication of Club reviews; examination of complaints and moderation4.4Publication: separate consent under Section 6; necessary moderation: legitimate interest subject to a balance of interests and duties to restrict unlawful processing
5.6Operation of the chat4.5Performance of the contract
5.7Acceptance of payment for Club subscriptions, payment accounting and generation of an electronic receipt4.6Performance of the contract; fulfilment of legal obligations concerning settlements and fiscalization
5.8Delivery of functional notifications (about event starts, table moves, mentions and other events related to participation)4.7Performance of the contract
5.8.1Delivery of notifications sent at the User's separate choice (including about knockouts) and other notifications not required for participation4.7The Subject's consent
5.8.2Reminder about a tournament of a Club the User added to favorites4.7 and the favorite flag in 4.8.1The User's separate choice/consent; disabled by removing the Club from favorites or in notification settings
5.9Ensuring the security of the Service, maintaining an immutable audit log, recording consents, logging significant actions4.8Legitimate interest; fulfilment of the Operator's obligations to ensure data security (Articles 18.1, 19 of 152-FZ)
5.10Product analytics, crash diagnostics and Service stability improvements4.8 (including diagnostic reports and installation identifiers)Legitimate interest subject to a balance of Data Subject rights; recipient and cross-border requirements are set out in sections 8 and 9
5.11Verification that the User has reached the age of 184.1 (date of birth)Performance of the contract; fulfilment of the requirements of child-protection legislation
5.12Handling User enquiries, support4.1, 4.2 and other enquiry dataPerformance of the contract; fulfilment of duties to handle Data Subject requests
5.13Informational and advertising mailings (subject to separate consent)e-mail address, identifiers for deliverySeparate consent of the Subject (Article 9 of 152-FZ, Article 18 of the Federal Law "On Advertising")

The processing of personal data carried out for the purposes specified in clauses 5.8.1 and 5.13 is performed only with the separate consent of the User and may be terminated at their request without consequences for access to the core functionality of the Service. Withdrawal of consent to non-mandatory notifications (5.8.1) and mailings (5.13) does not terminate the functional notifications necessary for participation in events (5.8).


6. Consent to the processing and to the dissemination of personal data

6.1. Procedure for giving consent

Where processing relies on consent, the User gives it through a separate affirmative action after reviewing the specific purpose, data and document. Acceptance of the Terms and a link to this Policy do not replace consent. Core account functions, participation and internal sports records rely on the applicable contractual and other lawful grounds.

6.2. Public actions by the user

A review is posted through the user’s action in the publication form, showing its text, rating and the author’s nickname. A résumé is published through a separate “Publish résumé” action, limited to the professional details described in the form. Résumé contact details are shared with an employer only after the user accepts a request. These actions do not authorize publication of other account information.

Established visibility is retained for previously public profiles and sporting information. Absence of a new general consent record is not treated as a withdrawal of an earlier publication choice. Explicit restrictions, withdrawals and additional conditions remain authoritative. Where separate consent for dissemination is the applicable basis, it is obtained separately from acceptance of the Terms of Use. Requests to change visibility or stop dissemination may be sent to privacy@sportpoker.app.

6.3. Recording public actions and consent

We record the user’s action, its scope and the server date and time. Résumé publication retains its own confirmation; a review retains the submission of its specific text and rating. General permission for every data category is not created automatically. Separate consent records retain the selected categories, conditions, document version and grant or withdrawal history. Registration or a policy text change does not establish consent retroactively.

6.4. Content of the confirmed consents

The Policy provides information; a separate consent document defines the permitted processing. An editorial change to the Policy does not by itself require renewed consent. New affirmative consent is required if purposes, data or other processing terms change beyond the existing consent’s scope. Silence and continued use do not expand permission.

6.5. Withdrawal of consent

Consent can be withdrawn by writing to privacy@sportpoker.app; optional notifications can be disabled in Service or device settings. An accepted request to stop dissemination is fulfilled under the procedure and deadlines below. Copies previously obtained by others and external caches are not erased by this action alone; the Operator addresses removal requests within its powers and duties.

A demand to stop transfer (dissemination, provision or access) of data permitted for public disclosure is fulfilled within 3 working days under Article 10.1 of 152-FZ. Other processing and destruction after withdrawal are governed by Article 21 and clause 10.4; any lawful ground other than the withdrawn consent is assessed separately. Withdrawal of optional consent does not end core access to the Service.


7. Methods and conditions of processing personal data

The processing of personal data is carried out with and without the use of automation tools and includes collection, recording, systematization, accumulation, storage, rectification (updating, modification), extraction, use, transfer (provision, access) in the cases provided for by the Policy, anonymization, blocking, deletion and destruction.

Decisions producing legal consequences for the Data Subject or otherwise substantially affecting their rights and legitimate interests may not be based solely on automated processing without the basis and safeguards required by Article 16 of 152-FZ. Automatic age, security and moderation checks may restrict an action in the Service. The Data Subject may request an explanation and human review of a decision using the contacts in clause 1. This statement of rights does not mean that every image passes through an external automated classifier or that a person reviews every technical decision in advance.

7.1. Localization of databases

The recording, systematization, accumulation, storage, rectification (updating, modification) and extraction of the personal data of citizens of the Russian Federation are carried out using databases located in the territory of the Russian Federation (part 5, Article 18 of 152-FZ).


8. Transfer of personal data to third parties and engagement of processors

The Operator does not sell personal data and does not transfer it to third parties, except in the cases provided for by this Policy and the law. The Operator does not place on the Website any third-party advertising trackers that carry out independent collection of Users' data for advertising purposes.

To collect attendance statistics and to improve the Service, the Operator uses on the Website a third-party web-analytics service, Yandex Metrika — a service of Yandex LLC (Russian Federation), including its visitor session-recording feature Webvisor. Yandex Metrika independently (on its own infrastructure) collects data of Website visitors: the IP address, information about the client application (user-agent), device and browser information, the pages viewed and the actions performed on the Website, and — via Webvisor — recordings of page interactions (cursor movements, clicks, scrolling, input into non-personal fields). After the authenticated User gives separate consent, a persistent pseudonymous analytics identifier derived from the internal account identifier through a one-way transformation is also transmitted; the internal identifier itself, phone number, email address, and nickname are not transmitted to Metrika. This processing is described further in clause 12.2 and in the processors table (clause 8.1). This is a separate processing that does not replace the Operator's own product analytics: product analytics is additionally conducted by the Operator in its own information system using pseudonymized identifiers (clauses 4.8, 5.10).

8.1. Engagement of processors (sub-processors) and other recipients

Data recipients support the stated purposes. When entrusting processing, the Operator must establish confidentiality, security, scope and oversight requirements under Article 6(3) of 152-FZ. The table describes functions and potential recipients; changing providers requires review of the transfer ground and terms. The cross-border column describes the function, not confirmation that notification procedures have been completed.

Recipient / processorPurposeData transferredCross-border
Connected payment and fiscal providerAcceptance of payment for Club subscriptions and generation of electronic receiptsShop identifier, amount, invoice number, service description, receipt composition (service name, quantity, amount, tax indicator), signature. Bank-card data and the payer's contact data are not transferredNo
Fiscal-data operator (OFD) — if actually engaged in certain fiscalization scenariosFiscalization in accordance with the cash-register legislationThe purchaser's e-mail address and the receipt line itemsNo
Other payment providers — in case alternative payment methods are connectedAcceptance of paymentAmount, invoice number, webhook dataDepends on the provider
Yandex Metrika (Yandex LLC)Web analytics and Website attendance statistics, including recordings of page interactions (Webvisor)IP address, information about the client application (user-agent), device/browser information, on-site behavior (pages viewed and actions), page-interaction recordings (Webvisor), and a pseudonymous analytics identifier for an authenticated User. The internal account identifier and direct identifiers are not transmitted. Set only after the User consents to analytics cookies (clauses 12.1, 12.2)No (RF)
Timeweb (S3-compatible object storage)Storage of media files (player avatars, Club logos, venue photos)Uploaded image filesNo
MapTiler; Carto basemapsWeb and mobile mapsIP address and tile/style requests reflecting the viewed areaYes
DaData (address geocoding and validation)Geocoding of Club addresses, suggestions and verification of Clubs' addresses and organization details (INN/OGRN)The Club's address string / INN / organization name (not related to a player's PD)No
Phone-ownership verification providers (SMS-Prosto Wait Call; SMS.ru CallCheck when that integration is explicitly enabled)Phone ownership confirmation: the User calls the issued toll-free number and the call is not answeredPhone number and technical verification identifier; no SMS/voice code is transferredNo
Timeweb SMTPSign-in emails and service notificationsRecipient address and email contentAccording to the actual delivery infrastructure
Browser and platform push services (Google/FCM, Mozilla, Apple/APNs/WebKit)Delivery of web and mobile pushAn encrypted message/token and notification content (via the VAPID protocol — for web push)Yes
Huawei Push Kit (HMS) — for the AppGallery buildMobile push deliveryPush token, technical app and device information, notification contentDepends on the actual Huawei infrastructure; the project region does not guarantee the absence of cross-border transfers
Google / Firebase CrashlyticsCrash detection, diagnostics and mobile app stabilityDiagnostic reports, technical app/device details and installation identifiers, as described in clause 4.8Yes; the Huawei region does not determine Firebase data location
Organizing Clubs (independent operators — clause 1.1)Ensuring a player's participation in the Club's event and sporting recordkeepingNickname, avatar, the status and time of registration/arrival, sporting results, "who knocked out whom" links, a review of the Club with the author's nickname/avatarNo

The external NSFW classifier is disabled in the current production configuration; this does not mean every image has been automatically checked. Available moderation and complaint procedures apply. Enabling an external check requires separate assessment of the data, recipient and ground.

8.2. Payment details

Full bank-card details are processed on the side of the payment provider, which ensures compliance with the requirements of the payment-card industry (PCI DSS). The Operator does not receive or store such details. Automatic (recurring) debiting of funds from a bank card is carried out only where the Club has given separate consent to auto-renewal (opt-in) and is performed by the payment provider using the recurring-payment binding (token) stored on its side; the full card details remain unavailable to the Operator. The Club may disable auto-renewal at any time (clause 4.6.1).

8.3. Transfer at the request of authorized bodies

The Operator has the right to transfer personal data to state bodies in the cases and in the manner established by the legislation of the Russian Federation (upon a lawful request of a court, law-enforcement and other authorized bodies).


9. Cross-border transfer of personal data

Firebase Crashlytics also receives the diagnostic reports and installation identifiers listed in clause 4.8. The Huawei data-processing region does not control Firebase data location. Diagnostic report location and retention depend on the provider terms and actual configuration; this Policy does not claim exclusive storage in the Russian Federation or automatic deletion together with a SportPoker account.

Apple/APNs and Google/FCM push services and MapTiler / Carto map services may receive data outside the Russian Federation: notification tokens and content, and, for maps, IP addresses and requests for the visible area. Current email delivery uses Timeweb SMTP; Mailgun and an external NSFW classifier are not used in the production configuration.

For cross-border transfers the Operator must comply with Article 12 of 152-FZ, including a separate prior notification to Roskomnadzor, assessment of the recipient and applicable restrictions, and a lawful transfer ground. The general processing notification under Article 22 does not replace the cross-border notification. Transfers are limited to the relevant function’s purpose; enabling a function does not permit unrelated use of data.


10. Periods of processing and storage of personal data. Deletion and destruction

10.1. General periods

The Operator processes personal data for the period necessary to achieve the purposes of processing, and where processing is based on consent — until the purpose is achieved or consent is withdrawn, unless a different period is established by law. The User's personal data is stored for the duration of the account and the use of the Service. After deletion of the account, the data is processed in the manner described in clause 10.2.

10.2. Deletion of the account. Composition of anonymized and retained data

Confirmed account deletion ends its sessions and public display of personal data. Email, phone number, date of birth, password, two-factor secret, external sign-in identities, push tokens and the avatar reference are removed; the nickname is replaced with a neutral value. The fact that adulthood was verified and necessary sports or financial facts may remain where a corresponding ground exists. Replacing a name with a technical identifier does not automatically anonymise linked records.

Source media files are deleted through a separately persisted task. Backups and images already cached by a CDN or other parties do not disappear synchronously with account closure; requests concerning those copies and applicable periods are handled separately. Withdrawal restricts subsequent publication rather than asserting destruction of every copy.

Data retained by Clubs. A client card, participation and settlement history may remain for justified purposes of the relevant Club as an independent controller. Access is limited to that Club’s authorised staff. This is not permission to retain all contacts and documents indefinitely: the Club must have a ground and period for each data category and address Data Subject requests. Requests concerning the Operator’s processing can be sent to privacy@sportpoker.app.

10.3. Specific periods

  • Audit, internal analytics and security data are retained only as needed for the relevant purpose or duty; there is no universal automatic “12 months” period for all logs.
  • IP addresses, user-agent data and coordinates/accuracy in legacy consent records become eligible for cleanup after 365 days at the next successful daily run. A documented hold for a dispute or lawful request with an expiry date temporarily excludes the relevant records. Failures and queued work are monitored as part of request fulfilment; this is not the retention period of the consent evidence itself.
  • Publication decisions, including the necessary full name and contact, are retained as evidence of the processing ground for the applicable period; continued need must be assessed separately, not extended indefinitely by default.
  • Expired one-time email codes become eligible for cleanup 24 hours after expiry and are removed at the next successful daily run (normally about 24–48 hours after expiry). Failures and queued work are monitored separately. The device coordinate cache is limited to 15 minutes (clause 4.9).
  • 30 days is the regular backup-cycle period for the main PostgreSQL cluster (CNPG). It is not a common period for separate off-site or additional backups: their retention and deletion are checked separately. A record is not removed synchronously from every existing copy; deletion and withdrawal decisions must be reapplied after restoration.
  • Payment and fiscal documents follow mandatory statutory periods. Justified preservation for a dispute or lawful request is documented separately with a limited period and does not automatically cover all account data.
  • When destruction of personal data processed by automated means is confirmed, the signed destruction record and log export are retained for 3 years from destruction under Roskomnadzor Order No. 179 of 28 October 2022. This period applies to destruction evidence; it is not a general retention period for personal data. A technical log alone does not replace the signed record.

10.4. Destruction upon achievement of purposes and upon request

The deadline depends on the ground for the request. When the processing purpose is achieved or consent is withdrawn and no other ground applies, processing ends and data is destroyed within 30 calendar days under Article 21 of 152-FZ. A demand to stop processing under Article 21(5.1) is fulfilled within 10 working days, extendable by no more than 5 working days with a reasoned notice. Identified unlawful processing must stop within 3 working days; if it cannot be made lawful, the data must be destroyed within 10 working days.

If destruction within the required period is impossible, data is blocked and destroyed within the period under Article 21(6), no more than six months unless federal law sets another period. Retention on another lawful ground requires a specific justification. Requests are assessed according to the actual data and applicable rule rather than one universal deadline.


11. Rights of the personal-data subject and the procedure for exercising them

In accordance with Articles 14–17, 20–21 of 152-FZ, the Data Subject has the right:

  • to access information concerning the processing of their personal data and to receive such information;
  • to rectify (correct, update) personal data in case of its incompleteness, inaccuracy or non-currency;
  • to block personal data in the cases established by law;
  • to delete (destroy) personal data processed unlawfully or upon achievement of the purpose of processing / withdrawal of consent (subject to the specifics set out in clauses 10.2, 10.4);
  • to object to processing and to withdraw consent (Section 6.5), including consent to dissemination (clause 6.2);
  • to receive a copy of their data — upon the Subject's request (clause 11.1);
  • to apply to the Operator and to appeal the Operator's actions or inaction to the authorized body for the protection of the rights of personal-data subjects (Roskomnadzor) and to a court.

Operator's response times. The Operator responds to a request for access/rectification within 10 (ten) business days from the date of the request (with the possibility of extension by no more than 5 business days with notice to the Subject). Blocking and/or destruction of personal data upon detection of unlawful processing is carried out within the periods established by Article 21 of 152-FZ.

11.1. Mechanisms implemented in the Service

  • Data access. Processing information and a copy of processed data are available on request to privacy@sportpoker.app under Articles 14 and 20 of 152-FZ. Automated data export in the personal account/application is not provided.
  • Account deletion. Available in personal settings under clauses 10.2–10.4. Signing out alone is not confirmation of deletion.
  • Publication. To change restrictions, withdraw consent or obtain the decision history, send a request to privacy@sportpoker.app. A specific review or resume is published through its respective form.
  • Age. The Service verifies age 18 or older; the verification fact may remain after account closure without the date of birth.

11.2. Enquiries to the Operator

To exercise their rights, the Data Subject has the right to send the Operator a request to privacy@sportpoker.app or to other contacts indicated in clause 1. The request must contain information enabling the Subject to be identified and their connection with the processed data to be confirmed. The Operator considers the enquiry and provides a response within the periods indicated above and established by 152-FZ. The Operator has the right to request additional information to verify the identity of the applicant in order to prevent disclosure of data to third parties.


12. Cookies, analytics and push notifications

12.1. Cookies and similar technologies

The Website uses cookies and similar technologies. Cookies are divided into:

  • strictly necessary — ensure the operation of the Website, authentication, session security (their disabling may make the use of the Service impossible);
  • analytics — used to collect pseudonymized/anonymized usage statistics and to improve the Service. The analytics (non-mandatory) cookies include, in particular, the cookies of the third-party web-analytics service Yandex Metrika (clause 12.2), which are set and loaded only after the User's consent is obtained.

On the first visit to the Website, the User is shown an informational notice (banner) about the use of cookies with the ability to manage their use; until the User's consent is obtained, analytics (non-mandatory) cookies, including Yandex Metrika cookies, are not set. The User can restrict or disable cookies in their browser settings; disabling strictly necessary cookies may affect the operability of the Service.

12.2. Analytics

Product analytics is carried out on the basis of a predefined list of events associated with pseudonymized identifiers; the properties accompanying the events are cleared of personal data at the collection stage, and the results are used predominantly in an anonymized (aggregated) form. Pseudonymized data remains personal data and is processed on the legal ground of legitimate interest (clause 5.10).

Third-party web analytics — Yandex Metrika. In addition to its own product analytics, the Operator uses on the Website the web-analytics service Yandex Metrika, operated by Yandex LLC (Russian Federation). Yandex Metrika processes the IP address, device and browser information (user-agent), the pages viewed and the actions performed on the Website, and — via its Webvisor feature — recordings of page interactions (cursor movements, clicks, scrolling, input into non-personal fields). For an authenticated User, after consent, Metrika also receives a separate persistent analytics identifier produced by a one-way cryptographic transformation of the internal account identifier. It makes it possible to link the same User's visits, but it does not contain, and is never replaced on failure with, the account UUID, phone number, email address, nickname, full name, or Club details. This data is used to compile audience statistics and to improve the Service. The processing is carried out on Yandex's infrastructure located in the territory of the Russian Federation; no cross-border transfer takes place in connection with the use of Yandex Metrika. The Yandex Metrika script is set and loaded only after the User has accepted analytics cookies (the consent banner — clause 12.1). The service's terms of use are available at https://yandex.ru/legal/metrica_termsofuse/. The User can opt out of data collection by Yandex Metrika — by not consenting to analytics cookies, by using a blocker / browser settings, as well as via the Yandex Metrika opt-out tool (https://yandex.ru/support/metrica/general/opt-out.html).

12.3. Push notifications (web push based on VAPID and mobile push)

Push notifications are delivered with the User's consent to receive notifications, expressed in the browser/device (a system permission request) and/or in the Service settings. Functional notifications necessary for participation in events (start, table move, mention) are sent within the framework of performing the contract; non-mandatory notifications (including about knockouts) and marketing messages — on the basis of separate consent (clauses 5.8.1, 5.13). The User can at any time withdraw consent and disable notifications — in the Service settings, as well as in the browser or device settings. Web push is delivered via browser push services as an encrypted message; mobile push is delivered via APNs (Apple), FCM (Google), or, in AppGallery builds, Huawei Push Kit (HMS) (Section 9).


12.4. Links after installation from AppGallery

If the app was installed through a tournament or club link, SPORTPOKER can ask the installed AppGallery for that link's saved parameter. This request is made only after separate permission in the app and may start AppGallery in the background. The SPORTPOKER package name is sent; only the link parameter for our own app is read. We do not request installation times, advertising identifiers or clipboard contents, and do not use this mechanism for advertising analytics. A valid link is stored locally until it is opened once after sign-in and profile completion. After opening, a local marker retains the link type and tournament or club identifier to prevent reopening it. Users can decline; normal sign-in and new links continue to work.

12.5. Links after installation from RuStore

In the RuStore build, the app can ask the installed RuStore for a saved tournament or club link parameter. The request is made only after separate permission in the app. RuStore receives the SPORTPOKER package name and returns the link parameter and technical installation details (package name, version and timestamps). SPORTPOKER uses and stores only the validated link type and club or tournament identifier; other fields are neither stored nor sent to our server. The reader library version used does not contain an advertising analytics module. The link is stored locally until it is opened once after sign-in and profile completion; a local marker prevents reopening. A newly opened explicit link takes priority. Users can decline; normal sign-in and new links continue to work. RuStore determines how long the original link remains available; recovery after a long installation delay is not guaranteed.

13. Age restriction (18+)

The Service is intended exclusively for persons who have reached the age of 18. The age restriction is due to the need for full legal capacity to enter into a contract, as well as the ability to post and view user content (reviews, chat messages, images) and applicable requirements for information products. By registering with the Service, the User confirms that they have reached the age of majority. The Operator does not deliberately collect the personal data of minors. Upon detection of the use of the Service by a person under 18, the Operator has the right to block the relevant account and delete (anonymize) the related data in the manner of Section 10; a decision made in an automatic mode may be reviewed with human involvement upon the Subject's request.


14. Measures to ensure the security of personal data

The Operator takes the necessary legal, organizational and technical measures to protect personal data from unlawful or accidental access, destruction, modification, blocking, copying, provision, dissemination, as well as from other unlawful actions (Articles 18.1, 19 of 152-FZ), including:

  • storage of passwords in a protected (hashed) form; passwords in clear form are not stored;
  • storage of the two-factor-authentication secret in an encrypted form and its masking in logs;
  • support for two-factor authentication;
  • maintaining an immutable audit log of significant actions with masking of sensitive values;
  • separation of access rights and access control to data;
  • the use of protected data-transmission channels;
  • engaging processors on the conditions of compliance with confidentiality and security requirements.

The details of the technical security measures are not disclosed to an extent that could reduce their effectiveness. No information system provides absolute protection; the Operator does not warrant the complete security of data in the event of circumstances beyond its reasonable control (Section 1.2) but takes reasonable and sufficient measures in accordance with the law.

In the event of detection of an incident involving the unlawful or accidental transfer (provision, dissemination, access) of personal data that resulted in a violation of subjects' rights, the Operator takes response measures and notifies the authorized body (Roskomnadzor) within the periods and in the manner established by Article 21 of 152-FZ.


15. Amendment of the Policy

The current revision is published at sportpoker.app/privacy with its effective date. The Operator informs Users of material processing changes through available means. Correcting a description or translation is not new consent. Where changed processing requires new consent, it is requested separately before that processing starts; continued use of the Service does not replace it.


16. Final provisions

  • The law of the Russian Federation applies to this Policy and to the relations related to the processing of personal data.
  • If any provision of the Policy is found to be invalid, this does not affect the validity of the remaining provisions.
  • This Policy is a publicly available document and is subject to posting on the Operator's Website.
  • Information about the Operator is entered into the register of personal-data operators on the basis of a notification sent to Roskomnadzor in the manner of Article 22 of 152-FZ.
  • On all matters related to the processing of personal data, the User may contact the Operator using the contacts indicated in Section 1.

Operator: individual entrepreneur Balayan Gurgen Aleksandrovich, INN 263606960022, OGRNIP 326774600691392, registered 23.09.2026. Contact for enquiries on personal-data matters: privacy@sportpoker.app, tel. +7 977 607-65-47.

Note: This is a translation provided for convenience. In the event of any discrepancy, the Russian-language version prevails.