TYPES OF COOKIES

DEPENDING ON THE ENTITY THAT MANAGES THEM

OWN COOKIES

They are those that are collected by the publisher himself to provide the service requested by the user.

THIRD PARTY COOKIES

They are those that are collected and managed by a third party, therefore these cannot be considered their own.

DEPENDING ON THE DEADLINE

TIME THAT

Remain

Activated

SESSION COOKIES

They collect dwhile the user browses the network in order to provide the requested service.

PERSISTENT COOKIES

They are stored in the terminal. The information obtained will be used by the person responsible for the cookie in order to provide the requested service.

ACCORDING TO ITS PURPOSE

TECHNICAL COOKIES

They are necessary for the correct navigation of the web.

PERSONALIZATION COOKIES

They allow to apply their own features for the user's navigation on the website (e.g. language).

ANALYSIS COOKIES

They allow the provider the analysis linked to the navigation carried out by the user, in order to keep track of the use of the website, as well as to perform statistics of the most visited contents, number of visitors, etc.

ADVERTISING COOKIES

They allow the publisher to include advertising spaces on the web, depending on the content of the website itself.

BEHAVIORAL ADVERTISING COOKIES

They allow the publisher to include advertising spaces on the website according to the information obtained through the user's browsing habits.

TYPE OF COOKIES

Cookie

Purpose

Expiration

WEBSITE USAGE MEASUREMENT (GOOGLE ANALYTICS

_utma

This randomly generated number is used to determine unique visitors to our site

2 years

_utmb

This randomly generated number works _utmc to calculate the average time users spend on our site

30 minutes

_utmc

This randomly generated number works _utmc to calculate the average time users spend on our site

When the boat is closed

_utmz

This is a randomly generated number and information about how a site was reached (for example, directly or through a link, organic or paid search)

6 months

ONLINE STORE CUSTOMIZATION (USES A SINGLE ENCRYPTED COOKIE TO STORE ALL SESSION INFORMATION)

date_add

The date and time of the cookie has been created (in the format YYYY-MM-DD HH: MM:SS).

20 days

id_lang

The ID of the selected language.

id_currency

The ID of the selected currency.

last_visited_category

The ID of the last category visited for product ads.

ajax_blockcart_display

If the purchasing block is "folded" or "deployed".

viewed

Product IDs viewed as a comma-separated list.

id_wishlist

The ID of the current list that is displayed in your list block.

id_guest

The visitor's customer ID when they have not authenticated

id_connections

The connection ID of the visitor's current session

id_customer

The visitor's customer ID when authenticated

customer_lastname

The customer's last name.

customer_firstname

The customer's first name

logged

If the customer is connected

Passwd

The MD5 hash of the _COOKIE_KEY_ in config / settings.inc.php and the password that the client uses to log in

email

The email address that the client uses to log in

id_cart

The ID of the current basket displayed in the shopping block.

date_add

The date and time of the cookie has been created (in the format YYYY-MM-DD HH: MM:SS).

id_lang

The ID of the selected language.

id_employee

The employee ID.

lastname

The employee's last name.

firstname

The employee's first name.

email profile

The email address the employee uses to log in

profile

The identification of the profile that determines which tabs the employee can access.

Passwd

The MD5 hash of _COOKIE_KEY_ in config/settings.inc.php and the password that the employee uses to log in

Checksum

"The Blowfish checksum is used to determine whether the cookie has been modified by a third party. If the checksum does not match, the client will have the session closed and the cookie will be cleared. "