Cookies are activated and used during your navigation of the www.philippelaw.eu website.
Cookies are small text files, usually consisting of numbers and letters, which do not pose a security risk to your computer, tablet or smartphone.
They allow to:
You can consult the various cookies and find out what they are used for in the list below.
These cookies are necessary for purely technical reasons for the use of the website. Due to the technical necessity, only an information obligation applies and these are set as soon as you access the website.
| Name | Duration | Content | Goal |
|---|---|---|---|
| PHPSESSID | Expires at the end of the session | A token | This cookie sets the unique session of the user on the site. |
| pll_language | 1 year | A string of characters | This cookie sets the language of the user. |
| cookielawinfo-checkbox-[category] | 1 year | A string of characters | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category “Non Necessary”. |
| CookieLawInfoConsent | 1 year | A string of characters | The cookie is set by the GDPR Cookie Consent plugin and is used to remember the user’s choice about cookies on the website to avoid opening the popup after acceptance. |
| viewed_cookie_policy | 1 year | A string of characters | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
These cookies are necessary for WordPress to function properly while the user is logged on to the site.
The actual cookie data is hashed. So you don’t have to worry about your username or password being recovered by reading the cookie data. Hashing is the result of a specific mathematical formula applied to certain input data (in this case, your username and password). It is extremely complicated to reverse a hash (and almost impossible on today’s computers). It is therefore very difficult to take a hash and “unhash” it to find the original data.
WordPress uses both cookies to bypass the password entry portion of wp-login.php. If WordPress recognizes that you have valid, unexpired cookies, you can access the WordPress administration interface directly. If you do not have these cookies, or they have expired, or they are invalid for some reason (if you have manually changed them, for example), WordPress will ask you to log in again to get new cookies.
| Name | Duration | Content | Goal |
|---|---|---|---|
| wordpress_[hash] | Except for essential cookies, all cookies expire after two weeks | An encrypted character string | This cookie is set by WordPress and is used to store the authentication details on login. The authentication details include the username and double hashed copy of the password. However, this usage of the cookie is limited to the admin console area, the backend dashboard of the website. Here [hash] represents the value that is obtained by applying a specific mathematical formula applied to the username and password. It is to ensure that the input values are safe, and no one can access these data using the cookies as it is difficult to ‘unhash’ the hashed data. More info: https://wordpress.org/support/article/cookies/ |
| workpress_logged_in_[hash] | Except for essential cookies, all cookies expire after two weeks | An encrypted character string | This cookie is set by WordPress and is used to to indicate when you are logged in, and who you are. This cookie is maintained on the front-end of the website as well when logged in. More info: https://wordpress.org/support/article/cookies/ |
| wp-settings-{time}-[UID] | Except for essential cookies, all cookies expire after two weeks | An encrypted character string | This cookie is set by WordPress and is used to customize the view of your admin interface and the front-end of the website. The value represented by [UID] is the individual user ID of the user as given to them in the users’ database table. More info: https://wordpress.org/support/article/cookies/ |
|
wordpress_test_cookie |
Except for essential cookies, all cookies expire after two weeks |
A string of characters |
This cookie is set by WordPress and is used to store the authentication details on login. The authentication details include the username and double hashed copy of the password. However, this usage of the cookie is limited to the admin console area, the backend dashboard of the website. Here [hash] represents the value that is obtained by applying a specific mathematical formula applied to the username and password. It is to ensure that the input values are safe, and no one can access these data using the cookies as it is difficult to ‘unhash’ the hashed data. More info: https://wordpress.org/support/article/cookies/ |
These cookies are necessary for the proper functioning of WooCommerce when the user is logged into the site.
| Name | Duration | Content | Goal |
|---|---|---|---|
| woocommerce_cart_[hash] | Except for essential cookies, all cookies expire after two weeks | / | This cookie is set by WooCommerce and is used to help WooCommerce determine when cart contents/data changes. More info: https://docs.woocommerce.com/document/woocommerce-cookies/ |
| woocommerce_items_in_cart | Except for essential cookies, all cookies expire after two weeks | / | This cookie is set by WooCommerce and is used to help WooCommerce determine when cart contents/data changes. More info: https://docs.woocommerce.com/document/woocommerce-cookies/ |
| wp_woocommerce_session_ | Expires at the end of the session | A token | This cookie is set by WooCommerce. It contains a unique code for each customer so that it knows where to find the cart data in the database for each Customer. More info: https://docs.woocommerce.com/document/woocommerce-cookies/ |
| tk_ai | Expires at the end of the session | A string of characters | This cookie is set by WooCommerce. It stores a randomly-generated anonymous ID. This is only used within the dashboard (/wp-admin) area and is used for usage tracking, if enabled. More info: https://docs.woocommerce.com/document/woocommerce-cookies/ |
These cookies allow us to recognise and count the number of visitors and to see how visitors move around our site when they use it. This helps us to improve the operation of our site, for example, by ensuring that users can easily find what they are looking for. You can always refuse these cookies.
| Name | Duration | Content | Goal |
|---|---|---|---|
| __utma | 2 years | A numeric value | Used to distinguish users and sessions. The cookie is created when the javascript library executes and no existing __utma cookies exists. The cookie is updated every time data is sent to Google Analytics. More info: https://developers.google.com/analytics/devguides/collection/analyticsjs/cookie-usage |
| __utmb | 30 minutes | A numeric value | Used to determine new sessions/visits. The cookie is created when the javascript library executes and no existing __utmb cookies exists. The cookie is updated every time data is sent to Google Analytics. More info: https://developers.google.com/analytics/devguides/collection/analyticsjs/cookie-usage |
| __utmc | Expires at the end of the session | A numeric value | This cookie operates in conjunction with the __utmb cookie to determine if there is a new visit from the current visitor.. More info: https://developers.google.com/analytics/devguides/collection/analyticsjs/cookie-usage |
| __utmt | 10 minutes | A numeric value | Used to throttle request rate. More info: https://developers.google.com/analytics/devguides/collection/analyticsjs/cookie-usage |
| __utmv | 2 years | A numeric value | Used to store visitor-level custom variable data. This cookie is created when a developer uses the _setCustomVar method with a visitor level custom variable. This cookie was also used for the deprecated _setVar method. The cookie is updated every time data is sent to Google Analytics. More info: https://developers.google.com/analytics/devguides/collection/analyticsjs/cookie-usage |
| __utmz | 6 months | A string of characters | Stores the traffic source or campaign that explains how the user reached your site. The cookie is created when the javascript library executes and is updated every time data is sent to Google Analytics. More info: https://developers.google.com/analytics/devguides/collection/analyticsjs/cookie-usage |
| _fbp | 3 months | A string of characters | Used by Facebook to provide a variety of advertising products such as real-time bidding from third-party advertisers. |
| 1P_JAR | 1 month | A date | This cookie provides information about how the end user uses the website and any advertising that the end user may have seen before visiting that website. It is added by Google with the tracking of Linkedin. |
| AnalyticsSyncHistory | 30 days | A string of characters | Used to store data about when a synchronisation was performed with the lms_analytics cookie. |
| ANID | 9 months | A string of characters | This is a Google advertising cookie (which may be injected when using a service such as Facebook Pixel, MailChimp or Linkedin). |
| bcookie | 1 year | A string of characters | This cookie is set by Linkedin for the tracking of on-board services. |
| bscookie | 2 years | A string of characters | This cookie is set by Linkedin for the tracking of on-board services. |
| c_user | 3 months | A string of characters | This cookie is used by Facebook for social sharing of information and integration of Facebook services. |
| cli_user_preference | 1 year | A string of characters | Stores the consent status of the user’s cookies. |
| CONSENT | ±18 years | A string of characters | This cookie stores information related to user consent and stores the user’s language. |
| datr | 2 years | A string of characters | Cookie for statistical analysis of Facebook advertising. For more information, please see Facebook’s Cookie Usage Policy. |
| DSID | 2 weeks | A string of characters | Is used to identify a user who is signed in to his or her Google Account on non-Google sites and to store his or her ad personalization preferences. |
| fr | 3 months | A string of characters | The “fr” cookie is used to deliver, measure and improve the relevance of advertisements, and its lifespan is 90 days. |
| IDE | 13 months | A string of characters | Used by Google to present Google Ads ads to users on non-Google sites. |
| JSESSIONID | Expires at the end of the session | A string of characters | This cookie is set by Linkedin to define a new session. |
| lang | Expires at the end of the session | A string of characters | This cookie stores the language of the browser. This cookie is added by Linkedin. |
| li_at | 1 year | A string of characters | This cookie is set by Linkedin for the tracking of on-board services. This cookie is used to protect against XSS attacks. |
| li_oatml | 1 month | A string of characters | Indirect ID of the member for conversation tracking, retargeting and user. This cookie is added by Linkedin. |
| lidc | 1 day | A string of characters | Linkedin cookie used for routing. |
| lissc | 1 year | A string of characters | This cookie is set by Linkedin for the tracking of on-board services. |
| lms_ads | 3 days | A string of characters | Used to identify LinkedIn members outside LinkedIn in designated countries for advertising purposes. |
| lms_analytics | 30 days | A string of characters | Used to identify LinkedIn members in designated countries for analysis purposes |
| NID | 6 months | A string of characters | This Google cookie is used to personalize advertisements. It stores a unique identifier that allows Google to save preferences and other information such as language. |
| sb | 2 years | A string of characters | This cookie is used by Facebook for social sharing of information and integration of Facebook services. |
| UserMatchHistory | 30 days | A string of characters | This Linkedin cookie is used to track visitors so that the most relevant advertisements can be shown based on the visitor’s preferences. |
| xs | 90 days | A string of characters | This cookie from Facebook stores a certain amount of session data when a person is connected to Facebook via their browser or device. |
If you want to know which cookies are installed on your device or if you want to delete them, you can use the following link Set cookies or a setting in your browser. You can find more information on how to do this via the links below.
| Firefox | Chrome | Safari | Internet Explorer |
| Firefox (mobile) | Chrome (mobile) | Safari (mobile) | Microsoft Edge |
More information about cookies, including how to block or delete them on browsers other than those listed above, can be found at www.allaboutcookies.org. This site is only available in English.
You will not be denied access to our site if you disable cookies, but some features may not be available.
If you have any further questions, comments or requests about our cookie policy or the way we use cookies on our site, you can contact us by email at privacy@philippelaw.eu.