This Cookie Policy (hereinafter referred to as the “Policy”) is developed and used by Beterra Joint-Stock Company, INN [Taxpayer Identification Number]: 7704154440, OGRN [Primary National Registration Number]: 1027700115409, registered address: unit / off. VII/57, No. 32A Khoroshovskoye Shosse, 125284 Moscow, and Beterra Limited Liability Company, INN: 7714783649, OGRN: 1097746380511, registered address: bldg. 3, No. 47 Leningradsky Prospekt, Khoroshevsky Municipal District intra-city municipality, 125167 Moscow, in respect of the website beterra.ru (hereinafter referred to as the “Website”).
The Policy has been developed pursuant to the current legislation of the Russian Federation, including the Federal Law of 27.07.2006, No.
1. Terms and definitions
The Policy uses the following terms:
Company, “we” — Beterra Joint-Stock Company (Beterra JSC) and Beterra Limited Liability Company (Beterra LLC).
Website Visitor (Visitor) — a person who visits and uses the Website.
Website — a suite of computer software and hardware that enables public-domain publication of information and data collated for a single purpose by means of facilities used for communications between computers on the Web. The Website is available on the Web at the following URL: https://beterra.ru/.
Cookies — a small piece of data that the Website requests from a browser used on a computer or mobile device of Visitor. Cookies record Visitor’s preferences or activities on the Website, as well as a description of his hardware and the date and time of the session. Cookies are stored locally on Visitor’s computer or mobile device. Visitor can delete the stored cookies in the settings of the browser.
IP address — the unique address of a site on a computer network built as per IP protocol.
2. Types of cookies used
We use the following categories of cookies files:
2.1 Session (temporary)
Such cookies are saved in temporary storage for the duration of Visitor’s stay on the Website’s page. Browsers usually delete session cookies once Visitor closes the Website’s tab. Session cookies make it possible for the Website to store information about Visitor’s choice on the Website’s previous page to preclude the need for data re-entry.
2.2 Persistent
Cookies that are stored on Visitor’s computer and are not deleted when the browser is closed. Persistent cookies can save user settings for the Website, making it possible to use these preferences in future browsing sessions. Such cookies make it possible to identify Visitor as a unique user of the Website and help retrieve information about Visitor and previous activities when the Website is revisited.
2.3 Statistical
Such cookies include information on how Visitor uses the Website. For example, what pages Visitor visits, what links he follows. The primary objective of such cookies is to improve the functionality of the Website.
2.4 Required
The minimum set of cookies that the Website needs to function correctly.
2.5 A list of the cookie files used, with their functional purpose and life specified, is provided in the Appendix hereto.
3. Purposes of cookies
We use cookie files for various purposes, the main ones being as follows:
3.1 ensure the serviceability of the Website: cookie files help us make the Website easy to use.
3.2 analysis of user activities: cookie files help us understand how Visitor uses the Website, which enables us to improve its performance and contents.
3.3 provision of individualized information and advertisements (subject to the consent of Visitor).
4. To whom we disclose information about Website Visitors collected using cookie files
To achieve the goals specified in section 3 hereof, we disclose information collected using analytic and advertising (marketing) cookie files to the following third parties that we engage to process cookie files and which implement adequate personal data security measures:
Yandex.Metrics — Yandex LLC, registered address: No. 16 Lva Tolstogo str., 119021 Moscow, INN: 7736207543, OGRN: 1027700229193.
1S Bitrix — 1S-Bitrix LLC, registered address: prem.
5. Whether we perform cross-border transfer of information collected using cookie files
5.1 We use cookie files provided by the third parties named in section 4 hereof to perform cross-border transfer of data unrelated to the identification of a specific Visitor.
5.2 Cross-border transfer of cookie file contents is performed to countries that ensure a proper level of protection for data subject rights.
6. Obtaining consent
Upon the first visit to the Website, we ask for Visitor’s consent to use cookies by means of a popup notice (banner). Visitor can accept all files or customize his choice. Declining cookies can affect the functionality of the Website.
7. Cookie management
Most browsers are configured by default to accept cookie files. Visitor can at any time delete or disable cookies in the browser settings. Cookie control options for popular browsers:
● Google Chrome: https://support.google.com/chrome/answer/95647
● Mozilla Firefox: https://support.mozilla.org/ru/kb/udalenie-cookies
● Safari: https://support.apple.com/ru-ru/guide/safari/sfri11471/mac
● Microsoft Edge: https://support.microsoft.com/ru-ru/microsoft-edge/delete-cookies
● Yandex: https://browser.yandex.ru/help/personal-data-protection/cookies.html
8. Changes to the Policy
Company reserves the right to make changes to this Policy. The current version is always accessible at the following URL: https://beterra.ru/en/about/beterra-company/cookie_usage_policy/.
Appendix
To the Cookie Policy
Information about cookie files used on the Website
Name of cookie file |
Life |
Purpose |
АЕС |
6 months |
Guarantees that enquiries during a browsing session are made by Visitor rather than by other websites. These files make it impossible for malicious websites to pose as Visitor without his knowledge. |
SID |
1 year |
A popular name of a cookie file, but if it is a session cookie file, then it will most likely be used for session control. |
APISID |
Used by Google to store user preferences and information when pages with Google maps are viewed. |
|
SSID |
||
HSID |
||
SAPISID |
||
DV |
7 minutes |
Categorized as “Preferences” or “Functional” cookie files. Its specific purpose and use can differ depending on the website or service that installs it. |
PHPSESSID |
Until the browser is closed |
Session identifier that is generated and stored at the server end to monitor Visitors’ sessions. It is usually used in PHP to maintain the session status on the website. |
SIDCC |
1 day |
Security cookie file that protects Visitor’s data against unauthorized access. |
__Secure-1PAPISID |
1 year |
Cookie file for targeting. It is used for targeting purposes to create the website visitor’s interest profile in order to display relevant and individualized advertisements on Google. |
__Secure-1PSID |
||
__Secure-1PSIDCC |
||
__Secure-1PSIDTS |
||
__Secure-3PAPISID |
||
__Secure-3PSID |
||
__Secure-3PSIDCC |
||
__Secure-3PSIDTS |
||
__Secure-BUCKET |
||
__Secure-ENID |
||
i |
1 year |
Temporary file installed by Yandex Metrics. Makes it possible to identify visitors. |
_ym_uid |
||
_ym_isad |
2 days |
Temporary file installed by Yandex Metrics. Used to determine if visitors have ad blockers. |
_ym_d |
1 year |
Temporary file installed by Yandex Metrics. Stores the date of the visitor’s first visit to the website. |
_ym_visorc |
30 minutes |
Temporary file installed by Yandex Metrics. Used for correct operation of Webvisor. |
BITRIX_SM_LOGIN |
1 year |
Stores information about the login of the website user. |
BX_USER_ID |
1 year |
Enables the correct operation of the website management system |
ClientType |
Until the browser is closed |
Temporary file. Used to identify the type of the user’s device |
utm_campaign |
1 year |
Temporary file. Required to monitor conversions. To link conversions to specific traffic sources and campaigns even on pages where the send form does not appear directly after navigation. Session rescheduling. To save information about a traffic source and to use it when the user visits again. |
utm_content |
||
utm_medium |
||
utm_source |
||
utm_term |