-
Canal de signalement interne : quelles questions se poser ?
Fanny Coton
Sophie Everarts de Velp
-
Facebook et son rôle dans la chasse aux commentaires dénigrants
Alexandre Cassart
-
Lanceurs d’alerte : votre canal interne de signalement est-il prêt ?
Fanny CotonElena Caes
-
Training
Workshop : dénigrement en ligne, comment réagir ?
Fanny Coton -
Journalistes, universitaires, artistes : RGPD à la sauce belge
Fanny Coton
Canal de signalement interne : quelles questions se poser ? was successfully added to your cart!
This website uses cookies. Some cookies are necessary for the proper functioning of this website and cannot be refused if you wish to visit this website. Other cookies are used for playing videos and analysis: Cookies Policy. You can refuse them if you wish. Refuse Settings ACCEPT ALL
ACCEPT ALL
The necessary cookies are essential for the proper functioning of the website. This category only includes cookies that provide basic functionality, website security, language management, document downloads and online consultation.
| Cookie | Type | Duration | Description |
|---|---|---|---|
| _wpas_session | session | 30 minutes | This cookie is used by Awesome Support (online consultation / SOS) to keep track of website state between page loads and to store temporary information essential to the website's ability to work properly.More info: https://getawesomesupport.com/documentation/awesome-support/cookies/ |
| cookielawinfo-checkbox-necessary | persistent | 11 months | This cookie is set by GDPR Cookie Consent plugin. The purpose of this cookie is to check whether or not the user has given the consent to the usage of cookies under the category 'Necessary'. |
| cookielawinfo-checkbox-non-necessary | persistent | 11 months | This cookie is set by GDPR Cookie Consent plugin. The purpose of this cookie is to check whether or not the user has given their consent to the usage of cookies under the category 'Non-Necessary'. |
| PHPSESSID | session | This cookie is native to PHP applications. The cookie is used to store and identify a users' unique session ID for the purpose of managing user session on the website. The cookie is a session cookie and is deleted when all the browser windows are closed. | |
| pll_language | persistent | 1 year | This cookie is set by Polylang and is used to remember the language selected by the user when he comes back to visit again the website. This cookie is also used to get the language information when not available in another way. Examples are ajax requests or the login page.More info: https://polylang.pro/doc/is-polylang-compatible-with-the-eu-cookie-law/ |
| viewed_cookie_policy | persistent | 1 hour | 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. |
| woocommerce_cart_hash | session | 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_ | session | 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/ | |
| wordpress_[hash] | session | 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/ | |
| wordpress_logged_in_[hash] | persistent | 14 days | This cookie is set by Wordpress and is used 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/ |
| wordpress_test_cookie | session | 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/ | |
| wp_woocommerce_session_ | persistent | 2 days | 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/ |
| wp-settings-{time}-[UID] | persistent | 1 year | 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/ |
Lexing uses Google Analytics 4 for analytical purposes.
| Cookie | Type | Duration | Description |
|---|---|---|---|
| _ga | third party | 2 years | This cookie is installed by Google Analytics 4. The cookie is used to distinguish users for the site's analytics report.Opt-out: https://tools.google.com/dlpage/gaoptout/More info: https://developers.google.com/analytics/devguides/collection/analyticsjs/cookie-usage |
| _ga_ | third party | 2 years | This cookie is installed by Google Analytics 4 to persist session state.Opt-out: https://tools.google.com/dlpage/gaoptout/More info: https://developers.google.com/analytics/devguides/collection/analyticsjs/cookie-usage |
Lexing uses YouTube to allow video playback on its site.
| Cookie | Type | Duration | Description |
|---|---|---|---|
| GPS | third party | 30 minutes | This cookie is set by YouTube and registers a unique ID for tracking users based on their geographical locationMore info: https://policies.google.com/technologies/types?hl=en |
| IDE | third party | 2 years | Used by Google DoubleClick and stores information about how the user uses the website and any other advertisement before visiting the website. This is used to present users with ads that are relevant to them according to the user profile.More info: https://policies.google.com/technologies/types?hl=en |
| VISITOR_INFO1_LIVE | third party | 5 months | This cookie is set by YouTube. Used to track the information of the embedded YouTube videos on a website.More info: https://policies.google.com/technologies/types?hl=en |
| YSC | third party | This cookie is set by YouTube and is used to track the views of embedded videos.More info: https://policies.google.com/technologies/types?hl=en |
Powered by 