In order to make the visit of our website/app attractive and to enable the use of certain functions, we use so-called cookies on various pages. These are small text files that are stored on your device. Some of the cookies we use are deleted after the end of the browser session, i.e. after closing your browser (so-called session cookies). Other cookies remain on your device and allow us to recognize your browser on your next visit (persistent cookies). You can set your browser so that you are informed about the setting of cookies and individually decide on their acceptance or exclude the acceptance of cookies for specific cases or in general. Failure to accept cookies may limit the functionality of our website/app.
What categories of cookies we use?
Required cookies are needed so that you can move around a website/app and use its features. Without these cookies, functionality cannot be guaranteed, such as actions taken during a visit (e.g. text entry), even when navigating between pages on the site. 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. These cookies do not store information that allows identification of the user. The collected information is aggregated and anonymous. These cookies are used exclusively to improve the performance of a website/app and thus the user experience.
Functionality 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 includes cookies from third parties.
Personalization cookies, cookies for marketing purposes are used to play more targeted advertising relevant to the user and adapted to his interests. They are also used to limit the frequency of an ad and measure the effectiveness of advertising campaigns. They register whether you have visited a website/app or not. This information may be shared with third parties (e.g. Advertisers). To improve targeting and advertising cookies are often linked to third party site functionalities.
How do we use this data?
The primary objective of using such data is to enable the website to operate appropriately, for which it is necessary to monitor of data relating to visits of the website and to filter out of potential abusive use of the website. The data specified in this Policy may be used by our Company to note your personal preferences (e.g. most frequently viewed content on the website), or to remember your password. sen a weboldalra látogatási adatok nyomon követése, és a weboldal használattal kapcsolatos esetleges visszaélések kiszűrése. A jelen tájékoztatóban meghatározott adatokat egyebekben személyes preferenciáik (pl. legsűrűbben nézett tartalmak a weboldalon), illetve jelszava megjegyzése céljából is felhasználhatjuk.
In addition, we may also use this information to analyze the tendencies of use and to improve and develop the functions of the website, and also to obtain complex traffic data of the overall use of the website.
Our Company can use the information obtained in that manner to create and analyze statistics on the use of the website, and to transfer such statistical data, not suitable for identification (e.g., number of visitors and registrations, most frequently viewed topics and contents) to third parties, or to publish them on a consolidated basis, with anonymous data.
How does the ‘Keep me logged in’ function work?
AIf you provide consent for it, by activating the ‘Keep me logged in’ function you shall remain logged in even after leaving the site. In this case, you shall not be logged out due to inactivity or soon after leaving the site, but the system will keep you logged in for 90 days for a possible later return, when it shall automatically log you into your profile after loading the page. This function works for both normal and Facebook login accounts. If you wish to log out, you must visit the page (if you have closed it) and click ‘Logout’ on your profile.
If you do not want our Company to collect and analyze information about your visit, you can object to this at any time for the future (opt-out).
For technical implementation of this contradiction, an opt-out cookie will be set in your browser. This cookie is solely for the purpose of mapping your opposition. Please note that for technical reasons an opt-out cookie can only be used for the browser from which it was set. If you delete cookies or use a different browser or device, you will need to repeat this process.
Below, by clicking the appropriate box(es) you can adjust your choices about cookie setting.
|_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|