Cookies, SDKs and Web-Tracking Policy
Please rest assured that we will process device data in a pseudonymous manner only. At no point will we use these data to identify you as an individual person.
Cookies are not the only way to process device data online. There are similar technologies, like web beacons (sometimes called "tracking pixels", “pixel tags” or "clear gifs"). These are tiny graphics files that contain a unique identifier enabling us to recognize when someone has visited our platform. This allows us, for example, to monitor the traffic patterns of users from one page within our platform to another, to deliver or communicate with cookies, to understand whether you have come to our platform from an online advertisement displayed on a third-party website, or to improve performance. In many instances, these technologies are reliant on cookies to function properly, and so declining cookies will impair their functioning.
For mobile applications, we also use software development kits (SDKs). SDKs are part of the built-in code of our mobile applications and function in a way similar to cookies: They collect certain information about your device or the interaction with our platform, e.g. adding a certain meal to your order cart before submitting the order to the restaurant, or having clicked an advertisement for our platform shown on a third-party website or app.
The types of cookies and similar technologies we use
We classify our cookies and similar technologies into four categories:
They are required to navigate our platform, and in order to use its core features. Without the use of such cookies, the proper functioning of our web offering cannot be guaranteed. You cannot opt out of these technologies.
They are used to deliver personalized online advertisements for our services, targeted to your specific interests. These technologies are used to show you ads not only on our own platforms but also on third-party websites and apps hosted by publishers who are not part of our group of companies. They also serve to provide you with special offers and promotional campaigns relevant to your preferences.
Through cookies and other web-tracking technologies we also communicate limited device information such as your IP address, device ID, MAC address, operating system, device type, Apple Advertiser ID (IDFA) or Google Ad ID (GAID) to our partners (Google Ireland Ltd, Gordon House, Barrow Street, Dublin 4, Ireland operates the Google Ads network; Facebook Ireland Ltd, 4 Grand Canal Square, Grand Canal Harbour, Dublin 2, Ireland delivers advertisements on Facebook and Instagram). If you opt out of cookies and other web-tracking technologies, this will also stop any sharing of device information with external recipients.
Opting out of cookies and web-tracking
If you do not want us to collect and analyze information about your visit to, or use of, the service, you can opt out at any time. You can do so by configuring your browser to delete all cookies and reject them in the future. You can also use our cookie and web-tracking preference manager. There, you can select which category of cookies and web-tracking technologies you would rather like to have deactivated. However, please note that you cannot opt out of required cookies and similar technologies. Furthermore, deactivating web-tracking technologies does not mean you will no longer see any advertisements. Instead of personalized contents we will be showing you non-personalized app contents or advertisements, less relevant to your interests.
To implement your opt-out, a cookie will be set in your browser (to remember your preference) or, if you use the mobile app, an API call will be made to the SDK you would like to deactivate. 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.
See the categories of cookies below and adjust your choices.
List of our cookies
|_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||foodpanda Application Cookie||Cookie is used to read language locale||Session|
|gdpr-cookies-preference||foodpanda Application Cookie||differentiates what the user's GDPR settings are and therefore differentiates between required and advertising.||1 Month|
|gdpr-cookies-banner-decision||foodpanda 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||foodpanda 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||foodpanda 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||foodpanda Application Cookie||Enables payments on the platform.||Session|
|refresh_token||foodpanda Application Cookie||This token helps in the login activity and keeping the customer logged in||1 Year|
|token||foodpanda Application Cookie||This token helps in the login activity||1 Hour|
|device_token||foodpanda Application Cookie||This token helps in the login activity||10 Years|
|tooltip-reorder||foodpanda 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|