1. General

This personal data processing policy (the “Policy”) applies to the muerri.shop website and describes what data is collected by Andrei Valerievich Shishmakov, acting as a self-employed professional income taxpayer, INN 861501922618 (the “Operator”), why it is collected, and what rights the user (the “User”, the data subject) has.

The Controller operates from the Russian Federation. This notice explains the processing and is not used as a blanket consent. Separate consent is requested for optional analytics and wherever consent is the applicable legal basis.

2. What data is processed

• Account data: email address and password (the password is stored only as an irreversible hash).
• Game profile (at the User's choice): Riot ID (name and tag), region and the technical account identifier (PUUID), which the User provides when linking a Riot account.
• Game statistics: publicly available data about played matches (score, map, agent, round events) obtained by the User-provided name from open statistics sources, as well as the reviews and progress metrics built on top of them.
• Order data: product, amount, status, order/payment identifiers, timestamps, document versions and checkout acknowledgements. Card details are handled by Robokassa and are not received or stored by the Controller.
• Uploaded materials (optional): game recordings, if the User uploads them for review.
• Technical data: necessary cookies/localStorage for sign-in and preferences, IP address and standard server logs for security and diagnostics.
• Optional analytics data: visited pages, traffic source, device, on-page interactions and a Webvisor session recording without form-field contents, collected only after a separate choice.

3. Purposes of processing

• registration and signing in to the personal account, password recovery;
• the core function of the service: automatic reviews of played matches and keeping a progress journal;
• performance of the contract — providing access to paid products;
• service notifications related to the operation of the service (e.g. a password reset email);
• keeping the service operational and protecting it from abuse;
• analysing traffic and usability, only after consent to optional analytics.

Data is not sold to third parties and is not shared with advertising networks.

4. Cookies, localStorage and Yandex Metrica

Necessary storage supports sign-in, language, payment safety and the saved analytics choice. It remains available when analytics is declined.

Yandex Metrica tag 110831071, click maps and Webvisor load only after “Allow analytics”. The tag uses limited mode and recording of all form-field contents is disabled. Declining does not prevent registration, Riot linking, episodes or payment.

Change the analytics-cookie choice.

5. Purposes and legal bases

Depending on the activity, processing is necessary to perform the contract or take requested pre-contract steps, comply with legal obligations, protect the service and users against abuse, or pursue the Controller's legitimate interest in reliable operation. Optional analytics relies on consent and can be refused or withdrawn without affecting the service.

6. Recipients and location

Data is shared with third parties only to the extent necessary for the service to work:

• Robokassa — payment processing, confirmation and receipts;
• Yandex — SmartCaptcha, service email and, only after consent, Yandex Metrica/Webvisor;
• match-statistics providers — retrieving available match data for the Riot ID supplied by the User;
• hosting and technical providers — only as necessary to operate and secure the service.

Data may also be disclosed upon a lawful request of authorised state bodies.

The service and its main database are hosted in the Russian Federation. A user outside Russia should understand that account and game data will be processed there. Where a transfer mechanism or additional safeguard is legally required, the Controller will provide information about the applicable arrangement on request.

7. Public reviews

Match reviews are private by default: only the User can see them. The User may, at their own choice, create a public link to a specific review — in the public version the names of all other match participants are automatically masked. The public link can be turned off at any time in the same review — after that it stops opening.

8. Retention and protection

Data is stored in the Operator's protected database and processed automatically. Only the Operator has access to the data. The connection to the site is protected by HTTPS, passwords are stored as hashes, and backups are created to prevent data loss.

Account, Riot, match and episode data is retained until account deletion or while needed to provide the service. Order, receipt and acceptance evidence is kept for mandatory tax and contract limitation periods. Security logs and backups are deleted or overwritten on the operational retention cycle when no longer needed for security and recovery.

9. User rights

• obtain information about the processing of their data;
• request correction, blocking or deletion of data;
• withdraw consent to processing;
• delete the account entirely — the delete button is available in the personal account; the game profile, match history, reviews and public links are deleted together with the account;
• contact the Operator at siniyzakat99@yandex.ru — requests are handled within 30 days;
• appeal the Operator's actions to the supervisory authority or a court.
• where the GDPR applies: object to processing based on legitimate interests, request restriction, receive portable data where applicable, and lodge a complaint with the data-protection authority in the country of habitual residence.

10. Minors and automated decisions

Independent purchases are intended for adults. A minor may use the service and make a payment only with a legal representative's consent and responsibility. The Controller will delete a minor's data following a substantiated request from the legal representative.

Automated analysis produces coaching content and does not make decisions that have legal or similarly significant effects on the User.

11. Changes

The Controller may update this notice and will publish the new version with a date. A fresh consent will be requested when legally required.

Current edition of 18 July 2026.