In order for your visit to Dame Jidlo to be attractive and to allow some features to be used, we use so-called cookies on various pages. Cookies are small text files that are stored in your browser. Some of the cookies we use are deleted after the end of your browser session, i.e. after you close the browser. Other cookies remain in your browser and allow us to recognize your browser on your next visit (permanent cookies). You can configure your browser to know how to set cookies and decide individually whether or not to accept them for specific occasions or in general. Not accepting cookies may limit the functionality of our site.
We classify the cookies we use into three categories:
Below you will find more information about your choices as well as a detailed list of cookies we use.
The required cookies are necessary to navigate our site and use its features. Without the use of these cookies, the proper functioning of our site is not guaranteed (e.g. text input) when browsing the pages of the website. In addition, they are cookies that collect information about how visitors use our site, for example, which pages they visit more often and if they receive error messages. They also allow our site to remember your choices, such as language or area, to provide improved features. They are also used to store information about the consent option where required. No action is required from you to activate them.
Functional cookies allow us to continuously improve the services we offer, collecting and analyzing information about our website traffic. They can also be used to send ads and bids or to measure the effectiveness of our ad campaigns. So they give us the opportunity to suggest and help you find what you are looking for. This category also include cookies from third parties.
Personalization cookies are used to create tailor-made content for you to give you the best possible Dame Jidlo experience.
If you do not want us to collect and analyze information about your visit, you can opt-out at any time for the future.
For the technical implementation, an exception cookie will be set in your browser. This cookie is solely intended to map your objection. Please note that for technical reasons the opt-out cookie can only be used for the specific browser from which it is set. If you delete cookies or use a different browser or device, you will need to repeat this process.
What are cookies
Cookies are small text files that are stored in your browser. See the categories of cookies below and adjust your choices.
|_uetsid||Google Tag Manager||Cookie functions: store and track visits across websites||1 Month|
|_uetvid||Google Tag Manager||Cookie functions: store and track visits across websites||1 Month|
|ab.storage.sessionId.###||Braze||Out-of-the-box randomly generated string used to determine whether the user is starting a new or existing session, in order to sync messages and calculate session analytics.||1 Year|
|ab.storage.deviceId.###||Braze||Out-of-the-box randomly generated string used to identify anonymous users, and to differentiate users’ devices and enables device-based messaging||1 Year|
|ab.storage.userId.###||Braze||Used to determine whether the currently-logged-in user has changed, and to associate events with the current user.||1 Year|
|hl||Foodora Application Cookie||Cookie is used to read language locale||Session|
|gdpr-cookies-preference||Foodora Application Cookie||differentiates what the user's GDPR settings are and therefore differentiates between required, functional and personalization.||1 Month|
|gdpr-cookies-banner-decision||Foodora Application Cookie||differentiates whether or not the users accpeted or denied the GDPR cookie consent.||1 Month|
|_hjid||Hotjar||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.||1 Year|
|userSource||Foodora Application Cookie||Identifies the user as b2c or b2b customer.||1 Hour|
|dhhPerseusGuestId||Delivery Hero Tracking||Internally created device identifier for internal global services.||2 Years|
|dhhPerseusHitId||Delivery Hero Tracking||Internally created hit/event identifier for internal global services.||1 Hour|
|dhhPerseusSessionId||Delivery Hero Tracking||Internally created session identifier for internal global services.||30 Minutes|
|_hjIncludedInSessionSample||Hotjar||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.||30 Minutes|
|_hjAbsoluteSessionInProgress||Hotjar||This cookie is used to detect the first pageview session of a user. This is a True/False flag set by the cookie.||30 Minutes|
|_ga||Google Analytics||Used to distinguish users.||2 Years|
|_gid||Google Analytics||Used to distinguish users.||1 Day|
|_gat_myTrackerDHH||Delivery Hero Tracking||Used to throttle request rate (based on Tracker Name set in GTM)||5 Minutes|
|_dc_gtm_UA-###||Google Tag Manager||Used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_<property-id>.||5 Minutes|
|_hjTLDTest||Hotjar||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.||Session|
|ld_key||Foodora Application Cookie||this cookie stores the unique identifier for user for fetching feature flags||2 Months|
|dps-session-id||Delivery Hero Tracking||this cookie is identifier for each dynamic pricing session||20 Minutes|
|PHPSESSID||Delivery Hero Tracking||generated in legacy application(b2c) for each user session||10 Minutes|
|orderPay||Foodora Application Cookie||Enables payments on the platform.||Session|
|refresh_token||Foodora Application Cookie||This token helps in the login activity and keeping the customer logged in||1 Year|
|token||Foodora Application Cookie||This token helps in the login activity||1 Hour|
|device_token||Foodora Application Cookie||This token helps in the login activity||10 Years|
|tooltip-reorder||Foodora Application Cookie||This helps users to re-order previous selections||Session|
|AppVersion||Delivery Hero Tracking||Determines the version of the app||1 Month|
|_px3||Perimeter X||This cookie helps protect the site from bad traffic||5 Minutes|
|_pxhd||Perimeter X||This cookie helps protect the site from bad traffic||Session|
|_pxvid||Perimeter X||This cookie helps protect the site from bad traffic||1 Year|
|_pxff_fp||Perimeter X||This cookie helps protect the site from bad traffic||5 minutes|
|_tq_id.TV-#id||TVSquared||Reporting of site visits and actions for analytical reporting to TV Squared.||2 Years|
|_fbp||The pixel automatically saves a unique identifier to an _fbp cookie for the website domain if one does not already exist.||1 Year|
|_gcl_au||Google AdSense||This cookie is used by Google AdSense for experimenting with advertisement efficiency||3 Months|