Cookie Policy
01
Cookies are small text files which a website may put on your computer or mobile device when you first visit a site or page. The cookie will help the website, or another website, to recognise your device the next time you visit. We use the term “cookies” in this policy to refer to all files that collect information in this way.
There are many functions cookies serve. For example, they can help us to remember your preferences, analyse how well the Website is performing, or even allow us to recommend content we believe will be most relevant to you.
Certain cookies contain personal information. Most cookies will not collect information that identifies you, but will instead collect more general information such as how users arrive at and use the Website.
02
Generally, our cookies perform up to four different functions:
Some cookies are essential for the operation of the Website. If you opt to disable these cookies, you will not be able to access or use all of the features that the Website incorporates.
We utilise other cookies to analyse how our visitors use the Website and to monitor performance. This allows us to provide a high quality experience by customising our offering and quickly identifying and fixing any issues that arise. For example, we might use performance cookies to keep track of which pages are most popular, which method of linking between pages is most effective, and to determine why some pages are receiving error messages.
We use functionality cookies to allow us to remember your preferences, such as your customisation preferences.
We use targeting cookies in order to be able to deliver targeted advertising.
03
We do use or allow third parties to serve cookies that fall into the three categories above. For example, like many companies, we use third party analytic tools to help us monitor our traffic. We may also use third party cookies to help us with market research, revenue tracking, improving site functionality and monitoring compliance with our terms and conditions and copyright policy.
04
As we have explained above, cookies help you to get the most out of the Website.
However, if you do wish to disable cookies then you can do so by amending the settings within your browser or mobile device.
Please remember that if you do choose to disable cookies, you may find that certain sections of the website do not work properly.
05
Please see below for a full list of the cookies used on this website.
More detail on how businesses use cookies generally is available at www.allaboutcookies.org. If you have any queries regarding this Cookie Policy please contact us by email at data@thehox.com.
| Cookie | Duration | Description |
|---|---|---|
| Set by The Hoxton | ||
| CookieDisclaimer | 29 days | Stores the user’s cookie consent state for the main website. |
| CookieConsent | 1 year | Stores the user’s cookie consent state for the booking engine. |
| location[property] e.g. locationChicago | 29 days | Used to personalise content on the homepage based on user behaviour. |
| theme-ui-color-mode | persistent | Remembers the user’s preferences for font size and colours on the booking engine. |
| Set by Google | ||
| _dc_gtm_UA-[googleAnalyticsId] | 365 days | Google Tag Manager, injects other Google Analytics cookies for tracking purposes |
| _ga | 365 days | Used to identify user for tracking purposes |
| _gali | 365 days | Used for Enhanced Link Attribution https://developers.google.com/analytics/devguides/collection/analyticsjs/enhanced-link-attribution |
| _gat | 365 days | Used to throttle request rate by Google to not make too many requests to their doubleclick.net server during tracking. https://developers.google.com/analytics/devguides/collection/analyticsjs/display-features |
| _gid | 365 days | Used to identify user for tracking purposes. |
| collect | session | Used to send data to Google Analytics about the visitor’s device and behaviour. Tracks the visitor across devices and marketing channels. |
| ads/ga-audiences | session | Used to send data to Google Analytics about the visitor’s device and behaviour. Tracks the visitor across devices and marketing channels. |
| _gcl_au | 3 months | Used by Google AdSense for experimenting with advertisement efficiency across websites using their services. |
| Set by DoubleClick.net (Google Advertising Platform) | ||
| test_cookie | 1 day | Used to check if the user’s browser supports cookies. |
| pagead/landing | session | Collects data on visitor behaviour from multiple websites, in order to present more relevant advertisement – This also allows the website to limit the number of times that they are shown the same advertisement. |
| ARRAAffinity | session | Used for load balancing to minimise site response time |
| Set by Trip Tease (tech platform for hotels) | ||
| triptease-identity-data | 365 days | Used to understand user behaviour. |
| pf-api-key | session | Used to uniquely identify hotels and sharing this data amongst TripTease applications. |
| pf-ticket-id | session | Used for conversion tracking and sharing this data amongst TripTease applications. |
| triptease-conversion | 7 days | Used to understand user behaviour. |
| triptease-session-id | 1 day | Used to identify the visitor upon re-entry to the website. |
| triptease-user-id | 1 year | Used to identify the visitor upon re-entry to the website. |
| triptease.integration.previous-pages | session | Collects information on search criteria for relevant promotions and advertisements. |
| tt_message_engine_latest_visit_info | persistent | Determines which product the user has viewed, for advertising purposes. |
| tt-domain-user-id | persistent | Collections information on user behaviour on multiple websites. This is used to optimize the relevance of advertising messages. |
| triptease-anonymous-id | persistent | Used to identify the visitor upon re-entry to the website. |
| triptease-experiments | 5 years | Used to categorise users for AB tests. |
| Set by Hotjar (user behaviour tracking) | ||
| _hjid | 365 days | Hotjar cookie that is set when the customer first lands on a page with the Hotjar script. It is used to persist the Hotjar User ID, unique to that site on the browser. This ensures that behaviour in subsequent visits to the same site will be attributed to the same user ID. |
| _hjRecordingLastActivity | session | This should be found in Session storage (as opposed to cookies). This gets updated when a visitor recording starts and when data is sent through the WebSocket (the visitor performs an action that Hotjar records). |
| _hjTLDTest | session | When the Hotjar script executes we try to determine the most generic cookie path we should use, instead of the page hostname. This is done so that cookies can be shared across subdomains (where applicable). To determine this, we try to store the _hjTLDTest cookie for different URL substring alternatives until it fails. After this check, the cookie is removed. |
| _hjUserAttributesHash | session | User Attributes sent through the Hotjar Identify API are cached for the duration of the session in order to know when an attribute has changed and needs to be updated. |
| _hjCachedUserAttributes | session | This cookie stores User Attributes which are sent through the Hotjar Identify API, whenever the user is not in the sample. These attributes will only be saved if the user interacts with a Hotjar Feedback tool. |
| _hjLocalStorageTest | under 100ms | This cookie is used to check if the Hotjar Tracking Script can use local storage. If it can, a value of 1 is set in this cookie. The data stored in_hjLocalStorageTest has no expiration time, but it is deleted almost immediately after it is created. |
| _hjIncludedInPageviewSample | 30 minutes | This cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by your site’s pageview limit. |
| _hjIncludedInSessionSample | 30 minutes | This cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by your site’s daily session limit. |
| _hjAbsoluteSessionInProgress | 30 minutes | This cookie is used to detect the first pageview session of a user. This is a True/False flag set by the cookie. |
| _hjFirstSeen | session | This is set to identify a new user’s first session. It stores a true/false value, indicating whether this was the first time Hotjar saw this user. It is used by Recording filters to identify new user sessions. |
| _hjViewportId | session | This stores information about the user viewport such as size and dimensions. |
| _hjRecordingEnabled | session | This is added when a Recording starts and is read when the recording module is initialised to see if the user is already in a recording in a particular session. |
| Set by Facebook (advertising) | ||
| _fbp | 3 months | Used by Facebook to deliver a series of ad products such as real time bidding from third party advertisers. |
| fr | session | Used by Facebook to deliver a series of ad products such as real time bidding from third party advertisers. |
| tr | session | Used by Facebook to deliver a series of ad products such as real time bidding from third party advertisers. |
| Set by Optimand (web analytics and business intelligence tool) | ||
| four_pc_cache | session | This cookie is used to load Optimand’s scripts, improving loading times and general performances. |
| four_ref_cache | session | This cookie is used to track users’ main referrals. It does not contain any personal data about the user. |
| four_returning | 60 days | This cookie tracks information about the number of visits with a duration of 60 days. |
| fourCache | 1 hour | This cookie is used to improve the user experience during the booking process. It will not contain any user’s data and only lasts for the duration of your visit, being deleted as soon as you close your web browser. |
| Set by Stripe (payments system on booking engine) | ||
| __stripe_mid | 1 year | This cookie is necessary for making credit card transactions on the website. The service is provided by Stripe.com which allows online transactions without storing any credit card information. |
| __stripe_sid | 1 day | This cookie is necessary for making credit card transactions on the website. The service is provided by Stripe.com which allows online transactions without storing any credit card information. |
| M | 2 years | This cookie is necessary for making credit card transactions on the website. The service is provided by Stripe.com which allows online transactions without storing any credit card information. |
Still Got a Question?
If you haven’t found the answer you need, fill out the enquiry form and we’ll get back to you as soon as possible.
