Version 1.0 – September 2022
The Site and the Platform use cookies for the following purposes: provide you with a better browsing experience, perform computer authentication, monitor sessions, store information on specific configurations of users accessing the server.
This document provides detailed information on the use of cookies and similar technologies, how they are used on the Site and the Platform and how to manage them.
Users have the possibility to configure their browser in order to be notified of the receipt of cookies or to refuse them. The acceptance of cookies by the browser can be disabled by changing the above settings.
For further information on the processing of personal data by the Data Controller click here.
- DEFINITIONS
- Cookies are short text fragments (letters and/or numbers) that allow the web server to store information on the browser to be reused during the same visit to the Website (session cookies) or later, even after a few days (persistent cookies). Cookies are stored, according to the user’s preferences, by the individual browser on the specific device used (computer, tablet, smartphone).
- There are different categories of cookies, with different characteristics and uses:
- Technical cookies: these are cookies that are essential for the proper functioning of the Website and are used for the sole purpose of carrying out the transmission of a communication over an electronic communication network, or to the extent strictly necessary for the provider of an information society service explicitly requested by the subscriber or user to provide such a service;
- Analytical cookies: these are cookies used to collect and analyse Website traffic and usage in an anonymous way. These cookies do not identify the user, but they allow us, for example, to detect whether the same user returns to the Website at different times. They also allow us to monitor the system and improve its performance and usability. These cookies can be deactivated without any loss of functionality.
- Profiling cookies: these are persistent cookies used to identify (anonymously or otherwise) the user’s preferences and improve the user’s browsing experience; they are often used to create profiles of the user and are used to send advertisements in line with the preferences expressed by the user while browsing the web.
- Third-party cookies (analytical and/or profiling): these are cookies generated by organisations that are not part of the Website, but which are integrated into parts of the Website’s pages. Examples include Google widgets (e.g. Google Maps) or social plug-ins (Facebook, Twitter, LinkedIn, etc.).
- The handling of information collected by “third parties” is governed by their policies, which you should refer to, and which for your convenience are indicated in the links below.
- The Site and the Platform use the following cookies:
N. | ID cookie | Party | Provider | Type | Purpose | Duration | Further information |
1 | __cf_bm | Third | HubSpot / Cloudflare | Technical | Security | 30 minutes | This cookie is set by HubSpot’s CDN provider and is a necessary cookie for bot protection. It expires in 30 minutes. Learn more about Cloudflare cookies. |
2 | __hs_cookie_cat_pref | First | publicpressure.io | Technical | Technical | 1 year | Cookie that stores the category of cookies to which the user has already given consent. |
3 | __hs_do_not_track | First | publicpressure.io | Technical | Technical | 6 months | This cookie can be set to prevent the tracking code from sending any information to HubSpot. |
4 | __hs_opt_out | First | publicpressure.io | Technical | Technical | 1 year | Set by Piwik PRO. This cookie is used by the opt-in privacy policy to remember not to ask the visitor to accept cookies again. |
5 | __hssc | Third | HubSpot | Analytics | Traffic analysis | 30 minutes | This cookie keeps track of sessions. This is used to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. It contains the domain, viewCount (increments each pageView in a session), and session start timestamp. |
6 | __hssrc | Third | HubSpot | Analytics | Traffic analysis | Session | Whenever HubSpot changes the session cookie, this cookie is also set to determine if the visitor has restarted their browser. If this cookie does not exist when HubSpot manages cookies, it is considered a new session. It contains the value “1” when present. |
7 | __hstc | Third | HubSpot | Analytics | Traffic analysis | 6 months | The main cookie for tracking visitors. It contains the domain, utk, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session). |
8 | _hjAbsoluteSessionInProgress | Third | HotJar | Analytics | Traffic analysis | 30 minutes | This cookie is used by HotJar to detect the first pageview session of a user. This is a True/False flag set by the cookie. |
9 | _hjFirstSeen | Third | HotJar | Analytics | Traffic analysis | Session | Identifies a new user’s first session on a website, indicating whether or not Hotjar’s seeing this user for the first time. |
10 | _hjIncludedInSessionSample | Third | HotJar | Analytics | Traffic analysis | 30 minutes | This cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by your site’s daily session limit. |
11 | _hjSession_NNNNNNN | Third | HotJar | Analytics | Traffic analysis | 30 minutes | A cookie that holds the current session data. This ensues that subsequent requests within the session window will be attributed to the same Hotjar session. |
12 | _hjSessionUser_NNNNNNN | Third | HotJar | Analytics | Traffic analysis | 1 year | Hotjar cookie that is set when a user 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. |
13 | _hjIncludedInPageviewSample | Third | HotJar | Analytics | Traffic analysis | 30 minutes | Set to determine if a user is included in the data sampling defined by your site’s pageview limit. |
14 | _hjIncludedInSessionSample | Third | HotJar | Analytics | Traffic analysis | 30 minutes | Set to determine if a user is included in the data sampling defined by your site’s daily session limit. |
15 | _pk_id.<…> | First | publicpressure.io | Analytics | Traffic analysis | 13 months | Set by Piwik PRO. Used to recognize visitors and hold their various properties. |
16 | _pk_ses.<…> | First | publicpressure.io | Analytics | Traffic analysis | 30 minutes | Shows an active session of the visitor. If the cookie isn’t present, the session has finished over 30 minutes ago and it was counted in a pk_id cookie. |
17 | hubspotutk | First | publicpressure.io | Analytics | Traffic analysis | 6 months | Keeps track of user identity. It is communicated to HubSpot when the form is submitted and used during contact deduplication. |
18 | messagesUtk | Third | HubSpot | Technical | Technical | 6 months | This cookie is used to recognize visitors who chat with us 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. If you chat with a visitor who later returns to your site in the same cookied browser, the chatflows tool will load their conversation history. It contains an opaque GUID to represent the current chat user. |
19 | stg_externalReferrer | First | publicpressure.io | Analytics | Traffic analysis | Session | Set by Piwik PRO. Stores an URL of a website that referred a visitor to your website. |
20 | stg_last_interaction | First | publicpressure.io | Analytics | Traffic analysis | 1 year | Set by Piwik PRO. Determines whether the last visitor’s session is still in progress or a new session has started. |
21 | stg_returning_visitor | First | publicpressure.io | Analytics | Traffic analysis | 1 year | Set by Piwik PRO. Determines if the visitor has already been to your website — they are returning visitors. |
22 | stg_traffic_source_priority | First | publicpressure.io | Analytics | Traffic analysis | 30 minutes | Set by Piwik PRO. Stores the type of traffic source that explains how the visitor reached your website. |
23 | __smToken | First | publicpressure.io | Technical | Technical | 1 year | Set by Sumo. The __smUser cookie is set when a user logs in to Sumo on the website and the cookie value is the User ID |
24 | __smVID | First | publicpressure.io | Technical | Technical | Session | Set by Sumo. Sumo cookie for logged in users |
25 | __smListBuilderShown | First | publicpressure.io | Technical | Technical | Session | Set by Sumo. Purposes and functionality not explained by Sumo (https://sumo.com/) |
26 | __smSubscribed | First | publicpressure.io | Technical | Technical | Session | Set by Sumo. Purposes and functionality not explained by Sumo (https://sumo.com/) |
27 | __smUser | First | publicpressure.io | Technical | Technical | Session | Set by Sumo. Purposes and functionality not explained by Sumo (https://sumo.com/) |
28 | PHPSESSID | First | publicpressure.io | Technical | Technical | Session | The PHPSESSID cookie is a native PHP cookie and allows websites to store session state data. On the website, it is used to establish a user session and to communicate status data via a temporary cookie, commonly referred to as a session cookie. Since the PHPSESSID cookie has no expiry date, it disappears when the client is closed. |
- For further information about HubSpot cookies, see https://knowledge.hubspot.com/reports/what-cookies-does-hubspot-set-in-a-visitor-s-browser
- For further information about HotJar cookies, see https://help.hotjar.com/hc/en-us/articles/6952777582999-Cookies-Set-by-the-Hotjar-Tracking-Code#tracking_code_cookies;
- For further information about Piwik PRO cookies, see https://help.piwik.pro/support/privacy/cookies-created-by-piwik-pro/
- MANAGEMENT
- The User can decide whether or not to accept cookies by using the settings of his browser.
- The usability of the contents is also possible by completely disabling cookies, with the exception of “session” cookies if the User wishes to authenticate himself, and the disabling of “third party” cookies does not affect the navigability of the Website in any way.
- The setting can be defined specifically for different websites and web applications. Moreover, the best browsers allow you to define different settings for different types of cookies:
- Firefox: Managing cookies | Firefox support
- Microsoft Edge: Delete and manage cookies in Microsoft Edge
- Chrome: Delete, enable and manage cookies in Chrome – Android – Google Chrome Help
- Opera: Web preferences – Opera Help
- Safari for Mac: https://support.apple.com/it-it/guide/safari/sfri11471/mac
- Safari for iOS: How to clear history and cookies from Safari on iPhone, iPad or iPod touch
- Please note that it is possible to use special tools to manage privacy regarding cookies for advertising purposes, such as Your Online Choices (https://www.youronlinechoices.com/), limited to advertising networks that adhere to the initiative. For further information, https://edaa.eu/