Sign in

Cookie policy

Last updated 10 May 2018.

A cookie is a small text file that a website stores on your computer. Like many other websites ECA uses cookies to enable our systems to recognise you when you visit our website and to allow you to navigate the website more easily. ECA uses cookies to collect clickstream data, so that we can identify and analyse the pages you visit, your Internet protocol (IP) address and your browser type.

Overall, cookies help us to provide you with a better website, by enabling us to monitor which pages you find useful and which you do not. They are also used for security purposes to prevent unauthorised access to secure areas.

We know that people have concerns about cookies, but we believe the benefit that we both gain from their proper use is worthwhile. You may set your web browser to notify you of cookie placement requests or to remove cookies completely. You can delete the files that contain cookies – those files are stored as part of your web browser. However, rejecting cookies may affect your ability to use some of the products and/or services at our websites. You can learn more about cookies and how to disable/enable them here.

If you want to learn more about what targeting and advertising cookies are on your device (whether or not related to us) and how to disable them you can do so here.

Our website may use the following cookies:

Cookie Level/Source Description
CMSCookieLevel System Specifies which cookies are allowed by the visitor.
ASP.NET_SessionId System Keeps the user session ID for security reasons.
CMSCsrfCookie System Store's a security token that the system uses to validate all form data submitted via POST requests. Helps protect against cross site request forgery.
CMSPreferredCulture Essential Stores the visitor's preferred content culture.
CMSMobileRedirected Essential Indicates if the visitor has been redirected to the mobile version of the website by the mobile device redirection web part.
CMSCurrentTheme Essential Stores the name of the current visual theme to provide proper design to the dialog windows.
Webauthtoken Essential Live ID authentication cookie.
CMSForumPostAnswer Essential Keeps a list of Question-Answer forum posts in which the user voted for an answer to prevent repeated votes.
CMSVotedPolls Essential Keeps a list of polls where the user voted to prevent repeated votes.
CMSRatedDocuments Essential Keeps a list of pages that the user rated to prevent repeated votes.
CMSShowDesktopVersion Essential Indicates that the visitor has switched to the desktop (default) version of the website from a specific device profile.
VisitorStatus Visitor Indicates if the visitor is new or returning. Used for tracking the visitors statistic in Web analytics.
Source Visitor 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.
Campaign Visitor Stores the name of the campaign assigned to the visitor.
Content Visitor Stores the specific content item through which the visitor arrived as part of a campaign. Based on the utm_content query string parameter.
TrackedCampaigns Visitor Stores all the campaigns, which should be tracked within a JavaScript snippet.
UrlReferrer Visitor Stores the URL referrer from which the user arrives on the website.
CurrentContact Visitor Stores the GUID of the contact related to the current site visitor. Used to track activities on the website.
CMSAB<ABtestname> Visitor 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 (an online marketing technique).
CMSMVT<mvtestname> Visitor 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.
CMSShoppingCart Visitor 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).
CMSBodyClass Visitor Body element class to provide accessibility standards.
CMSUserPage Visitor Stores the IDs (DocumentID, NodeID) of the last visited page. Used for logging landing and exit page web analytics and activities.
ChatLoggedInToken Visitor Stores the login state for the Chat application (indicates if the user is in the online state).
ChatSupportLoggedInToken Visitor Indicates if the user is logged in to the support chat.
<Window name>_<Group ID>_roomID Visitor Stores bindings between groups of chat web parts and chat rooms (for a specific window or tab).
chat_autoinitchat_displayed_<GUID> Visitor Remembers if the automatically initiated chat web part was shown to the user (prevents multiple chat initiation messages).
chat_kick_roomid_<room ID> Visitor Indicates that the user was kicked from the specified chat room (and is not allowed to return).
StrandsSBS_* Visitor Used by the Strands Recommender solely for its own purposes. The cookies are managed on the Strands side.
CMSStrandsTrackEvent_* Visitor Stores persistent HTTP context after a page is reloaded. Used for tracking of shopping cart events.
__openid_selector_* Visitor Stores OpenId user identification for authentication purposes.
CMSLandingPageLoaded Visitor 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.
_SS, MUID, SRCHD, SRCHHPGUSR, SRCHUID, SRCHUSR Bing Maps Microsoft set a number of cookies on any page that includes a Bing Map. We have no control over the cookies set by Microsoft. They include pieces of information to identify unique users, to measure the number and behaviour of Bing Maps users, and connect data from the Bing advertising network with actions performed on the website.
__Secure-3PAPISID, __Secure-3PSID, __Secure-3PSIDCC, 1P_JAR, ANID, APISID, CONSENT, HSID, NID, SAPISID, SID, SIDCC, SSID, ssm_au_c Google Maps Google set a number of cookies on any page that includes a Google Map. We have no control over the cookies set by Google. They include pieces of information to identify unique users, to measure the number and behaviour of Google Maps users, and connect data from the Google advertising network with actions performed on the website
__qca, __ssid, __zlcmid, _abexps, _delighted_web, _fbp, _ga, _mkto_trk, continuous_play_v3, has_logged_in, has_uploaded, is_logged_in, player, sd_client_id, ssm_au_c, vimeo_cart, vuid Vimeo Vimeo sets a number of cookies on any page that embeds a video hosted in Vimeo. We have no control over these cookies. They include pieces of information to measure the number and behaviour of Vimeo viewers, to hold information about current viewing video settings as well as a personal identification token if you are logged into Vimeo. 

Unique tracking codes / 'web beacons'

When we send html email messages about new products, services, seminars or promotions these messages may contain tracking codes unique to you. This enables us to check how successful a marketing campaign is as we are able to check if individuals are opening our emails or clicking through to our website.
We may also use unique tracking codes on this website in order to (for example):

  • count the number of visitors to this website;
  • establish interest levels for particular items or aspects of this website or particular products and services available on this website;
  • assess whether advertisements or competitions result in sales; or
  • understand how popular a product or service is, and how interest levels vary between particular ECA products and services.

As explained in the Direct Marketing section of our Privacy Policy, you will always be entitled to opt-out of such marketing communications. Each email will have an opt-out option for future communications or you can contact the Data Management Team at the address listed in the Contacts and complaints section of our Privacy Policy.