Cookie Notice | Hitachi Rail
Cookie Notice
The following cookie notice relates to the same legal entities as covered by the privacy notice.
General information
What are cookies?
In general, a cookie is a small amount of data (text file), which may contain a single anonymous ID code and which is usually sent from a web server of the website visited on the user’s device (computer, notebook, tablet, smartphone) to the web browsing software (browser) of the website visitor, to be subsequently re-sent to the visited website at the subsequent visit. The cookie is then read again and identified only by the website which has sent it whenever the user visits that website. When browsing, users may also receive cookies on their device which are then sent from other websites or web servers (the so-called “third parties”), which may contain some elements (such as, for example, images, maps, sounds, specific links to pages of other domains) present on the website the user is visiting.
Cookies may be used for various purposes: monitoring sessions, storing information on specific settings regarding the users who access the server, carrying out authentication processes, etc.
It is possible to define and classify them in various ways, for example by distinguishing between “technical” and “profiling” cookies.
Technical cookies
Technical cookies are those cookies used for the sole purpose of “carrying out the transmission of a communication on an electronic communications network, or insofar as this is strictly necessary to the provider of an information society service that has been explicitly requested by the contracting party or user to provide said service” and their use does not require the user’s consent.
They are not used for additional purposes and are normally installed directly by the website owner or manager. They may be classified as follows:
- browsing or session cookies: they ensure the normal website browsing experience and website use;
- analytics cookies, similar to technical cookies when used directly by the website manager to collect information in aggregate form on the number of users and their browsing habits;
- functionality cookies, which enable users to browse the website based on a set of selected criteria (for example their preferred language) in order to improve the service provided.
Profiling cookies
Profiling cookies are aimed at creating user profiles and are used to send advertising messages in line with the preferences shown by the user during their navigation on the web. Web users must be adequately informed of the use of such cookies and must consent to such use.
Third-party cookies
These enable the website to remember the user data throughout their visit (and for subsequent visits) enabling the user to browse the pages efficiently, interact with social networks, and use third party services.
Any browser may be set to accept all cookies, to reject them all or to receive a notice at the time of receipt. It is also possible to delete the cookies which have been stored on one’s computer. In the following websites it is possible to find information on the cookie settings of the most widespread browsers:
Mozilla Firefox
Google Chrome
Internet Explorer
Safari
Opera
De-activating some cookies may limit the website functions.
Most of the services provided through the Hitachi Rail website do not require the acceptance of cookies. However, blocking cookies completely may result in some services provided by Hitachi Rail becoming unavailable.
How Hitachi Rail uses cookies
Hitachi Rail uses cookies for the following reasons:
to track records of navigation sessions on its website in anonymous form;
to avoid that opinion surveys or pop-up windows, if any, are brought to the attention of the user more than once;
Hitachi Rail uses cookies for anonymous profiling; to gain information on the browser used (eg. Chrome), the country the user is in, and an anonymous user ID reference.
Amendments to this cookie notice
At Hitachi Rail's discretion, the contents of this document may be amended in future, for example in those cases in which should Hitachi Rail decide to add or remove options or characteristics of its own services and products, or should Hitachi Rail decide to rely on new content providers.
Below is a list of the cookies used in this website, divided by category:
Essential cookies
Name | Purpose | Duration | 1st or 3rd party | Essential |
---|---|---|---|---|
UMB-XSRF-V | Stores the backoffice antiforgery token validation value | Session | 1st | Yes |
UMB_UCONTEXT | Stores an ID of the user's session (CMS) | 15 minutes | 1st | Yes |
UMB_UCONTEXT_C | Session context cookie used by CMS | Session | 1st | Yes |
UMB-XSRF-TOKEN | Passes authentication token used for antiforgery (CMS) | Session | 1st | Yes |
UMB_UPDCHK | Enables the system to check for Umbraco software updates | Session | 1st | Yes |
UMB_Preview | Enables a page being edited in Umbraco to be previewed in your browser | Session | 1st | Yes |
UMB-WEBSITE-PREVIEW-ACCEPT | Tracks whether the user has accepted entering Preview Mode when visiting the site | Session | 1st | Yes |
UMB_SESSION | Preserves the visitor’s session state across multiple page requests | Session | 1st | Yes |
LR_disclaimer | Records the user’s acknowledgement of a disclaimer | Session | 1st | Yes |
ApplicationGatewayAffinity | Azure Application Gateway session affinity | Session | 1st | Yes |
ApplicationGatewayAffinityCORS | Maintains sticky sessions for cross-origin-request | Session | 1st | Yes |
CookieControl | Set in the browser when a backoffice user logs in | Session | 1st | Yes |
ASP.NET_SessionId | Stores a unique session identifier for each visitor | Session | 1st | Yes |
Analytics cookies
Name | Purpose | Duration | 1st or 3rd party | Essential |
---|---|---|---|---|
_ga | Collects analytics data | 1 year | 1st | No |
_gid | ID used to identify users for 24 hours | 24 hours | 1st | No |
Functional cookies
Name | Purpose | Duration | 1st or 3rd party | Essential |
---|---|---|---|---|
_cf_bm | Distinguishes between humans and bots | 30 minutes | 3rd | No |
_cfuvid | Used by Cloudflare WAF to distinguish users on the same IP | Session | 3rd | No |
_cfduid | Set by Cloudflare service to identify trusted web traffic | 5 years | 1st | Yes |
_cfruid | Used by the content network, Cloudflare to identify trusted web traffic | Session | 1st | Yes |
cf_chl_2 | Used by Cloudflare for the execution of JavaScript or Captcha challenges | Session | 1st | Yes |
_cflb | When enabling session affinity with Cloudflare Load Balancer, Cloudflare sets a __cflb cookie with a unique value on the first response to the requesting client. | 30 minutes | 1st | Yes |
cf_clearance | Whether a CAPTCHA or JavaScript challenge has been solved | 1 year | 1st | Yes |
Media cookies
Name | Purpose | Duration | 1st or 3rd party | Essential |
---|---|---|---|---|
player | Vimeo player settings | 1 year | 1st | No |
vuid | Vimeo analytics on embedded videos | 1 year | 1st | No |
continuous_play_v3 | Keeps track of whether continuous play is on or not for a user | 2 years | 3rd | No |
Azure cookies
Name | Purpose | Duration | 1st or 3rd party | Essential |
---|---|---|---|---|
buid | Used by Microsoft to securely identify your login information | 30 days | 1st | Yes |
esctx | Used by Microsoft to securely identify your login information | Session | 1st | Yes |
fpc | Used by Microsoft to securely identify your login information | 30 days | 1st | Yes |
stsservicecookie | Azure Active Directory B2C-verification | Session | 1st | Yes |
ARRAffinity | Ensures that requests from one visitor’s browsing session are always handled by the same server in the cluster | Session | 1st | Yes |
ARRAffinitySameSite | Ensures that requests from one visitor’s browsing session are always handled by the same server in the cluster | Session | 1st | Yes |
_AntiXsrfToken | Used to prevent Cross-site request forgery attacks of the website | Session | 1st | Yes |
.ASPXANONYMOUS | Configures anonymous identification for application authorization | 2 months | 1st | Yes |
.ASPXAUTH | Identifies if the user is authenticated | Session | 1st | Yes |
nSGT- | Used by Microsoft to securely verify your Sharepoint login information | Session | 3rd | No |
RpsContextCookie | Used by Microsoft to securely verify your Sharepoint login information | Session | 3rd | No |
ASLBSACORS | Used to direct your browser to the appropriate back-end server | Session | 1st | Yes |
ASLBSA | Used to direct your browser to the appropriate back-end server | Session | 1st | Yes |
ASPSESSIO | Browsing session: the asterisks identify an alphanumerical code that varies from session to session in automatic mode | Session | 1st | Yes |
VisitorStorageGuid | Used to keep a user session on the same server | Session | 1st | Yes |
ApplicationGatewayAffinity | Azure Application Gateway session affinity | Session | 1st | Yes |
ApplicationGatewayAffinityCORS | Maintains sticky sessions for cross-origin-request | Session | 1st | Yes |
Google, YouTube and Advertising cookies
Name | Purpose | Duration | 1st or 3rd party | Essential |
---|---|---|---|---|
_Secure-1PAPISID | Advertising, personalisation and security cookie | 1 year | 3rd | No |
_Secure-1PSID | Advertising, personalisation and security cookie | 1 year | 3rd | No |
_Secure-1PSIDCC | Advertising, personalisation and security cookie | 1 year | 3rd | No |
_Secure-3PAPISID | Advertising, personalisation and security cookie | 1 year | 3rd | No |
_Secure-3PSID | Advertising, personalisation and security cookie | 1 year | 3rd | No |
_Secure-3PSIDCC | Advertising, personalisation and security cookie | 1 year | 3rd | No |
_Secure-END | Advertising, personalisation and security cookie | 1 year | 3rd | No |
_Secure-ROLLOUT_TOKEN | Advertising, personalisation and security cookie | 6 months | 3rd | No |
_Secure-YEC | Advertising, personalisation and security cookie | 1 year | 3rd | No |
APISID | Embedded YouTube content and general web session management | 1 year | 3rd | No |
HSID | Embedded YouTube content and general web session management | 1 year | 3rd | No |
LOGIN_INFO | Embedded YouTube content and general web session management | 1 year | 3rd | No |
NID | Embedded YouTube content and general web session management | 6 months | 3rd | No |
SAPISID | Embedded YouTube content and general web session management | 1 year | 3rd | No |
SID | Embedded YouTube content and general web session management | 1 year | 3rd | No |
SIDCC | Embedded YouTube content and general web session management | 1 year | 3rd | No |
SSID | Embedded YouTube content and general web session management | 1 year | 3rd | No |
VISITOR_INFO1_LIVE | YouTube embedded videos – bandwidth estimation, session validation and video recommendations | 6 months | 3rd | No |
VISITOR_PRIVACY_METADATA | YouTube – stores user privacy metadata | 6 months | 3rd | No |
YSC | YouTube embedded videos – bandwidth estimation, session validation and video recommendations | Session | 3rd | No |
GPS | Registers a unique ID on mobile devices to enable tracking based on geographical GPS location | 1 day | 1st | No |
PREF | Stores your preferences and other information, in particular preferred language, how many search results you wish to be shown on your page and whether or not you with to have Google’s SafeSearch filter turned on | 10 years | 3rd | No |
DEVICE_INFO | Detects if the visitor has accepted marketing category in the cookie banner | 180 days | 3rd | No |
Pardot cookies
Name | Purpose | Duration | 1st or 3rd party | Essential |
---|---|---|---|---|
Visitor_id | Pardot form cookie, assigns a unique visitor ID number to each visitor. Used to track activity | 1 year | 3rd | No |
Resources
For additional information, please visit the following website: