With this cookie policy, we would like to explain what cookies and cookie-like technologies are, how we and other service provider use them on this website, what information they collect, for how long and for what purposes we use them.
Table of contents
- Controller of the website
- Addition to the privacy policy
- What are cookies and similar technologies?
- What is the legal basis for setting/reading cookies?
- What rights does the website visitor have?
- How to manage cookies in a browser?
- What types of cookies exist?
- Who can set cookies on this website?
- Which cookies are used on this website?
Controller of the website
- Provider: Schwollbachhof, Hauptstraße 48, 55767 Schwollen, Germany
- Email: info@schwollbachhof.de
- Phone: +49 157 56642802
- Contact form: schwollbachhof.de/en/contact/
Addition to the privacy policy
This cookie policy is a supplement to this website's privacy policy. The cookie policy specifies how a website uses cookies and what data it collects through them, while the privacy policy is a more comprehensive overview of all data processing activities on the website and beyond.
What are cookies and similar technologies?
Cookies are small pieces of information similar to text files that can be stored and read on the end device. They serve various purposes, including maintaining basic functionalities of the website, security and privacy, providing optional functions of the website, collecting statistic data on visitor flows and providing marketing systems. Practical examples of what can be stored in cookies are the storage of login status in user accounts, the content of shopping baskets in e-commerce platforms, or a user ID for tracking behavior on the website.
The information can technically be stored in various ways. The best-known examples of this are HTTP cookies and cookie-like technologies like local storage, session storage or IndexedDB. Each type of storage has different properties, which determine the technical handling, accessibility and controllers authorized to access the information. All these types of storage are usually summarized under the term "cookies" and are therefore called as such in this cookie policy.
What is the legal basis for setting/reading cookies?
The setting and reading of cookies in the European Union (EU) and the European Economic Area (EEA) is in accordance with Art. 5 (3) ePrivacy Directive and Recital 66 ePrivacy Directive only permitted if a user has given his consent on the basis of comprehensive information about the purposes of the processing. The website operator may also set cookies if they are strictly necessary to provide you as a user with the expressly requested service, e.g. the basic content of this website or other strictly necessary cookies for basic functionality of the website to be displayed to you without your consent.
What rights does the website visitor have?
Services and their cookies can be set and read on the legal basis of your consent or a legitimate interest. When you first visited this website, you were asked for your consent and you had the opportunity to object to the use of certain services. We explained which legal basis is used for which service in our consent dialog.
You have the right to view the history of your decisions, change your privacy settings, object to the use of services and revoke your consent at any time. Below you find possibilities to exercise your rights:
How to manage cookies in a browser?
- How to remove cookies in a browser: To remove cookies from your device, you can clear the browsing data in the settings of your browser. This action will remove all cookies from all websites you've visited, potentially including saved login details and site preferences. In some browsers, you can just delete the cookies and similar data without deleting the whole browsing history.
- How to control cookies in a browser: For more granular control over cookies specific to certain websites, navigate to the privacy and cookie settings within your used browser. Here, you can adjust preferences related to individual sites' cookie usage.
- How to block cookies in a browser: It's possible to configure most modern browsers in their settings to block all cookies from being placed on your device. But blocking cookies could lead to certain services and functionalities not functioning correctly, e.g. logins as a user. You can also use extensions for many browsers which can block the setting of cookies on websites.
- How to manage cookies on this website: To tailor your preferences regarding cookies on this website, you can change your preferences at any time by clicking on the link in the section "Rights of the website visitor".
You can find more information on the handling of cookies devowl.io/rcb/cookie-handling/.
What types of cookies exist?
- Essential cookies are indispensable for the basic functionality of a website and enable functions such as saving login information or access to secure areas of the site. These include, for example, security cookies, which can identify a bot that is not wanted on the website by storing an authentication key in a cookie.
- Functional cookies improve the user experience by storing information and preferences such as language settings or appearance settings of the website to provide personalized. This includes, for example, preference cookies that store the user's preferred video quality on a website.
- Statistics cookies collect data about the use of a website to gain insights into user behavior and optimize the performance of the site. This includes, for example, a randomly assigned user ID that makes it possible to attribute whether you have visited a subpage of the website.
- Marketing cookies are used to track user behavior across different websites and to display personalized advertising based on the interests and surfing behavior of users. This includes, for example, advertising cookies that store an interaction with an advertisement on the website and pass it on to advertisers or a chat system for pre-sale questions and customer support.
Who can set cookies on this website?
On this website, both the operator of the website and third-party services which are used on this website may set cookies and access its content. Who can access which cookies and their content differs between first-party and third-party cookies. First-party cookies are created by the visited website and can only be read by the website operator and integrated third-party services on this website. Third-party cookies are set by usually third-party services on other domains, can be read on all websites on which the service that controls the domain is embedded and, for example, used by advertising networks to track user behavior across different websites and offer personalized advertising.
Which cookies are used on this website?
| Category | Technical cookie name | Technical cookie host | Service | Duration | Type | Purpose |
|---|---|---|---|---|---|---|
| Essential | wfwaf-authcookie-* | schwollbachhof.de | Wordfence | 12 months | HTTP Cookie | Authentifizierungs-Token, um eingeloggte Benutzer zu erkennen und damit die Firewall zu entlasten |
| Essential | wf_loginalerted_* | schwollbachhof.de | Wordfence | 12 months | HTTP Cookie | Eindeutiger Wert, um Anmeldungen und verdächtige Anmeldeaktivitäten von neuen Geräten oder unbekannten Standorten zu erkennen |
| Essential | wfCBLBypass | schwollbachhof.de | Wordfence | 12 months | HTTP Cookie | Eindeutiger Wert, der es Nutzern ermöglicht, die Website trotz einer regionalen Beschränkung zu besuchen |
| Essential | wfls-remembered-* | schwollbachhof.de | Wordfence | 30 days | HTTP Cookie | Token, um Nutzer nach einer Zwei-Faktor-Authentifizierung (2FA) für eine bestimmte Zeit zu erkennen |
| Essential | pll_language | schwollbachhof.de | Polylang | 1 year | HTTP Cookie | Ausgewählte Sprache der Website |
| Essential | real_cookie_banner* | .schwollbachhof.de | Real Cookie Banner | 365 days | HTTP Cookie | Eindeutiger Identifikator für die Einwilligung, aber nicht für den Website-Besucher. Revisionshash für die Einstellungen des Cookie-Banners (Texte, Farben, Funktionen, Servicegruppen, Dienste, Content Blocker usw.). IDs für eingewilligte Services und Service-Gruppen. |
| Essential | real_cookie_banner*-tcf | .schwollbachhof.de | Real Cookie Banner | 365 days | HTTP Cookie | Im Rahmen von TCF gesammelte Einwilligungen, die im TC-String-Format gespeichert werden, einschließlich TCF-Vendoren, -Zwecke, -Sonderzwecke, -Funktionen und -Sonderfunktionen. |
| Essential | real_cookie_banner*-gcm | .schwollbachhof.de | Real Cookie Banner | 365 days | HTTP Cookie | Die im Google Consent Mode gesammelten Einwilligungen in die verschiedenen Einwilligungstypen (Zwecke) werden für alle mit dem Google Consent Mode kompatiblen Services gespeichert. |
| Essential | real_cookie_banner-test | .schwollbachhof.de | Real Cookie Banner | 365 days | HTTP Cookie | Cookie, der gesetzt wurde, um die Funktionalität von HTTP-Cookies zu testen. Wird sofort nach dem Test gelöscht. |
| Essential | real_cookie_banner* | https://schwollbachhof.de | Real Cookie Banner | - | Local Storage | Eindeutiger Identifikator für die Einwilligung, aber nicht für den Website-Besucher. Revisionshash für die Einstellungen des Cookie-Banners (Texte, Farben, Funktionen, Service-Gruppen, Services, Content Blocker usw.). IDs für eingewilligte Services und Service-Gruppen. Wird nur solange gespeichert, bis die Einwilligung auf dem Website-Server dokumentiert ist. |
| Essential | real_cookie_banner*-tcf | https://schwollbachhof.de | Real Cookie Banner | - | Local Storage | Im Rahmen von TCF gesammelte Einwilligungen werden im TC-String-Format gespeichert, einschließlich TCF Vendoren, Zwecke, besondere Zwecke, Funktionen und besondere Funktionen. Wird nur solange gespeichert, bis die Einwilligung auf dem Website-Server dokumentiert ist. |
| Essential | real_cookie_banner*-gcm | https://schwollbachhof.de | Real Cookie Banner | - | Local Storage | Im Rahmen des Google Consent Mode erfasste Einwilligungen werden für alle mit dem Google Consent Mode kompatiblen Services in Einwilligungstypen (Zwecke) gespeichert. Wird nur solange gespeichert, bis die Einwilligung auf dem Website-Server dokumentiert ist. |
| Essential | real_cookie_banner-consent-queue* | https://schwollbachhof.de | Real Cookie Banner | - | Local Storage | Lokale Zwischenspeicherung (Caching) der Auswahl im Cookie-Banner, bis der Server die Einwilligung dokumentiert; Dokumentation periodisch oder bei Seitenwechseln versucht, wenn der Server nicht verfügbar oder überlastet ist. |
| Functional | SIDCC | .google.com | YouTube | 1 year | HTTP Cookie | - |
| Functional | SIDCC | .youtube.com | YouTube | 1 year | HTTP Cookie | - |
| Functional | VISITOR_INFO1_LIVE | .youtube.com | YouTube | 7 months | HTTP Cookie | - |
| Functional | LOGIN_INFO | .youtube.com | YouTube | 13 months | HTTP Cookie | - |
| Functional | CONSENT | .youtube.com | YouTube | 9 months | HTTP Cookie | - |
| Functional | CONSENT | .google.com | YouTube | 9 months | HTTP Cookie | - |
| Functional | OTZ | www.google.com | YouTube | 1 day | HTTP Cookie | - |
| Functional | yt-remote-device-id | https://www.youtube.com | YouTube | - | Local Storage | Eindeutige Geräte-ID, Zeitpunkt der Erstellung und Ablaufs des Objekts |
| Functional | yt-fullerscreen-edu-button-shown-count | https://www.youtube.com | YouTube | - | Local Storage | - |
| Functional | yt-remote-connected-devices | https://www.youtube.com | YouTube | - | Local Storage | Liste mit Geräten, die mit einem YouTube-Konto verbunden sind, Zeitpunkt der Erstellung und Ablaufs des Objekts |
| Functional | yt-player-bandwidth | https://www.youtube.com | YouTube | - | Local Storage | Informationen zur Bandbreitennutzung des YouTube-Players, Zeitpunkt der Erstellung und Ablaufs des Objekts |
| Functional | LogsDatabaseV2:*|| | https://www.youtube.com | YouTube | - | IndexedDB | - |
| Functional | ServiceWorkerLogsDatabase | https://www.youtube.com | YouTube | - | IndexedDB | - |
| Functional | YtldbMeta | https://www.youtube.com | YouTube | - | IndexedDB | - |
| Functional | yt-player-quality | https://www.youtube.com | YouTube | - | Local Storage | Ausgabe-Videoqualität für YouTube-Videos, Zeitpunkt der Erstellung und Ablaufs des Objekts |
| Functional | yt-player-performance-cap | https://www.youtube.com | YouTube | - | Local Storage | - |
| Functional | PersistentEntityStoreDb:*|| | https://www.youtube.com | YouTube | - | IndexedDB | - |
| Functional | yt-idb-pref-storage:*|| | https://www.youtube.com | YouTube | - | IndexedDB | - |
| Functional | yt.innertube::nextId | https://www.youtube.com | YouTube | - | Local Storage | - |
| Functional | yt.innertube::requests | https://www.youtube.com | YouTube | - | Local Storage | - |
| Functional | yt-html5-player-modules::subtitlesModuleData::module-enabled | https://www.youtube.com | YouTube | - | Local Storage | - |
| Functional | yt-remote-session-app | https://www.youtube.com | YouTube | SESSION | Session Storage | Genutzte Applikation für die Sitzung und Zeitpunkt der Erstellung des Objekts |
| Functional | yt-remote-cast-installed | https://www.youtube.com | YouTube | SESSION | Session Storage | Status der Installation der "remote-cast"-Funktion und Zeitpunkt der Erstellung des Objekts |
| Functional | yt-remote-session-name | https://www.youtube.com | YouTube | SESSION | Session Storage | Namen der aktiven Sitzung und Zeitpunkt der Erstellung des Objekts |
| Functional | yt-remote-cast-available | https://www.youtube.com | YouTube | SESSION | Session Storage | Status der Verfügbarkeit der "remote-cast"-Funktion und Zeitpunkt der Erstellung des Objekts |
| Functional | yt-remote-fast-check-period | https://www.youtube.com | YouTube | SESSION | Session Storage | Zeitpunkt der Erstellung des Objekts als Feststellung, ob "remote-cast"-Funktion erreichbar ist |
| Functional | *||::yt-player::yt-player-lv | https://www.youtube.com | YouTube | - | Local Storage | - |
| Functional | swpushnotificationsdb | https://www.youtube.com | YouTube | - | IndexedDB | - |
| Functional | yt-player-local-media:*|| | https://www.youtube.com | YouTube | - | IndexedDB | - |
| Functional | yt-it-response-store:*|| | https://www.youtube.com | YouTube | - | IndexedDB | - |
| Functional | __HOST-GAPS | accounts.google.com | YouTube | 13 months | HTTP Cookie | - |
| Functional | OTZ | accounts.google.com | YouTube | 1 day | HTTP Cookie | - |
| Functional | __Secure-1PSIDCC | .google.com | YouTube | 1 year | HTTP Cookie | - |
| Functional | __Secure-1PAPISID | .google.com | YouTube | 1 year | HTTP Cookie | - |
| Functional | __Secure-3PSIDCC | .youtube.com | YouTube | 1 year | HTTP Cookie | - |
| Functional | __Secure-1PAPISID | .youtube.com | YouTube | 13 months | HTTP Cookie | - |
| Functional | __Secure-1PSID | .youtube.com | YouTube | 13 months | HTTP Cookie | - |
| Functional | __Secure-3PSIDCC | .google.com | YouTube | 1 year | HTTP Cookie | - |
| Functional | __Secure-ENID | .google.com | YouTube | 13 months | HTTP Cookie | - |
| Functional | __Secure-1PSID | .google.com | YouTube | 13 months | HTTP Cookie | - |
| Functional | ytGefConfig:*|| | https://www.youtube.com | YouTube | - | IndexedDB | - |
| Functional | __Host-3PLSID | accounts.google.com | YouTube | 13 months | HTTP Cookie | - |
| Functional | LSID | accounts.google.com | YouTube | 13 months | HTTP Cookie | - |
| Functional | ACCOUNT_CHOOSER | accounts.google.com | YouTube | 13 months | HTTP Cookie | - |
| Functional | __Host-1PLSID | accounts.google.com | YouTube | 13 months | HTTP Cookie | - |
| Functional | __Secure-3PAPISID | .google.com | YouTube | 13 months | HTTP Cookie | - |
| Functional | SAPISID | .google.com | YouTube | 13 months | HTTP Cookie | - |
| Functional | APISID | .google.com | YouTube | 13 months | HTTP Cookie | - |
| Functional | HSID | .google.com | YouTube | 13 months | HTTP Cookie | - |
| Functional | __Secure-3PSID | .google.com | YouTube | 13 months | HTTP Cookie | - |
| Functional | __Secure-3PAPISID | .youtube.com | YouTube | 13 months | HTTP Cookie | - |
| Functional | SAPISID | .youtube.com | YouTube | 13 months | HTTP Cookie | - |
| Functional | HSID | .youtube.com | YouTube | 13 months | HTTP Cookie | - |
| Functional | SSID | .google.com | YouTube | 13 months | HTTP Cookie | - |
| Functional | SID | .google.com | YouTube | 13 months | HTTP Cookie | - |
| Functional | SSID | .youtube.com | YouTube | 13 months | HTTP Cookie | - |
| Functional | APISID | .youtube.com | YouTube | 13 months | HTTP Cookie | - |
| Functional | __Secure-3PSID | .youtube.com | YouTube | 13 months | HTTP Cookie | - |
| Functional | SID | .youtube.com | YouTube | 13 months | HTTP Cookie | - |
| Functional | VISITOR_PRIVACY_METADATA | .youtube.com | YouTube | 7 months | HTTP Cookie | - |
| Functional | PREF | .youtube.com | YouTube | 1 year | HTTP Cookie | Eindeutige ID, um bevorzugte Seiteneinstellungen und Wiedergabeeinstellungen wie explizite Autoplay-Optionen, zufällige Wiedergabe von Inhalten und Playergröße festzulegen |
| Functional | YSC | .youtube.com | YouTube | Session | HTTP Cookie | Eindeutige Sitzungs-ID, um zu erkennen, dass Anfragen innerhalb einer Browsersitzung vom Benutzer und nicht von anderen Websites stammen |
| Functional | SOCS | .youtube.com | YouTube | 9 months | HTTP Cookie | Einstellungen zur Einwilligung von Nutzern zu Google-Diensten, um deren Präferenzen zu speichern |
| Functional | SOCS | .google.com | YouTube | 13 months | HTTP Cookie | Einstellungen zur Einwilligung von Nutzern zu Google-Diensten, um deren Präferenzen zu speichern |
| Functional | NID | .google.com | YouTube | 7 months | HTTP Cookie | Eindeutige ID, um bevorzugte Einstellungen wie z. B. Sprache, Menge der Ergebnisse auf Suchergebnisseite oder Aktivierung des SafeSearch-Filters von Google |
| Functional | IDE | .doubleclick.net | YouTube | 9 months | HTTP Cookie | Eindeutige Identifikationstoken zur Personalisierung von Anzeigen auf allen Websites, die das Google-Werbenetzwerk nutzen |
| Functional | yt-player-headers-readable | https://www.youtube.com | YouTube | - | Local Storage | Zustand der technischen Lesbarkeit vom YouTube-Player-Header, Zeitpunkt der Erstellung und Ablaufs des Objekts |
| Functional | __Secure-YEC | .youtube.com | YouTube | 1 year | HTTP Cookie | Einzigartiger Identifikator zur Erkennung von Spam, Betrug und Missbrauch |
| Functional | yt-player-volume | https://www.youtube.com | YouTube | - | Local Storage | Ton-Einstellungen des YouTube-Players, Zeitpunkt der Erstellung und Ablaufs des Objekts |
| Functional | yt-player-volume | https://www.youtube.com | YouTube | SESSION | Session Storage | Ton-Einstellungen des YouTube-Players und Zeitpunkt der Erstellung des Objekts |
| Functional | AEC | .google.com | YouTube | 6 months | HTTP Cookie | Eindeutiger Identifikator zur Erkennung von Spam, Betrug und Missbrauch |
| Functional | ytidb::LAST_RESULT_ENTRY_KEY | https://www.youtube.com | YouTube | - | Local Storage | - |
| Functional | test_cookie | .doubleclick.net | YouTube | 1 day | HTTP Cookie | Testet, ob Cookies gesetzt werden können |
| Functional | __Secure-3PSIDCC | .google.com | Google Maps | 1 year | HTTP Cookie | - |
| Functional | __Secure-1PSIDCC | .google.com | Google Maps | 1 year | HTTP Cookie | - |
| Functional | SIDCC | .google.com | Google Maps | 1 year | HTTP Cookie | - |
| Functional | __Secure-3PAPISID | .google.com | Google Maps | 13 months | HTTP Cookie | - |
| Functional | SSID | .google.com | Google Maps | 13 months | HTTP Cookie | - |
| Functional | __Secure-1PAPISID | .google.com | Google Maps | 13 months | HTTP Cookie | - |
| Functional | HSID | .google.com | Google Maps | 13 months | HTTP Cookie | - |
| Functional | __Secure-3PSID | .google.com | Google Maps | 13 months | HTTP Cookie | - |
| Functional | __Secure-1PSID | .google.com | Google Maps | 13 months | HTTP Cookie | - |
| Functional | SID | .google.com | Google Maps | 13 months | HTTP Cookie | - |
| Functional | SAPISID | .google.com | Google Maps | 13 months | HTTP Cookie | - |
| Functional | APISID | .google.com | Google Maps | 13 months | HTTP Cookie | - |
| Functional | CONSENT | .google.com | Google Maps | 13 months | HTTP Cookie | - |
| Functional | __Secure-ENID | .google.com | Google Maps | 13 months | HTTP Cookie | - |
| Functional | _c;;i | https://www.google.com | Google Maps | - | Local Storage | - |
| Functional | LH;;s-* | https://www.google.com | Google Maps | - | Local Storage | - |
| Functional | sb_wiz.zpc.gws-wiz. | https://www.google.com | Google Maps | - | Local Storage | - |
| Functional | sb_wiz.ueh | https://www.google.com | Google Maps | - | Local Storage | - |
| Functional | NID | .google.com | Google Maps | 6 months | HTTP Cookie | Eindeutige ID, um bevorzugte Einstellungen wie z. B. Sprache, Menge der Ergebnisse auf Suchergebnisseite oder Aktivierung des SafeSearch-Filters von Google |
| Functional | AEC | .google.com | Google Maps | 6 months | HTTP Cookie | Einzigartiger Identifikator zur Erkennung von Spam, Betrug und Missbrauch |
| Statistic | _pk_ses.* | schwollbachhof.de | Matomo | 30 minutes | HTTP Cookie | - |
| Statistic | _pk_id.* | schwollbachhof.de | Matomo | 13 months | HTTP Cookie | - |
| Statistic | _pk_ref.* | schwollbachhof.de | Matomo | 6 months | HTTP Cookie | - |
| Statistic | _pk_cvar.* | schwollbachhof.de | Matomo | 30 months | HTTP Cookie | - |
| Statistic | _pk_hsr.* | schwollbachhof.de | Matomo | 30 minutes | HTTP Cookie | - |
| Statistic | _pk_testcookie.* | schwollbachhof.de | Matomo | Session | HTTP Cookie | - |
| Statistic | mtm_consent | schwollbachhof.de | Matomo | 1 year | HTTP Cookie | - |
The cookie policy was last updated on 15. July 2025.
Cookies for the Siteminder / Little Hotelier Booking Engine
Strictly necessary
These cookies are essential for you to browse the website and use its features, such as accessing secure areas of the site.
These cookies cannot be disabled
- aws-waf-token The token is encrypted and serves as a detailed fingerprint of the client session. It contains a sticky granular identifier with several key pieces of information. This includes timestamps of the client’s most recent successful responses to silent challenges and CAPTCHAs. The token also incorporates additional data about the client and their behavior to distinguish legitimate users from unwanted traffic. This data consists of various client identifiers and client-side signals that can detect automated activities, though the information is non-unique and cannot be linked to specific individuals. All tokens include data from client browser interrogation, such as indicators of automation and inconsistencies in browser settings, gathered by scripts run during challenge actions. The token also includes passively collected information about the end user’s interactions with the application page, such as mouse movements, key presses, and form interactions. This interactivity data helps AWS WAF assess the level of human engagement and challenge users who don’t appear to be human. Party: First party Expiry: 4 Days Data Type: String
- sm-cookie-consent Record the response of the user in session whether they have accepted, rejected, or customised the cookie consent Party: First party Expiry: 12 months Data Type: String
- _gha_gcid, _gha_phid, _gads_gcid, _gads_gclabel There cookies are added by google and not processed by D+. Party: Third party Expiry: 30 Days Data Type: String
- campaign_source This holds the value of “DemandPlus” to attribute reservations coming from Trivago, Google Hotel Ads or TripAdvisor Party: Third party Expiry: 30 Days Data Type: String
- booking_source Determines the kind of commission rate that would be payable by the hotel for Demand Plus reservations. Values could be either “cpc”, “commissions” or “organic”. Party: Third party Expiry: 30 Days Data Type: String
- meta Identifies the metasearch channel from where the reservation is coming from, i.e. Google, Trivago, TripAdvisor. Party: Third party Expiry: 30 Days Data Type: String
- landing_page_params Captures meta source (Google, Trivago, Tripadvisor) and all other values in query parameters. Allows us to capture conversions per meta and provide conversion information to metas. Party: Third party Expiry: 90 Days Data Type: JSON
- _GRECAPTCHA reCAPTCHA sets a necessary cookie (_GRECAPTCHA) when executed for the purpose of providing its risk analysis. Party: First party Expiry: Session
- dataLayer partner config Contains plug-in apps configuration attributes such as property keys and script URLs Party: First party Expiry: Session Data Type: JSON
Preference cookies
Allows us to remember choices you have made in the past, like what language you prefer.
- hijiffy_session Application Session Party: Third party Expiry: 1 Day Data Type: HTTP
- wg_[WIDGET_TOKEN]_hj_web Save widget state (open or closed). It allows to automatically open the widget according to the last time the client was on the website Party: Third party Expiry: 2 years Data Type: HTTP
- wg_[WIDGET_TOKEN]_hj_ut Unique User ID token. It allows HiJiffy to load the last conversation if it exists Party: Third party Expiry: 2 years Data Type: HTTP
- fs_optly_pending_events Temporary storage of XMLHttpRequest information, enabling to reliably send requests even if the visitor navigates to a new page while a request is in progress Party: Third party Expiry: Persistent Data Type: HTTP
- triptease-conversion Used to understand behaviour of a user across hotel websites Party: Third party Expiry: 7 Days Data Type: HTTP
- triptease-user-id Used to understand behaviour of a user across hotel websites Party: Third party Expiry: 5 years Data Type: HTTP
- triptease-session-id Used to understand behaviour of a user across hotel websites during a single session Party: Third party Expiry: 8 hours Data Type: HTTP
- triptease-domain-user-id CookieModal.preference.triptease-domain-user-id_purpose Party: Third party Expiry: 5 years Data Type: HTTP
- triptease-identity-data Used to understand behaviour of a user across hotel websites Party: Third party Expiry: 5 hours
- _session_id A cookie that preserves the user status across pages Party: Third party Expiry: Unknown
- request-Method A temporary cookie used in determining the type of request to the website Party: Third party Expiry: Unknown
- vanity_id This cookie is set to make split-tests on the website Party: Third party Expiry: Unknown
- first_name This cookie is set based on known Guestbook member details for the current user Party: Third party Expiry: Unknown
- last_name This cookie is set based on known Guestbook member details for the current user Party: Third party Expiry: Unknown
- email Is used to determine if the current user has a registered member account with The Guestbook Party: Third party Expiry: Unknown
- pid This cookie is set based on known Guestbook member details for the current user Party: Third party Expiry: Unknown
- member_login_new_user Used to determine if the user created a member account with The Guestbook during the current session Party: Third party Expiry: Session
- lang Session-based cookie that remembers the user’s selected language version of a website Party: Third party Expiry: Session
- lidc Used by LinkedIn for routing Party: Third party Expiry: 1 Day
- li_gc Used by LinkedIn to store consent of guests regarding the use of cookies for non-essential purposes Party: Third party Expiry: 729 Days
- thn_id This cookie is created to identify the users with a unique ID formed by a hexadecimal carriage of characters. This cookie is used to be able to identify the users in theri next visit to the hotels websites in the network. This cookie allows to personalise the user experience. Party: Third party Expiry: 730 Days
- __thn_ss This cookie is created to manage server session. It is a PHP session that creates it. This cookie allows to personalise the user experience. Party: Third party Expiry: Session
- Guest details This cookie is used to save the guest details in the checkout form. Party: First party Expiry: Session Data Type: JSON
Statistics cookies
Collect information about how you use a website, like which pages you visited and which links you clicked on. None of this information can be used to identify you. It is all aggregated and, therefore, anonymised.
- dataLayer cancellation data Contains the booking reference of the cancelled reservation and the email of the guest. Party: First party Expiry: Session Data Type: JSON
- dataLayer impression data Contains guest date and occupancy selection and best price Party: First party Expiry: Session Data Type: JSON
- dataLayer conversion data Contains booking information Party: First party Expiry: Session Data Type: JSON
- _ga Used to distinguish users. Party: Third party Expiry: 2 years
- _gid Used to distinguish users. Party: Third party Expiry: 24 hours
- _gat Used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_<property- id>. Party: Third party Expiry: 1 minute
- AMP_TOKEN Contains a token that can be used to retrieve a Client ID from AMP Client ID service. Other possible values indicate opt-out, inflight request or an error retrieving a Client ID from AMP Client ID service. Party: Third party Expiry: 30 seconds to 1 year
- _gac_<property-id> Contains campaign related information for the user. If you have linked your Google Analytics and Google Ads accounts, Google Ads website conversion tags will read this cookie unless you opt-out. Party: Third party Expiry: 90 Days
- _hjSessionUser{site_id} Hotjar cookie that is set when a user 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 behavior in subsequent visits to the same site will be attributed to the same user ID. Party: Third party Expiry: 365 Days Data Type: JSON
- _hjSession{site_id} A cookie that holds the current session data. This ensues that subsequent requests within the session window will be attributed to the same Hotjar session. Party: Third party Expiry: 30 minutes Data Type: JSON
- _hjClosedSurveyInvites Hotjar cookie that is set once a user interacts with an External Link Survey invitation modal. It is used to ensure that the same invite does not reappear if it has already been shown. Party: Third party Expiry: 365 Days Data Type: Boolean
- _hjDonePolls Hotjar cookie that is set once a user interacts with an External Link Survey invitation modal. It is used to ensure that the same invite does not reappear if it has already been shown. Party: Third party Expiry: 365 Days Data Type: Boolean
- _hjMinimizedPolls Hotjar cookie that is set once a user minimizes an On-site Survey widget. It is used to ensure that the widget stays minimized when the user navigates through your site. Party: Third party Expiry: 365 Days Data Type: Boolean
- _hjShownFeedbackMessage Hotjar cookie that is set when a user minimizes or completes Incoming Feedback. This is done so that the Incoming Feedback will load as minimized immediately if the user navigates to another page where it is set to show. Party: Third party Expiry: 365 Days Data Type: Boolean
- _hjSessionTooLarge Causes Hotjar to stop collecting data if a session becomes too large. This is determined automatically by a signal from the WebSocket server if the session size exceeds the limit. Party: Third party Expiry: Session Data Type: Boolean
- _hjSessionRejected If present, this cookie will be set to 1 for the duration of a user’s session, if Hotjar rejected the session from connecting to our WebSocket due to server overload. This cookie is only applied in extremely rare situations to prevent severe performance issues. Party: Third party Expiry: Session Data Type: Boolean
- _hjSessionResumed A cookie that is set when a session/recording is reconnected to Hotjar servers after a break in connection. Party: Third party Expiry: Session Data Type: Boolean
- _hjid 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 behavior in subsequent visits to the same site will be attributed to the same user ID. Party: Third party Expiry: 365 Days Data Type: UUID
- _hjRecordingLastActivity This should be found in Session storage (as opposed to cookies). This gets updated when a user recording starts and when data is sent through the WebSocket (the user performs an action that Hotjar records). Party: Third party Expiry: Session Data Type: Numerical Value (Timestamp)
- _hjUserAttributesHash 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. Party: Third party Expiry: Session Data Type: Hash
- _hjCachedUserAttributes This cookie stores User Attributes which are sent through the Hotjar Identify API, whenever the user is not in the sample. Collected attributes will only be saved to Hotjar servers if the user interacts with a Hotjar Feedback tool, but the cookie will be used regardless of whether a Feedback tool is present. Party: Third party Expiry: Session Data Type: JSON
- _hjLocalStorageTest 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. Party: Third party Expiry: Under 100ms Data Type: Boolean
- _hjIncludedInPageviewSample This cookie is set to let Hotjar know whether that user is included in the data sampling defined by your site’s pageview limit. Party: Third party Expiry: 30 minutes Data Type: Boolean
- _hjIncludedInSessionSample This cookie is set to let Hotjar know whether that user is included in the data sampling defined by your site’s daily session limit. Party: Third party Expiry: 30 minutes
- _hjAbsoluteSessionInProgress This cookie is used to detect the first pageview session of a user. This is a True/False flag set by the cookie. Party: Third party Expiry: 30 minutes Data Type: Boolean
- _hjFirstSeen 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. Party: Third party Expiry: Session Data Type: Boolean
- _hjViewportId This stores information about the user viewport such as size and dimensions. Party: Third party Expiry: Session Data Type: UUID
- _hjRecordingEnabled This is added when a Recording starts and is read when the recording module is initialized to see if the user is already in a recording in a particular session. Party: Third party Expiry: Session Data Type: Boolean
- _hjTLDTest 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. Party: Third party Expiry: Session Data Type: Boolean
- _ga-ft Google analytics identifier for Flip.to plug-in Party: Third party Expiry: Unknown
- ft-person-id Legacy google analytics identifer Party: Third party Expiry: Unknown
- ft-app-confirmation-status-[xxx] Maintains flip.to confirmation status Party: Third party Expiry: Unknown
- ft-trn-[xxxx] Maintains transaction state Party: Third party Expiry: Unknown
- ft-ot-[xxxx] Maintains flip.to components interaction state Party: Third party Expiry: Unknown
- hijiffy_track_ts Register the date and hour of the firing of the pixel. Party: Third party Expiry: 29 Days Data Type: HTTP
- hijiffy_track_uuid Unique Global User ID to register user events. Party: Third party Expiry: 29 Days Data Type: HTTP
- hijiffy_track_uuid_[CLIENT_ID] Unique company User ID to register events. Party: Third party Expiry: 29 Days Data Type: HTTP
- hijiffy_track_wid_[WIDGET_TOKEN] Unique widget User ID to register events. Party: Third party Expiry: 29 Days
- triptease-experiments Used to categorise users for AB tests. Party: Third party Expiry: 5 years Data Type: HTTP
- pf-ticket-id Used for conversion tracking and sharing this data amongst our applications.’ Party: Third party Expiry: Session Data Type: HTTP
- pf-api-key Used to uniquely identify hotels and sharing this data amongst our applications. Party: Third party Expiry: Session Data Type: HTTP
- _ga Registers a unique ID that is used to generate statistical data on how the visitor uses the website Party: Third party Expiry: Unknown
- _hjSessionUser_(site_ID) Hotjar cookie that is set when a user first lands on a page with the Hotjar script. It is used to persist the Hotjar Iser 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. Party: Third party Expiry: Unknown
Marketing cookies
Track your online activity to help advertisers deliver more relevant advertising or to limit how many times you see an ad. These cookies can share that information with other organisations or advertisers.
- dataLayer loyalty data Contains personal information such as user full name, email and phone number. Party: First party Expiry: Session Data Type: JSON
- _fbp Used by Facebook to deliver a series of advertisement products such as real time bidding from third party adveritisers. Party: Third party Expiry: 90 Days
- fr Used by Facebook to deliver a series of advertisement products such as real time bidding from third party adveritisers. Party: Third party Expiry: 90 Days Data Type: ID number
- _gcl_au Primarily used to help advertisers determine how many times users who click on their ads end up taking an action on their site, such as making a purchase. Cookies used for measuring conversion rates aren’t used to personalise ads. ‘_gcl_’ cookies last for 90 days. Party: Third party Expiry: 90 Days
- adh Google Ads Data Hub ID of traveler Party: Third party Expiry: up to 7 days Data Type: ID number
- apnid Xander/AppNexus ID of traveler Party: Third party Expiry: up to 90 days Data Type: ID number
- cid Sojern ID of traveler Party: Third party Expiry: up to 1 year Data Type: ID number
- dc-adv, dc-part Serve dynamic ads to the traveler Party: Third party Expiry: up to 2 years Data Type: Intent data from Sojern pixels firing from your site. No PII (personally identifiable information)
- gid Google ID of traveler Party: Third party Expiry: up to 1 year Data Type: ID number
- ttdid TradeDesk ID of traveler Party: Third party Expiry: up to 30 days Data Type: ID number
- __wihptics2 WiHP ID of traveler Party: Third party Expiry: up to 30 days Data Type: ID number
- muid Microsoft User Identifier tracking cookie used by Bing Ads Party: Third party Expiry: up to 2 years Data Type: ID number