ParentsTeachersBlog
Log inCreate account
LARNES · legalAll documents
  1. 01Company details and contacts
  2. 02Terms of use
  3. 03Personal data processing policy
  4. 04Personal data processing consent
  5. 05Child data processing consent
  6. 06B2B SaaS offer and data processing instructions
  7. 07Public offer
  8. 08Payments, cancellation, and refunds
  9. 09Cookies and analytics
  10. 10Marketing communications consent
  11. 11Child safety rules
←All documents

Legal documents

Child data processing consent

This is a separate legal-representative consent for processing a specific child's personal data in LARNES. It covers the family profile, learning activity, and selected connections, but does not permit advertising, public disclosure, photo or video recording, or health-data processing.

Status
Effective
Data controller
Индивидуальный предприниматель Бояркин Алексей Станиславович
Who gives consent
Parents, adoptive parents, guardians, trustees, and other representatives whose authority to act for the specific minor has been verified by the controller.
Contents
  1. 01Meaning of consent
  2. 02Controller, child, and representative
  3. 03Who participates in consent
  4. 04Child's age
  5. 05Family profile
  6. 06Learning and results
  7. 07Classroom, QR, and technical session
  8. 08Teachers, organisations, and other adults
  9. 09Representative data and authority verification
  10. 10Data operations
  11. 11Storage and technical processors
  12. 12What is excluded
  13. 13Period and adulthood
  14. 14Withdrawal and deletion
  15. 15Child and representative rights
  16. 16How consent is recorded
  17. 17Final terms
01

Meaning of consent

  1. The representative freely and in the child's interests permits the LARNES owner to process the listed data solely for the stated purposes.

  2. Consent is separate from the Terms, Privacy Policy, offer, and other confirmed documents under Article 9(1) of Federal Law No. 152-FZ.

  3. A separate consent is recorded for each child. Adding another child, purpose, or recipient category requires a separate representative action.

  4. Opening this page, creating an adult account, holding a family role, or using the site does not constitute child-data consent.

02

Controller, child, and representative

  1. The controller (оператор) is the platform owner whose name, individual-entrepreneur status, tax and registration numbers, address, and contacts appear on the Company details page.

  2. The data subject is the specific minor named in the consent form. The representative is an adult acting for and in the interests of that child.

  3. Where a school, network, or independent teacher uploads data as an independent controller, LARNES may act as a processor under their instructions. That controller determines its collection ground, family notice, retention, and request handling; this LARNES consent does not replace those duties.

03

Who participates in consent

  1. Before processing, the following rules apply:

    • for a child under 14, consent is given by a parent, adoptive parent, or appointed guardian;
    • from age 14 to 18, LARNES obtains the teenager's own consent for ordinary personal data and, where processing is connected to a transaction or another scenario requiring approval, separate approval from a parent, adoptive parent, or trustee;
    • an emancipated or married minor acts independently after full legal capacity is verified;
    • another representative only where applicable law and a verified instrument expressly permit that consent.
  2. Being a grandparent, other relative, invited family member, or adult account holder does not itself prove authority to consent.

  3. The controller must verify authority before processing using a minimally sufficient method: civil-status information, birth or adoption certificate, guardianship authority act, or another lawful source. A full document copy is not retained without a separate need.

  4. The representative confirms there is no established conflict of interest, restriction, or termination of authority and must report any change.

04

Child's age

  1. LARNES uses an adult family-account model: the child does not accept the Terms or receive an independent adult account.

  2. For a child aged 14 to 18, the interface must obtain the teenager's own action and any required adult approval separately. Neither replaces the other.

  3. At age 18, representative consent ceases to support new operations. Before continuing, LARNES obtains the adult user's own ground or deletes or anonymises data that is no longer needed.

05

Family profile

  1. The purpose is to create and maintain a non-public child profile in the family workspace, distinguish children in one family, and let the representative control selected relationships.

  2. This purpose covers:

    • first and last name and patronymic, if any;
    • date of birth and sex;
    • internal child, family, and linked-representative identifiers;
    • the selected card colour and catalogue character avatar;
    • profile creation, update, deletion, or hiding dates;
    • family relationships and granted or terminated access.
  3. Address, phone, email, passport, national insurance number, education documents, and a child photograph are not needed for the ordinary family profile and are not collected under this consent.

06

Learning and results

  1. The purpose is to assign and perform learning activity, show progress to the child and authorised adults, and maintain schedules, attendance, and outcomes.

  2. Processing may include:

    • directions, programmes, topics, lessons, assignments, and selected parameters;
    • homework assignment, current step, start and completion status;
    • learning-programme position, status, progress, start, completion, and finish dates;
    • schedule, group, teacher, organisation, enrolment, and enrolment status;
    • attendance, absences, and lesson grades;
    • internal links to an organisation's accrual, agreement, or payment record without the child's bank-card details.
  3. Task sequencing and progress display do not make legally significant decisions about the child's rights, admission to education, or medical condition.

07

Classroom, QR, and technical session

  1. The purpose is to open an assigned lesson safely on a family or classroom device without disclosing an adult password.

  2. Processing covers internal child, classroom, group, lesson, programme, device, and session identifiers; token hash, version and revocation status; session timestamps, device command, and lesson result.

  3. A child browser session normally lasts up to 12 hours. A classroom device may remain enrolled for up to one year or until unbound; learning outcomes follow the relevant learning-workspace retention period.

08

Teachers, organisations, and other adults

  1. Child data becomes available to a teacher, school, network, or another family member only after a separate role connection supported by the Platform.

  2. Before confirmation, the representative must see the recipient, connection purpose, accessible data categories, and revocation method. Access may be granted only within the displayed scope; processing consent is not automatic permission for every invited adult to see all information.

  3. A family role and legal-representative authority are different. An invited relative may receive only explicitly authorised access from a verified representative but gains no right to issue new consents for the child.

  4. If an organisation obtained child data before a family connection, it is responsible for its ground and data-subject notice. LARNES may begin processing such data only after documented processing instructions are in place.

09

Representative data and authority verification

  1. To link consent to the child, LARNES processes the representative's account ID, name, verified contact, asserted legal status, verification method and result, verification date, and authority status.

  2. Supporting-document details are collected only where necessary. A document image, passport data, and registered address are not added to the ordinary form automatically.

  3. Verification data is used only to prove representation, resolve an access dispute, and demonstrate consent lawfulness.

10

Data operations

  1. Permitted automated operations are collection, recording, organisation, accumulation, storage, correction, retrieval, use for stated functions, provision of strictly defined role access, blocking, anonymisation, deletion, and destruction.

  2. Manual processing is allowed for authority verification, family requests, support, incident review, or error correction.

  3. Disclosure to the public is not permitted. A new purpose, data category, or recipient category requires a new ground and, where applicable, new separate consent.

11

Storage and technical processors

  1. Before processing begins, the primary profile and learning records must be hosted in the LARNES database on the production infrastructure described in the Privacy Policy. Initial recording, organisation, accumulation, storage, and retrieval of Russian citizens' data must use a database located in the Russian Federation.

  2. The hosting and database provider receives access only under written processing instructions and only as needed for storage and maintenance. Its legal entity, address, country, and processing terms are stated in the Privacy Policy.

  3. SMS.ru, Resend, Cloudflare Turnstile, advertising integrations, and Telegram do not receive a child's profile, date of birth, assignments, answers, or results under this consent.

  4. No foreign service receives child personal data until necessity, country, and recipient are reviewed, Article 12 of Federal Law No. 152-FZ is satisfied, and the representative is separately informed.

12

What is excluded

  1. This consent does not permit:

    • marketing messages to the child or advertising targeting with child data;
    • non-essential advertising or third-party behaviour analytics;
    • public disclosure of name, photographs, video, audio, reviews, achievements, or results;
    • lesson photo or video recording or image or voice recognition;
    • health, diagnosis, disability, ethnicity, religion, or other special-category data;
    • biometric personal data;
    • transfer to undefined partners or cross-border transfer without a named country, recipient, purpose, and ground;
    • creation of an independent adult account for the child.
  2. Users must not enter such information into comments, answers, CRM, agreement templates, or free-text fields. If a future feature needs it, LARNES must first create a separate legal and technical framework.

13

Period and adulthood

  1. Consent applies from the recorded affirmative action until the earliest of withdrawal, end of representative authority, profile deletion, purpose termination, or the child reaching age 18.

  2. The ordinary family-workspace action archives the profile and allows restoration. Legal erasure starts through a separate /legal/data-request request after identity and authority are re-verified; only data supported by an independent ground and defined period remains.

  3. After purpose termination or withdrawal, data based only on consent is destroyed within 30 days. If destruction is technically impossible, it is blocked and destroyed within no more than six months.

  4. A limited consent, authority-verification, and withdrawal record is retained for three years after consent ends and, if disputed, until final resolution without continuing the withdrawn purpose.

14

Withdrawal and deletion

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

  2. The request must identify the representative, child, and consent. The controller re-verifies authority but does not request excessive passport data through unsecured email.

  3. Withdrawal ends family processing based on this consent. If a school or teacher is an independent controller, LARNES must identify the request channel and follow that controller's documented instruction; LARNES consent cannot override its lawful retention period.

  4. Ending one representative's access must not automatically erase the profile against another legal representative's valid consent or an education organisation's independent ground; disputed access is blocked during review.

15

Child and representative rights

  1. The child, considering age, and legal representative may obtain processing information and data access, request correction, blocking or destruction, withdraw consent, and complain to Roskomnadzor or a court.

  2. LARNES must explain processing to the child in age-appropriate language and consider the child's objection, especially from age 14, even where the legal action is taken by the representative.

  3. The general request process and response periods are in the Privacy Policy.

16

How consent is recorded

  1. Before the first child-profile save, the form must require legal-status selection, authority verification, review of data, purposes and recipients, a separate pre-unchecked box, and a create or confirm action.

  2. An invitation cannot create a new profile before consent. If an existing child is selected, the representative separately confirms the specific connection and access scope rather than issuing repeated blanket consent.

  3. For evidence, the controller must record the representative and child, legal status and authority-verification result, version, language and text hash, purposes, data and recipients, timestamp, scenario, affirmative action, IP address, session or device ID, status, and withdrawal.

  4. If authority verification and the consent record are not created, LARNES does not save a new profile or start processing on this consent.

  5. The representative must be able to view the accepted version, active or withdrawn consent, and current child-data access grants.

17

Final terms

  1. Consent applies together with the specific form naming the child and selected purposes. This public page without that action creates no consent.

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

Related documents
Company details and contacts↗Personal data processing policy↗Personal data processing consent↗