Website Privacy Policy

Privacy Policy for diabetes-app.ru

This Policy explains what technical and analytics data is processed when you visit the Diabet app website, why analytics is used, and which services receive the relevant information.

Publication date: August 13, 2026 Current version

1. General provisions and user consent

This Policy applies to https://diabetes-app.ru/, including its language versions and informational pages published on the website.

By visiting and continuing to use the website, you confirm that you have read this Policy and consent to the automated processing of the technical and analytics data described below, including through cookies and similar technologies.

The website is provided for informational purposes. It does not contain registration forms or forms for entering health indicators. The website does not collect diabetes diary data, glucose readings, treatment information, or other medical data.

2. Operator and contact details

Website operator: Vladimir Dmitrievich Orlov, self-employed, Taxpayer Identification Number 231848100961.

Website: https://diabetes-app.ru/

For questions about data processing or the website, contact mail@diabetes-app.ru.

3. Data we process

The following information may be processed automatically when you visit the website:

  • IP address and approximate location inferred from the network address;
  • cookie, browser, device, installation, or advertising profile identifiers;
  • browser type and version, operating system, device type, screen resolution, and language settings;
  • date and time of the visit, session duration, page address, traffic source, and referrer;
  • website usage events, including section views, link visits, clicks, scroll depth, and interaction with page elements;
  • technical information about page loading, errors, and performance;
  • interface interaction recordings generated by Yandex Metrica Webvisor, including pointer movements, scrolling, and clicks.

The operator does not use this information to determine a user's name or access their medical diary. Where possible, statistical reports are analyzed in aggregated or anonymized form.

4. Purposes of processing

Technical and analytics data is used to:

  • measure traffic and understand which sections of the website are most useful;
  • analyze visits to app stores, communities, and other external resources;
  • improve the website's structure, content, speed, and stability;
  • diagnose errors and prevent abuse;
  • evaluate the effectiveness of informational and advertising materials;
  • build audiences and display relevant advertising through retargeting services.

5. Analytics and retargeting services

The website uses the following third-party services:

  • Yandex Metrica, including Webvisor, click maps, and link tracking, receives information about page views, device and browser parameters, cookie identifiers, and actions on the page. Processing is governed by the Yandex Privacy Policy.
  • Google Analytics receives information about page views, events, traffic sources, technical parameters, and analytics identifiers. Processing is governed by the Google Privacy Policy.
  • Google Tag Manager is used to load and manage website analytics tags and may process technical information required for those tags to operate.
  • Firebase Analytics is used to analyze website visits and events and may create an installation identifier and receive device parameters and event information. The service is provided by Google.
  • Top.Mail.Ru receives information about page views, technical parameters, cookie identifiers, and configured goal completions. Processing is governed by the Mail Services Privacy Policy.
  • VK Retargeting receives information about website visits, technical and advertising identifiers, and events related to visits and product interest in order to build advertising audiences. Processing is governed by the VK Privacy Policy.

The scope and retention periods of data held by third-party services are determined by their settings, technologies, and published policies. The operator mainly receives statistical reports and information about configured goal completions.

6. Cookies and similar technologies

The website and connected services may use cookies, browser local storage, pixels, installation identifiers, and similar technologies. These technologies help distinguish sessions, save settings, measure traffic, and compile statistics.

To save the selected language, the website stores diabetes-site-language-v1 in the browser's local storage. Analytics services may create their own identifiers, including _ym cookie families for Yandex Metrica and _ga cookie families for Google Analytics. The set and lifetime of these identifiers may be changed by the respective services.

You can restrict or delete cookies and website data in your browser settings. Blocking technical storage may affect language persistence and certain analytics functions.

8. Data retention

Statistical reports and events are retained for as long as necessary to analyze traffic, evaluate website effectiveness, diagnose errors, and protect the operator's legitimate interests.

The retention periods for cookies and technical data held by third-party services are set by those services. Users can delete locally stored data through their browser.

9. User requests

For questions about data processing or requests for information, correction, or deletion of information held by the operator, contact mail@diabetes-app.ru.

To review a request, the operator may ask for information necessary to verify the applicant's identity and locate relevant information.

10. Data security

The operator applies reasonable organizational and technical measures to protect processed information against unauthorized access, alteration, disclosure, or destruction.

However, no method of transmitting or storing data on the internet can guarantee absolute security.

11. Changes to this Policy

This Policy may be updated when the services used, analytics settings, website functionality, or legal requirements change.

The current version is published on this page. Continued use of the website after changes are published means that the user has reviewed the updated Policy.