{"id":18934,"date":"2025-04-29T14:16:54","date_gmt":"2025-04-29T14:16:54","guid":{"rendered":"https:\/\/extentis.fr\/politique-de-cookies-ue\/"},"modified":"2025-04-29T14:16:54","modified_gmt":"2025-04-29T14:16:54","slug":"eu-cookie-policy","status":"publish","type":"page","link":"https:\/\/extentis.fr\/en\/politique-de-cookies-ue\/","title":{"rendered":"Cookie Policy (EU)"},"content":{"rendered":"\n

This Cookie Policy was last updated on April 29, 2025 and applies to citizens and legal permanent residents of the European Economic Area and Switzerland.<\/i>
<\/p>

1. Introduction<\/h2>

Our website, https:\/\/extentis.fr\/en<\/a> (hereinafter: \"the website\") uses cookies and similar technologies (for convenience, all such technologies are referred to as \"cookies\"). Cookies are also placed by third parties with whom we have contracted. In the document below, we will inform you about our use of cookies on our website.<\/p>

2. What are cookies?<\/h2>

A cookie is a small, simple file that is sent along with pages from this website and stored by your browser on your computer's hard drive or another device. The information stored within it may be returned to our servers or the servers of relevant third parties during a subsequent visit.<\/p>

3. What are scripts?<\/h2>

A script is a piece of program code that is used to make our website function properly and interactively. This code is executed on our server or on your device.<\/p>

4. What is a web beacon?<\/h2>

A web beacon (or pixel tag) is a small, invisible piece of text or an image on a website that is used to monitor traffic on that website. To do this, various data about you is stored using web beacons.<\/p>

5. Cookies<\/h2>

5.1 Technical or functional cookies<\/p>

Some cookies ensure that certain parts of the website work properly and that your user preferences remain known. By placing functional cookies, we make it easier for you to visit our website. This way, you do not need to repeatedly enter the same information when visiting our website and, for example, the items remain in your shopping cart until you have paid. We may place these cookies without your consent.<\/p>

5.2 Marketing\/Tracking cookies<\/p>

Marketing\/tracking cookies are cookies or any other form of local storage used to create user profiles to display advertising or to track the user on this website or across several websites for similar marketing purposes.<\/p>

5.3 Social media<\/p>

On our website, we have included content from LinkedIn to promote web pages (e.g. \u201clike\u201d, \u201cpin\u201d) or share (e.g. \u201ctweet\u201d) on social networks like LinkedIn. This content is embedded with code derived from LinkedIn and places cookies. This content might store and process certain information for personalised advertising.<\/p>

Please read the privacy statements of these social networks (which may change regularly) to understand what they do with your (personal) data that they process using these cookies. The data retrieved is anonymised as much as possible. LinkedIn is based in the United States.<\/p>

6. Cookies placed<\/h2>
\n\t
\n\t\t

Elementor<\/h3>\n\t\t

Statistics (anonymous)<\/p>\n\t\t

\n\t\t

Usage<\/h4>\n\t\t

We use Elementor for content creation. Read more about Elementor<\/a><\/p>\n\t<\/div>\n\t

\n\t\t

Sharing data<\/h4>\n\t\t

This data is not shared with third parties.<\/p>\n\t<\/div>\n\t

\n

Statistics (anonymous)<\/h4><\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
Elementor<\/a><\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
persistent<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
Store activities performed on the website<\/div>\n\n<\/div>\n<\/details>\n
\n\t
\n\t\t

WordPress<\/h3>\n\t\t

Functional<\/p>\n\t\t

\n\t\t

Usage<\/h4>\n\t\t

We use WordPress for website development. Read more about WordPress<\/a><\/p>\n\t<\/div>\n\t

\n\t\t

Sharing data<\/h4>\n\t\t

This data is not shared with third parties.<\/p>\n\t<\/div>\n\t

\n

Functional<\/h4><\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
wpEmojiSettingsSupports<\/a><\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
session<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
Store browser details<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
wp-settings-*<\/a><\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
persistent<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
Store user preferences<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
wp-settings-time-*<\/a><\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
1 year<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
Store user preferences<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
wordpress_test_cookie<\/a><\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
session<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
See if cookies can be placed<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
wp_lang<\/a><\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
session<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
Gem language settings<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
wordpress_logged_in_*<\/a><\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
persistent<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
Save logged-in users<\/div>\n\n<\/div>\n<\/details>\n
\n\t
\n\t\t

Google Analytics<\/h3>\n\t\t

Statistics<\/p>\n\t\t

\n\t\t

Usage<\/h4>\n\t\t

We use Google Analytics for website statistics. Read more about Google Analytics<\/a><\/p>\n\t<\/div>\n\t

\n\t\t

Sharing data<\/h4>\n\t\t

For more information, please read the Google Analytics Privacy Statement<\/a>.<\/p>\n\t<\/div>\n\t

\n

Statistics<\/h4><\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
_ga<\/a><\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
2 years<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
Store and count pageviews<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
_ga_*<\/a><\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
1 year<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
Store and count pageviews<\/div>\n\n<\/div>\n<\/details>\n
\n\t
\n\t\t

Google AdSense<\/h3>\n\t\t

Marketing<\/p>\n\t\t

\n\t\t

Usage<\/h4>\n\t\t

We use Google Adsense for showing advertisements. Read more about Google Adsense<\/a><\/p>\n\t<\/div>\n\t

\n\t\t

Sharing data<\/h4>\n\t\t

For more information, please read the Google Adsense Privacy Statement<\/a>.<\/p>\n\t<\/div>\n\t

\n

Marketing<\/h4><\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
_gcl_au<\/a><\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
persistent<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
Store and track conversions<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
Google AdSense Settings<\/a><\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
persistent<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
Provide ad delivery or retargeting<\/div>\n\n<\/div>\n<\/details>\n
\n\t
\n\t\t

LiteSpeed<\/h3>\n\t\t

Functional<\/p>\n\t\t

\n\t\t

Usage<\/h4>\n\t\t

We use LiteSpeed for website hosting. Read more about LiteSpeed<\/a><\/p>\n\t<\/div>\n\t

\n\t\t

Sharing data<\/h4>\n\t\t

This data is not shared with third parties.<\/p>\n\t<\/div>\n\t

\n

Functional<\/h4><\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
_lscache_vary<\/a><\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
2 days<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
Preventing cached pages involves a combination of server-side and client-side strategies.\n\n**Server-Side Strategies:**\n\n* **HTTP Headers:** This is the most common and effective method. You can instruct browsers and intermediate caches (like CDNs or proxies) on how to handle caching for specific resources.\n * `Cache-Control: no-cache`: This directive tells the browser to revalidate the cached version with the origin server before using it. The server will then send a `304 Not Modified` response if the content hasn't changed, or a new version if it has.\n * `Cache-Control: no-store`: This is the strongest directive. It tells the browser and any intermediate caches not to store the response at all. The resource will be fetched from the server every time.\n * `Cache-Control: max-age=0`: Similar to `no-cache`, it means the cached version is immediately stale.\n * `Expires` header: This is an older header that specifies an expiry date\/time for the cached resource. Setting it to a date in the past effectively disables caching.\n * `Pragma: no-cache`: This is an HTTP\/1.0 header and is mainly used for backward compatibility. It's often used in conjunction with `Cache-Control`.\n * `Vary` header: This header is crucial when your page content can change based on request headers (e.g., `Accept-Encoding`, `User-Agent`, `Cookie`). If you have `Cache-Control: no-cache`, but don't use `Vary` correctly, a cached version for one user might be served to another user with different request headers. The `Vary` header tells caches which request headers should be considered when storing and retrieving cached versions.\n\n* **Dynamic Content Generation:** If your content is highly dynamic and changes frequently, it might be best not to cache it at all. Ensure your server-side code generates the content on each request.\n\n* **URL Versioning\/Query Parameters:** While this doesn't *prevent* caching, it forces browsers to treat different versions of a URL as distinct resources. For example, `style.css?v=1.2` will be cached separately from `style.css?v=1.3`. This is a common strategy for cache-busting when you *do* want to cache, but need to ensure users get the latest version after an update. If you want to *prevent* caching it, this isn't the primary method, but can be used adjunctively if the content is truly unique per request.\n\n**Client-Side Strategies (Primarily JavaScript):**\n\n* **Disabling Browser Caching with JavaScript:** You can attempt to influence browser caching behaviour using JavaScript, although this is less reliable and more resource-intensive than server-side methods.\n * Dynamically adding script tags: When you dynamically load JavaScript files using `document.createElement('script')`, you can append a timestamp or a random number as a query parameter to the URL to ensure a fresh download.\n ```javascript\n const script = document.createElement('script');\n script.src = 'path\/to\/your\/script.js?t=' + new Date().getTime();\n document.body.appendChild(script);\n ```\n * Using `fetch` or `XMLHttpRequest` with caching disabled:\n ```javascript\n fetch('your_resource.json', { cache: 'no-store' })\n .then(response => response.json())\n .then(data => { \/* process data *\/ });\n\n \/\/ For XMLHttpRequest\n const xhr = new XMLHttpRequest();\n xhr.open('GET', 'your_resource.json?t=' + new Date().getTime(), true); \/\/ Adding timestamp for cache busting\n xhr.setRequestHeader('Cache-Control', 'no-cache, no-store, must-revalidate');\n xhr.setRequestHeader('Pragma', 'no-cache');\n xhr.send();\n ```\n * Service Workers: Service workers provide more fine-grained control over network requests. You can intercept requests and decide whether to fetch from the network, use a cache, or serve an error. You can implement custom caching logic to avoid caching certain responses.\n\n**Important Considerations:**\n\n* **Performance Trade-offs:** Disabling caching can significantly degrade website performance. Resources will be downloaded from the server on every request, leading to longer load times and increased server load. Only disable caching for resources that absolutely *must* be fresh on every request.\n* **CDN Caching:** If you are using a Content Delivery Network (CDN), you'll need to configure its caching rules as well to respect your `Cache-Control` headers or to explicitly prevent caching for certain assets.\n* **User Experience:** For most web applications, aggressive caching is beneficial for user experience. Use cache-busting techniques (like versioning in URLs) to allow for caching while ensuring users get updates, rather than disabling caching entirely.\n* **Security:** For highly sensitive information that changes frequently, disabling caching is a security measure to ensure users always see the most up-to-date and relevant data.\n\n**In summary, the most robust and recommended way to prevent cached pages is by using appropriate HTTP headers (`Cache-Control: no-store`, `Cache-Control: no-cache`, and `Expires`) on the server.** Client-side JavaScript methods are supplementary and can be used for specific dynamic resource loading scenarios but should not be relied upon as the sole method for preventing caching.<\/div>\n\n<\/div>\n<\/details>\n
\n\t
\n\t\t

Wordfence<\/h3>\n\t\t

Functional<\/p>\n\t\t

\n\t\t

Usage<\/h4>\n\t\t

We use Wordfence for security and fraud prevention. Read more about Wordfence<\/a><\/p>\n\t<\/div>\n\t

\n\t\t

Sharing data<\/h4>\n\t\t

For more information, please read the Wordfence Privacy Statement<\/a>.<\/p>\n\t<\/div>\n\t

\n

Functional<\/h4><\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
wfwaf-authcookie*<\/a><\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
1 day<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
Check if the user is logged in<\/div>\n\n<\/div>\n<\/details>\n
\n\t
\n\t\t

Complianz<\/h3>\n\t\t

Functional<\/p>\n\t\t

\n\t\t

Usage<\/h4>\n\t\t

<\/p>\n\t<\/div>\n\t

\n\t\t

Sharing data<\/h4>\n\t\t

This data is not shared with third parties. For more information, please read the Complianz Privacy Statement<\/a>.<\/p>\n\t<\/div>\n\t

\n

Functional<\/h4><\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
cmplz_functioal<\/a><\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
365 days<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
Store cookie consent preferences<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
cmplz_preferences<\/a><\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
365 days<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
Store cookie consent preferences<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
cmplz_marketing<\/a><\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
365 days<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
Store cookie consent preferences<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
cmplz_consented_services<\/a><\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
365 days<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
Store cookie consent preferences<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
cmplz_policy_id<\/a><\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
365 days<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
Store accepted cookie policy ID<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
cmplz_statistics<\/a><\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
365 days<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
Store cookie consent preferences<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
cmplz_banner-status<\/a><\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
365 days<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
Store if the cookie banner has been dismissed<\/div>\n\n<\/div>\n<\/details>\n
\n\t
\n\t\t

LinkedIn<\/h3>\n\t\t

Functional, Marketing, Statistics, Preferences<\/p>\n\t\t

\n\t\t

Usage<\/h4>\n\t\t

We use LinkedIn for display of recent social posts and\/or social share buttons. Read more about LinkedIn<\/a><\/p>\n\t<\/div>\n\t

\n\t\t

Sharing data<\/h4>\n\t\t

For more information, please read the LinkedIn Privacy Statement<\/a>.<\/p>\n\t<\/div>\n\t

\n

Functional<\/h4><\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
sdsc<\/a><\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
session<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
Provide load balancing functionality<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
Li_gc<\/a><\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
6 months<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
Store cookie consent preferences<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
BizographicsOptOut<\/a><\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
10 years<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
Store privacy preferences<\/div>\n\n<\/div>
\n

Marketing<\/h4><\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
lms_ads<\/a><\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
30 days<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
Store and track visits across websites<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
_guid<\/a><\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
90 days<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
Store and track a visitor's identity<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
oatmeal<\/a><\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
1 month<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
Provide ad delivery or retargeting<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
sugar<\/a><\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
90 days<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
Store and track a visitor's identity<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
UserMatchHistory<\/a><\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
30 days<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
Provide ad delivery or retargeting<\/div>\n\n<\/div>
\n

Statistics<\/h4><\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
lms_analytics<\/a><\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
30 days<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
Store and track a visitor's identity<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
AnalyticsSyncHistory<\/a><\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
30 days<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
Store and track visits across websites<\/div>\n\n<\/div>
\n

Preferences<\/h4><\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
li_alerts<\/a><\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
1 year<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
Store if a message has been displayed<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
bcookie<\/a><\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
1 year<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
Store browser details<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
LIDC<\/a><\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
1 day<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
Provide load balancing functionality<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
Biscuit<\/a><\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
1 year<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
Save logged-in users<\/div>\n\n<\/div>\n<\/details>\n
\n\t
\n\t\t

Hotjar<\/h3>\n\t\t

Statistics<\/p>\n\t\t

\n\t\t

Usage<\/h4>\n\t\t

<\/p>\n\t<\/div>\n\t

\n\t\t

Sharing data<\/h4>\n\t\t

This data is not shared with third parties.<\/p>\n\t<\/div>\n\t

\n

Statistics<\/h4><\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
_hjSessionUser_*<\/a><\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
1 year<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
Store a unique user ID<\/div>\n\n<\/div>\n<\/details>\n
\n\t
\n\t\t

Miscellaneous<\/h3>\n\t\t

Purpose pending investigation<\/p>\n\t\t

\n\t\t

Usage<\/h4>\n\t\t

<\/p>\n\t<\/div>\n\t

\n\t\t

Sharing data<\/h4>\n\t\t

Sharing of data is pending investigation<\/p>\n\t<\/div>\n\t

\n

Purpose pending investigation<\/h4><\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
e_kit-elements-defaults<\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
localTimeZone<\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
isReturningVisitor<\/a><\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
mp_gen_new_tab_id_mixpanel_150605b3b9f979922f2ac5a52e2dcfe9<\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
mp_tab_id_mixpanel_150605b3b9f979922f2ac5a52e2dcfe9<\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
DataTables_user_identity_list_\/wp-admin\/admin.php<\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
LogLevel<\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
DataTables_policy_list_\/wp-admin\/admin.php<\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
DataTables_role_identity_list_\/wp-admin\/admin.php<\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
6cb1f90cba489c85caa3c2ee6ebd0ccc<\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
__EXT_APP_REFRESH_BLACK_SUB_DOMAINS__<\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
<\/div>\n\n<\/div>\n<\/details>\n<\/div>

7. Consent<\/h2>

When you visit our website for the first time, we will display a pop-up explaining our use of cookies. Once you click \"Save preferences\", you consent to us using the categories of cookies and plug-ins that you selected in the pop-up, as detailed in this Cookie Policy. You can disable cookies through your browser settings, but please be aware that our website may then be affected and might not function as intended.<\/p>

7.1 Manage your consent settings<\/p>