Imperial Engineering Cookies Policy

This website uses Google Analytics to help analyse how visitors view this website. By using this website and agreeing to this policy, you consent to Imperial Engineering’s use of cookies in accordance with the terms of this policy.

A cookie is a file containing an identifier (a string of letters and numbers) that is sent by a web server to a web browser and is stored by the browser. The information is then sent back to the server each time the browser requests a page from the server. This enables a web server to identify and track web browsers.

There are two main kinds of cookies: session cookies and persistent cookies. Session cookies are deleted from your computer when you close your browser, whereas persistent cookies remain stored on your computer until deleted, or until they reach their expiry date.

Why does Imperial Engineering use cookies?

When visiting www.imperialengineering.co.uk, we collect standard cookie information so we can track visitor behaviour patterns. We do this to monitor how users visit or how long visitors spend in different parts of the site. This helps us to improve our web site and to plan our future work.

How can I delete and block cookies?

Most modern web browsers give you some control over cookies. You can set your web browser to accept or reject all cookies or to accept or reject specific cookies. You may also be able to set your browser to alert you every time a cookie is offered.

You can find out how to control and delete cookies on AboutCookies.org.

We use both session and persistent cookies on our website. The names of the cookies that we use on our website, and the purposes for which they are used, are set out below:

Cookie NameDefault Expiration TimeDescription
__utma2 years from set/updateUsed 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.
__utmb30 mins from set/updateUsed 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.
__utmcEnd of browser sessionNot 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.
__utmz6 months from set/updateStores 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.
__utmv2 years from set/updateUsed 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.