Applies when filling out the form on the "I want a review" page and when corresponding with the Telegram bot that page links to, on the site evskakunova-ai.ru
This is an English translation for reference. The Russian-language version is the legally binding document under Russian law.
Version dated 22.08.2026. Valid until replaced by a new version.
1.1. This document (the "Consent") is drawn up in accordance with Art. 9 of Federal Law No. 152-FZ of 27.07.2006 "On Personal Data" (hereinafter "152-FZ") and governs the processing of personal data that an individual (the "Subject") shares voluntarily, on their own initiative, while corresponding with the Controller's Telegram bot.
1.2. Personal data controller: Evgenia Vladimirovna Skakunova, a payer of tax on professional income (self-employed) under Federal Law No. 422-FZ of 27.11.2018, Taxpayer ID (INN) 774395464289, email evskakunova777@yandex.ru, Telegram @EvgeniaSkakunova (the "Controller").
1.3. This Consent is a standalone document, separate from the Privacy Policy. The Privacy Policy governs the anonymized technical data that Yandex.Metrica automatically collects on the Site; this Consent covers the data that the Subject personally and knowingly shares while corresponding with the bot.
1.4. On the page /en/consultation/ there are two equivalent ways to reach the Controller: (a) a form with the fields "Name," "Phone," "Email"; (b) the "I want a review" button / link to the Controller's Telegram bot. Both methods technically feed into the processing of the request within the same funnel: data submitted through the form is forwarded to the same Telegram bot and the same ChatPlace funnel of the Controller as a conversation started directly in the bot. The processing terms, purposes, retention periods, and rights of the Subject set out in this Consent apply equally to data received through either route; the only difference is in how consent is obtained (an explicit checkbox on the form versus conclusive consent when messaging the bot), see section 2.
2.1. In accordance with Art. 9(1) of 152-FZ, consent to the processing of personal data may be given by the Subject in any form that allows the fact of its receipt to be confirmed, unless federal law expressly requires otherwise. Data that the Subject voluntarily shares about themselves while corresponding with the bot (not belonging to the special categories, biometric, or other data for which 152-FZ requires a separate written form under Art. 9(4)) may be processed on the basis of such consent, including conclusive, electronic consent.
2.2. A link to this Consent is placed on the page /en/consultation/ next to the button leading to the bot, and must also be duplicated in the bot's own first message on first contact. By following the link to the bot and sending the bot their first message (including the code word "REVIEW"), the Subject confirms that they have reviewed the terms of this Consent and gives consent to the processing of the personal data they go on to share, under the terms set out below.
2.3. If the Subject does not agree with the terms, they simply do not send the bot any messages and do not share their data; reviewing the Site's materials without proceeding to the bot does not constitute consent to the processing of personal data.
2.4. The form on the page /en/consultation/ contains the fields "Name," "Phone," "Email" and a separate checkbox for consent to the processing of personal data under the terms of this Consent, with a link to its text. The checkbox is not checked by default (the Subject checks it themselves) and is a mandatory condition for submitting the form: without checking the box, the form cannot be submitted.
2.5. Unlike the conclusive consent given when messaging the bot (section 2.2), when using the form, consent is given through an explicit action by the Subject: checking the box and then submitting the form. Both options comply with Art. 9(1) of 152-FZ, which allows any form that confirms the fact that consent was received; the form with a separate checkbox records this fact with additional rigor.
2.6. After the form is submitted, the request data is forwarded to the same Telegram bot of the Controller (see section 1.4) for further processing. Repeated consent for any subsequent correspondence in the bot regarding this same request is not required: the consent given on the form covers such correspondence for the purposes stated in section 4.
3.1. The bot does not contain a form with mandatory fields: the Subject describes their situation in free text. Typically the conversation includes: a name (or however the Subject chooses to introduce themselves), contact details (a phone number and/or the Telegram account, which the Controller can already see technically as the message sender, and/or an email, if the Subject provides it themselves), and the content of the request (a description of the situation, niche, tasks, and questions for the Controller).
3.2. The Controller does not request or collect special categories of personal data through the bot (health, ethnicity, religious or political views, etc.) and asks the Subject not to share such information about themselves in the conversation without clear necessity.
3.3. Through the site form, a fixed, predetermined set of data is processed (name, phone number, email) corresponding to the form's fields. Unlike the conversation with the bot (section 3.1), where the Subject describes their situation in free text, the form does not request or store arbitrary comments or any data beyond these three fields.
4.1. Personal data shared in the conversation with the bot is processed for the purposes of: conducting a free review of the Subject's situation and responding to their request; consulting on the "Clients From Content" method and the Controller's related products/services; informing the Subject about the Controller's products, services, cohort openings, and terms of cooperation; and concluding and performing the agreement (public offer), if the Subject decides to make a payment as a result of the conversation.
4.2. The Controller does not process data for purposes beyond those in section 4.1 (for example, transferring it to third parties for advertising purposes).
5.1. Processing is carried out on the basis of the personal data subject's consent (Art. 6(1)(1), Art. 9 of 152-FZ), and, to the extent necessary for concluding and performing an agreement under the public offer, also on the basis of Art. 6(1)(5) of 152-FZ (processing necessary for the performance of an agreement to which the Subject is a party).
6.1. Consent remains in effect until it is withdrawn by the Subject (section 7) or until the purposes of processing stated in section 4 are achieved, whichever occurs first.
6.2. If the correspondence between the Controller and the Subject results in an agreement (payment for a Material under the public offer), then, with respect to the data necessary to perform this agreement, consent remains in effect for the entire term of its performance and additionally for the retention periods for documents established by Russian law (in particular, for accounting and tax purposes related to the self-employed activity).
7.1. The Subject may withdraw consent at any time by sending a notice of withdrawal to evskakunova777@yandex.ru or to Telegram @EvgeniaSkakunova (or to the same bot where the conversation took place), specifying exactly what is being withdrawn and a contact for a response.
7.2. Upon withdrawal of consent, the Controller stops processing and destroys (or ensures the destruction of) the relevant personal data within no more than 30 days of receiving the withdrawal, except where longer retention is required on another lawful basis (for example, to retain documents for a payment already made), Art. 21 of 152-FZ.
8.1. The Subject has the rights provided for in Art. 14 of 152-FZ: to obtain information about the processing of their data, to request its correction, blocking, or destruction in cases of incompleteness/inaccuracy/unlawful processing, to withdraw consent, and to appeal the Controller's actions to Roskomnadzor or to court. The full procedure for exercising these rights and the Controller's response timeframes are set out in section 7 of the Privacy Policy, which also applies to data covered by this Consent.
9.1. Correspondence takes place within the Telegram interface; the storage and technical protection of messages on the messenger's side is governed by Telegram's terms of use. The Controller restricts access to correspondence and does not transfer data to third parties for commercial purposes: see sections 8-9 of the Privacy Policy for details.
10.1. The Controller may amend the text of this document by publishing a new version on this page indicating the version date. Correspondence that has already taken place is governed by the version in effect at the time of the Subject's first contact with the bot, unless the Controller expressly states otherwise.
Controller: Evgenia Vladimirovna Skakunova
Status: payer of tax on professional income (self-employed)
Taxpayer ID (INN): 774395464289
Email: evskakunova777@yandex.ru
Telegram: @EvgeniaSkakunova
Version dated: 22.08.2026