PLEASE READ THE COOKIE POLICY CAREFULLY AND CONFIGURE THEM IN THE SETTINGS PANEL BEFORE USING THE SERVICES OF THE www.mediatraker.com (HERE IN AFTER "MEDIATRAKER")
Cookies Policy
1. SCOPE OF APPLICATION
MEDLAB must fulfil Article 22.2 of Law 34/2002, of June 11, on Information Society Services and Electronic Commerce(LSSI-CE), as well as the recommendations that the Agencia Española de Protección de Datos (Spanish Agency for Data Protection) has published in its guide on the use of cookies. This website uses cookies and/or similar technologies that store and retrieve information when the User browses. Cookies allow a website or platform, among other things, to store and retrieve information about the browsing habits of a User or their equipment and, depending on the information they contain and the way they use their equipment, they can be used to recognise the User. The User can modify the personalised configuration HERE
2. DEFINITION AND FUNCTIONS OF COOKIES
The information provided below will help you understand the different types of cookies:
TYPES OF COOKIES | ||
---|---|---|
ACCORDING TO THE ENTITY THAT MANAGES THEM | PROPRIETARY COOKIES | These cookies are gathered by the website publisher themselves, in order to provide the service requested by the user. |
THIRD-PARTY COOKIES | These cookies are gathered and managed by a third party, and cannot be considered our own cookies. | |
ACCORDING TO THE AMOUNT OF TIME THEY REMAIN ACTIVE | SESSION COOKIES | These collect information for as long as the user browses the webpage, in order to provide the requested service. |
PERSISTENT COOKIES | These are stored in the terminal, and the information obtained will be used by the entity in charge of the cookie to provide the requested service. | |
ACCORDING TO THEIR PURPOSE | TECHNICAL COOKIES | These are needed for correct web browsing. |
CUSTOMIZATION COOKIES | These allow the user to choose certain features (e.g. language) during their browsing of the website. | |
ANALYTICAL COOKIES | These allow the provider of a service to associate browsing behaviour with a user, in order to understand their use of the webpage and to analyse statistics on the most-visited content, number of visitors, etc. | |
ADVERTISING COOKIES | These allow the website publisher to include advertisements on their webpage that are adapted to its content. | |
BEHAVIOURAL ADVERTISING COOKIES | These allow the website publisher to include advertisements on their webpage that are adapted to the information obtained on the user’s browsing habits. |
3. INFORMATION ON THE TYPE OF COOKIES USED BY MEDIATRAKER
According to what is established in Article 22.2 of Law 34/2002, of June 11,on Information Society Services and Electronic Commerce (LSSI-CE), MEDLAB must inform users of the cookies used on our website MEDIATRAKER:
COOKIES MEDIATRAKER | ||||||||
---|---|---|---|---|---|---|---|---|
PROVIDER | TYPE OF COOKIES | NAME | PURPOSE | COOKIE EXPIRATION | ||||
Microsoft Clarity | Third party | _clck | Persists the Clarity User ID and preferences, unique to that site is attributed to the same user ID. | Session | ||||
Third party | _clsk | Connects multiple page views by a user into a single Clarity session recording. | Session | |||||
Third party | CLID | Identifies the first-time Clarity saw this user on any site using Clarity. | Session | |||||
Third party | ANONCHK | Indicates whether MUID is transferred to ANID, a cookie used for advertising. Clarity doesn't use ANID and so this is always set to 0. | Session | |||||
Third party | MR | Indicates whether to refresh MUID. | Session | |||||
Third party | MUID | Identifies unique web browsers visiting Microsoft sites. These cookies are used for advertising, site analytics, and other operational purposes. | Session | |||||
Third party | SM | Used in synchronizing the MUID across Microsoft domains. | Session | |||||
Google Analytics | Third party | _ga | Used to distinguish users. | 2 years | ||||
Third party | _gid | Used to distinguish users. | 24 hours | |||||
Third party | _gat | Used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_* | 1 minute | |||||
Third party | AMP_TOKEN | Contains a token that can be used to retrieve a Client ID from AMP Client ID service. Other possible values indicate opt-out, inflight request or an error retrieving a Client ID from AMP Client ID service. | 30 seconds to 1 year | |||||
Third party | _gac_* | Contains campaign related information for the user. | 90 days | |||||
Third party | __utma | 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. | 2 years from set/update | |||||
Third party | __utmt | Used to throttle request rate. | 10 minutes | |||||
Third party | __utmb | 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. | 30 mins from set/update | |||||
Third party | __utmc | Not used in ga.js. Set for interoperability with urchin.js. Historically, this cookie operated in conjunction with the __utmb cookie to determine whether the user was in a new session/visit. | Session | |||||
Third party | __utmz | 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. | 6 months from set/update | |||||
Third party | __utmv | 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. | 2 years from set/update | |||||
Third party | __utmx | Used to determine a user's inclusion in an experiment. | 18 months | |||||
Third party | __utmxx | Used to determine the expiry of experiments a user has been included in. | 18 months | |||||
Third party | _gaexp | Used to determine a user's inclusion in an experiment and the expiry of experiments a user has been included in. | Depends on the length of the experiment, but typically 90 days. | |||||
Third party | _opt_awcid | Used for campaigns mapped to Google Ads Customer IDs. | 24 hours | |||||
Third party | _opt_awmid | Used for campaigns mapped to Google Ads Customer IDs. | 24 hours | |||||
Third party | _opt_awgid | Used for campaigns mapped to Google Ads Ad Group IDs | 24 hours | |||||
Third party | _opt_awkid | Used for campaigns mapped to Google Ads Criterion IDs | 24 hours | |||||
Third party | _opt_utmc | Stores the last utm_campaign query parameter. | 24 hours | |||||
Third party | _opt_expid | This cookie is created when running a redirect experiment. It stores the experiment ID, the variant ID and the referrer to the page that's being redirected. | 10 seconds | |||||
Hubspot | Third party | __hs_opt_out | This cookie is used by the opt-in privacy policy to remember not to ask the visitor to accept cookies again. | 6 months | ||||
Third party | __hs_do_not_track | This cookie can be set to prevent the tracking code from sending any information to HubSpot. | 6 months | |||||
Third party | __hs_initial_opt_in | This cookie is used to prevent the banner from always displaying when visitors are browsing in strict mode. | 7 days | |||||
Third party | __hs_cookie_cat_pref | This cookie is used to record the categories a visitor consented to | 6 months | |||||
Third party | __hs_gpc_banner_dismiss | This cookie is used when the Global Privacy Control banner is dismissed. | 180 days | |||||
Third party | __hs_notify_banner_dismiss | This cookie is used when the website uses a Notify consent banner type. | 180 days | |||||
Third party | hs_ab_test | This cookie is used to consistently serve visitors the same version of an A/B test page they’ve seen before. | session | |||||
Third party | When visiting a password-protected page, this cookie is set so future visits to the page from the same browser do not require login again. | 14 days | ||||||
Third party | hs-messages-is-open | This cookie is used to determine and save whether the chat widget is open for future visits.It is set in your visitor's browser when they start a new chat, and resets to re-close the widget after 30 minutes of inactivity. If your visitor manually closes the chat widget, it will prevent the widget from re-opening on subsequent page loads in that browser session for 30 minutes. | 30 minutes | |||||
Third party | hs-messages-hide-welcome-message | This cookie is used to prevent the chat widget welcome message from appearing again for one day after it is dismissed. | 1 day | |||||
Third party | __hsmem | This cookie is set when visitors log in to a HubSpot-hosted site. | 7 days | |||||
Third party | hs-membership-csrf | This cookie is used to ensure that content membership logins cannot be forged. | session | |||||
Third party | hs_langswitcher_choice | This cookie is used to save a visitor’s selected language choice when viewing pages in multiple languages. | 2 years | |||||
Third party | __cfruid | This cookie is set by HubSpot’s CDN provider because of their rate limiting policies. | session | |||||
Third party | __cfuvid | This cookie is set by HubSpot’s CDN provider because of their rate limiting policies. | session | |||||
Third party | __cf_bm | This cookie is set by HubSpot's CDN provider and is a necessary cookie for bot protection. | 30 minutes | |||||
Third party | __hstc | The main cookie for tracking visitors. | 6 months | |||||
Third party | hubspotutk | This cookie keeps track of a visitor's identity. It is passed to HubSpot on form submission and used when deduplicating contacts. | 6 months | |||||
Third party | __hssc | This cookie keeps track of sessions. This is used to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. | 30 minutes | |||||
Third party | __hssrc | Whenever HubSpot changes the session cookie, this cookie is also set to determine if the visitor has restarted their browser. | session | |||||
Third party | messagesUtk | This cookie is used to recognize visitors who chat with you via the chatflows tool. If the visitor leaves your site before they're added as a contact, they will have this cookie associated with their browser. | 6 months |
4. COOKIE SETTINGS
In addition, MEDLAB informs users that they have the option of configuring their browser so that they are informed of the reception of cookies, allowing them to prevent these cookies from being installed on their hard drive if they wish. Below, we provide links for different browsers that can be used to complete this configuration:
- For Firefox, click here: https://support.mozilla.org/en-US/kb/enable-and-disable-cookies-website-preferences
- For Chrome, click here: http://support.google.com/chrome/bin/ answer.py?hl=es&answer=95647
- For Explorer, click here: http://windows.microsoft.com/es-es/internet-explorer/delete-manage-cookies#ie=ie-10
- For Safari, click here:: https://support.apple.com/kb/ph17191?locale=en_US
- For Opera, click here: https://help.opera.com/en/latest/web-preferences/#cookies
LAST UPDATED: September 2023