This site uses “technical” cookies and “third-party” cookies.
The purpose of this page is to describe which cookies are used, for what purposes and how you can delete them from your browser.

What are Cookies

Cookies are small data files that a browser saves on your computer or device. Cookies help the browser navigate websites, but they cannot collect any information stored on your computer or in your files. When the server uses a web browser to read cookies, they can make the website provide a more user-friendly service. To protect your privacy, the browser allows the website to access only the cookies it has already sent you and not the cookies generated by other websites.

Why we use Cookies

We use cookies to better understand how you interact with our content; cookies also help us improve your experience of visiting our website. Cookies remember the type of browser you use and store your preferences such as the language of navigation. Some cookies are permanent, others are deleted automatically when you close your web browser. How to delete cookies. Cookies are not used to store personal information; you can always delete them. The most common web browsers allow deletion on user command or automatically when the browser is closed. It is also possible to configure the web browser to block the creation of cookies, in this case it is not possible to guarantee the correct functioning of the service offered.

How to delete cookies

Cookies are not used to store personal information; you can always delete them. The most common web browsers allow deletion on user command or automatically when the browser is closed. It is also possible to configure the web browser to block the creation of cookies, in this case it is not possible to guarantee the correct functioning of the service offered.

Necessary cookies:

(These are essential cookies that do not require consent.)

__hs_opt_out
This cookie is used by the privacy opt-in policy to remember not to ask the visitor to accept cookies again.
This cookie is set when one gives visitors the option to choose not to accept cookies.
It contains the “yes” or “no” string.
It expires in 6 months

Do not track me
This cookie can be set to prevent the tracking code from sending information to HubSpot.
It contains the “yes” string.
It expires in 6 months

__hs_initial_opt_in
This cookie is used to prevent the banner from always being displayed when visitors browse in strict mode.
It contains the “yes” or “no” string.
It expires in seven days.

__hs_cookie_cat_pref
This cookie is used to record the categories to which the visitor has consented.
It contains the data relating to the agreed categories.
It expires in 6 months.

__hs_gpc_banner_dismiss
This cookie is used when you close the Global Privacy Control banner.
It contains the “yes” or “no” string.
It expires in  180 days.

__hs_notify_banner_dismiss
This cookie is used when the website uses a type of banner for consent notification.
It contains the boolean value True.
It expires in 180 days.

hs_ab_test
This cookie is used to provide visitors with the same version of an A/B test page that they have previously viewed.
It contains the ID of the A/B test page and the ID of the variant chosen for the visitor.
It expires at the end of the session.

<id>_key
When visiting a password-protected page, this cookie is set so that future visits to the page from the same browser do not require a new login.
The cookie name is unique for each password-protected page.
It contains an encrypted version of the password, so that future visits to the page do not require the password again.
It expires in 14 days.
hs-messagges-is-open
This cookie is used to determine and save if the chat widget is open for future visits.
It is set in the visitor’s browser when a new chat starts and resets to close the widget again after 30 minutes of inactivity.
If the visitor manually closes the chat widget, it will prevent the widget from reopening on subsequent page loads in that browser session for 30 minutes.
If present, it contains the boolean value True.
It expires in 30 minutes

hs-messages-hide-welcoming message
This cookie is used to prevent the chat widget welcome message from being displayed again for one day after it is closed.
It contains a boolean value of True or False.
It expires in one day.

__hsmem
This cookie is set when visitors access a site hosted by HubSpot.
It contains encrypted data that identifies the user of the subscription when they are currently logged in.
It expires in seven days.

hs-member-csrf
This cookie is used to ensure that content member logins cannot be spoofed.
It contains a random string of letters and numbers used to verify the authenticity of a user’s login.
It expires at the end of the session.

hs_langswitcher_choice
This cookie is used to save the choice of language selected by the visitor when viewing pages in multiple languages.
It is set when a visitor selects a language from the language selector and is used as a language preference to redirect them in future to sites in the chosen language, if available.
It contains a two-dot bounded string with the choice of ISO639 language code on the left and the top-level private domain it applies to on the right. An example will be “EN-US:hubspot.com”.
It expires in 2 years.

__cfruid
This cookie is set by HubSpot’s CDN provider due to its speed limitation policies. It expires at the end of the session.

__cfuvid
This cookie is set by HubSpot’s CDN provider due to its speed limitation policies. It expires at the end of the session.

__cf_bm
This cookie is set by HubSpot’s CDN provider and is a necessary cookie for bot protection.  It expires in 30 minutes.

Analytical cookies

(These are non-essential cookies controlled by the banner cookie. You can choose not to consent to these cookies.)

__hstc

• The main cookie for visitor tracking.
• It contains the domain, hubspotutk, the initial timestamp (first visit), the last timestamp (last visit), the current timestamp (this visit) and the session number (which increases for each subsequent session).
• It expires in 6 months.

hubspotutk

• This cookie keeps track of the visitor’s identity. It is transmitted to HubSpot when the form is submitted and used for contact deduplication.
• It contains an opaque GUID to represent the current visitor.
• It expires in 6 months.

__hssc

• This cookie keeps track of sessions.
• It is used to determine whether HubSpot should increase the session number and timestamps in the __hstc cookie.
• It contains the domain, the viewCount (increments each pageView in a session), and the logon timestamp.
• It expires in 30 minutes

__hssrc

• Whenever HubSpot changes the session cookie, this cookie is also set to determine if the visitor has restarted the browser.
• If this cookie does not exist when HubSpot handles cookies, it is considered a new session.
• When it is present, it contains the value “1”.
• It expires at the end of the session.

Functionality cookies

Cookie Chatflow
This is the cookie used for the chatflows tool. If you are a visitor, this allows you to chat with a representative on the site.

MessagesUtk

• This cookie is used to recognise visitors chatting via the chatflows tool. If the visitor leaves your site before being added as a contact, this cookie will be associated with their browser.
• With the setting Consent to the collection of chat cookies on: if you chat with a visitor who later returns to the site with the same browser, the chatflows tool will load the conversation history.
  • The messagesUtk cookie will be treated as a necessary cookie.
  • When the chat cookie collection Consent setting is disabled, the messagesUtk cookie is controlled by the Processing Consent setting in the chat flow.
• HubSpot will not delete the messagesUtk cookie for visitors who have been identified via the visitor identification API. The analytical cookie banner will not be impacted.
• This cookie will be specific to a subdomain and will not be transferred to other subdomains. For example, the cookie issued for info.example.com will not apply to the visitor when visiting www.example.com, and vice versa.
• It contains an opaque GUID to represent the current chat user.
• It expires after 6 months.

Other cookies

COOKIE NAME: __PHPSESSIONID
PURPOSE: Used by Museoauto to manage the .php session
EXPIRY: At the end of the session
ORIGIN: Museoauto

COOKIE NAME: __ga
PURPOSE: Used by the Google Analytics tool to identify visitors
EXPIRY: 2 years.
ORIGINS: Third Parties

COOKIE NAME: __gat
PURPOSE: Used by the Google Analytics tool to report tunneling data
EXPIRY: 10 minutes
ORIGINS: Third Parties

COOKIE NAME: viewed_cookie_policy
PURPOSE: Used by WordPress to store cookie acceptance
EXPIRY: 1 year after setup/update
ORIGINS: Third Parties

COOKIE NAME: __VISITOR_INFO1_LIVE
PURPOSE: Used by the Youtube tool to measure bandwidth
EXPIRY: At the end of the session
ORIGINS: Third Parties

COOKIE NAME: __YSC
PURPOSE: Used by the Youtube tool to expose targeted ad
EXPIRY: at the end of the session
ORIGINS: Third Parties

COOKIE NAME: __GEUP
PURPOSE: Used by the Youtube tool to acquire user georeferencing information
EXPIRY: at the end of the session
ORIGINS: Third Parties

COOKIE NAME: __PREF
PURPOSE: Used by the Youtube tool to store any user settings
EXPIRY: at the end of the session
ORIGINS: Third Parties

COOKIE NAME: __icl_current_language
PURPOSE: Used by MuseoAuto to manage language selection
EXPIRY: at the end of the session
ORIGIN: MuseoAuto

Data Controller

RECOGNIZED ASSOCIATION MUSEO NAZIONALE DELL’AUTOMOBILE “AVVOCATO GIOVANNI AGNELLI”, based in Turin, Corso Unità d’Italia n. 40

Data controller email address: privacy@museoauto.it

Since the installation of Cookies and other tracking systems operated by third parties via the services used in this Application cannot be technically controlled by the Data Controller, every specific reference to Cookies and tracking systems installed by third parties is to be considered as approximate. For more comprehensive information, Users are invited to consult the privacy policy of any third-party services listed in this document.

Given the objective complexity of identification of the technologies based on the Cookies, Users are invited to contact the Data Controller if they wish to receive any further information regarding the use of the Cookies themselves through this Website.