Academy CanLup · Legal information
Personal data policy
Edition dated 10 November 2026 · 2026.11.10-D
1. Operator and scope
Personal data operator: Alla Antonovna Batsa (Баца Алла Антоновна). Russian taxpayer identification number: 890603453994. A self-employed professional income tax payer, without individual entrepreneur status, in the Russian Federation. Personal data enquiries: batsaaleksey@gmail.com. The operator’s address is plot 963, SNT Pishchevik, Khutor Kutok, Anapsky District, Russian Federation.
This policy covers academy.canlup.com, academyproinvest.com, Academy accounts and the features used. The service is intended for adults in Russia. The policy provides information. It does not itself constitute consent. Access requests have a separate consent document.
2. Data processed
People concerned include site visitors, applicants, buyers, account users, customer representatives, invited participants and people contacting support. Sources are the individual, their device and service activity, and authorised customers for invitations and corporate materials. Data obtained from someone else requires a lawful basis and any information to the individual required by law.
Processing may be automated, non-automated or mixed, depending on the function and legal basis. Authorised people are involved where necessary for the relevant task or compliance with law. Operations include collection, recording, organisation, accumulation, storage, correction, retrieval, use, authorised access, blocking, deletion and destruction within the relevant purpose.
- Requests: email, selected use case and industry. In the extended form, full name, job title, organisation, team size, needs, optional contact and comment. The consent edition, timestamp and request status are recorded.
- Accounts: name, email, profile image and settings, identifiers, roles and sessions. Password verification uses cryptographic hashes. Passkeys use public keys and technical records. Device biometrics are not received.
- Selected features: uploaded materials, messages, support enquiries, assignments and results, personal notes, AI requests, supplied context and outputs. Other people’s data requires appropriate authority and a lawful basis.
- Technical records: IP address or protective derivatives, request time, browser/device details, authentication, error and security events.
For a paid order the operator processes the buyer’s email, recipient of access, plan or package, order number, amount, date and status of payment, refund or allocation, payment identifier and receipt details. An organisation’s or individual entrepreneur’s taxpayer ID is also used for its receipt. Sources are the buyer, the order record and confirmation from YooKassa. Do not enter full card details or authentication codes in Academy support forms.
3. Purposes and legal bases
- Applicants: email, the selected form details and confirmation records are used to review the request, verify contact details and send access-related service emails. The basis is separate consent under Article 6(1)(1) of Federal Law No. 152-FZ. Processing lasts until review of the application and related service messages are completed or consent is withdrawn, whichever occurs first. Data are deleted or anonymised when no longer necessary for the stated purpose, except records retained on a separate lawful basis.
- Account users: profile and authentication details, selected materials and outputs support the requested account, features and related support. Basis: entering into a contract at the individual’s initiative and performing it under Article 6(1)(5). Retention follows the requested functions and the end of the relevant basis.
- Corporate participants: work contacts, roles, materials and results support the functions instructed by the customer, within the agreed scope and period. The customer establishes the basis for participant data. Provider obligations follow Article 6(3) and the specific instructions. Company membership does not itself expose personal account materials to a manager.
- Visitors and users: necessary network, session and technical records support authentication, service protection, error investigation and abuse prevention. Bases: necessary contractual activity and legitimate interests respecting individual rights under Article 6(1)(5) and (7). Retention is limited to the relevant protection or diagnostic purpose.
- Advertising and public dissemination are outside access-request consent. Advertising requires separate prior consent. Personal data dissemination requires its own basis and separate consent where Article 10.1 requires it. A closed workspace does not make a person’s materials public.
Order data is needed to provide paid access, reconcile transactions and handle contractual refunds (Article 6(1)(5) of Law No. 152-FZ). Necessary business contacts of a corporate representative are used in the parties’ legitimate interest in fulfilling the order while respecting the representative’s rights (point 7). Receipt and tax records are processed to comply with Law No. 422-FZ (point 2). The seller provides YooKassa with the details needed to identify the order and settle the payment. Receipt information goes to the Federal Tax Service. The bank and payment service discharge their own applicable duties in processing the payment.
For enquiries only information needed for a reply is used. Statutory data subject requests are handled under point 2 and contractual support for a user under point 5. Relevant evidence for a specific dispute may be retained under point 7 while respecting individual rights. For data received from a third party for independent purposes the operator provides the information required by Article 18(3) of Law No. 152-FZ before processing begins, subject to the exceptions in Article 18(4).
4. Retention and deletion
An application is processed until its review and related service messages are completed or consent is withdrawn, whichever occurs first. Completion is determined by the review outcome or the end of necessary application-related interaction. A closed application is not used to continue communication without a separate lawful basis. Access-granting records may subsequently be retained on an independent account-related basis.
Account and feature data is kept while needed to provide them. Enquiries are kept until answered and the matter is closed. Technical records are kept for diagnosis or investigation of the relevant event. Mandatory records and evidence for a substantiated dispute are retained under the applicable basis. Losing company access does not automatically delete a personal account.
Completion of the purpose or withdrawal requires processing to stop and data to be destroyed within no more than 30 days unless the law permits continued processing. A demand to cease processing has a separate deadline: no more than 10 working days, with a reasoned extension of up to 5 working days where permitted. The general request-retention period does not replace these deadlines.
Backups are included in deletion handling. If destruction within the required period is impossible, Article 21(6) requires blocking followed by destruction within no more than six months unless federal law provides otherwise. Restoration must not resume processing without a lawful basis. Destruction is documented as required.
You can request account deletion by email. Closing the account ends processing of the profile and materials for personal access. Evidence of consent is kept separately only to the extent and for the time necessary to demonstrate lawful processing. Records of a specific dispute are retained as necessary until resolution and enforcement. Tax records and documents needed to calculate and pay tax are kept for five years unless the Russian Tax Code provides otherwise (Article 23(1)(8)). Processors receive corresponding instructions to stop processing and destroy data.
5. Cookies and device storage
Essential cookies, local storage and cache support sign-in, request protection, account selection and settings. Removing them may end a session or reset settings. It does not delete server-side account data.
Optional analytics and advertising tracking are not covered by request consent. Optional analytics is enabled only after the visitor gives separate consent. Reading legal pages also sends ordinary network information to the server.
Public marketing pages use Yandex Metrica counter 114113069 only with the visitor’s separate permission. The technical data recipient is YANDEX LLC, 16 Lev Tolstoy Street, Moscow, Russia. Its purpose is to measure visits and interest in examples, demonstrations and pricing, and improve the website. Metrica may process IP addresses, cookies and browser identifiers, device and browser details, public page URLs and titles, timestamps and fixed interaction events. The basis is the visitor’s separate consent. The counter does not load without it.
Session replay, form recording and click maps are disabled. Academy does not include names, email addresses, form entries, lesson or message contents, files, account identifiers, URL queries or fragments in event parameters. Permission can be withdrawn through Analytics settings in the website footer, stopping subsequent collection. Contact the operator regarding data already processed. Analytics is not required to browse, sign in or request access.
6. Access, technical services and location
Academy processes and stores personal data in the Russian Federation. The main database, files, logs and service backups are located in Russia. Providers for AI, message delivery, hosting and other functions are selected according to their terms for processing and storing data in Russia, protection and permitted use. Engagement depends on satisfying these requirements and having the necessary legal bases. Cross-border transfers of personal data are not provided for.
An email delivery processor receives the recipient address and message text to send a code or service email. Hosting and storage cover only data placed in the relevant system. Section 5 describes the analytics recipient and choices. Section 3 describes the payment participants. Before entrusting processing to another person, the operator specifies the purpose, data and operations, checks access terms and processing and storage locations, puts binding instructions in place and obtains the individual’s consent unless federal law provides otherwise. The operator remains responsible to the individual for the processor’s actions.
AI use is voluntary. Before the first transfer within a particular function, the user receives information about the processor, the request and additional context, whether requests and results are retained and for how long. The current terms are available within the relevant function and may apply to subsequent requests within the user’s valid choice. Where changes require fresh consent or permission, it is obtained before a new transfer. Terms may differ for text, image creation and image editing. Materials are not transferred without the required permission. The user selects materials and verifies their rights to provide them. Neither that choice nor application consent replaces a lawful basis for processing other people’s data. Materials are not provided for the processor’s independent model training as part of such a request.
You can obtain information about recipients, the name and address of a processor handling your data, and the duration and conditions of processing as described in section 7.
7. Rights, contact and protection
For access to processing information, correction, withdrawal or cessation, email batsaaleksey@gmail.com with the account/request email and the issue. Sign-in is not required. Do not send passwords or one-time codes. Proportionate verification of authority may be requested.
The operator provides processing information or a reasoned refusal within ten working days of a request. Where permitted by law, this period may be extended by up to five working days with a reasoned notice. Inaccuracies are corrected within seven working days of receipt of supporting evidence. Unlawful processing is stopped within three working days of detection. If lawful processing cannot be ensured, the data are destroyed within ten working days of detection. Disputed data are blocked during a review of unlawful processing. During a review of inaccuracy they are blocked if doing so does not infringe the rights or legitimate interests of the individual or third parties. If you establish that data was obtained unlawfully or is unnecessary for the stated purpose, the operator destroys it within seven working days after supporting evidence is provided (Article 20(3) of Law No. 152-FZ).
Withdrawal does not end processing with an independent lawful basis. The response explains that basis and the necessary scope of retention. Users may contact Roskomnadzor or a court. A service enquiry does not require agreement to advertising or a purchase.
Access controls, session checks, encrypted connections and abuse prevention support protection. Ordinary service forms should not be used for special categories of personal data or biometric identification data.
For incidents covered by Article 21(3.1) of Russian Federal Law No. 152-FZ, the operator notifies Roskomnadzor within 24 hours of discovery and reports the internal investigation results within 72 hours.
You may ask whether your data is processed and obtain information about your own data in an accessible form, including its source, purposes, bases, methods, duration, recipients and how to exercise your rights. You may request blocking, correction or destruction of incomplete, outdated, inaccurate, unlawfully obtained data or data not needed for the stated purpose. Information is provided free of charge while respecting others’ rights. If a formal request requires details and a signature under Article 14(3) of Law No. 152-FZ, the operator will explain how to provide them securely. The operator informs you of action taken and takes reasonable steps to notify recipients of corrected or destroyed data.
Repeated requests for information under Article 14(7) of Law No. 152-FZ and access to the data are handled under Article 14(4)–(6). Following a complete response, the statutory general interval is 30 days unless applicable rules or the contract provide a shorter period. An earlier repeated request is considered where the law provides, including an incomplete previous response. A reasoned refusal requires a lawful ground. These rules apply to those repeated information requests, rather than to all enquiries, consent withdrawals or requests to correct violations.
8. Updates and additional features
The edition and date are shown on this page. Updates do not retroactively change consent. New purposes require any necessary separate consent. File, microphone, screen and desktop-action permissions are handled in the relevant feature.