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.
1. Introduction
Our website, https://extentis.fr/en (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.
2. What are cookies?
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.
3. What are scripts?
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.
4. What is a web beacon?
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.
5. Cookies
5.1 Technical or functional cookies
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.
5.2 Marketing/Tracking cookies
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.
5.3 Social media
On our website, we have included content from LinkedIn to promote web pages (e.g. “like”, “pin”) or share (e.g. “tweet”) 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.
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.
6. Cookies placed
Sharing data
This data is not shared with third parties.
Statistics (anonymous)
persistent
Store activities performed on the website
Sharing data
This data is not shared with third parties.
Functional
session
Store browser details
persistent
Store user preferences
1 year
Store user preferences
session
See if cookies can be placed
session
Gem language settings
persistent
Save logged-in users
Statistics
2 years
Store and count pageviews
1 year
Store and count pageviews
Marketing
persistent
Store and track conversions
persistent
Provide ad delivery or retargeting
Sharing data
This data is not shared with third parties.
Functional
2 days
Preventing cached pages involves a combination of server-side and client-side strategies.
**Server-Side Strategies:**
* **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.
* `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.
* `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.
* `Cache-Control: max-age=0`: Similar to `no-cache`, it means the cached version is immediately stale.
* `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.
* `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`.
* `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.
* **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.
* **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.
**Client-Side Strategies (Primarily JavaScript):**
* **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.
* 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.
```javascript
const script = document.createElement('script');
script.src = 'path/to/your/script.js?t=' + new Date().getTime();
document.body.appendChild(script);
```
* Using `fetch` or `XMLHttpRequest` with caching disabled:
```javascript
fetch('your_resource.json', { cache: 'no-store' })
.then(response => response.json())
.then(data => { /* process data */ });
// For XMLHttpRequest
const xhr = new XMLHttpRequest();
xhr.open('GET', 'your_resource.json?t=' + new Date().getTime(), true); // Adding timestamp for cache busting
xhr.setRequestHeader('Cache-Control', 'no-cache, no-store, must-revalidate');
xhr.setRequestHeader('Pragma', 'no-cache');
xhr.send();
```
* 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.
**Important Considerations:**
* **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.
* **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.
* **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.
* **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.
**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.
Functional
1 day
Check if the user is logged in
Functional
365 days
Store cookie consent preferences
365 days
Store cookie consent preferences
365 days
Store cookie consent preferences
365 days
Store cookie consent preferences
365 days
Store accepted cookie policy ID
365 days
Store cookie consent preferences
365 days
Store if the cookie banner has been dismissed
Functional
session
Provide load balancing functionality
6 months
Store cookie consent preferences
10 years
Store privacy preferences
Marketing
30 days
Store and track visits across websites
90 days
Store and track a visitor's identity
1 month
Provide ad delivery or retargeting
90 days
Store and track a visitor's identity
30 days
Provide ad delivery or retargeting
Statistics
30 days
Store and track a visitor's identity
30 days
Store and track visits across websites
Preferences
1 year
Store if a message has been displayed
1 year
Store browser details
1 day
Provide load balancing functionality
1 year
Save logged-in users
Sharing data
This data is not shared with third parties.
Statistics
1 year
Store a unique user ID
Sharing data
Sharing of data is pending investigation
Purpose pending investigation
e_kit-elements-defaults
localTimeZone
mp_gen_new_tab_id_mixpanel_150605b3b9f979922f2ac5a52e2dcfe9
mp_tab_id_mixpanel_150605b3b9f979922f2ac5a52e2dcfe9
DataTables_user_identity_list_/wp-admin/admin.php
LogLevel
DataTables_policy_list_/wp-admin/admin.php
DataTables_role_identity_list_/wp-admin/admin.php
6cb1f90cba489c85caa3c2ee6ebd0ccc
__EXT_APP_REFRESH_BLACK_SUB_DOMAINS__
7. Consent
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.
7.1 Manage your consent settings
You have loaded the Cookie Policy without javascript support. On AMP, you can use the manage consent button on the bottom of the page.
8. Enabling/disabling and deleting cookies
You can use your internet browser to automatically or manually delete cookies. You can also specify that certain cookies may not be placed. Another option is to change the settings of your internet browser so that you receive a message each time a cookie is placed. For more information about these options, please refer to the instructions in the Help section of your browser.
Please note that our website may not function correctly if all cookies are disabled. If you do delete the cookies in your browser, they will be placed again after your consent when you visit our website again.
9. Your rights concerning personal data
You have the following rights with respect to your personal data:
- You have the right to know why your personal data is needed, what will happen to it, and how long it will be kept for.
- Right of access: You have the right to access your personal data that we hold.
- Right to rectification: you have the right to supplement, correct, have deleted or blocked your personal data whenever you wish.
- If you give us your consent to process your data, you have the right to revoke that consent and to have your personal data deleted.
- Right to data portability: you have the right to request all your personal data from the controller and transfer it in its entirety to another controller.
- Right to object: you may object to the processing of your data. We will comply with this, unless there are justified grounds for processing.
To exercise these rights, please contact us. Please refer to the contact details at the bottom of this Cookie Policy. If you have a complaint about how we handle your data, we would like to hear from you, but you also have the right to submit a complaint to the supervisory authority (the Data Protection Authority).
10. Contact details
For questions and/or comments about our Cookie Policy and this statement, please contact us by using the following contact details:
Extentis Group
5 RUE MARGUERITTE 75017 PARIS
France
Website https://extentis.fr/en
Email: jazuelos@ex.comextentis.fr
07633 13204
This Cookie Policy was synchronised with cookiedatabase.org On February 11, 2026.
