These files are required for the website functioning and thus can not be disabled.
These files are used for our website visitors' behaviour analysis, for example, the number of visitors and the most visited pages. Saving Analytical Cookies helps us to improve our website.
These files are used for social media platform integration for providing additional content or services.
These files are used to show you relevant adverts, interesting to you, and also to measure the advertising effectiveness on third-party websites. They are provided by third parties and gather your demography data, such as age and gender.
We also draw your attention to the fact that Severstal has pages on social networks. These sites also use and process cookies. This Policy does not apply to these third-party cookies. We therefore encourage you to read the cookie policies of these sites separately to understand what cookies they use and for what purposes.
Cookies are small files that, when using a website, are downloaded to the user's device when certain content is loaded. Cookies contain information about how the website is used, by summarizing the standard information in the log entries (IP address, connection time, connection duration), as well as information about the actions taken on the website.
The second type of cookies is analytical cookies, which are necessary to help analyze the website. For example, in order to understand the actions of visitors on the website, thus enabling us to improve and provide users with a more user-friendly website, the services of visitor analysis used in the legitimate interest of the controller, are used to inform society to represent, develop and carry out economic activities. You may refuse the use of analytical cookies, so you will only have functional cookies installed, without which the operation of the website would not be possible.
|BX_USER_ID||1 year||Allows us to track the user's current session number||Severstal cookie|
|PHPSESSID||Session||Allows us to track the user's current session number||
|_ym_d||1 year||Stores data about user's first session||Yandex.Metrica|
|_ym_isad||24 hours||Identifies whether the user has an ad blocker installed||Yandex.Metrica|
Identifies users of the website
Supports session capture feature
|_ym_metrika_enabled||60 minutes||Checks if other cookies are set correctly||Yandex.Metrica|
|gdpr||Up to 2 years||Allows you to distinguish visitors fr om the area covered by the General Data Protection Regulation (General Data Protection Regulation, GDPR)||Yandex.Metrica|
|is_gdpr||Up to 2 years||Allows you to distinguish visitors from the area covered by the General Data Protection Regulation (General Data Protection Regulation, GDPR)||Yandex.Metrica|
|is_gdpr_b||Up to 2 years||Allows you to distinguish visitors from the area covered by the General Data Protection Regulation (General Data Protection Regulation, GDPR)||Yandex.Metrica|
|_ym_debug||Session||Debug mode indicator||Yandex.Metrica|
|_ym_visorc_*||30 minutes||Used for the correct operation of the Webvisor||Yandex.Metrica|
|_ym_hostIndex||24 hours||Allows you to lim it the number of requests||Yandex.Metrica|
|i||1 year||Allows you to distinguish visitors||Yandex.Metrica|
|yandexuid||1 year (in some countries the period may be longer)||Allows you to distinguish visitors||Yandex.Metrica|
|yuidss||1 year (in some countries the period may be longer)||Allows you to distinguish visitors||Yandex.Metrica|
|ymex||1 year||Stores auxiliary information for the operation of the Metrica: the creation time of identifiers and their alternative values||Yandex.Metrica|
|usst||1 year||Stores auxiliary information for synchronizing visitor identifiers between different Yandex domains||Yandex.Metrica|
|top100_id||1 year||Identifies site users||Rambler’s Top100|
|tildasid||30 minutes||Identifies the session ID||Services Tilda.cc|
|tildauid||90 days||Identifies site users||Services Tilda.cc|
|VID||366 days||Contains the user’s identifier given in sequence||VK Pixel|
|tmr_lvid||333 days||Local cookie file, visitor’s identifier on the website. It is used to provide the functionality of getClientID method, cache VID cookie issuance and calculate the audience size for browsers not supporting the 3-party cookie||VK Pixel|
|tmr_lvidTS||333 days||Local cookie file. Contains cookie tmr_lvid generation timestamp||VK Pixel|
|tmr_detect||24 hours||Local cookie file. Keeps the results related to the website ad blocking by browser||VK Pixel|
|p||399 days||It is used to track the user's interaction with the website.||VK Pixel|
|mtrc||7 days||It is used to track the user's interaction with the website.||VK Pixel|
|mtrcu||399 days||It is used to track the user's interaction with the website.||VK Pixel|
|ruid||1 year 1 month||Saves a unique user ID.||Rambler Pixel|
|top100_id||1 year||Identifies site users.||Rambler Pixel|
|proto_uid||1 year 1 month||Saves a unique user ID for transmitting statistics.||Rambler Pixel|
|adtech_uid||1 year||It is installed by the Rambler statistics service.||Rambler Pixel|
|t3_sid_7714744||1 year||Saves the unique the counter ID.||Rambler Pixel|
|last_visit||1 year 1 month||Saves the ID of the last session.||Rambler Pixel|
|1f_uid||1 year 1 month||Saves the ID of the customer on whose website the tracker is installed.||SmartContact Tracker|
|_ct||1 year 1 month||An identifier is assigned to each site visitor. It is unique within the domain of the monitored site. It is needed to identify each individual site visitor.||CallTouch pixel|
|_ct_client_global_id||1 year 1 month||Issued .mod.calltouch.ru . This cookie is native to PHP applications. The cookie stores and identifies a unique user session ID to manage user sessions on the website. It is a session cookie and will be deleted when all browser windows are closed.||CallTouch pixel|
|_ct_client_global_id||1 year 1 month||Issued severstal.com . The identifier is assigned to each site visitor, used to identify the customer in different products.||CallTouch pixel|
|_ct_ids||Session||This cookie stores a set of data for site and session identification, namely: script mod_id (Calltouch script ID), site_id (site ID in Calltouch), session_id (session ID in Calltouch).||CallTouch pixel|
|_ct_session_id||Session||The session ID allocated by the Calltouch script is recorded in a separate heap. When updating the session id, the cookie is overwritten.||CallTouch pixel|
|_ct_site_id||Session||ID of the monitored site in the Calltouch system.||CallTouch pixel|
|_ct_server||1 year 1 month||An identifier is assigned to each site visitor. It is unique within the domain of the monitored site. It is needed to identify each individual site visitor. This cookie begins to be recorded when the "cookie lifetime extension via DNS" functionality is active.||CallTouch pixel|
|call_s||30 minutes||This cookie stores: the mod_id of the script (the ID of the Calltouch script), the opening time of the session in Calltouch, the id of the Calltouch session, the ids of the pools and numbers that were allocated within the session.||CallTouch pixel|
|cted||Session||This cookie stores the Yandex visitor id, Google cid, and Facebook visitor id, which we received during the session on the site and linked to our session.||CallTouch pixel|
|directCrm-session||1 year 1 month||Session cookie in Mindbox.||Jivo pixel|
|mindboxDeviceUUID||1 year 1 month||User ID in Mindbox.||Jivo pixel|
|popmechanic _sbjs_migrations||5 months||Popmechanic cookie.||Jivo pixel|
Analytical cookies are provided by analytical services:
for evaluating the activities of visitors and preparing an appropriate summary report for the controller. The ability to identify you is reduced to a minimum, however, the above actions do not ensure complete anonymity of data.