Website version · Русская версия

Personal Data Processing Policy of the «My ChuvSU» Platform

Effective from 8 October 2026. A single document for the web portal online.chuvsu.ru and the «My ChuvSU» mobile application (Android / iOS / RuStore).

Contents

  1. General Provisions
  2. Principles and Legal Grounds
  3. Data Subjects and Information Sources
  4. Purposes and Scope of Primary Processing
  5. Voluntary Analytics and Personal Notifications
  6. Obtaining and Withdrawal of Consent
  7. Special Categories of Data and Access to Device Functions
  8. Data Recipients and Territorial Conditions
  9. Specifics of Technical Support and Artificial Intelligence
  10. Retention Periods and Termination of Processing
  11. User Rights and Request Procedure
  12. Protection Measures and Changes to this Policy

This English version is provided for informational purposes only. In case of any discrepancy between the English and the Russian versions, the Russian version prevails.

1. General Provisions

1.1. This Policy defines the purposes, legal grounds, scope and conditions of personal data processing when using the web portal https://online.chuvsu.ru and the «My ChuvSU» mobile application for Android and iOS, including interaction with the University information systems and the technical support line. Hereinafter, the said portal and application are jointly referred to as the Platform.

1.2. The personal data Operator is the Federal State Budgetary Educational Institution of Higher Education «I.N. Ulianov Chuvash State University» (hereinafter also – the University, the Operator). Operator address: 15 Moskovsky Prospekt, Cheboksary, Chuvash Republic, 428015, Russian Federation. Email address for personal data processing and technical support matters: online@chuvsu.ru. A request may also be sent to the Operator postal address, indicating that it concerns personal data on the Platform.

1.3. This Policy specifies data processing on the Platform and applies together with the general personal data policy of the University published in the Documents section of the official website at https://www.chuvsu.ru/sveden/document/. The specifics of the support line at https://bitrix.chuvsu.ru are also set out in a separate policy of that line, available from its interface. These documents may neither expand the legal grounds for processing established by law nor restrict the rights of personal data subjects.

1.4. This Policy does not automatically extend to all University websites or to websites of third-party organisations linked from the Platform. Processing in the underlying educational and HR systems, in application stores and in third-party services used on their own is governed by the documents applicable to them. The receipt and transfer of data between the Platform and such systems is described by this Policy in the part concerning Platform operations.

1.5. Reviewing this Policy, signing in to an account, installing the application and continued use of the Platform do not by themselves constitute consent to personal data processing. Where consent is required, the University obtains it separately in accordance with section 6. The Policy is a document on data processing and does not replace consent.

2. Principles and Legal Grounds

2.1. Personal data means any information relating to an individual who is identified or identifiable, directly or indirectly. A technical identifier, a notification delivery token, information about a device or a usage event may constitute personal data if they make it possible to identify the user directly or indirectly or to associate the information with that person.

2.2. Processing includes collection, recording, systematisation, accumulation, storage, updating (clarification), retrieval, use, transfer in the form of provision of or access to data, de-identification, blocking, deletion and destruction. For each purpose, only the operations necessary for that purpose are allowed. Processing is performed by means of automation tools; when handling requests and preparing documents, processing without such tools is also possible.

2.3. The University observes the principles of lawfulness and fairness, of limiting processing to specific pre-defined purposes, of the proportionality of the data scope to those purposes, of accuracy and of limiting retention periods. Obtaining consent does not exempt the University from observing these principles. Combining information processed for incompatible purposes is not allowed.

2.4. The principal act governing processing is Federal Law No. 152-FZ of 27 July 2006 "On Personal Data". Depending on the specific purpose, Federal Law No. 273-FZ of 29 December 2012 "On Education in the Russian Federation", labour legislation, archival legislation, the terms of contracts with data subjects and other applicable norms also apply.

2.5. Independent legal grounds for processing are defined by Article 6 of Federal Law No. 152-FZ. Point 2 of part 1 applies to the performance of duties established by law; point 5 of part 1 applies to the necessary performance of a contract with the data subject or of a contract under which the data subject is a beneficiary; point 7 of part 1 applies to the protection of legitimate rights and interests while observing the rights and freedoms of the data subject. For voluntary operations indicated in this Policy, consent under point 1 of part 1 applies. The existence of educational or employment relations does not by itself create a legal ground for any additional analytics or data transfer.

2.6. Encryption, name replacement or removal of individual attributes do not by themselves mean that data have been de-identified. The University takes into account the possibility of identifying a user from the combination of remaining identifiers, events, timing of actions, device information and other available data. Processing exclusively for statistical or other research purposes on the basis of point 9 of part 1 of Article 6 requires mandatory de-identification.

3. Data Subjects and Information Sources

3.1. The Platform may process data of visitors to the web portal, users of the application, students and employees of the University, persons contacting support, their representatives and other persons whose information has been lawfully included in requests or documents.

3.2. Data are received from the users themselves or their authorised representatives, from the corporate single sign-on system «ChuvSU Key», from the University educational and HR systems, and also automatically during interaction with the Platform within the scope of the selected functions and the applicable legal grounds for processing.

3.3. Sources of educational information include systems for tracking academic performance, personal accounts and portfolio, timetables, the education portal, certificate requests and research achievements. Displaying information on the Platform does not change its primary source. The University ensures that erroneous data are corrected in the appropriate system and that related copies are updated.

3.4. When receiving information from a party other than the data subject, the University performs its information duties towards the data subject provided for by Article 18 of Federal Law No. 152-FZ, except for the exceptions established by that Article. Warning the user to provide only information relevant to the matter does not exempt the University from its own obligations regarding the processing of the data received.

4. Purposes and Scope of Primary Processing

4.1. Provision of access and account management. For users with an account, the following are processed: surname, first name, patronymic (if any), email address and its confirmation status, portal identifier, account and session identifiers, and status and role information necessary for granting access. A contact telephone number is used where it is required for the selected function. The legal grounds are the performance of applicable educational or employment duties and of contractual relations to the extent necessary for access. The data are processed until the relevant access is terminated or the need for the account ceases; subsequent retention is allowed only on an independent legal ground under section 10.

4.2. Provision of educational information and interaction with the University. For students and employees, within the scope of their respective roles, the following are processed: grade book number and other study identifiers as necessary, faculty, academic group and subgroup, year of study, form and level of study, field and profile of the programme, duration and status of studies, and information on timetables, learning results, attendance, assignments, academic debts and retakes. Where the relevant function is provided, information about the study contract and the status of settlements under it is processed. For employees, information about the department, position, academic degree and title may be processed. Date of birth, sex, library card identifier and additional profile details are used only in the functions for which they are necessary. The legal grounds are educational or employment duties provided for by law and the necessary performance of the applicable contract. Processing on the Platform continues for as long as the relevant function is provided; retention periods for primary documents are determined by law and applicable archival rules.

4.3. Consideration of applications and issuance of certificates. The following are processed: the applicant's identification and contact details, the type and content of the application, the study information required, the status and history of its consideration, and attached documents. The scope of mandatory information is determined by the requirements of the specific procedure. The legal ground is the performance of the University's duties or the performance of the applicable contract; additional voluntary information not covered by these grounds requires a separate legal ground for processing. The period is determined by the completion of the procedure and the retention period established for the relevant document. Technical copies do not automatically receive the same retention period as archival originals.

4.4. Portfolio maintenance and recording of research achievements. The following may be processed: information about the author and their affiliation with the University, achievements, participation in research events, research works, dates and supporting documents. Mandatory record-keeping is based on applicable rules on educational activity and the relevant contract. Additional voluntary publication of information is carried out on the basis of consent. The processing period is determined by the period of portfolio maintenance or of the recording of the relevant achievement and, for processing based on consent, also by its validity. Publication of information to an unrestricted circle of persons is governed by clause 7.3.

4.5. Consideration of technical requests. To register a request, diagnose the problem and prepare a reply, the following are processed: account information necessary to match the request with the user, contact details, the text and history of the correspondence, attachments, the technical context of the problem and records of its consideration. The legal ground is the need to perform the applicable contract or a duty established by law; for requests and additional operations not covered by these grounds, consent is used. Processing for the purpose of resolving the matter ends after the request has been considered and the necessary actions have been taken. Further retention is allowed under the rules of section 10. Additional processing by an external artificial intelligence service is governed by section 9.

4.6. Ensuring security and operability. For all users, to the necessary extent, the following are processed: network address, information about the browser or application and the operating system, session and request identifiers, time of the request, and signs of technical errors and abuse. The legal grounds are compliance with data protection requirements and the protection of the legitimate rights and interests of the University and users while observing their rights and freedoms. Technical logs are retained for no more than 90 calendar days from the moment of recording, except for information related to a specific incident under investigation, the further retention of which has a separate legal ground.

4.7. Automatic recording of technical errors. When errors occur in the mobile application, technical data are collected automatically from all users, regardless of whether consent to voluntary analytics has been given or withdrawn. Purpose of processing: identifying the causes of errors, fixing them and ensuring the operability of the application. The following are transmitted to the University's error recording system: the exception description, the sequence of technical actions without the content of user input, the application version, device and operating system information, and technical request metadata. Only information necessary for diagnostics is collected; passwords and authorisation tokens are excluded. The processing is based on point 7 of part 1 of Article 6 of Federal Law No. 152-FZ, where necessary for the exercise of the legitimate rights and interests of the University and users and in observance of the rights and freedoms of data subjects. Reports are retained for no more than 90 calendar days from the moment of collection; further retention of a specific report is allowed only on an independent legal ground. User requests are handled under clause 4.5. Collection of crash information by means of voluntary analytics requires consent under section 5.

4.8. Optional functions chosen by the user. To save settings, upload a profile picture, add timetable entries to the calendar, configure reminders and use the Credential Vault, information necessary for the selected action is processed. The legal ground is the necessary performance of the applicable agreement on the function or, where no other ground exists, separate consent. The picture and settings are retained until they are deleted, changed or the relevant profile is no longer used. Logins and passwords of other University systems are stored only under separate express consent and are used exclusively for the interaction with those systems selected by the user. They are deleted at the user's request, upon withdrawal of consent or when the need for the vault ceases.

5. Voluntary Analytics and Personal Notifications

5.1. Web portal analytics is used to study attendance, interface usability and the detection of technical problems. For these purposes, Yandex Metrica and the Mail traffic measurement service may be used. On the basis of separate consent, technical information about the browser and device, identifiers, information about visited pages and interaction events are transmitted. Passwords, the content of requests and documents, grades and other information from educational systems must not be included in analytics events, page addresses or request parameters.

5.2. The mobile application uses AppMetrica and Firebase Analytics. Voluntary analytics is intended for studying the user experience of interaction with the interface, detecting failures and difficulties, and the technical analysis of a problem when the user contacts support. Linking the analytics history to a specific request must be disclosed to the user and covered by their consent. Refusal of such analytics does not limit the core educational functions of the Platform or the ability to contact support.

5.3. The scope of data transmitted to AppMetrica may include the following categories within the specific purposes of the consent:

a) profile information: name, sex, user portal identifier, academic group;

b) usage information: interaction events in the application, time of the last launch, information about sessions, notification openings and failures, and the state of the notification permission;

c) technical identifiers: the AppMetrica device identifier and the technical profile identifier; the Firebase Cloud Messaging token is transmitted for the purpose of personal notifications if the user has separately selected that function;

d) approximate location information: country, region, city. Such information may be derived from network and technical data and differs from the precise coordinates of the device;

e) software and device information: application version, name and version of the operating system, manufacturer, model and type of device, interface language, screen resolution, and an indication of whether extended system permissions are present on the device.

5.4. The portal identifier and academic group are used to match a technical problem with the account and the interfaces and data related to it. The name is used for the personal form of address in a notification selected by the user. The transmission of sex, approximate location and other additional attributes is allowed only where there is a specific research or diagnostics task for which this information is necessary and which is disclosed in the consent. Fields not needed for the selected task are not transmitted. The stated purposes do not require the collection of precise device coordinates.

5.5. The name, portal identifier and academic group make the AppMetrica profile attributable to a specific user. Such information and the related event history are processed as personal data. The absence of a surname and patronymic does not mean that the profile has been de-identified.

5.6. For Firebase Analytics, this Policy establishes the permissible data scope: application instance identifier, usage events and their technical parameters, session time and duration, information about the application version, device, operating system, language, and the approximate country, region and city. The transmission of additional user parameters beyond this scope is not allowed without a prior change to the disclosed terms and obtaining the necessary consent. The use of Firebase Analytics is also subject to the limitations of section 8, including the requirements concerning initial data collection.

5.7. Personal notifications about the correction of an interface problem reported by the user constitute a separate purpose of processing. For this purpose, the following are used: the identifier of the user or of the related request, information about the problem and the result of its correction, the selected notification channel and the technical delivery token. The name is used only for a personal form of address in the message text, if the user has selected such an address. Obtaining the name is not a necessary condition for the technical delivery of the notification.

5.8. The University obtains separate consent for personal notifications about corrections and for the transmission of data to the delivery provider necessary for sending them. The user may decline analytics while keeping the selected notifications, and may decline such notifications while keeping consent to analytics. Consent to analytics purposes is not automatically consent to personal notifications, advertising or the processing of messages by an external model.

5.9. Analytics information is not used by the University for advertising, for the assessment of academic performance, for attendance control, for disciplinary measures or for decisions on the rights and obligations of the user. For the purposes of the Platform, the inclusion of advertising tracking, the collection of advertising identifiers and the transfer of data to advertising partners are not allowed. Any independent use by the provider of genuinely de-identified aggregated results is disclosed in the applicable terms of the provider and does not give the University a ground to transmit excessive personal data.

5.10. Raw analytics events and related technical exports are retained for no more than 12 months from the moment of the event and, in any event, no longer than required for the stated purpose and permitted by the applicable legal ground for processing. The personalised analytics profile is used during the validity of the relevant consent and while access to the Platform continues. After 12 months without activity, processing of the profile ends and the data are subject to destruction, unless another independent legal ground exists for a specific operation. Withdrawal of consent entails the consequences provided for by clauses 6.6 and 10.4.

6.1. Consent is executed separately from this Policy, the terms of use and other documents confirmed by the user. Before consent is given, the user receives information about the Operator, the specific purposes, the data scope, the actions performed with the data, the recipients, the period or conditions for ending processing and the method of withdrawal. For external services, their name, role and the terms applicable to the operation are disclosed, including the envisaged cross-border transfer.

6.2. For consent that the law allows to be obtained in electronic form without a mandatory written form, a separate active user action is used after the terms have been presented. A pre-set tick mark, absence of action or closing of a notification is not deemed consent. The University keeps evidence of the receipt of consent and of its content. Where a written form is mandatory, the requirements of part 4 of Article 9 of Federal Law No. 152-FZ apply.

6.3. A separate expression of will is required for voluntary analytics, personal notifications about corrections, password storage and the processing of a request by an external artificial intelligence service. Consent must make it possible to identify each purpose it covers. If a single form covers several purposes, the choice must allow the user to accept or decline independent voluntary operations.

6.4. Until the necessary consent has been obtained, voluntary collection and transmission of data to external analytics services are not carried out. On the web portal, the user is provided with actions to consent, decline and change the choice. In the application, the corresponding choice is available when the function is enabled and in the settings. Browser settings and blocking tools may be used in addition and do not replace obtaining consent from the Operator.

6.5. The user may withdraw consent through the settings provided for the relevant function or by writing to online@chuvsu.ru. The withdrawal relates to a specific purpose or operation and does not end processing for which another independent legal ground remains. The University explains which data continue to be processed and for what purpose if this is necessary to reply to the user's request.

6.6. After consent to analytics has been withdrawn, new analytics operations for which no other legal ground exists end. The sending of a previously accumulated queue of events within the withdrawn consent also ends. Personal data related to this purpose, including the profile, events and exports, are subject to the end of processing and destruction within the periods established by law, unless another independent ground remains.

6.7. Erasing the name, sex, academic group and portal identifier while retaining the technical profile identifier and events does not by itself confirm destruction or de-identification. Retaining statistical results after the end of personal data processing is allowed where de-identification has been verified, excluding the identification of the user without additional information, and subject to the applicable requirements. If additional information available to the Operator or the recipient makes it possible to restore the link to the user, the question of further processing is decided taking this possibility into account. The absence of a convenient deletion tool at the provider does not remove the University's obligation to ensure that the user's rights are observed.

6.8. An operating system or browser permission to show notifications or to access the camera, images or the calendar is a technical permission. It does not replace consent to the processing or transfer of personal data where such consent is required by law. Declining one permission must not automatically mean refusal of or consent to other purposes of processing.

7. Special Categories of Data and Access to Device Functions

7.1. The Platform is not intended for the arbitrary collection of information about health, racial or ethnic origin, political views, religious or philosophical beliefs or intimate life. Where such information is necessary for a specific lawful procedure, the purpose, scope and special legal ground for processing under Article 10 of Federal Law No. 152-FZ are determined before it is obtained. Consent to ordinary analytics or sending a message does not replace the required special legal ground.

7.2. A profile picture constitutes personal data if it relates to an identified user. Its processing as biometric personal data is determined by its use for identity establishment under Article 11 of Federal Law No. 152-FZ. On the Platform, the picture is used to display the profile; processing of images for biometric identity establishment without a separate legal ground provided for by law is not allowed.

7.3. Employee access to user information within official powers does not constitute publication to an unrestricted circle of persons. Public dissemination of voluntarily posted personal data requires an independent legal ground and, where consent is used, it is executed separately in compliance with Article 10.1 of Federal Law No. 152-FZ. A user uploading a file to a closed personal account does not mean consent to its public dissemination.

7.4. The camera and access to selected images are used upon a user action to upload a picture or read a code provided for by the function. Calendar access is used to add timetable entries selected by the user. Permissions for reminders and alarms are used for the selected notifications. For these functions, access is limited to the necessary information; the contents of the calendar and address book must not be transmitted to analytics or to an external artificial intelligence model. Any separate expansion of the scope of collected information requires prior disclosure of the terms and of a legal ground.

7.5. Passwords, confirmation codes, payment details and information about oneself or other persons not relevant to the matter should not be included in technical requests. Upon receiving excessive or unlawfully processed information, the University restricts access and applies the measures of updating, blocking or destruction provided for by law. The user's voluntary inclusion of information does not exempt the Operator from these obligations.

7.6. Data of minors are processed taking into account their age, legal capacity, the nature of the legal relationship and the applicable requirements of law. Where the consent of a legal representative is necessary, the University obtains it and verifies the representative's authority. Processing necessary by force of law for educational relations and consent to voluntary analytics are treated separately. Reaching the age of 14 is not established by this Policy as a universal ground for independent consent to any operations.

8. Data Recipients and Territorial Conditions

8.1. Access to data within the University is granted to employees who need it to perform their official duties. Exchange between the single sign-on systems, educational systems, image processing, error recording and support is treated as processing by a single Operator where these systems are indeed operated by the University and no separate legal entity participates in the processing. The use of a software product does not by itself mean the transfer of data to its developer.

8.2. The following external services may be used as part of the Platform functions within the purposes and legal grounds disclosed to the user:

a) YANDEX LLC: AppMetrica for application analytics and the selected personal notifications, Yandex Metrica for web analytics, Yandex SmartCaptcha for form protection, and corporate email for message delivery. The scope transmitted is limited to the relevant function. For email delivery, this is the recipient's address and the content of the message, which may also contain personal data;

b) VK LLC: the Mail traffic measurement service and the loading of materials from official communities. When an embedded item is loaded, the third-party service may receive the network address, information about the browser, the page of the request and related technical identifiers. The absence of sign-in via a social network does not guarantee that no data are processed by that network;

c) Google LLC and the persons related to the selected service specified in the applicable contractual terms: Firebase Analytics, Firebase Cloud Messaging, Firebase Installations and Google reCAPTCHA. Depending on the function, analytics information, installation identifiers, delivery tokens and the content of a notification or the technical data of the protected form check are transmitted. The conditions for admitting these operations are determined by this section and the relevant separate consent;

d) RuStore LLC: delivery of notifications via RuStore Push using a technical token and the content of the notification;

e) Apple Inc. and the persons providing the Apple Push Notification service under the applicable terms: delivery of notifications to iOS devices, including the delivery of Firebase Cloud Messaging messages through this service. Delivery technical details and the content of the notification are transmitted;

f) TIMEWEB.CLOUD LLC: processing of requests to the selected artificial intelligence model for technical support in accordance with section 9.

8.3. A specific service is used only for a function selected by the user or for an operation that has another applicable legal ground. Before consent is obtained, the recipient legal entity, the transmitted information, its role and the processing terms are disclosed. The University ensures that the settings, contracts and routes used correspond to the stated purposes. Access by additional recipients or the inclusion of new purposes is not allowed on the basis of a general mention of a category of providers alone.

8.4. Entrusting processing to another party is executed in accordance with part 3 of Article 6 of Federal Law No. 152-FZ, with the consent of the data subject unless otherwise provided by federal law. The entrustment defines the data, operations, purposes, confidentiality, protection measures, localisation requirements, provision of supporting documents and the procedure for reporting incidents. In the relations governed by the agreement at https://yandex.ru/legal/dpa_appmetrica/, when processing the data of application users, Yandex acts on behalf of the University under an entrustment. The University is liable to the data subject for such processing to the extent provided by law.

8.5. If a recipient is an independent operator, it must have its own legal ground for processing. Its policy does not replace the legal ground for the transfer by the University. The user is entitled to receive from the University information about the persons having access to their data and about their role, including the name and address of the party entrusted with processing.

8.6. When collecting personal data of citizens of the Russian Federation, the University must comply with part 5 of Article 18 of Federal Law No. 152-FZ. Recording, systematisation, accumulation, storage, updating and retrieval of such data using databases outside the Russian Federation at the time of collection are not allowed, except for exceptions directly established by law. Consent already obtained, a Russian copy of the database or the existence of a foreign privacy policy do not remove this requirement.

8.7. The use of a foreign service, including Firebase Analytics, is not allowed until the lawfulness of the specific route of initial collection and subsequent processing has been confirmed. The cross-border transfer procedure does not substitute for compliance with the collection requirements. If these conditions cannot be ensured, the relevant operation with personal data through such a service is not carried out.

8.8. Before starting a cross-border transfer, the University performs the requirements of Article 12 of Federal Law No. 152-FZ: it obtains the necessary information from the foreign recipient, carries out the prescribed assessment, sends a separate notification to the authorised body and observes the applicable restrictions and deadlines for the start of the transfer. In determining the admissibility of the transfer, the current list of foreign states ensuring adequate protection of data subject rights is taken into account. Consent does not replace these actions.

8.9. Before the relevant operation begins, the user receives information about the specific foreign recipients and states of transfer, its purposes, data scope and legal ground. The wording "Europe" or a reference to the provider's rules alone does not replace the disclosure of specific states. Where the transfer is prohibited or restricted, the University complies with the decision of the authorised body and the requirements provided by law regarding previously transferred data.

8.10. A change of provider, of the scope of transmitted information, of the country or of the purpose of processing is assessed by the University in advance. Where necessary, notifications, contractual terms, public information and consents are updated. Transfer to public authorities is allowed in the manner established by law and to the necessary extent.

9. Specifics of Technical Support and Artificial Intelligence

9.1. When contacting the support line, the information listed in clause 4.5 is received into the University system at https://bitrix.chuvsu.ru. Requests are considered by employees; a chat bot may be used for automated consultations selected by the user. For contact without the use of an external model, the address online@chuvsu.ru is available.

9.2. The current route for preparing replies uses the timeweb/gpt-oss-120b model through the Timeweb Cloud AI Gateway service of TIMEWEB.CLOUD LLC. The separate support policy states that requests to this model are processed on infrastructure in the Russian Federation, with reference to the provider's written response. This information relates to this route and does not mean that there is no cross-border transfer in other components of the Platform.

9.3. The request to the model may include the message text, up to 20 history messages from the last two hours, selected technical information, system instructions and permitted knowledge base materials. The technical context limits the set of fields: error code, notification text, application screen, platform, operating system and application versions, network and its configuration details, and launch attempt information. The name and identifiers of the user or dialogue are not included as separate fields.

9.4. Free text and correspondence history do not become de-identified as a result of limiting the technical fields. If the user has included identifying information in the message, it may be part of the transmitted request. This circumstance is disclosed to the user before the transfer. Additional processing of the request by an external model is carried out on the basis of separate consent and duly executed terms with the provider; the absence of legal grounds excludes such a transfer.

9.5. The University does not allow the transmission to the model of passwords, access tokens and other secrets not necessary for the request. Processing of special categories of data is allowed only if there is a corresponding legal ground and the prescribed protection measures. Automatic checking of the outgoing reply and employee supervision do not replace control over the lawfulness and scope of the incoming request.

9.6. The limitation of the transmitted history to two hours and 20 messages is a rule for forming the model context and does not establish a deletion period for the correspondence, logs, review materials and backups. The periods and terms of processing by the provider, deletion and any possible use of requests for training must be determined before personal data are transferred to it. If such terms are not defined to the extent necessary for lawful processing, the transfer is not carried out.

9.7. Chat bot replies are technical consultations. They are not used for making solely automated decisions about grades, enrolment, expulsion, tuition payment or other rights and obligations of the user. A transfer of data that has already taken place is not cancelled by connecting an employee or replacing the model. Issues of previous processing routes and previously transferred data are considered separately in observance of the rights of data subjects.

10. Retention Periods and Termination of Processing

10.1. For each purpose, the periods and conditions for ending processing specified in sections 4 and 5 apply. Where specific documents must be retained by law, their period is determined by the relevant provision, the type of document and the approved records nomenclature. A reference to a document formatting standard does not establish a retention period for data. Archival retention is not a ground for keeping all technical copies, analytics profiles and identifiers.

10.2. Temporary copies of educational data made to speed up the operation of the Platform are retained for no more than 24 hours from the moment the specific copy is created. Repeated retrieval of up-to-date data is allowed for as long as there is a lawful need to provide the function. Using a backup copy when the source is unavailable must not mislead the user about the currency of the information. Deleting such a copy does not destroy the lawfully retained primary information in the educational system.

10.3. Delivery tokens and subscription settings are processed for the duration of the relevant subscription and while the token remains valid. If the user declines the relevant category of notifications, their sending ends. Data for a separate notification about a problem correction are processed until such a notification is sent, the user declines it or the need for the notification ends. Retaining the token for other selected notifications is allowed on an independent legal ground.

10.4. Upon achievement of the purpose or withdrawal of consent, where no independent ground for further processing exists, the University ends processing and ensures the destruction of the data within a period not exceeding 30 calendar days in the cases provided for by parts 4 and 5 of Article 21 of Federal Law No. 152-FZ. This rule extends to data held by the Operator and by parties acting on its behalf. Lawfully produced de-identified statistical results may be used subject to clause 6.7.

10.5. Materials of official requests and applications are retained in accordance with the applicable records management and archival retention rules. Technical correspondence and additional copies, after the matter has been resolved, are subject to the end of processing and destruction under clause 10.4 unless another independent ground exists. Information necessary for a specific dispute or investigation is separated out and used only for that purpose; the possibility of a future dispute does not by itself justify the indefinite retention of all data.

10.6. Evidence of consents and of their withdrawal is retained to the necessary extent to confirm the lawfulness of processing and to protect rights on an independent legal ground. Confirmation of destruction is executed in accordance with the applicable requirements of the authorised body. The destruction act and the required log export are retained for three years from the moment of destruction in accordance with Order of Roskomnadzor No. 179 of 28 October 2022.

10.7. Backup copies and exports are taken into account when processing ends. Data subject to destruction are excluded from ordinary use; restoration must not resume processing that has lost its legal ground. The existence of a backup copy or provider specifics do not create an independent retention ground. If destruction within the established period is objectively impossible, blocking is applied and destruction takes place no later than six months under part 6 of Article 21 of Federal Law No. 152-FZ, unless another period is established by federal law. This possibility is not a general retention period for backup copies.

10.8. Deleting a Platform account does not mean the automatic destruction of all University documents. The University ends the processing of service information that is no longer needed and explains which documents continue to be retained by force of law or on another independent ground. Withdrawal of consent to voluntary functions does not end educational or employment relations.

11. User Rights and Request Procedure

11.1. The user is entitled to receive confirmation of processing and information about its purposes, legal grounds, methods, data scope and sources, retention periods, the Operator, the recipients, the parties acting on the Operator's behalf and their addresses, any completed or envisaged cross-border transfer, and the ways in which the Operator performs its statutory duties. The user is entitled to access free of charge the processed data relating to that person.

11.2. The user is entitled to demand the updating of incomplete, inaccurate or outdated data, the blocking or destruction of unlawfully obtained data or data not necessary for the stated purpose, to withdraw consent and to demand the end of processing in the cases provided for by law. Limitations of the right of access are allowed only by federal law.

11.3. Requests are sent to online@chuvsu.ru or to the address indicated in clause 1.2. For an access request under Article 14 of Federal Law No. 152-FZ, the user must indicate the number of the main identity document, the date of its issue and the issuing authority, information confirming the relationship with the Operator or the fact of data processing, and the signature of the data subject or representative. An electronic document is signed with an electronic signature in the manner established by law. Where a representative applies, their authority is verified.

11.4. A full copy of the passport is not required for an ordinary question, for withdrawal of consent through the provided settings or for clarifying the request procedure. The University requests only the information necessary for the relevant type of request and for verifying authority, and uses it exclusively for that purpose. If a request requires clarification or proper formalisation, the University informs the user and explains how to submit it.

11.5. Information about processing and the possibility of access are provided upon request or within 10 business days after the request is received. The period may be extended by no more than five business days with a reasoned notification. A refusal is issued as a reasoned reply with a reference to the law within the periods provided for by Article 20. Technical impossibility of automatic export does not remove the right of access; an additional machine-readable export may be provided by the means available on the Platform.

11.6. Confirmed inaccurate, incomplete or outdated information is corrected within seven business days from the day confirming information is provided. Unlawfully obtained information or information not necessary for the purpose is destroyed, upon a confirmed request, within seven business days in the cases of part 3 of Article 20. While the review is ongoing, the blocking rules provided for by law apply. The University notifies the data subject of the results and takes reasonable measures to notify the recipients of the data.

11.7. Unlawful processing, once identified, is ended no later than three business days from the date of identification. If its lawfulness cannot be ensured, the data are destroyed no later than 10 business days from the date of identification. Where the data subject demands the end of processing, a period of no more than 10 business days applies, with a possible reasoned extension of no more than five business days and subject to lawful exceptions. For withdrawal of consent and achievement of the purpose, the special rules of clause 10.4 apply.

11.8. The user is entitled to challenge the actions or inaction of the University before the Federal Service for Supervision of Communications, Information Technology and Mass Media (Roskomnadzor), whose details are published at https://rkn.gov.ru, or before a court. Exercising these rights does not require prior withdrawal from studies or dismissal.

12. Protection Measures and Changes to this Policy

12.1. The University must take the necessary legal, organisational and technical data protection measures, appoint a person responsible for organising processing, define employee powers, restrict access, ensure protected transmission, keep records of significant actions and monitor the performance of obligations by recipients. Specific measures are determined by the nature of the data, the threats and the applicable requirements of legislation. A reference to encryption does not replace compliance with these requirements.

12.2. Upon establishing the fact of an unlawful or accidental transfer, provision, dissemination of or access to personal data that violated the rights of data subjects, the University notifies the authorised body within 24 hours of the moment the incident is identified, and reports the results of the internal investigation within 72 hours, in accordance with part 3.1 of Article 21 of Federal Law No. 152-FZ. Measures are taken to end the violation and limit its consequences.

12.3. The Policy applies after its approval by the University and publication. The current text must be available without signing in to an account on the web portal, via a link from the application and at the points where consent is obtained. The date and edition details are indicated upon publication; previous editions are retained for verifying the conditions of processing that has taken place.

12.4. Where the purposes, data scope, recipients or essential processing conditions change, the University updates this Policy in advance and informs users by the means available on the Platform. If a change is not covered by previously obtained consent or another legal ground, the necessary ground is secured before new operations begin. Publication of an edition does not legalise retroactively processing that has already taken place and is not deemed obtaining new consent.


Revision History