MYBIGGAMING
LIVE
Mandatory document

Personal data processing policy

What MyBigGaming collects, why it is processed, where it is stored and how data-subject rights are exercised.

Version 2026-09-08 · effective 8 сентября 2026 года

1. Operator

Родионов Дмитрий Иванович is the data operator. Privacy enquiries: privacy@mybiggaming.ru. The operator provides a postal address in response to a proper data-subject request where required by Russian law. This policy covers mybiggaming.ru, its language versions, accounts and connected web services.

2. Data and purposes

  • Technical logs: IP address, time, URL, referrer, browser and security events.
  • Account data: name, email, password hash, profile and security settings.
  • User functions: preferences, bookmarks, reading history, reactions and gaming content.
  • Newsletter: email, language, consent version and confirmation/withdrawal evidence.
  • Enquiries: name, email, organisation, category, message and technical evidence.
  • Yandex Metrica data only after optional analytics consent.

3. Retention

  • Ordinary logs: up to 52 days.
  • Inactive account: up to three years unless a separate legal period applies.
  • Pending newsletter request: seven days; active subscription until withdrawal; consent evidence for three years after withdrawal.
  • Ordinary enquiry: one year; claims, privacy requests and incidents: up to three years or a mandatory period.

4. Location and recipients

Primary databases, files and logs are hosted in the Russian Federation with FirstVDS. Subscriber addresses and form contents are not transferred to foreign email services. Yandex Metrica is used only with consent. Google Analytics, Google reCAPTCHA, Google Fonts and Meta/Facebook Pixel are not used on Russian public pages.

5. Your rights

You may request access, correction, restriction or deletion, withdraw consent and complain to the competent authority or a court. Send a request to privacy@mybiggaming.ru. Identity verification may be required to prevent disclosure to another person.

6. Security

Measures include access controls, HTTPS, CSRF protection, rate limits, local anti-bot controls, consent evidence, backups, updates, logging and incident response.

Cookies

We use cookies

The site uses technically necessary cookies for sign-in, security, storing preferences, and correct page operation. Analytics and other non-essential technologies should only be enabled after your consent. You can read more about data categories, purposes, and retention in the privacy policy.

Cookie policy
Quick actions