cookies policy
Cookies - это небольшие файлы данных, которые хранятся в браузере или на жестком диске вашего компьютера в случае вашего согласия. Для получения более подробной информации о файлах cookie посетите сайт www.allaboutcookies.org.
Вы можете запретить использование файлов cookie, активировав в своем интернет-браузере настройку браузера, которая позволяет отказаться от установки всех или некоторых файлов cookie. Однако, если вы используете настройки браузера для блокирования всех файлов cookie (включая основные), вы можете не получить доступ ко всем или некоторым частям нашего веб-сайта. cookies), вы можете оказаться не в состоянии получить доступ ко всем или некоторым частям нашего сайта. Управление настройками файлов cookie
Управление предпочтениями в отношении файлов cookie
A breakdown of how we use your cookie data:
Our use of cookies
Our website uses cookies to distinguish you from other users.
You can find more information about the individual cookies we use and the purposes for which we use them in the table below:
You can find more information about the individual cookies we use and the purposes for which we use them in the table below:
Cookies policy table
Cookie name
Purpose
Duration
Google analytics _utma
This cookie is used to distinguish users and sessions. The cookie is created when the javascript library executes and no existing __utma cookies exists. The cookie is updated every time data is sent to Google Analytics.
2 years from set/update
Google analytics _utmb
This cookie is used to determine new sessions/visits. The cookie is created when the javascript library executes and no existing __utmb cookies exists. The cookie is updated every time data is sent to Google Analytics.
30 mins from set/update
Google analytics _utmc
This cookie operates in conjunction with the __utmb cookie to determine whether the user was in a new session/visit.
End of browser session
Google analytics _utmz
This cookie stores the traffic source or campaign that explains how the user reached your site. The cookie is created when the javascript library executes and is updated every time data is sent to Google Analytics.
6 months from set/update
Google analytics _utmv
This cookies stores visitor-level custom variable data. This cookie is created when a developer uses the _setCustomVar method with a visitor level custom variable. This cookie was also used for the deprecated _setVar method. The cookie is updated every time data is sent to Google Analytics.
2 years from set/update
CMSCookieLevel
This cookie specifies which cookies are allowed by the visitor.
1 year
ASP.NET_SessionId
This cookie keeps the user session ID for security reasons.
Session based
CMSCsrfCookie
This cookie stores a security token that the system uses to validate all form data submitted via POST requests. It helps prevent cross site request forgery.
1 year
CMSPreferredCulture
This cookie stores the visitor's preferred content culture.
1 year
CMSMobileRedirected
This cookie indicates if the visitor has been redirected to the mobile version of the website by the Mobile device redirection web part.
1 year
CMSCurrentTheme
This cookie stores the name of the current visual theme to provide proper design to the dialog windows.
1 year
Webauthtoken
Live ID authentication cookie.
1 year
CMSForumPostAnswer
Keeps a list of Question-Answer forum posts in which the user voted for an answer to prevent repeated votes.
1 year
CMSVotedPolls
Keeps a list of polls where the user voted to prevent repeated votes.
1 year
CMSRatedDocuments
Keeps a list of pages that the user rated to prevent repeated votes.
1 year
CMSShowDesktopVersion
Indicates that the visitor has switched to the desktop (default) version of the website from a specific device profile.
1 year
CMSWindowsUser
Stores information for users who were imported from an Active Directory domain during authentication.
1 year
.ASPXFORMSAUTH
Stores the user's encrypted authentication ticket when using forms authentication.
Session based
VisitorStatus
Indicates if the visitor is new or returning. Used for tracking the visitors statistic in Web analytics.
1 year
Source
Stores the channel from which the visitor arrived as part of a campaign (e.g., email, Facebook, Twitter, etc.). Based on the utm_source query string parameter.
1 year
Campaign
Stores the name of the campaign assigned to the visitor.
1 year
Content
Stores the specific content item through which the visitor arrived as part of a campaign. Based on the utm_content query string parameter.
1 year
TrackedCampaigns
Stores all the campaigns, which should be tracked within a JavaScript snippet.
1 year
UrlReferrer
Stores the URL referrer from which the user arrives on the website.
1 year
CurrentContact
Stores the GUID of the contact related to the current site visitor. Used to track activities on the website.
1 year
CMSAB<ABtestname>
Used to track conversions for the test and maintain consistent page content for the visitor. Stores the name of the page variant assigned to the visitor, the list of performed conversions and information whether visitor is included in A/B testing specified by an A/B test.
1 year
CMSMVT<mvtestname>
Stores the combination of variants assigned to the visitor by an MVT test. Used to track conversions for the test and maintain consistent page content for the visitor.
1 year
CMSShoppingCart
Stores a GUID reference to the user's shopping cart. Allows the system to recover the shopping cart for unregistered customers, even after it is cleared from the cache (for example after an application restart).
1 year
CMSBodyClass
Body element class to provide accessibility standards.
1 year
CMSUserPage
Stores the IDs (DocumentID, NodeID) of the last visited page. Used for logging landing and exit page web analytics and activities.
1 year
ChatLoggedInToken
Stores the login state for the Chat application (indicates if the user is in the online state).
1 year
ChatSupportLoggedInToken
Indicates if the user is logged in to the support chat.
1 year
<Window name>_<Group ID>_roomID
Stores bindings between groups of chat web parts and chat rooms (for a specific window or tab).
1 year
chat_autoinitchat_displayed_<GUID>
Remembers if the Automatically initiated chat web part was shown to the user (prevents multiple chat initiation messages).
1 year
chat_kick_roomid_<room ID>
Indicates that the user was kicked from the specified chat room (and is not allowed to return).
1 year
StrandsSBS_*
Used by the Strands Recommender solely for its own purposes. The cookies are managed on the Strands side.
1 year
CMSStrandsTrackEvent_*
Stores persistent HTTP context after a page is reloaded. Used for tracking of shopping cart events.
1 year
__openid_selector_*
Stores OpenId user identification for authentication purposes.
1 year
CMSLandingPageLoaded
Indicates that the landing page has already been visited and the Landing page activity is not logged again for the current visitor. Expires after 20 minutes and the expiration period of the key is renewed every time the website is accessed again.
1 year
_hjClosedSurveyInvites
Hotjar cookie that is set once a visitor interacts with an External Link Survey invitation modal. It is used to ensure that the same invite does not reappear if it has already been shown.
1 year
_hjDonePolls
Hotjar cookie that is set once a visitor completes a survey using the On-site Survey widget. It is used to ensure that the same survey does not reappear if it has already been filled in.
1 year
_hjMinimizedPolls
Hotjar cookie that is set once a visitor minimizes an On-site Survey widget. It is used to ensure that the widget stays minimized when the visitor navigates through your site.
1 year
_hjShownFeedbackMessage
Hotjar cookie that is set when a visitor minimizes or completes Incoming Feedback. This is done so that the Incoming Feedback will load as minimized immediately if the visitor navigates to another page where it is set to show.
1 year
_hjid
Hotjar cookie that is set when the customer first lands on a page with the Hotjar script. It is used to persist the Hotjar User ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID.
1 year
_hjRecordingLastActivity
This should be found in Session storage (as opposed to cookies). This gets updated when a visitor recording starts and when data is sent through the WebSocket (the visitor performs an action that Hotjar records).
Session based
_hjTLDTest
When the Hotjar script executes we try to determine the most generic cookie path we should use, instead of the page hostname. This is done so that cookies can be shared across subdomains (where applicable). To determine this, we try to store the _hjTLDTest cookie for different URL substring alternatives until it fails. After this check, the cookie is removed.
Session based
_hjUserAttributesHash
User Attributes sent through the Hotjar Identify API are cached for the duration of the session in order to know when an attribute has changed and needs to be updated.
Session based
_hjCachedUserAttributes
This cookie stores User Attributes which are sent through the Hotjar Identify API, whenever the user is not in the sample. These attributes will only be saved if the user interacts with a Hotjar Feedback tool.
Session based
_hjLocalStorageTest
This cookie is used to check if the Hotjar Tracking Script can use local storage. If it can, a value of 1 is set in this cookie. The data stored in_hjLocalStorageTest has no expiration time, but it is deleted almost immediately after it is created.
Under 100ms
_hjIncludedInPageviewSample
This cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by your site's pageview limit.
30 minutes
_hjIncludedInSessionSample
This cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by your site's daily session limit.
30 minutes
_hjAbsoluteSessionInProgress
This cookie is used to detect the first pageview session of a user. This is a True/False flag set by the cookie.
30 minutes
_hjFirstSeen
This is set to identify a new user’s first session. It stores a true/false value, indicating whether this was the first time Hotjar saw this user. It is used by Recording filters to identify new user sessions.
Session based
hjViewportId
This stores information about the user viewport such as size and dimensions.
Session based
_hjRecordingEnabled
This is added when a Recording starts and is read when the recording module is initialized to see if the user is already in a recording in a particular session.
Session based
Our email marketing platform's use of cookies
Vuture, our email marketing platform, uses web tracking cookies that are persistent and are retained for one year by default. The use of cookies can track a user's website journey, uniquely identify their visit, and connect their website journey with their email journey. The information stored in the cookie is not transferred to any third parties. If a user disables cookies in their browser, they will not be tracked by Vuture's web tracking.
You can find more information about the individual cookie and the purpose for which we use them in the table below:
Cookie name
Purpose
Duration
VxSessionId intEmailHistoryId
Used when a person clicks through from an email to identify their visit to our website which then records the pages visited on our Website and the time spent on those pages.
1 year
