Cookie policy

1. Our Cookie Policy

JHI respects the privacy of all visitors to our website. This Cookie Policy outlines our policy concerning the use of cookies on our website. We may update our Cookie Policy to reflect any changes in technology or data protection law. Our Cookie Policy will always be available from our website. JHI only uses cookies which are strictly necessary to allow you to access our website, to move between pages and to receive services which you have requested.

2. What are cookies

Cookies are small data files placed on your computer or internet enabled device by websites in order to add functions and help it work better. A cookie can be used to identify your computer or internet device to our website, or to other third-party websites. This allows us to improve the way we work, such as remembering preferences expressed by you or tracking your use of a website for statistical analysis and advertising.

3. Cookies on the JHI website

The only cookies installed by JHI on your device when you visit our website are  the ones used by Google Analytics, please see here for reference.

In summary, Google Analytics is a simple, easy-to-use tool that helps website owners measure how users interact with website content. As a user navigates between web pages, Google Analytics provides website owners JavaScript tags (libraries) to record information about the page a user has seen, for example the URL of the page. The Google Analytics JavaScript libraries use HTTP Cookies to “remember” what a user has done on previous pages / interactions with the website.

Google Analytics supports three JavaScript libraries (tags) for measuring website usage: gtag.js, analytics.js, and ga.js. The following sections describe how each use cookies.

gtag.js and analytics.js – cookie usage

The analytics.js JavaScript library is part of Universal Analytics and uses first-party cookies to:

  • Distinguish unique users
  • Throttle the request rate

gtag.js and analytics.js set the following cookies:

Cookie NameFunctionRetention period
_gaUsed to distinguish users2 years
_gidUsed to distinguish users24 hours
_gat or  _dc_gtm_<property-id>Used to throttle request rate1 minute
AMP_TOKENContains a token that can be used to retrieve a Client ID from AMP Client ID service. Other possible values indicate opt-out, inflight request or an error retrieving a Client ID from AMP Client ID service30 seconds to 1 year
_gac_<property-id>Contains campaign related information for the user90 days

ga.js – cookie usage

The ga.js JavaScript library uses first-party cookies to:

  • Determine which domain to measure
  • Distinguish unique users
  • Throttle the request rate
  • Remember the number and time of previous visits
  • Remember traffic source information
  • Determine the start and end of a session
  • Remember the value of visitor-level custom variables

By default, this library sets cookies on the domain specified in the ‘document.host’ browser property and sets the cookie path to the root level (/).

This library sets the following cookies

Cookie NameFunctionRetention period
__utmaUsed 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
__utmtUsed to throttle request rate.10 minutes
__utmbUsed 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
__utmcNot used in ga.js. Set for interoperability with urchin.js. Historically, this cookie operated in conjunction with the __utmb cookie to determine whether the user was in a new session/visit.End of browser session
__utmzStores 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 Analytics6 months from set/update
__utmvUsed to store 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 Analytics2 years from set/update

Managing and disabling cookies

If you do not want your browser to accept cookies, turn off the cookie acceptance option here [insert hyperlink].

For more information about cookies, please see here.