Cookies policy

This website uses cookies. Cookies on this website are used to personalize content and ads, provide social media features and analyze traffic. Additionally, we share information about your use of the website with our social media, advertising and analytics partners who may combine it with other information that you have provided to them or that they have collected from your use of their services.

Cookies are small text files that websites can use to make the user experience more efficient.

The law states that we can store cookies on your device if they are strictly necessary for the operation of this page. For all other types of cookies we need your permission.

This page uses different types of cookies. Some cookies are placed by third party services that appear on our pages.

You can change or withdraw your consent at any time from the Cookie Statement on our website.

Find out more about who we are, how you can contact us and how we process personal data in our Privacy Policy.

When contacting us regarding your consent, please indicate the ID and date of your consent.

Your consent applies to the following domains:

Necessary cookies help make a website usable by enabling basic functions such as page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

What are cookies?

Cookies are small data files that a web server stores in our browser when we visit a page. There are many types of  cookies . The purposes of these files are varied, among others, collecting information about the user’s browsing habits and their activity within the website, as well as storing access data to the site (username, password, page personalization, date of last visit). , etc.) making web browsing more comfortable for the user. Some  cookies  also allow the user to be tracked between websites, creating an anonymous profile aimed at use by online marketing companies.

Generally, they do not represent a problem if they are  cookies  for own use or within the site, since these have a functional mission. If, on the other hand, they are   third-party cookies , they can collect personal data that could put the user’s privacy at risk.

Types of cookies and functions

Although there are several classifications of  cookies  depending on who manages them and their purpose, in this article we will focus on the most common and used ones, which are classified according to the time they remain active:

  • Session cookies:  data is collected only while the user remains on the website, then it is deleted.
  • Persistent:  data is collected that can remain stored for a certain period of time defined by the website administrator.

 Types of cookies according to their purpose

Technical cookies: They allow the user to navigate through the website or platform and use the different options or services that exist there, such as, for example, controlling traffic and data communication, identifying the session, accessing restricted access parts, use security elements during navigation or store content for the dissemination of videos or sound or share content through social networks. These are session and persistent cookies.

Personalization cookies: They allow the user to access the service with some predefined characteristics based on a series of criteria on the user’s terminal, such as the type of browser through which the service is accessed, the regional configuration from which the service is accessed. , etc. Third parties such as Google, YouTube or Twitter use this type of persistent personalization cookies regarding their services.

Analytical cookies: These are those that allow us to quantify the number of users and thus carry out the measurement and statistical analysis of the use made by users of our website. To do this, your navigation on our website is analyzed in order to improve it.

Cookie legislation

Cookies   appear for the first time in the  LSSI-CE , Law on Information Society Services and Electronic Commerce, and the former LOPD, Organic Law on Protection of Personal Data, and from the beginning they raised many comments, both from users , as well as companies and particularly in the online marketing sector. A controversial aspect has been knowing when and how to ask for consent.

Currently, the LSSI-CE is still in force and data protection is regulated by the  LOPDGDD  (LOPD and Digital Rights Guarantee) and by the European Data Protection Regulation or  RGPD . In Europe,  cookies  have been the subject of the  e-Privacy directive , now in the Regulation proposal phase and therefore still subject to modifications. This regulation, once approved, will be mandatory for all EU member countries.

The Spanish Data Protection Agency has recently published a  Guide on the use of cookies  to guide web page designers and administrators and online marketing companies in the use of cookies  according  to current legislation.

Cases where it is not necessary to ask the user for consent

For a  cookie  to be exempt from the user’s consent, its expiration must be related to its purpose, being as minimal as possible, or being eliminated in a short period of time. Thus, GT29 (Working Group 29) currently replaced by the EDPB (European Data Protection Committee)  has interpreted  that the  cookies  that may be excluded from the consent request would be those whose purpose is:

  •  “user input” cookies ;
  •  authentication or user identification (session) cookies ;
  •  media player cookies ;
  • session cookies  for load balancing on the web server;
  •  interface customization cookies ;
  •  Plug  -in cookies  for exchanging social content.
It is understood that this type of cookies would be exempt from the scope of application of article 22.2 of the LSSI and it would not be necessary to inform or obtain consent from the user. Although for reasons of transparency, it is recommended to notify the user about their use, either in the cookie policy or in the privacy policy.
Below are a series of informative links on this issue of the most used browsers:

Google Chrome:

Mozilla Firefox:

Internet Explorer:

4.2. How to deactivate or delete cookies

To deactivate, restrict, block or delete cookies, the user must modify the settings of the browser used on their terminal, whether computer, smartphone or tablet. In general, browsers offer the following configuration options in relation to the installation of cookies:
That the browser rejects all cookies and therefore, that no cookie from any web page is installed on your terminal.
Let the browser notify you before the cookie is installed so that you can decide whether or not to accept its installation.
That the browser only rejects third-party cookies from the websites you visit but not those used by the website you browse.

The browsing option in private mode through which cookies are installed on the terminal but are automatically deleted when browsing the website ends:

Google Chrome:

Mozilla Firefox:

Internet Explorer:

Google cookie nameDefault durationDescription
_ga2 yearsIt is used to distinguish users.
_gid24 hoursIt is used to distinguish users.
_ga_<container-id>2 yearsIt is used to maintain the session state.
_gac_gb_<container-id>90 daysIncludes information related to the campaign. If you have linked your Google Analytics and Google Ads accounts, Google Ads website conversion tags will read this cookie unless you disable it.
_ga2 yearsIt is used to distinguish users.
_gid24 hoursIt is used to distinguish users.
_gat1 minuteUsed to limit the percentage of requests. If Google Analytics has been implemented through Google Tag Manager, this cookie will be called  ._dc_gtm_<property- id>
AMP_TOKENFrom 30 seconds to 1 yearIncludes a token that can be used to retrieve a client ID from the AMP Client ID service. Other possible values ​​indicate disables, requests in progress, or errors obtained when retrieving an ID from the AMP Client IDs service.
_gac_<property-id>90 daysIncludes campaign information related to the user. If you have linked your Google Analytics and Google Ads accounts, Google Ads website conversion tags will read this cookie unless you disable it.
__utma2 years from configuration or updateUsed to distinguish users and sessions. The cookie is created when the JavaScript library is executed and there is no __utma cookie. The cookie is updated each time data is sent to Google Analytics.
__utmt10 minutesUsed to limit the percentage of requests.
__utmb30 minutes from configuration or updateIt is used to determine new sessions or visits. The cookie is created when the JavaScript library is executed and there is no __utmb cookie. The cookie is updated each time data is sent to Google Analytics.
__utmcEnd of browser sessionNot used in ga.js. It is configured for interoperability with urchin.js. Previously, this cookie acted in conjunction with the cookie   to determine if the user was in a new session or visit.__utmb
__utmz6 months from configuration or updateStores the traffic source or campaign that explains how the user arrived at the website. The cookie is created when the JavaScript library is executed and is updated each time data is sent to Google Analytics.
__utmv2 years from configuration or updateUsed to store custom variable data at the visitor level. This cookie is created when a developer uses the method  _setCustomVar with a visitor custom variable. It was also used for the method  , which is no longer available. The cookie is updated each time data is sent to Google Analytics._setVar

The user of this website is notified that the cookies mentioned on this page may be used in whole or in part.

The versions in languages other than Spanish of this website are made with the Google translator, which automatically translates the published text while browsing. The translation is not proofread, so it may contain errors.

Any question