Cookie Policy

In addition to the information which you supply to us, information and data may be automatically collected through the use of cookies. Cookies are small text files employed on the Site to recognise repeat users and allow us to observe behaviour and compile aggregate data in order to improve the Site for you. For example, cookies will tell us whether you viewed the Site with sound or with text on your last visit. Cookies also allow us to count the number of unique and return visitors to our Site.  Some of our associated companies may themselves use cookies on their own websites. We have no access to, or control of these cookies, should this occur.

Cookies may be either “persistent” cookies or “session” cookies. A persistent cookie consists of a text file sent by a web server to a web browser, which will be stored by the browser and will remain valid until its set expiry date (unless deleted by the user before the expiry date). A session cookie, on the other hand, will expire at the end of the user session, when the web browser is closed.

The law states that we can store cookies on your machine if they are essential to the operation of the Site, but that for all others we need your permission to do so.

The list below explains the cookies we use and why:

Analytics And performance cookies

Google Analytics

We use Google Analytics to optimise the site

_ga

Lasts 2 years. Used to distinguish users.

_gid

Lasts 24 hours. Used to distinguish users.

_gat

Lasts 1 minute. Used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_<property-id>.

AMP_TOKEN

Lasts 30 seconds to 1 year. Contains 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 service.

_gac_<property-id>

Lasts 90 days. Contains campaign related information for the user. 

__utma

Lasts 2 years from set/update. 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.

__utmt

Lasts 10 minutes. Used to throttle request rate.

__utmb

30 mins from set/update. 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.

__utmc

Lasts until the end of browser session. Not 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.

__utmz

Lasts 6 months from set/update. 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.

__utmv

Lasts 2 years from set/update. Used 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 Analytics.

Controlling the use of cookies

Most web browsers are set to accept cookies by default. If you do not wish to receive cookies from us or any other website, you should be able to turn cookies off on your web browser: please follow your browser provider’s instruction in order to do so.  Unfortunately, we cannot accept liability for any malfunctioning of your PC or its installed web browser as a result of any attempt to turn off cookies. Please note that if you choose to remove or reject cookies, this could affect the availability and functionality of our Services.

To find out more about cookies, including how to see what cookies have been set and how to manage and delete them, visit www.aboutcookies.org or www.allaboutcookies.org.