Cookies policy
Current cookies
Please by aware that the providers listed below may change their cookie names without notice. As an example, we use the following cookies on our website:
Cookie: Google Analytics Example name: _utma, _utmb, _utmc, _utmz, GAPS, LSID, LSOSID, OTZ
Purpose: These cookies are used to collect information about how visitors use our site, which we use to help improve it. The cookies collect information in an anonymous form, including the number of visitors to the site, where visitors have come to the site from and the pages they visited. These cookies may also be identified as originating from england.nhs.uk More information about Google cookies.
Cookie: www.google.com (Google embedded search) Example name: __utmx, __utmxx, APISID, HSID, NID, PREF, SAPISID, SID, SSID
Purpose: These cookies are used to collect information about how visitors use our site, which we use to help improve it. The cookies collect information in an anonymous form, including the number of visitors to the site, where visitors have come to the site from and the pages they visited and what they have searched for. More information about Google cookies.
Cookie: www.events.england.nhs.uk Example name: PHPSESSID
Purpose: To track visitor information and for security authentication.
Embedded content
We want to provide interesting and engaging content on our website. On a number of pages we use ‘plug-ins’ or embedded media. For example, we embed YouTube videos in many pages. We also provide links to share content with popular social media sites such as LinkedIn, Facebook and Twitter.
The suppliers of these services may also set cookies on your device when you visit the pages where we have used this type of content. These are known as ‘third-party’ cookies. Third party cookies are delivered on behalf of their respective organisations and as such they may change their name and purpose from the cookies identified below, this is beyond the control of Homerton Hospitals NHS Foundation Trust.
Cookie: Ustream Example name: ab_test_1, ab_test_2, locale, optimizelyBuckets, optimizelyEndUserId, optimizelySegments, uTrack, ul, ustream-guest, _qca, PHPSESSID
Purpose: Used to enable certain features of the services, to better understand how you interact with the services in-order to deliver a better service. Also used to monitor aggregate usage by users and monitor web traffic on the service. More information about Ustream cookies.
Cookie: scorecardresearch.com Example name: UID, UIDR
Purpose: Used by Ustream video streaming (as described above), to better understand how you interact with their services in-order to deliver a better service. Also used to monitor aggregate usage by users and monitor web traffic on the service. More information about scoreandsearch.com cookies.
Cookie: YouTube Example name: PREF, VISITOR_INFO1_LIVE, use_hitbox
Purpose: To track visitor views, and to remember user preferences when viewing YouTube videos embedded in our website web pages. More information about YouTube cookies.
Cookie: Twitter Example name: guest_id, remember_checked, remember_checked_on, secure_sessions, twll
Purpose: To track visitor information and for security authentication. More information about Twitter cookies.
Cookie: LinkedIn Example name: csrftoken, L1e, visit, PHPSESSID
Purpose: To track visitor information and for security authentication. More information about LinkedIn cookies.
How to control and delete cookies
We will not use cookies to collect personally identifiable information about you.
However, if you wish to restrict or block the cookies which are set by our websites, or indeed any other website, you can do this through your browser settings. The ‘Help’ function within your browser should tell you how.
Alternatively, you may wish to visit www.aboutcookies.org which contains comprehensive information on how to do this on a wide variety of browsers. You will also find details on how to delete cookies from your machine as well as more general information about cookies.
Please be aware that restricting cookies may impact on the functionality of our website.
If you wish to view your cookie code, just click on a cookie to open it. You’ll see a short string of text and numbers. The numbers are your identification card, which can only be seen by the server that gave you the cookie.
For information on how to do this on the browser of your mobile phone you will need to refer to your handset manual.
To opt-out of third-parties collecting any data regarding your interaction on our website, please refer to their websites for further information.