Cookie policy

Megaphone

Information about our use of cookies

Our website uses cookies to distinguish you from other users of our website. This helps us to provide you with a good experience when you browse our website and also allows us to improve our site. By continuing to browse the site, you are agreeing to our use of cookies.

A cookie is a small text file that is downloaded onto ‘terminal equipment’ (e.g. a computer or smartphone) when the user accesses a website. It allows the website to recognise that user’s device and store some information about the user’s preferences or past actions.

We use the following cookies:

  • Strictly necessary cookies. These are cookies that are required for the operation of our website. They include, for example, cookies that enable you to log into secure areas of our website.
  • Analytical/performance cookies. They allow us to recognise and count the number of visitors and to see how visitors move around our website when they are using it. This helps us to improve the way our website works, for example, by ensuring that users are finding what they are looking for easily.
  • Functionality cookies. These are used to recognise you when you return to our website. This enables us to personalise our content for you, greet you by name and remember your preferences.
  • Targeting cookies. These cookies record your visit to our website, the pages you have visited and the links you have followed. We will use this information to make our website and the advertising displayed on it more relevant to your interests. We may also share this information with third parties for this purpose.

You can find more information about the individual cookies we use and the purposes for which we use them in the table below.

Cookie

Name

Purpose

More information

DoubleClick

test_cookie

Permission testing.

Read more

 

IDE

Advertising cookie.

Read more

       

Google Analytics

__utma

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 and expires 2 years from set up/update.

Read more

 

__utmb

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 and expires after 30 mins from set up/update.

Read more

 

__utmc

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. Expires after End of browser session.

Read more

 

__utmt

Used to throttle request rate. Expires after 10 minutes.

Read more

 

__utmv

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 is also used for the deprecated _setVar method. The cookie is updated every time data is sent to Google Analytics and expires after 2 years from set up/update.

Read more

 

__utmz

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 and expires after 6 months from set up/update.

Read more

 

_ga

Used to distinguish users and expires after 2 years.

 

Read more

 

_gat

Used to throttle request rate. Expires after 1 minute.

 

Read more

 

_gid

Used to distinguish users. Expires after 24 hours.

 

Read more

       

IQ-EQ

cookie-agreed

Defines whether a visitor has accepted our cookie policy

 

 

SESSION COOKIE

Functional cookie to allow site administrators to keep persistent log-ins.

 

 

 

 

 

Hubspot

hsfirstvisit

This cookie is used to keep track of a user's first visit. It expires after 10 years.

Read more

 

__hssc

Cookie for keeping track of sessions. This is used to determine if we should increment the session number and timestamps in the __hstc cookie. It contains: the domain, viewCount (it increments each pageView in a session), session start timestamp.

It expires after 30 minutes.

Read more

 

__hssrc

Whenever HubSpot changes the session cookie, this cookie is also set. We set it simply to the value "1", and use it to determine if the user has restarted their browser. If this cookie does not exist when we manage cookies, we assume it is a new session.

(Expires: None. Session cookie)

Read more

 

__hstc

The main cookie for tracking visitors. It contains: the domain, utk (see below), initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session)

It expires after 2 years.

Read more

 

hubspotuk

This cookie is used to keep track of a visitor's identity. This cookie is passed to HubSpot on form submission and used when de-duplicating contacts.

It expires after 10 years.

Read more

 

 

 

 

Vimeo

Vuid

Vimeo cookie

Read more

 

__utma

Google Analytics cookie

Read more

 

__utmb

Google Analytics cookie

Read more

 

__utmc

Google Analytics cookie

Read more

 

__utmt_player

 

Read more

 

__utmv

Google Analytics cookie

Read more

 

__utmz

Google Analytics cookie

Read more

 

GCLB

CDN Load Balancer settings
It expires when browser ends.

Read more

Please note that third parties (including, for example, advertising networks and providers of external services like web traffic analysis services) may also use cookies, over which we have no control. These cookie are likely to be analytical/performance cookies or targeting cookies.

You can block cookies by activating the setting on your browser that allows you to refuse the setting of all or some cookies. However, if you use your browser settings to block all cookies (including essential cookies) you may not be able to access all or parts of our website.