WHAT IS A COOKIE?
A cookie is a small computer file, a marker, which is stored and read on a device for example during the consultation of a website, the reading of an email or the installation or use of a software program or a mobile application, whatever the type of device used (computer, smartphone, tablet, etc.)
In this policy, we use the term “Cookies” to refer to all the markers stored and read on your device.
IMPORTANT INFORMATION CONCERNING CONSENT
The storing or reading of certain Cookies does not require prior obtaining of your consent, either because they do not process any Personal Data concerning you, or because they are strictly necessary for the provision of the service which you require.
Your prior consent must be obtained for the storing or reading of Cookies other than those mentioned in the paragraph above.
You may at any time oppose the storing or reading of the Cookies which we use, either by deleting them from your devices or by changing your browser settings.
Vein-Academy on behalf of Les Laboratoires Servier undertakes not to communicate the content of these cookies to third parties, unless they have an obligation to do so, as ordered by a judicial or administrative authority.
WHAT COOKIES DO WE USE?
We use various types of cookies whose purposes are described below.
- Functional cookies
These are the cookies which enable to archive your browsing preferences on our site/our application by storing the various options you chose during your last visit. We can thus propose them to you again to simplify your browsing on our website (e.g. the choice of the version to be displayed, standard or mobile-optimised). You can oppose them and delete them via your browser settings, but your user experience is liable to be impaired.
This concerns the following cookies:
|Name of cookie||Data collected||Purpose||Storage time|
|Tarteaucitron||Consent for each service||Records your consent or refusal for each service used by this site||13 months|
- Analytical cookies
These are cookies which tell us about the use and performances of our website and allow us to draw up statistics on traffic volumes and use of the various elements of our site/our application (contents visited and visitor paths), enabling us to make our services more interesting and user-friendly (pages or sections most often consulted, most read articles, etc.).
If you give your approval (consent), SERVIER will store cookies enabling collection of the information strictly necessary for the purposes described in the table below.
This concerns the following cookies:
|Name of cookie||Purpose||Expiration|
|_ga||Visitor identification||6 months|
|_gid||User journey||24 hours|
|_gat||Throttling request rate||10 minutes|
|_hjClosedSurveyInvites||Hotjar cookie that is set once a user interacts with an External Link Survey invitation modal. It is used to ensure that the same invite does not reappear if it has already been shown.||365 days|
|_hjDonePolls||Hotjar cookie that is set once a user completes a survey using the On-site Survey widget. It is used to ensure that the same survey does not reappear if it has already been filled in.||365 days|
|_hjMinimizedPolls||Hotjar cookie that is set once a user minimizes an On-site Survey widget. It is used to ensure that the widget stays minimized when the user navigates through your site.||365 days|
|_hjShownFeedbackMessage||Hotjar cookie that is set when a user minimizes or completes Incoming Feedback. This is done so that the Incoming Feedback will load as minimized immediately if the user navigates to another page where it is set to show.||365 days|
|_hjSessionTooLarge||Causes Hotjar to stop collecting data if a session becomes too large. This is determined automatically by a signal from the WebSocket server if the session size exceeds the limit.||Session|
|_hjSessionRejected||If present, this cookie will be set to '1' for the duration of a user's session, if Hotjar rejected the session from connecting to our WebSocket due to server overload. This cookie is only applied in extremely rare situations to prevent severe performance issues.||Session|
|_hjSessionResumed||A cookie that is set when a session/recording is reconnected to Hotjar servers after a break in connection.||Session|
|_hjid||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.||365 days|
|_hjRecordingLastActivity||This should be found in Session storage (as opposed to cookies). This gets updated when a user recording starts and when data is sent through the WebSocket (the user performs an action that Hotjar records).||Session|
|_hjTLDTest||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|
|_hjUserAttributesHash||User Attributes sent through the Hotjar Identify API are cached for the duration of the session in order to know when an attribute has changed and needs to be updated.||Session|
|_hjCachedUserAttributes||This cookie stores User Attributes which are sent through the Hotjar Identify API, whenever the user is not in the sample. Collected attributes will only be saved to Hotjar servers if the user interacts with a Hotjar Feedback tool, but the cookie will be used regardless of whether a Feedback tool is present.||Session|
|_hjLocalStorageTest||This cookie is used to check if the Hotjar Tracking Script can use local storage. If it can, a value of 1 is set in this cookie. The data stored in_hjLocalStorageTest has no expiration time, but it is deleted almost immediately after it is created.||Under 100ms|
|_hjIncludedInPageviewSample||This cookie is set to let Hotjar know whether that user is included in the data sampling defined by your site's pageview limit.||30 minutes|
|_hjIncludedInSessionSample||This cookie is set to let Hotjar know whether that user is included in the data sampling defined by your site's daily session limit.||30 minutes|
|_hjAbsoluteSessionInProgress||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|
|_hjFirstSeen||This is set to identify a new user’s first session. It stores a true/false value, indicating whether this was the first time Hotjar saw this user. It is used by Recording filters to identify new user sessions.||Session|
|_hjViewportId||This stores information about the user viewport such as size and dimensions.||Session|
|_hjRecordingEnabled||This is added when a Recording starts and is read when the recording module is initialized to see if the user is already in a recording in a particular session.||Session|
More information on the Hotjar cookies :
For further details, please see the ‘about Hotjar’ section of Hotjar’s support site.
The functionalities of this site listed below are based on services offered by third parties (video).
If you agree (consent), these third parties will deposit Cookies that will allow you to view content hosted by these third parties directly on the site address or to share our content.
This page allows you to give or withdraw your consent, either globally or purpose by purpose.
Preferences for all services : Cookies Management
Videos : The purpose of the cookies stored via the video sharing services is to enable the user to view multimedia content directly on the site.
To exercise your rights over the data collected by third parties, or for any question concerning this processing, you can contact them directly.
HOW DO YOU CONFIGURE YOUR BROWSER, SMARTPHONE AND SOFTWARE COMPONENTS?
If you have accepted the recording of Cookies in your browser software, they are stored in a dedicated area of your device.
If you refuse the recording of Cookies in your device or if you delete those which are recorded in it, you will no longer be able to benefit from certain functions even though they are necessary for browsing in certain areas of our website/our application. If applicable, we decline all responsibility for any consequences due to the downgraded operation of our website/our application resulting from the fact that it is impossible for us to store or consult the Cookies necessary for their functioning which you have deleted or refused.
How do you configure your browser?
Most browsers accept Cookies by default. However, you can decide to block these Cookies or ask your browser to inform you when a site attempts to install a Cookie on your device.
Please refer to your browser’s help menu to configure the Cookies according to your preferences. The links to the cookie setting instructions for the main browsers are given below:
- Internet Explorer: https://support.microsoft.com/en-us/help/278835/how-to-delete-cookie-files-in-internet-explorer
- Google Chrome: https://support.google.com/accounts/answer/61416?hl=en
- Mozilla Firefox: https://support.mozilla.org/en-US/kb/enhanced-tracking-protection-firefox-desktop
- Microsoft Edge: https://support.microsoft.com/en-us/help/10607
- Safari: https://help.apple.com/safari/mac/9.0/?lang=en#/sfri11471
- Opera: https://help.opera.com/en/latest/web-preferences/#cookies
How do you configure your confidentiality settings in your smartphone/tablet?
You can decide to change the confidentiality settings of your smartphone/tablet.
To configure your confidentiality settings:
- Android system: https://support.google.com/chrome/answer/95647?co=GENIE.Platform%3DAndroid&hl=en
- Apple system: https://support.apple.com/en-us/HT201265