Personal data processing consent

The user freely, by their own will and in their own interest, permits the LARNES owner to process the additional data listed below solely for the stated purpose.

This consent is separate from the Terms, Privacy Policy, and other documents as required by Article 9(1) of Federal Law No. 152-FZ.

Refusal does not prevent creation or use of the core account. A field covered by this consent cannot be mandatory for registration or a core function.

The controller is the platform owner whose name, individual-entrepreneur status, tax and registration numbers, address, and contacts appear on the Company details page.

The subject is a user who has confirmed that they are at least 18 and accepted consent in an authenticated account or during registration after phone or email verification.

This consent does not allow the user to authorise another adult's or a child's data. Child data requires separate legal-representative consent.

The purpose is voluntary creation and maintenance of an adult user's extended profile in non-public LARNES interfaces: completion, display, editing, distinguishing users with the same name, and support requested by the profile owner.

Before consent, the specific form must state the purpose of each requested field and the categories of LARNES users who can access it. A field without a defined purpose and recipients is not collected.

The data is not used for advertising, scoring, teacher search, a public profile, a legally significant automated decision, or advertising-model training.

Consent may cover only fields actually shown to the user:

• patronymic, if the user wishes to add it;
• the adult user's date of birth;
• city of residence;

The consent screen must list only fields entered in that scenario. Hidden categories, “other data”, or expanding the list without renewed consent are not permitted.

If date of birth, city, or patronymic is objectively needed for a mandatory function and has an independent contractual ground, it is removed from this consent and the need is explained before entry.

This consent does not cover:

• name, primary contact, account type, login, password hash, session, and other data needed to enter into and perform the Terms;
• IP address, login events, device ID, and other security data processed on an independent legal ground;
• child data or legal-representative authority data;
• marketing messages or advertising and non-essential analytics cookies;
• public profile disclosure, photographs, reviews, or achievements;
• special-category or biometric personal data;
• client, student, and staff data entered by a school or teacher into a work workspace.

Withdrawal does not end processing needed for an agreement, security, or law. Those grounds and periods are described in the Privacy Policy.

Permitted automated operations are collection, recording, organisation, accumulation, storage, correction, retrieval, use for private-profile display, role-based access for the user and authorised support, blocking, deletion, and destruction.

Manual processing is allowed only to perform a user request, review an incident, or correct an error.

The controller may not change the purpose, add data categories, or add recipients based on an existing checkbox. A new optional purpose requires new separate consent.

Additional profile data is stored in the primary LARNES database on the production infrastructure described in the Privacy Policy. Access is limited to the account holder and specific roles named in the consent form; support receives access only at the user's request or for a documented incident.

The hosting and database provider may access data only for technical maintenance under written processing instructions. Its full legal name, address, country, and processing terms are stated in the Privacy Policy.

SMS.ru, Resend, Cloudflare Turnstile, Mux, advertising integrations, and Telegram do not receive patronymic, date of birth, or city under this consent. Mapbox place search runs when autocomplete is used on other grounds — contract, registration, or processing instruction; the selected place is stored in the profile or center record.

Additional profile data is not transferred cross-border under this consent. Any future transfer requires a separate legal-ground review, notification, and new user information.

Consent applies from the recorded affirmative action until the earliest of withdrawal, deletion of covered fields, account closure, or purpose termination.

After purpose termination or withdrawal, data based only on this consent is destroyed within 30 days unless another legal ground applies.

A limited consent and withdrawal record is retained for three years after consent ends and, if disputed, until final resolution as evidence of the legal action. It is not used to continue the withdrawn purpose.

The user may withdraw through the provided profile control or send a request to the personal-data email or postal address on the Company details page.

The request must identify the user and specific consent. Excessive passport data should not be sent before instructions for secure identity verification.

Processing based only on consent ends and the data is destroyed within 30 days after withdrawal unless another legal ground applies. If destruction is technically impossible, the data is blocked and destroyed within no more than six months.

Optional fields remain empty or are cleared. The core account, login, and role functions continue where data processed under an agreement or law is sufficient.

If a separately requested feature objectively cannot work without a particular additional field, LARNES explains that dependency before consent. Refusal disables only that feature, not the whole workspace.

Consent is expressed through a separate, pre-unchecked box with clear text and a link to this version, followed by a save or continue action.

Silence, site use, page opening, Terms acceptance, or one box for several independent purposes is not consent.

Before collection, the controller must record the user, version and language, selected fields, purpose and recipients, timestamp, scenario, affirmative action, IP address, session or device ID, and outcome. If no such record is created, consent is not obtained and the optional fields are not processed.

The user must be able to view the accepted version and active or withdrawn consent status.

The user may obtain processing information and data access, request correction, blocking or destruction, withdraw consent, and complain to Roskomnadzor or a court.

Request procedures, response periods, and general security measures are described in the Privacy Policy.

Consent applies only together with the form listing specific voluntary fields. Merely publishing this page does not mean a visitor has consented.

If Russian and English versions differ for relations governed by Russian law, the Russian version prevails.