Cookies | Middlesex University London
Section navigation

Cookies

This policy explains what information we gather when you visit the Middlesex University website, and explains how that information is used.

It is important for you to appreciate that the website contains extensive links to and from other independent third-party sites, both within the University and elsewhere. This policy covers the central website, represented by URLs starting www.mdx.ac.uk. You will need to consult the appropriate information on other sites for information on their policies. Middlesex University is not responsible for any cookies that may be set by third party websites that are linked to from pages on this site.

Data collected

In common with most websites, this site automatically logs certain information about every request made of it (see below for more details). This information is used for system administration, for bug tracking, and for producing usage statistics.

We may collect and process the following data about you:

  • Information that you provide by filling in forms provided on this website for a specific purpose. By supplying this information you are consenting to the University holding and using it for the purposes for which it was provided.
  • If you contact us, we may keep a record of that correspondence.

Logged data

The following data is automatically collected for each request:

  • The name or network address of the computer making the request. Note that under some (but not all) circumstances it may be possible to infer from this the identity of the person making the request. Note also that the data recorded may be that of a web proxy rather than that of the originating client
  • The date and time of connection
  • The HTTP request, which contains the identification of the document requested
  • The status code of the request (success or failure etc.)
  • The number of data bytes sent in response
  • The contents of the HTTP Referrer header supplied by the browser
  • The content of the HTTP User-Agent header supplied by the browser

Logging of additional data may be enabled temporarily from time to time for specific purposes.

In addition, the computers on which the website is hosted keep records of attempts (authorised and unauthorised) to use them for purposes other than access to the web server. This data typically includes:

  • the date and time of the attempt;
  • the service to which access was attempted;
  • the name or network address of the computer making the connection; and
  • and may include details of what was done or was attempted to be done.

Personal data

Information about the University's use of personal data is available in our privacy policy.

Cookies

This website uses cookies, which are small pieces of information that are issued to your computer or other internet-enabled device when you visit the website. Cookies are stored by your browser and hard drive and are used to distinguish you from other visitors to the site.

The web browsers of most computers are set up to accept cookies. You can enable your web browser to disable cookies or prompt you when a website is attempting to add a cookie. You can also delete cookies that have previously been added to your computer's cookie file. Please visit the Information Commissioner's Office website to find out how to disable and delete cookies.

Cookies used on this website

TypeNamePurpose
Session cookies announcement_info  Information if user close announcement window 
  cookies_info Information if user accepts cookies
  pages Information about saved pages
  SQ_SYSTEM_SESSION  Automatically generated by Matrix lzZf
Google Analytics ga Used to distinguish users.
  _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.
 

_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.
  _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.
  _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.
  _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 was also used for the deprecated _setVar method. The cookie is updated every time data is sent to Google Analytics.

Google Maps

PREF
NID

Google used these to track how many people are using their maps, which appear on our location pages.

SiteImprove Analytics

nmstat

Persistent – expires after 1000 days. This cookie is used to help record the visitor’s use of the website.
It is used to collect statistics about site usage such as when the visitor last visited the site.
This information is then used to improve the user experience on the website. This Siteimprove Analytics cookie contains a randomly generated ID used to recognise the browser when a visitor reads a page.
The cookie contains no personal information and is used only for web analytics.

Cookies outside of our mdx.ac.uk domain

 

Name

Purpose

Information

DoubleClick by Google

id

Google uses these cookies to improve your online experience, while tracking ad response rates to improve the effectiveness of online advertising on external websites.

Read the overview of advertising and privacy at Google.

Session cookie

siteimproveses

SiteImprove uses this cookie to track the sequence of pages a visitor looks at during a visit to the site. This information can be used to reduce user journeys, and enable visitors to find relevant information quicker.

Read more about SiteImprove Analytics.

In this section

Back to top

We use Cookies

View our Privacy and Cookie policy

Continue