EN
Try it

Personal Data Processing Policy

Version of October 13, 2026.

1. General Provisions

This personal data processing policy has been drawn up in accordance with the requirements of Federal Law No. 152-FZ "On Personal Data" of July 27, 2006 and sets out the procedure for processing personal data and the measures for ensuring the security of personal data taken by Individual Entrepreneur Sofya Nikolaevna Efremova (TIN 241103602850).

The Operator considers the observance of human and civil rights and freedoms in the processing of personal data, including the protection of the rights to privacy and to personal and family secrets, to be its most important objective and a condition for carrying out its activities.

This Operator's policy on the processing of personal data (hereinafter, the "Policy") applies to all information that the Operator may obtain about visitors to the website https://app.cleverapp.pro, as well as about Users registered in the computer program "CleverApp", including when they use the AI Features (AI Chat, the "AI Agent" block in chatbots, the Knowledge Base), the Online Schools module and other services of the Operator.

This Policy also applies to the data of Students of online schools, Customers of shops, Mini App Users and Clients of appointment booking that Users process by means of the Program, subject to the specifics set out in Sections 8–11 of the Policy: with respect to such data, the Operator acts on the instruction of the User and does not determine the purposes of their processing.

2. Basic Terms Used in the Policy

Automated processing of personal data means the processing of personal data by means of computer equipment;

Blocking of personal data means the temporary suspension of the processing of personal data (except where processing is necessary to clarify the personal data);

Website means the set of graphic and informational materials, as well as computer programs and databases, ensuring their availability on the Internet at the network address https://app.cleverapp.pro;

Personal data information system means the set of personal data contained in databases and the information technologies and technical means ensuring their processing;

Depersonalization of personal data means actions as a result of which it is impossible, without the use of additional information, to determine whether personal data belong to a specific User or another personal data subject;

Processing of personal data means any action (operation) or set of actions (operations) performed with personal data with or without the use of automation tools, including collection, recording, systematization, accumulation, storage, clarification (updating, modification), retrieval, use, transfer (dissemination, provision, access), depersonalization, blocking, deletion and destruction of personal data;

Operator means a state body, municipal body, legal entity or individual that, independently or jointly with other persons, organizes and (or) carries out the processing of personal data and determines the purposes of processing personal data, the scope of personal data to be processed, and the actions (operations) performed with personal data;

Personal Data means any information relating directly or indirectly to an identified or identifiable User of the website https://app.cleverapp.pro;

User means any visitor to the website https://app.cleverapp.pro;

Online Schools module means the section of the Program that enables the User to create an online school, place courses, video lessons, tests and assignments in it, and grant Students access to them;

Online School (School) means a school created by the User by means of the Online Schools module, the portal of which is available on a subdomain of the Operator or on the User's own domain;

Student means an individual who has independently registered in the Student Portal of a particular Online School in order to take its courses. A Student is not a User and has no contractual relationship with the Operator: the Student's relationship arises with the User who owns the relevant Online School;

Student Portal means the interface of an Online School in which a Student studies, accesses course materials, submits assignments and communicates with the School's curators;

AI Features means the capabilities of the Program implemented using artificial intelligence technologies: the AI Chat, the "AI Agent" block in the User's chatbots, the Knowledge Base and auxiliary tools;

Model means a language or other generative artificial intelligence model of a third-party developer to which the Operator provides access as part of the AI Features;

Model Provider means a third party that operates a Model and (or) provides access to it, including one located outside the Russian Federation;

Provision of personal data means actions aimed at disclosing personal data to a specific person or a specific group of persons;

Dissemination of personal data means any actions aimed at disclosing personal data to an indefinite group of persons (transfer of personal data) or at making personal data available to an unlimited group of persons, including the publication of personal data in the mass media, posting in information and telecommunication networks, or providing access to personal data in any other way;

Cross-border transfer of personal data means the transfer of personal data to the territory of a foreign state: to an authority of a foreign state, a foreign individual or a foreign legal entity;

Destruction of personal data means any actions as a result of which personal data are irreversibly destroyed with no possibility of further restoring the content of the personal data in the personal data information system and (or) as a result of which the tangible media of personal data are destroyed.

3. The Operator May Process the Following Personal Data of the User

Last name, first name, patronymic;

Email address;

Telephone numbers;

Account data: login, a protected (hashed) representation of the password, interface language, information about connected sign-in methods;

Information on payments and services rendered: amounts, dates, transaction statuses, selected plans and connected paid services, and data required to issue settlement documents and cash receipts. Bank card data are not transferred to or stored by the Operator; they are processed by the payment service;

Technical data: IP address, information about the device and browser, date and time of requests, actions in the interface;

The content of requests to technical support and of correspondence with the Operator;

The content of prompts and responses when using the AI Features, as well as files and materials that the User uploads to the Program on their own, to the extent determined by the User;

The website also collects and processes depersonalized data about visitors (including cookies) by means of web analytics services (such as Yandex Metrica), where enabled on the website.

The above data are hereinafter in the Policy collectively referred to as Personal Data.

The Operator does not collect special categories of personal data (concerning racial or ethnic origin, political opinions, religious or philosophical beliefs, health, or intimate life) or biometric personal data, and asks Users not to place such data in the Program, including in conversations with Models and in the Knowledge Base.

4. Data Processed by the Operator on the Instruction of the User

When using the Program, the User may independently collect and process personal data of third parties: users of the User's chatbots, websites, forms and mailings, Students of the Online Schools the User has created, Customers of the Shops the User has created, Users of the mini apps the User has created, Clients and Specialists of the Appointment Booking module, as well as persons whose information the User places in the Knowledge Base and in conversations with Models. With respect to such data, the User is the operator: the User determines the purposes and scope of processing, and the Operator processes the data on the instruction of the User (Article 6 of Federal Law No. 152-FZ) to the extent necessary for the operation of the Program.

The User shall independently ensure that there are legal grounds for collecting such data, transferring them to the Operator and processing them further, including obtaining the consent of personal data subjects and submitting a notification to the authorized body for the protection of the rights of personal data subjects, and shall independently respond to requests from data subjects.

The Operator does not use the data of users of the User's chatbots for its own purposes, including marketing purposes.

5. Purposes of Processing Personal Data

The purposes of processing the User's personal data are: informing the User by sending emails; concluding, performing and terminating civil law contracts; providing the User with access to the services, information and/or materials contained on the website; providing technical support; calculating the cost of and accounting for services rendered, including the AI Features; ensuring the security of the Program and preventing abuse; and fulfilling the obligations imposed on the Operator by the legislation of the Russian Federation.

The Operator also has the right to send the User notifications about new products and services, special offers and various events. The User may at any time opt out of receiving informational messages by sending the Operator an email to info@cleverapp.pro marked "Opt-out of notifications about new products and services and special offers" or by using the unsubscribe link in the message itself.

Depersonalized data of Users collected by means of web analytics services are used to collect information about Users' actions on the website and to improve the quality of the website and its content.

6. Legal Grounds for Processing Personal Data

The Operator processes the User's personal data only if the User fills them in and/or submits them independently through special forms located on the website https://app.cleverapp.pro. The ground for such processing is the User's consent to the processing of personal data, which the User gives separately from this Policy and other documents by ticking a box in the form on the website. The text of the consent is available at https://app.cleverapp.pro/consent.

The legal grounds for processing also include: the License Agreement concluded with the User, available at https://app.cleverapp.pro/agreement; the fulfillment of obligations imposed on the Operator by the legislation of the Russian Federation; and the legitimate interests of the Operator in ensuring the security of the Program and protecting against abuse.

The Operator processes depersonalized data about the User if this is permitted in the settings of the User's browser (the storage of cookies and the use of JavaScript technology are enabled).

7. Processing of Data When Using the AI Features

The Program provides access to Models that are developed and operated by third parties. The Operator does not develop Models and does not perform the processing of prompts on its side.

When the AI Features are used, the Provider of the Model selected by the User receives what is necessary to generate a response: the text of the prompt, the content of the conversation, attached files and images, retrieved fragments of the Knowledge Base, and, when the "AI Agent" block is operating, the messages of the chatbot's correspondence with its user. Model Providers may be located outside the Russian Federation, and such a transfer is therefore cross-border (see Section 15 of the Policy).

The terms of further processing of the transferred data on the Model Provider's side are determined by the Model Provider's own rules. The Operator selects Providers whose terms correspond to the nature of the services rendered but does not control their infrastructure.

The Operator recommends that the User not transfer excessive personal data to Models, nor information access to which is restricted by law or by agreements with third parties.

The content of AI Chat conversations is stored in the User's account and is accessible only to the User and to persons to whom the User has granted access to the project. The Operator does not use the content of the User's conversations or the materials of the User's Knowledge Base to train Models and does not transfer them to third parties other than as specified in this Policy. Information on usage volume (model, number of tokens, cost, date) is stored for settlement purposes and is available to the User in the "Logs" section.

When tools for searching the Internet and retrieving the content of web pages are used, the corresponding query or link is transferred to an external search service or to the owner of the specified resource.

8. Processing of Personal Data of Online School Students

8.1. Roles of the parties. The Online Schools module enables the User to create an Online School, place courses in it and grant Students access to them. With respect to the personal data of Students, the operator is the User who owns the relevant Online School: the User determines the purposes and scope of processing, the content of the courses, the terms and price of access, and the manner of communication with Students. The Operator processes the personal data of Students solely on the instruction of the User (Article 6 of Federal Law No. 152-FZ) to the extent necessary for the functioning of the Program and does not determine the purposes of their processing. Section 4 of this Policy applies to such data in full.

The User shall independently determine and communicate to Students the terms of study and the User's own documents on the processing of personal data (offer, privacy policy, consent to the processing of personal data), the links to which the User specifies in the Student Portal settings, and shall independently ensure that there are legal grounds for processing, including obtaining the consent of Students and submitting a notification to the authorized body for the protection of the rights of personal data subjects.

8.2. Scope of the Student data processed. On the instruction of the User, the Operator processes: name (or other designation specified by the Student); email address; telephone number, if provided; a protected (hashed) representation of the password; profile image (avatar), if the Student has uploaded one; Portal language and time zone; information about access to courses, its terms and status; information about course orders and payments (amount, currency, status, date, payment identifier in the payment service); learning progress, test results, submitted work and files attached to it; correspondence with the School's curators and questions on lessons; information about issued certificates; technical data, namely IP address, date and time of requests, information about the device and browser, an irreversibly transformed (hashed) browser identifier, and information about active sessions; the identifier of the Student's messenger account, if the Student has voluntarily linked a messenger to the Portal.

8.3. Purposes of processing. Registering the Student and granting the Student access to the Portal; providing access to courses and learning materials; conducting the learning process, reviewing work and communicating with curators; issuing and verifying certificates; accounting for course orders and payments; sending service and learning notifications to the Student; protecting the School's learning materials against unauthorized copying and distribution; ensuring the security of the Portal and preventing abuse.

8.4. Protection of learning videos: email address overlay and key issuance log. Video lessons are stored in encrypted form, and the decryption key is issued to the Student's player for the duration of viewing. When a video lesson is played, an overlay with the Student's email address is displayed over the image; the Student sees this overlay at all times and is notified in the Portal interface that removing it is not permitted. Each issuance of a decryption key is recorded in a log that stores: the video identifier, the Student identifier, the IP address, an irreversibly transformed (hashed) browser identifier, and the date and time.

The sole purpose of such processing is to protect the exclusive rights to the School's learning materials and to detect cases of access being shared with third parties. The log is not used to monitor the Student or to assess the Student's personality: the content viewed, camera images, sound, geolocation, and information about other open programs and websites are not collected. A sharp divergence between the networks from which the key is requested may result in a temporary restriction on viewing.

8.5. Notifications. The Student receives at the email address the Student has provided service emails (address confirmation, password recovery, information about access to courses) and learning notifications (review of work, curators' replies, unlocking of lessons). The Student may opt out of learning notifications in the Portal profile; service emails necessary for the operation of the account and for security cannot be disabled.

8.6. Linking a messenger. The Student may, at the Student's discretion, link the Student's messenger account to the Portal in order to receive the School's notifications and open the Portal as a mini app. Linking is voluntary, is not required for study and may be cancelled by the Student at any time in the Portal profile. When linking and when notifications are sent, the Student's chat identifier and the text of the notification are transferred to the operator of the relevant messenger; the messenger operator processes these data under its own rules and may be located outside the Russian Federation (see Section 15 of the Policy).

8.7. Certificate verification. If the School issues certificates, the certificate verification page is accessible to anyone without authorization via a direct link (including a link from a QR code) and by certificate number. Such a page displays the Student's name, the name of the course and of the School, and the certificate number and date of issue. The public nature of the page is the purpose of the certificate: it allows third parties to verify its authenticity. A Student who does not wish such disclosure may request the School not to issue or to revoke the certificate.

8.8. School's access to data and exports. The User who owns the School and the curators appointed by the User have access to the data of their Students in the Program interface, including name, email address, profile image, progress, submitted work, correspondence and payment information, and may export summary reports, including in CSV format. From the moment of export, such data are processed by the User outside the Program, and the User bears responsibility for their further storage, use, transfer and destruction.

8.9. Payment for courses. Courses are sold to the Student by the School. Payment is made through a payment service connected by the User independently; the funds are received by the User. Bank card data are entered by the Student on the payment service's side and are not transferred to or stored by the Operator. On the instruction of the User, the Operator processes order information (amount, currency, status, date, payment identifier) to the extent necessary to open access to the course and to account for payments.

8.10. Retention periods and deletion. The Student's data are stored for the lifetime of the Student's account in the Portal. The Student may delete the account independently; within 30 (thirty) calendar days thereafter the account may be restored by signing in to the Portal, and upon expiry of that period the account and the data associated with it, including files uploaded by the Student, are irreversibly deleted. A Student account exists within a single School and does not provide access to other Schools.

The School's learning materials, including video recordings, are stored for as long as the User pays for the relevant plan of the Online Schools module. If payment ceases, the School's capabilities are restricted, and upon expiry of the period established by the License Agreement, the Operator may delete the materials and data of the unpaid School. Entries in the decryption key issuance log are stored no longer than necessary for the purpose specified in clause 8.4 and are deleted together with the corresponding video recording or the Student's account.

8.11. Requests from Students. A Student's requests concerning the processing of the Student's personal data, course content, payments and refunds are addressed to the School as the operator of such data, using the contact details specified in the Student Portal. Where necessary, the Operator provides the User with technical assistance in fulfilling them. If a request is received directly by the Operator, the Operator may forward it to the relevant User.

9. Processing of Personal Data of Shop Customers

9.1. Roles of the parties. The Shop module enables the User to place a product catalog and accept orders. With respect to the personal data of Customers, the operator is the User: the User determines the product range, the terms of sale and delivery, and the manner of interaction with Customers. The Operator processes Customer data solely on the instruction of the User, does not determine the purposes of their processing and does not use them for its own purposes, including marketing purposes.

The User shall independently determine and communicate to Customers the terms of sale and the User's own documents on the processing of personal data (offer, privacy policy and consent), and shall obtain the necessary consents. This Policy does not govern the relationship between the User and the User's Customers.

9.2. Scope of the Customer data processed. On the instruction of the User, the Operator processes: the name provided when placing the order; telephone number; email address; delivery address and order comment, if provided by the Customer; the contents, amount and status of the order; information about the selected delivery and payment method; the Customer's identifier in the chatbot or mini app through which the order was placed; the date and time of the order. Bank card data are not transferred to the Operator; they are processed by the payment service connected by the User.

9.3. Purposes of processing. Placing and storing the order; transmitting the order to the User; sending the Customer information about the order and its payment; maintaining the Customer's order history; generating sales analytics for the User.

9.4. User's access to data and exports. The User who owns the shop and the employees to whom the User has granted access see Customer data in the Program interface, including the customer list, orders and analytics, and may export them. From the moment of export, the data are processed by the User outside the Program; the User bears responsibility for their storage, use, transfer to third parties and destruction.

9.5. Payment for orders. Goods are sold to the Customer by the User. Payment is made through a payment service connected by the User independently; the funds are received by the User, bypassing the Operator. The Operator transfers to the payment service the information necessary to carry out the payment and issue the cash receipt, including the Customer's name, telephone number or email address and the contents of the order. The Operator is not the seller, the recipient of funds or a party to the settlements.

9.6. Retention periods and deletion. Customer data and orders are stored for as long as the User's shop exists. When the shop or the Project is deleted, the data are deleted together with it. Carts abandoned without placing an order are deleted automatically upon expiry of the period established by the Operator.

9.7. Requests from Customers. A Customer's requests concerning the processing of the Customer's personal data, the composition and quality of goods, payment, delivery and returns are addressed to the User as the operator and seller. The Operator may forward to the User any request from a Customer that it receives.

10. Processing of Personal Data of Mini App Users

10.1. Roles of the parties. The Mini Apps module enables the User to build a mini app from screens and logic blocks in the builder and to publish it. A published mini app opens at an address on a separate domain of the Operator intended for mini apps: in the Telegram and MAX messengers, in the bot's web chat on a website, in a browser, and it may also be installed on the home screen of a device. Individuals who open the User's mini apps (hereinafter, "Mini App Users") are not Users within the meaning of this Policy and have no contractual relationship with the Operator: their relationship arises with the User who owns the mini app. With respect to the personal data of Mini App Users, the operator is the User: the User determines the purpose and content of the mini app, the scope of the data requested, the logic of their processing and the persons to whom they are transferred. The Operator processes such data solely on the instruction of the User (Article 6 of Federal Law No. 152-FZ) to the extent necessary for the functioning of the Program, does not determine the purposes of their processing and does not use them for its own purposes, including marketing purposes. Section 4 of this Policy applies to such data in full.

The User shall independently communicate to Mini App Users the User's own documents on the processing of personal data (privacy policy, consent to the processing of personal data) and ensure that there are legal grounds for processing, including obtaining the consent of Mini App Users, including to the use of cookies and of services connected by the User's code, and submitting a notification to the authorized body for the protection of the rights of personal data subjects. This Policy does not govern the relationship between the User and Mini App Users.

10.2. Scope of the data processed. On the instruction of the User, the Operator processes the account information of a Mini App User: the platform through which the mini app is opened (messenger, web chat, browser or app installed on the home screen); the identifier in the messenger or, when opened in a browser without a messenger, a random guest account key; name, username and language; mini app variables, namely values entered in screen fields and forms, results of the operation of logic blocks and values written by the User's code; tags; information about the link to a contact of the User's chatbot; the date of the last visit. Data submitted through mini app forms are written to the lists of the User's project and processed in accordance with Section 4 of the Policy. If orders or appointment bookings are placed in the mini app, Sections 9 and 11 of the Policy also apply to the relevant data.

10.3. Data sources. Data are received: from the Mini App User themselves, when filling in screen fields and forms; from the messenger operator, which, when the mini app is launched in the messenger, transfers data signed by the messenger: identifier, name, username, language and launch parameter; from a contact of the User's chatbot, if the mini app is opened from a bot linked to it (clause 10.5 of the Policy); from the User's code and the mini app's logic blocks, including from responses of services to whose addresses HTTP requests are sent (clause 10.8 of the Policy); from the User and the User's employees, when they change tags and variables in the Program interface.

10.4. Purposes of processing. Launching the mini app and maintaining the Mini App User's session; displaying screens and executing the logic set by the User; saving entered values and transferring form data to the lists of the User's project; interacting with a contact of the User's chatbot, including sending messages on behalf of the bot; placing orders and appointment bookings, if such capabilities are used in the mini app; providing the User with depersonalized statistics and an error log of the mini app; ensuring the security of the Program and preventing abuse.

10.5. Link to a chatbot contact. If the mini app is opened from the User's chatbot to which it is linked, the Mini App User's account is linked to the contact of that chatbot. In this case, the contact's fields, variables and tags become available to the mini app, and the mini app may send messages to the contact on behalf of the bot and change the contact's tags. Chatbot contact data are processed in accordance with Section 4 of the Policy.

10.6. Storage of data on the device. The mini app stores on the Mini App User's device a session token and mini app data in the browser's local storage (localStorage) and, when installed on the home screen, also a service worker and a cache of the mini app shell that allow it to be opened without a network connection. The Operator does not set its own cookies in mini apps. The Mini App User may delete such data using the browser or device tools (by clearing site data or uninstalling the installed app); in doing so, the session saved on the device may be lost.

10.7. User's code and external scripts. The User may place the User's own program code in the mini app: the "JavaScript" block, the "HTML Code" element and screen, and app code executed when the mini app is launched. Such code is executed on the Mini App User's device (the "HTML Code" element and screen in an isolated frame) and may, in particular, read and write variables, read the data and tags of the linked chatbot contact, open links, request the device's geolocation (only with the permission of the Mini App User requested by the browser or messenger), use messenger capabilities, connect external scripts (analytics counters, widgets) and transfer data to third parties directly, bypassing the Operator. The Operator does not review or moderate the User's code. The Program saves values passed by code only for the variables and tags permitted by the User in the mini app settings; the "JavaScript" block may write any mini app variables.

The Operator does not receive or process data that the User's code and the external scripts connected by the User transfer directly to third parties. The User bears responsibility for such transfer, for cookies and other technologies used by the code and external scripts, and for obtaining the necessary consents of Mini App Users. If violations or a security threat are detected, the Operator may disable the code or unpublish the mini app in the manner established by the License Agreement.

10.8. HTTP requests. The "HTTP Request" block sends requests to addresses specified by the User, either from the Operator's server or from the Mini App User's device. The scope of the data transferred and their recipients are determined by the User; the Operator executes such requests on the instruction of the User and does not determine their content. Recipients process the data received under their own rules and are not persons acting on the instruction of the Operator; the User bears responsibility for the existence of legal grounds for such transfer, including cross-border transfer. The Program does not execute requests to local and internal network addresses.

10.9. Transfer of data to messenger operators. When messages are sent on behalf of the User's chatbot, including from a mini app, the recipient's identifier in the messenger and the text of the message are transferred to the operator of the relevant messenger (in particular, Telegram, MAX). The messenger operator processes these data under its own rules and may be located outside the Russian Federation (see Section 15 of the Policy).

10.10. Error log and statistics. To diagnose the operation of the mini app, the Program keeps an error log that stores the Mini App User's identifier and the error text, for HTTP requests the address, status code and a fragment of the server response, and for the User's code the call stack. A fragment of the server response may contain personal data if they were returned by a service chosen by the User. Mini app statistics are kept in the form of depersonalized counters (opens, screens, events).

10.11. User's access to data. The User who owns the mini app and the employees to whom the User has granted access see in the Program interface the accounts of Mini App Users, their variables and tags, the error log and statistics, and may change tags and variables. Data that the User obtains from the mini app outside the Program (including via HTTP requests and code) are processed by the User independently, and the User bears responsibility for them.

10.12. Templates. The User may save a mini app as a template. A template contains the screens, blocks, texts, images and code of the mini app but does not contain data of Mini App Users. A User's own template is visible only to the User who saved it; only the Operator may make a template publicly available, after review. When a template is installed, a copy of the mini app is created for the installing party. The User is responsible for ensuring that the texts and images of a saved template do not contain personal data of third parties without a lawful basis.

10.13. Retention periods and deletion. Guest accounts created when the mini app is opened in a browser without a messenger are deleted automatically after 90 (ninety) calendar days without visits. Error log entries are stored for 14 (fourteen) calendar days and deleted automatically. Other data of Mini App Users are stored for as long as the mini app exists, unless the User deletes them earlier, but no longer than the term of the License Agreement with the User; when the mini app or the Project is deleted, such data are subject to deletion together with it. Data saved on the Mini App User's device are stored until they are deleted using the browser or device tools (clause 10.6 of the Policy). Data contained in backup copies are destroyed in the course of the scheduled rotation of such copies.

10.14. Requests from Mini App Users. A Mini App User's requests concerning the processing of the Mini App User's personal data, the content and operation of the mini app, the User's code and the external services connected by the User are addressed to the User who owns the mini app as the operator of such data. Where necessary, the Operator provides the User with technical assistance in fulfilling them. If a request is received directly by the Operator, the Operator may forward it to the relevant User.

11. Processing of Personal Data of Appointment Booking Clients

11.1. Roles of the parties. The Appointment Booking module enables the User to create branches, a service catalog, profiles of the specialists who provide services (hereinafter, "Specialists"), work schedules and booking rules, to accept bookings from individuals for the User's services (hereinafter, "Clients") through chatbots, mini apps and other channels of the Program, and to enter bookings manually in the booking log. Clients have no contractual relationship with the Operator. Services are provided to Clients by the User; the Operator is not the provider of the services. With respect to the personal data of Clients and Specialists, the operator is the User: the User determines the list of services, the booking terms and the manner of interaction with Clients. The Operator processes such data solely on the instruction of the User (Article 6 of Federal Law No. 152-FZ) to the extent necessary for the functioning of the Program, does not determine the purposes of their processing and does not use them for its own purposes, including marketing purposes. Section 4 of this Policy applies to such data in full.

The User shall independently communicate to Clients the terms of service and the User's own documents on the processing of personal data, obtain the necessary consents of Clients and submit a notification to the authorized body for the protection of the rights of personal data subjects. The User shall also ensure that there are legal grounds for processing the data of Specialists, including the Specialist's consent to the processing of personal data permitted for dissemination, if information about the Specialist and the Specialist's image are available to Clients. This Policy does not govern the relationship between the User and the User's Clients and Specialists.

11.2. Scope of the Client data processed. On the instruction of the User, the Operator processes: the Client's name, telephone number and email address; the Client's comment on the booking; the User's internal note about the Client and the booking, which is not visible to the Client; information about the Client's link to a chatbot contact and to a Mini App User account; booking history and counters of visits, no-shows and cancellations, the date of the last visit; booking information, namely the branch, selected services, Specialist, date and time, status, amount and currency, booking source, reason for cancellation, and a mark confirming the visit in response to a reminder; the booking change history (who made which changes); the Client's reviews (clause 11.8 of the Policy).

11.3. Data of Specialists. On the instruction of the User, the Operator processes the information about Specialists that the User places: name, position, description, photo, work schedule and exceptions to it, as well as information about the Specialist's link to the account of an employee to whom the User has granted access to the Project, if such a link has been established. A Specialist's average rating is calculated from Clients' ratings. A Specialist's name, position, description, photo and rating may be displayed to Clients when booking.

11.4. Data sources. Client data are received from the Client themselves, when booking through a chatbot, mini app or other channel of the Program, when responding to a reminder and when submitting a review; from the chatbot contact and the Mini App User account through which the booking was made; from the User and the User's employees, when creating bookings manually, changing bookings and entering internal notes. Specialist data are entered by the User.

11.5. Purposes of processing. Booking the Client for services and maintaining the booking log; finding available time taking into account work schedules and booking rules; sending the Client booking confirmations and reminders and, after the visit, a request for a review; maintaining the Client's booking history and recording visits, no-shows and cancellations; collecting reviews and calculating Specialists' ratings; providing the User with information about bookings, Clients and reviews in the Program interface.

11.6. Notifications. Booking confirmations and reminders, as well as a request for a review after the visit, are sent to the Client on schedule through the User's chatbot in a messenger. In doing so, the Client's identifier in the messenger and the text of the notification containing booking information are transferred to the operator of the relevant messenger (in particular, Telegram, MAX); the messenger operator processes these data under its own rules and may be located outside the Russian Federation (see Section 15 of the Policy). The Client's response to a reminder is saved in the booking.

11.7. Calendar file. The Client may be provided with a link to a calendar file (.ics format) containing the booking data: services, date and time, the branch and its address and telephone number, the Specialist's name, and the booking number. The link is signed and valid for a limited period; during this period the file is accessible without authorization to anyone who has the link, so the Client should not share it with third parties. The Client may also be provided with a link for adding the booking to Google Calendar: when following it, the booking information is transferred to Google at the Client's own action and is processed by Google under its own rules.

11.8. Reviews and rating. A Client's review consists of a rating and a comment, is linked to the booking and the Specialist, and is taken into account when calculating the Specialist's average rating. Leaving a review is voluntary. The User may hide a review.

11.9. Special categories of personal data. The Appointment Booking module is not intended for processing special categories of personal data, including health information, and the Program does not provide special protection measures for them. The User must not request or collect such data through comments, internal notes or other booking fields unless the User has a lawful basis for processing them (Article 10 of Federal Law No. 152-FZ); the User bears responsibility for the processing of such data.

11.10. User's access to data and exports. The User and the employees to whom the User has granted access see Client data, bookings, their change history and reviews in the Program interface. If the Program provides the ability to export reports and other information containing personal data, from the moment of export such data are processed by the User outside the Program; the User bears responsibility for their storage, use, transfer to third parties and destruction.

11.11. Payment for services. If the Program provides the ability to prepay bookings, settlements are made through payment services connected by the User under the User's agreements with them, in a manner similar to that provided for in clause 9.5 of the Policy; bank card data are not transferred to the Operator. The Operator is not the provider of the services, the recipient of funds or a party to the settlements.

11.12. Retention periods and deletion. Bookings, their change history, notifications and reviews are stored for as long as the relevant branch of the User exists; Specialist data, for as long as the branch exists and the User has not deleted the Specialist's profile; information about Clients, for as long as the User's Project exists. Such data are stored no longer than the term of the License Agreement with the User; when the branch or the Project is deleted, they are subject to deletion together with it. Data contained in backup copies are destroyed in the course of the scheduled rotation of such copies.

11.13. Requests from Clients and Specialists. A Client's requests concerning the processing of the Client's personal data, the booking, and the provision, quality and payment of services, as well as a Specialist's requests concerning the information posted about the Specialist, are addressed to the User as the operator of such data and the provider of the services. Where necessary, the Operator provides the User with technical assistance in fulfilling them. If a request is received directly by the Operator, the Operator may forward it to the relevant User.

12. Cookies and Analytics Services

The Operator uses cookies and similar technologies to: ensure the operation of the User's authorization and session, save user settings, protect against unauthorized actions, and collect traffic statistics.

Statistics are collected using third-party web analytics services (such as Yandex Metrica), where enabled on the website. They may set their own cookies and process depersonalized information about visits in accordance with their own rules.

The User may disable or delete cookies in the browser settings. If strictly necessary cookies are disabled, certain capabilities of the Program, including authorization, may become unavailable.

For details on the cookies used, see the Cookie Policy.

13. Transfer of Personal Data to Third Parties

The Operator does not sell personal data and does not transfer them to third parties for their own purposes. Transfer is carried out only to the extent necessary to provide the services and only to the following categories of recipients:

Model Providers and other providers of artificial intelligence services, to the extent specified in Section 7 of the Policy;

payment services and banks, for carrying out settlements, issuing cash receipts and complying with legal requirements, including when orders are paid for in Users' Shops (clause 9.5 of the Policy);

operators of messengers and social networks, when transmitting messages of the User's chatbots, including messages sent from mini apps and notifications to appointment booking Clients (clauses 10.9 and 11.6 of the Policy), and when sending notifications to Online School Students who have voluntarily linked their messenger account (clause 8.6 of the Policy);

infrastructure providers (server hosting, data storage, delivery of email and SMS), to the extent necessary for the functioning of the Program;

web analytics services, with respect to depersonalized data;

authorized state bodies, in the cases and in the manner provided for by the legislation of the Russian Federation.

Persons processing personal data on the instruction of the Operator (including infrastructure providers) are obliged to maintain the confidentiality of the data processed and comply with security requirements for them. Payment services and banks, messenger and social network operators, Model Providers and web analytics services process the data received under their own rules and in accordance with the law; authorized state bodies, in accordance with the law.

The recipients of data sent by the "HTTP Request" block of mini apps, as well as external services connected by the User's code, are determined by the User. Such recipients are not persons acting on the instruction of the Operator; the Operator does not receive the data that the User's code transfers to them directly from the Mini App User's device (clauses 10.7 and 10.8 of the Policy).

14. Procedure for Collection, Storage, Transfer and Other Types of Processing of Personal Data

The security of personal data processed by the Operator is ensured through the implementation of legal, organizational and technical measures necessary to fully comply with the requirements of current legislation in the field of personal data protection.

The Operator ensures the safety of personal data and takes all possible measures to prevent access to personal data by unauthorized persons.

The recording, systematization, accumulation, storage, clarification and retrieval of personal data of citizens of the Russian Federation are carried out using databases located in the territory of the Russian Federation.

If inaccuracies in personal data are identified, the User may update them independently by sending the Operator a notification to the Operator's email address info@cleverapp.pro marked "Updating personal data".

Personal data are processed until the purposes of their processing specified in Section 5 of this Policy are achieved and are stored for the lifetime of the User's account. After the account is deleted or the purposes of processing are achieved, personal data are destroyed or depersonalized within a period not exceeding 30 (thirty) calendar days, except for data that the Operator is required to retain by law (including accounting and tax records), which are retained until the expiry of the retention periods established by law. Data contained in backup copies are destroyed in the course of the scheduled rotation of such copies.

The retention periods and deletion procedure for the data of Online School Students and for the learning materials of Online Schools are determined by clause 8.10 of this Policy, for the data of shop Customers by clause 9.6, for the data of Mini App Users by clause 10.13, and for the data of appointment booking Clients and Specialists by clause 11.12 of this Policy.

The User may at any time withdraw consent to the processing of personal data by sending the Operator a notification by email to the Operator's email address info@cleverapp.pro marked "Withdrawal of consent to the processing of personal data". Withdrawal of consent makes further use of the Program impossible; processing of data carried out on other lawful grounds (including for compliance with legal requirements) continues within the limits of the relevant ground.

15. Cross-Border Transfer of Personal Data

The Operator carries out cross-border transfer of personal data, including when using the AI Features and infrastructure services located outside the Russian Federation, and when sending messages via messengers.

Cross-border transfer is carried out in compliance with the requirements of Article 12 of Federal Law No. 152-FZ, including sending the authorized body for the protection of the rights of personal data subjects a notification of the intention to carry out cross-border transfer before it begins.

Before cross-border transfer begins, the Operator assesses whether the foreign recipients maintain the confidentiality and ensure the security of personal data. Transfer to states that do not ensure adequate protection of the rights of personal data subjects is carried out subject to the restrictions established by Article 12 of Federal Law No. 152-FZ and by decisions of the authorized body.

16. Rights of the Personal Data Subject

The User has the right to: receive the information concerning the processing of the User's personal data provided for by Part 7 of Article 14 of Federal Law No. 152-FZ; demand the clarification, blocking or destruction of the User's personal data if they are incomplete, outdated, inaccurate, unlawfully obtained or not necessary for the stated purpose of processing; withdraw consent to the processing of personal data; appeal against the actions or inaction of the Operator to the authorized body for the protection of the rights of personal data subjects or in court.

To exercise these rights, the User sends a request to the email address info@cleverapp.pro. The Operator considers the request and responds within the time limits established by Federal Law No. 152-FZ. The Operator may request additional information necessary to identify the person making the request.

Requests concerning data processed by the Operator on the instruction of the User (Section 4 of the Policy), including requests from Online School Students (clause 8.11 of the Policy), shop Customers (clause 9.7 of the Policy), Mini App Users (clause 10.14 of the Policy), and appointment booking Clients and Specialists (clause 11.13 of the Policy), are addressed to the relevant User as the operator of such data; where necessary, the Operator provides the User with technical assistance.

17. Protection Measures and Incident Response

The Operator applies organizational and technical protection measures, including: encryption of traffic, differentiation of employees' access rights, storage of passwords in irreversibly transformed form, maintenance of access logs, backup, and monitoring of infrastructure security.

Upon establishing the fact of an unlawful or accidental transfer of personal data that has resulted in a violation of the rights of data subjects, the Operator notifies the authorized body for the protection of the rights of personal data subjects of the incident within 24 hours and of the results of the internal investigation within 72 hours, and takes measures to eliminate the consequences of the incident.

18. Final Provisions

The User may obtain any clarification on matters of interest concerning the processing of the User's personal data by contacting the Operator by email at info@cleverapp.pro.

Any changes to the Operator's personal data processing policy will be reflected in this document. The Policy is valid indefinitely until it is replaced by a new version.

The current version of the Policy is freely available on the Internet at https://app.cleverapp.pro/privacy.

This English version of the Policy is a translation provided for convenience. In case of any discrepancy, the Russian version of this document prevails.