Royal Brompton & Harefield Hospitals Education
COOKIES POLICY
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.
A cookie is a small file of letters and numbers that we store on your browser or the hard drive of your computer if you agree. Cookies contain information that is transferred to your computer’s hard drive.
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, use a shopping cart or make use of e-billing services.
Analytical or performance cookies. These 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 (for example, your choice of language or region).
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:
| WordPress cookies |
|---|
| Name of cookie | Purpose | Expiry |
|---|---|---|
|
wordpress_[hash] |
This is used to store the authentication details on login. The authentication details include the username and double hashed copy of the password. This usage of the cookie is limited to the admin console area, the back-end dashboard of the website. This cannot be seen on the front-end of the website, even when logged in. |
At the end of a user session. |
|
wordpress_logged_in_[hash] |
The is used to indicate when you are logged in, and who you are. This cookie is maintained on the front-end of the website as well as when logged in. Here [hash] represents the value that is obtained by applying a specific mathematical formula applied to the username and password. This is to ensure that the input values are safe and no one can access these data using the cookies. |
At the end of a user session. |
|
wp-settings-{time}-[UID] |
This is used to customise the view of your admin interface and the front-end of the website. The value represented by [UID] is the individual user ID of the user as given to them in the user’s database table. |
At the end of a user session. |
|
wordpress_test_cookie |
This is used to check if the cookies are enabled on the browser to provide an appropriate user experience to the users. |
At the end of a user session. |
| WooCommerce cookies |
|---|
| Name of cookie | Purpose | Expiry |
|---|---|---|
|
woocommerce_cart_hash |
This helps determine when cart contents/data changes. |
At the end of a user session. |
|
woocommerce_items_in_cart |
This determines when cart contents/data changes. |
At the end of a user session. |
|
wp_woocommerce_session_ |
This contains a unique code for each customer so that it knows where to find the cart data in the database for each customer. Its duration is 2 days. |
2 days. |
|
woocommerce_recently_viewed |
This powers the ‘Recent Viewed Products’ widget. |
At the end of a user session. |
|
store_notice[notice id] |
This allows customers to dismiss the Store Notice. |
At the end of a user session. |
|
woocommerce_snooze_suggestions__[suggestion] |
This allows dashboard users to dismiss Marketplace suggestions, if enabled. |
2 days. |
|
woocommerce_dismissed_suggestions__ |
This stores a count of Marketplace suggestion dismissals, if enabled. |
1 month. |
|
tk_ai |
This stores a randomly-generated anonymous ID. This is only used within the dashboard (/wp-admin) area and is used for usage tracking, if enabled. |
At the end of a user session. |
Please note that the following third parties may also use cookies, over which we have no control. These named third parties may include, for example, advertising networks and providers of external services like web traffic analysis services. These third party cookies are likely to be analytical cookies or performance cookies or targeting cookies:
| Name of cookie | Purpose | Expiry |
|---|---|---|
|
_ga |
This Cookie is placed by Google. It enables us to learn information about our user’s use of the web site such as the time of visit, the pages viewed, whether the user has visited before and the web site visited prior to visiting the our web site. |
2 years. |
| Name of cookie | Purpose | Expiry |
|---|---|---|
|
fbevents.js |
This Cookie is placed by Facebook. It enables us to measure, optimise and build audiences for advertising campaigns served on Facebook. In particular, it enables Metia to see how our users move between devices when accessing our web site and Facebook, to ensure that our Facebook advertising is seen by our users most likely to be interested in such advertising, by analysing which content a user has viewed and interacted with on the our web site. |
180 days. |
| Name of cookie | Purpose | Expiry |
|---|---|---|
|
LC1 |
This Cookie is placed by LinkedIn. It enables us to measure, optimise and build audiences for advertising campaigns served on LinkedIn. In particular it enables us to see how our users move between devices when accessing our web site and LinkedIn, to ensure that our LinkedIn advertising is seen by our users most likely to be interested in such advertising, by analysing which content a user has viewed and interacted with on our web site. |
2 years. |
You can restrict or deactivate cookies within the settings of your browser:
If your browser is not listed here, here is guidance for other browsers.