Skip to main content
Logo
There is a newer version of Contensis. Click to find out more and download the latest version.

Contensis cookies

If your website is within the EU, your website privacy policy should include information on how cookies are used across the site. In order to help you with this, we've detailed the cookies set by Contensis below. You only need to include information relevant to the particular functionality you are using.

Cookies set or used by web controls

There are a number of Contensis standard web controls that use cookies in order to remember user selections. If you don't use these controls on your site then no cookies will be set. The following controls use cookies:

Favourites Control

Name: [ID of Control]_Favourites
Typical Content: Stores favourites which have been selected by the user
Expires: When the user clears cookies

Font Size Selector

Name: CMSFontSizeCookie
Typical Content: Stores your current font size selection 
Expires: 12 months

Stylesheet Switcher

Name:  CMSStylesheetCookie
Typical Content: Stores the user's current stylesheet selection 
Expires: 12 months

Forums

Name: .ASPXAUTH 
Typical Content: Used to determine if a user is authenticated 
Expires: 12 months 

Cookies set or used by ADFS / Azure AD

The following cookies are set once you login to a Contensis site. If authentication is turned off (ie. there are no login facility on your site), these cookies will not be set.

Name: idsrv
Expires: 1 Hour

Name: idsrv.xsrf
Expires: 1 Hour

Name: idsrv.clients 
Expires: 1 Hour

Name: idsrv.session
Expires: When the user exits the browser

Cookies set or used by Contensis authentication

The following cookies are set once you login to a Contensis site. If authentication is turned off (ie. there are no login facility on your site), these cookies will not be set.

Name: ContensisCMSUsername
Typical Content: Stores information to re-authenticate a user when they have selected Save Password when logging in
Expires: When the user exits the browser

Name: ContensisDisplayName
Typical Content: Stores a user's display name in the format as specified in Contensis global settings
Expires: When the user exits the browser

Name: ContensisLastUserName
Typical Content: Stores a user's username – this is set when a user logs in for the first time
Expires: 25 years or until the user clears cookies

Name:  ContensisAvatar
Typical Content: Stores the URL to a user's avatar image, this is set when a user logs in for the first time
Expires: 25 years or until the user clears cookies

Session cookies used by the published site

Session cookies are used for remembering user selections during their visit to your site. A typical scenario may be to remember information entered in a form when navigating to different pages. If you have used sessions in your custom code then you will also be using the ASP.NET_SessionId cookie. Contensis uses the following cookies for session information:

Name:  csession
Typical Content: Randomly generated session ID 
Expires: When the user exits the browser

Name:  ASP.NET_SessionId
Typical Content: randomly generated session ID
Expires: When the user exits the browser

Google analytics

Google Analytics sets a number of cookies (default is 4) in order to evaluate the use of your site and compile reports.

Name:  _utma
Typical Content: randomly generated number
Expires: 2 years

Name:  _utmb
Typical Content: randomly generated number
Expires: 30 minutes

Name:  _utmc
Typical Content: randomly generated number
Expires: when the user exits the browser

Name: _utmz
Typical Content: randomly generated number, plus information on how the site was reached (for example, directly, via a link or through organic search)
Expires: 6 months

Other considerations

There are other web controls that we offer – such as Facebook controls and the tweet this control – which embed an external iFrame into a page. These sites could therefore set cookies on a client's machine. We have performed some testing and could not see cookies being set, but this could change in the future and would be out of our control.

You must also take any bespoke development you have carried out or custom code you have used in your templates into consideration. If you have implemented functionality such as a JQuery plugin or social bookmarks, you may find that these uses cookies.