Privacy
Cookie policy
Please read this cookie policy (“cookie policy”, “policy”) carefully before using the Eddington Cambridge (www.eddington-cambridge.co.uk) website (“website”, “service”) operated by the University of Cambridge (“us”, ‘we”, “our”). For the University of Cambridge’s full Cookie Policy please click here.
What are cookies?
Cookies are simple text files that are stored on your computer or mobile device by a website’s server. Each cookie is unique to your web browser. It will contain some anonymous information such as a unique identifier, website’s domain name, and some digits and numbers.
What types of cookies do we use?
Necessary cookies
Necessary cookies allow us to offer you the best possible experience when accessing and navigating through our website and using its features. For example, these cookies let us recognize that you have created an account and have logged into that account.
Functionality cookies
Functionality cookies let us operate the site in accordance with the choices you make. For example, we will recognize your username and remember how you customized the site during future visits.
Analytical cookies
When you visit our website, we use the third-party Google Analytics service to collect standard internet log information, which includes your IP address. We do this to find out how visitors use our website and to improve its usability. The data is anonymised before it is stored and before we see or use it for analytics processing. We do not make, and do not allow Google to make, any attempt to find out the identities of those visiting our site. For more information about how Google Analytics uses this information, please see the Google privacy policy.
Marketing Preferences
Third-party services that we embed on some of our webpages – such as Instagram feeds, Twitter feeds and YouTube videos – may set cookies to measure how you use their services and record what advertising you see during your use of their service.
| Cookie | Name | Default Expiration Time | Description | More Information |
| Google Analytics | __utma | 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. | Link here |
| Google Analytics | __utmt | 10 minutes | Used to throttle request rate. | Link here |
| Google Analytics | __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. | Link here |
| Google Analytics | __utmc | 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. | Link here |
| Google Analytics | __utmz | 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. | Link here |
| Google Analytics | __utmv | 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. | Link here |
| YouTube | PREF | 1 year | Stores information such as a user’s preferred page configuration and playback preferences like autoplay, shuffle content, and player size. | Link here |
| YouTube | VISITOR_INFO1_LIVE | 6 months | Stores information such as a user’s preferred page configuration and playback preferences like autoplay, shuffle content, and player size. | Link here |
| YouTube | YSC | End of session | This period shows the length of the period at which a service can store and/or read certain data from your computer by using a cookie, a pixel, an API, cookieless tracking, or other resources. | Link here |
| _ga guest_id lang personalization_id eu_cn |
Up to 2 years | Embedded Twitter feeds may appear on selected web pages. Where a feed is present, Twitter uses both session cookies and persistent cookies to understand how you interact with its services, to monitor aggregate usage patterns, and to personalise and otherwise operate its services. Its use of cookies is also for the provision of account security, personalisation of the content it shows you including advertisements, and to remember your language preferences. | Link here | |
| csrftoken ig_cb mid |
Up to 2 months | Photography from Instagram accounts may appear on selected web pages. Where an Instagram post does feature on our website, Instagram uses cookies to: show you related and relevant content, improve your experience, and help protect Instagram and its users. | Link here |
How to delete cookies?
If you want to restrict or block the cookies that are set by our website, you can do so through your browser setting.
Below are links to information about popular web browsers and how to block cookies using them.
Other web browsers – see the Information Commissioner’s Office’s website
Contacting us
If you have any questions about this policy or our use of cookies, please contact us.