MeteoCare.RU
Legal documents

Personal Data Processing Rules

For users of the MeteoCare.RU mobile application

MC-RULES-PD-1.3 Revision dated 10.08.2026

This is a translation provided for convenience. The Russian-language text is legally binding, and the Russian version prevails in the event of any discrepancy.

1. Status and Purpose of the Document

1.1. These Personal Data Processing Rules (hereinafter — the Rules) are a publicly available document setting out the Operator's policy on the processing of personal data in connection with the operation of the MeteoCare.RU mobile application, the website at https://meteocare.ru/, and the API at https://api.meteocare.ru/.

1.2. The Privacy Policy is a concise summary of these Rules for the User. Consent to data processing for personalized advertising is executed separately from the Terms of Use and other documents.

1.3. The Application does not involve registration, profile creation, or User authorization.

1.4. This translation is provided for convenience. The Russian-language text of these Rules is legally binding; in the event of any discrepancy between this translation and the Russian version, the Russian version prevails: https://meteocare.ru/personal-data-processing-rules.

2. Information about the Operator

3. Terms

  • User — an individual using the Application or contacting the support service;
  • Installation — a specific instance of the Application on a device, to which a UUID is assigned;
  • Installation UUID — a random technical identifier used for interaction with the API and for request statistics; it is not the User's name or account;
  • Diary Data — records of well-being and indicators that the User enters into the Application's storage on their device;
  • Advertising SDK — the Yandex Mobile Ads SDK, which provides advertising display;
  • Disclosure of personal data — the revealing of data to a specific person or a specific group of persons;
  • Dissemination of personal data — the revealing of data to an indefinite group of persons.

4. Processing Principles

4.1. Processing is carried out on the basis of the following principles:

  • lawfulness, good faith, and limitation of processing to predetermined purposes;
  • minimization of the scope and volume of data;
  • separation of server data from Diary Data;
  • not using Diary Data for advertising, analytics, or profiling;
  • providing the option of manual city selection instead of mandatory geolocation;
  • executing Consent to personalized advertising separately and allowing its withdrawal;
  • confidentiality, security, and limitation of retention periods.

5. Categories of Data Subjects and Data

5.1. The data subjects are Users of the Application and persons contacting the support service.

5.2. Server data includes:

  • the installation UUID;
  • coordinates, where geolocation is permitted, or the selected city and the city identifier;
  • the platform, version, build number, and distribution channel;
  • the IP address, the time and type of request, technical logs, errors, and security events.

5.3. Advertising data includes:

  • the advertising identifier and other personalization identifiers;
  • the IP address and information about the network connection;
  • information about the device, the operating system, and the Application;
  • information about the advertising unit, impressions, clicks, and other advertising events;
  • the selected advertising mode.

5.4. Support data includes:

  • email address and name, if provided;
  • the text of the inquiry and information about the issue;
  • technical information, screenshots, and other files voluntarily submitted by the requester.

The Operator requests that diary entries and health information not be sent. Such information is not required for support purposes and, if received inadvertently, is deleted or masked where possible.

5.5. The Operator does not process biometric data. Diary entries may contain health information; however, they are not transmitted to the MeteoCare.RU server database, are not linked by the Operator to the installation UUID, and are not used by the Operator for analytics, advertising, or profiling.

5.6. The Application is intended for persons who have reached 18 years of age. The Operator does not knowingly request age information and does not purposefully collect the personal data of persons under 18 years of age.

6. Purposes, Data, Legal Grounds, and Retention Periods

6.1. Processing is carried out for the following purposes:

The device's coordinates are not transmitted to the advertising SDK or advertising-infrastructure participants for any of the advertising purposes (clause 9.3 of these Rules).

6.2. Processing based on legitimate interests is limited to technical identifiers and request parameters, is not used for profiling the User, including profiling related to health status, and is not linked to diary entries.

6.3. Withdrawal of Consent to personalized advertising terminates further processing for personalization and does not affect the processing of data on other legal grounds.

7. Obtaining and Recording Consent

7.1. Before advertising personalization begins, the Application displays a separate Consent text. The fact of Consent is recorded together with the installation UUID, the date and time, the Application version, the build number, the platform, the distribution channel, and the document revision.

7.2. The geolocation permission is granted through the operating system's native interface and is not part of the Consent to personalized advertising. Declining it does not deprive the User of the ability to select a city manually.

7.3. The choice of advertising mode is recorded separately. Changing the mode to non-personalized advertising constitutes withdrawal of Consent to personalization from the moment the setting is applied and the selected mode is transmitted to the advertising SDK.

7.4. Withdrawal of Consent does not affect the lawfulness of processing carried out before the withdrawal and does not prevent processing on other legal grounds.

8. Processing of Diary Data

8.1. Diary entries are stored on the User's device. The MeteoCare.RU server does not receive their content and does not link them to the installation UUID.

8.2. The Operator does not access the diary's content and does not disclose it to providers of server, advertising, or other infrastructure.

8.3. The User independently manages diary entries, their deletion, synchronization, and backup using the tools of the Application and the device's operating system.

9. Geolocation

9.1. Geolocation is used solely to determine a suitable city and is not mandatory. Its accuracy depends on the permission and settings of the operating system.

9.2. Coordinates are transmitted to the MeteoCare.RU server over a secure connection. The Operator does not create a history of movements. Coordinates may temporarily appear in request logs until they are rotated.

9.3. The device's coordinates are not transmitted to the advertising SDK or advertising-infrastructure participants. The use of location data for ad targeting has been disabled by the Operator programmatically using the advertising SDK's built-in tools. This setting operates independently of whether the system geolocation permission has been granted.

10. Advertising and Interaction with YANDEX LLC

10.1. The Yandex Mobile Ads SDK is used to display advertising in the Application. The advertising SDK may receive a limited set of technical data necessary for ad delivery, security, frequency capping, and the recording of advertising events. The device's coordinates are not transmitted via the advertising SDK.

10.2. Advertising personalization is carried out only where a separate Consent has been given. If Consent is not given or is withdrawn, non-personalized advertising is displayed, for which the processing of minimal technical data may continue.

10.3. Further processing of data obtained by the advertising SDK directly from the device is carried out by the relevant advertising-infrastructure participants in accordance with the documents and legal grounds applicable to them. This does not relieve the Operator of the obligation to integrate and configure the advertising SDK lawfully.

11. Processing Procedure and Methods

11.1. Server-side processing is carried out by automated means. Permitted operations are: collection, recording, systematization, accumulation, storage, updating, retrieval, use, disclosure to specific persons, anonymization, blocking, deletion, and destruction.

11.2. Dissemination to an indefinite group of persons is not carried out without separate consent to dissemination or another lawful basis.

11.3. Support inquiries may be processed by mixed means, including handling by the Operator without the use of automation tools.

12. Recipients and Infrastructure

12.1. YANDEX LLC (Russian: ООО «ЯНДЕКС») and advertising-infrastructure participants — for the operation of the advertising SDK and the display of advertising, without transmitting the device's coordinates via the advertising SDK.

12.2. Providers of server and network infrastructure — for the operation of the API, technical logs, backup of server systems, and secure connections.

12.3. Email service providers — for receiving and handling support inquiries.

12.4. Authorized government bodies and other persons — in cases provided for by law.

12.5. When assigning processing, the Operator determines the purposes, the scope of data and operations, the confidentiality and security requirements, assistance in exercising data subjects' rights, and incident notification. This clause applies to the providers of server, network, technical, and email infrastructure specified in clauses 12.2 and 12.3.

12.6. The processing of data by YANDEX LLC and advertising-infrastructure participants is carried out in accordance with the applicable contractual terms, their own documents, and their legal grounds.

13. Data Localization and Cross-Border Transfer

13.1. The MeteoCare.RU server database, containing installation UUIDs, request statistics, and technical logs, is located in the Russian Federation. The initial processing of the data of citizens of the Russian Federation is carried out using Russian databases.

13.2. The Operator does not itself carry out any cross-border transfer of MeteoCare.RU server data. If such a transfer becomes necessary, the procedures required by law are completed and the applicable documents are updated before it begins.

14. Retention Periods

14.1. Technical logs are generally retained for no more than 90 calendar days. In the event of an incident, records related to it may be retained until the investigation is completed and mandatory requirements are fulfilled.

14.2. Request statistics linked to the installation UUID are retained for no more than 12 months after the corresponding installation's last activity, after which the UUID is deleted or the statistics are anonymized.

14.3. Records of Consent being given or withdrawn may be retained for up to three years after withdrawal or the last event related to its application, to confirm compliance with requirements and to protect rights.

14.4. Support inquiries are retained until their handling is completed and, generally, for no more than three years after the last interaction.

14.5. The retention periods for advertising-infrastructure participants' independent processing of advertising data are determined by their applicable documents. Diary entries are stored on the device until deleted by the User or by operating system tools.

15. Deletion and Cessation of Processing

15.1. The User may delete diary entries and other local data using the Application's tools, clear the Application's data, or delete the Application. Backup and synchronized copies created by operating system tools are managed by the User separately.

15.2. Changing the advertising mode to non-personalized terminates further processing for personalization once the setting is applied and the selected mode is transmitted to the advertising SDK. This does not terminate the processing of the minimal technical data necessary to display non-personalized advertising.

15.3. Deleting the Application stops any further transmission of data from the corresponding device. Previously performed processing ceases, and the data is deleted or anonymized upon expiry of the periods established by these Rules, unless otherwise provided by law.

16. Rights of Data Subjects

16.1. The User is entitled to obtain information about the processing of personal data.

16.2. The User is entitled to request that data be updated, blocked, or deleted in cases provided for by law.

16.3. The User is entitled to withdraw Consent to personalized advertising by changing the advertising mode in the Application.

16.4. The User is entitled to change the geolocation permission using operating system tools.

16.5. The User is entitled to object to processing based on legitimate interests.

16.6. The User is entitled to file a complaint with Roskomnadzor (the Federal Service for Supervision of Communications, Information Technology and Mass Media) or with a court.

16.7. General requests and inquiries should be sent to info@1294studio.ru or to the Operator's postal address and are handled in the manner established by the legislation of the Russian Federation.

17. Security Measures

17.1. The Operator applies:

  • individual credentials and restricted administrative access;
  • HTTPS/TLS and a secure connection between server components;
  • verification of the Application key and restriction of the permitted API methods;
  • request-rate limiting and restricted network access to the database;
  • logging, updates, and configuration control;
  • backup and recovery of server systems;
  • separation of the server database from Diary Data.

18. Incidents

18.1. If unlawful access, transfer, or loss of data is identified, the Operator stops the violation, conducts an investigation, assesses the consequences, takes remedial measures, and interacts with Roskomnadzor in the manner and within the time limits established by law.

19. Liability

19.1. The Operator is liable to the extent established by the legislation of the Russian Federation. The User is responsible for the security of their device, system account, and the accuracy of information voluntarily submitted to support.

20. Final Provisions

20.1. The Rules remain in effect until replaced by a new revision. Material changes are communicated to the User before they take effect. If changes affect processing based on Consent, the text of the Consent is updated and a new Consent is obtained before the corresponding processing begins.

20.2. The current revision is published at: https://meteocare.ru/personal-data-processing-rules

21. Contacts

Terms of Use: https://meteocare.ru/terms

Privacy Policy: https://meteocare.ru/privacy

Consent to Personalized Advertising: https://meteocare.ru/personal-ads-consent

Consent to Personal Data Processing: https://meteocare.ru/personal-data-consent