Cookie Policy
General informations
What are cookies?
Cookies are small text files that the sites visited by users send to their terminals, where they are stored before being re-transmitted to the same sites on the next visit. Cd cookies “third parties” are instead set by a website other than the one the user is visiting. This is because on each site there may be elements (images, maps, sounds, specific links to web pages of other domains, etc.) that reside on servers other than that of the site visited.
What are cookies for?
Cookies are used for different purposes: computer authentication, session monitoring, storing information on specific configurations concerning users accessing the server, storing preferences, etc.
What are “technical” cookies?
These are cookies used to browse or provide a service requested by the user. They are not used for other purposes and are normally installed directly by the website owner. Without the use of these cookies, some operations could not be performed or would be more complex and / or less secure, such as, for example, home banking (account statement display, bank transfers, bill payments, etc.), for the which cookies, which allow you to make and keep the user’s identification within the session, are essential.
Analytics cookies are “technical” cookies?
No. The Guarantor (see provision of 8 May 2014) has specified that they can be assimilated to technical cookies only if used for the purpose of optimizing the site directly by the owner of the site itself, which can collect information in aggregate form on the number of users and how they visit the site. Under these conditions, for analytics cookies the same rules apply, in terms of information and consent, provided for technical cookies.
What are “profiling” cookies?
These are cookies used to track user browsing on the net and create profiles on his tastes, habits, choices, etc. With these cookies advertising messages can be transmitted to the user’s terminal in line with the preferences already shown by the same user while browsing online.
Specific information on the use of cookies by the site
What cookies does this site use?
Only analytical cookies (analytics) with the characteristics and value of technical cookies.
Below is the list of cookies used:
GOOGLE COAL COOKIES:
__ga: cookie duration 10 min.
__gat: duration of the cookie 2 years.
__utma: duration of the cookie 2 years.
__utmb: cookie duration 30 min.
__utmc: cookie duration until the end of the session (browser closing)
__utmz: duration of the cookie 6 months.
__utmt: cookie duration 10 min.
__utmv: duration of the cookie 2 years.
COOKIE ANALYTICS OF SHINYSTAT
SSID_maxillo: duration of the cookie until the end of the session (browser closing)
SV_maxillo: duration of the cookie until the end of the session (browser closing)
SN_maxillo: duration of the cookie 6 months
PHPSESSID: duration of the cookie until the end of the session (browser closing)
All the aforementioned cookies are third-party cookies (Google Analytics and ShinyStat) whose service is aimed at the statistics of access to the site. For an in-depth description, read the following paragraphs.
Google Analytics and use of cookies
Google analytics is a web traffic analysis service provided by Google, Inc. (“Google”). These are third-party cookies collected and managed anonymously to monitor and improve the performance of the host site (performance cookies).
For example, the __utma cookie keeps track of the number of times a visitor has been on the site and when it was the first and last visit.
The __utmb and __utmc cookies work together, in the sense that the first captures the exact moment when the user enters the site and the second the exact moment when the user leaves the site, in order to calculate the time the actual user spent on the site.
The __utmz cookie keeps track of the visitor’s origin, which search engine was used, which link was clicked, which keyword was used to find the site page, and in which city of the world you are located when you have accessed the website.
The __utmt cookie gives an indication of a temporary status, and is used to check the rate of requests that customers can make for an API.