Cookies Policy

What are cookies?

Cookies are text files containing small amounts of information which are downloaded to your device when you visit a website. Cookies are then sent back to the originating web domain on your subsequent visits to that domain. Most web pages contain elements from multiple web domains so when you visit the Website, your browser may receive cookies from several sources.

Cookies are useful because they allow a website to recognise a user’s device. Cookies allow you to navigate between pages efficiently, remember preferences and generally improve the user experience. They can also be used to tailor advertising to your interests through tracking your browsing across websites.

Session cookies are deleted automatically when you close your browser and persistent cookies remain on your device after the browser is closed (for example to remember your user preferences when you return to the site).

What types of cookies does Mitsubishi Electric Europe B.V. use?

We describe the categories of cookies Mitsubishi Electric Europe B.V. and its affiliates and its contractors use below.

Strictly Necessary Cookies

These cookies are essential in order to enable you to move around the website and use its features. Without these cookies, services you have asked for (such as navigating between pages, MyMitsubishi) cannot be provided.

This Website currently uses the following strictly necessary cookies:

auth_atThis cookie stores the access token. The access token is a randomly generated key that the website uses to identify an authenticated user and make sure that all actions in the MyMitsubishi area are done on his/her behalf. This cookie is very short-lived and gets frequently refreshed for security purposes.Local ServerPersistent
auth_rtIn order to refresh the authentication token, we use a random key named Refresh token. The token is long-lived and protects user data from being stolen.Local ServerPersistent
auth_cvIn order to provide safe authentication we generate a random key, encrypt and store it in cookies. This key is used to check the validity of other tokens and protect the authentication flow from MITM attacks.Local ServerSession
auth_stateThis cookie contains a randomly generated string named State. State parameter protects the application endpoint by binding the original authorization requests to responses. This is CSRF protection.Local ServerSession
auth_return_loginShort-lived cookie to return the user to the current page after login.Local Server15 minutes
auth_return_logoutShort-lived cookie to return the user to the current page after logout.Local Server1 minute
_csrfThis cookie stores a randomly generated string that is tied to the user session and ensures that all user actions are relevant and not forged by someone else. It is used to protect users from CSRF attacks.Local ServerSession
_cookie_consentThe cookie "_cookie_consent" is used to record your selection in the cookie notification popup to prevent the cookie notification appearing on every page of our website.Local Server6 month
_skip_market_infoThis cookie is used to store your choice of the preferred local website in the popup to prevent the popup appearing on every page of our website.Local Server6 month
AUTH_SESSION_IDID of the current authentication session.Local ServerSession
AUTH_SESSION_ID_LEGACYID of the current authentication session.Local ServerSession
KC_RESTARTKC_RESTART is the cookie, which is created at the beginning of the authentication flow. It contains client information encoded in the JWS token. The cookie is used in case the root authentication session expires, and to re-create the new authentication session from the client information supplied in the cookie.Local ServerSession
KEYCLOAK_IDENTITYContains a token with the authenticated user id.Local Server10 hours
KEYCLOAK_IDENTITY_LEGACYContains a token with the authenticated user id.Local Server10 hours
KEYCLOAK_REMEMBER_METhe cookie will be set when the user checks the “Remember me” checkbox on login and stores in this case the username.Local Server1 year
KEYCLOAK_SESSIONID of the current browser session.Local Server10 hours
KEYCLOAK_SESSION_LEGACYID of the current browser session.Local Server10 hours
KEYCLOAK_LOCALEStores the local website the user logged in from for Keycloak.Local ServerSession
_GRECAPTCHARisk analysis on form submit.Google Recaptcha6 month

Performance Cookies

We make use of analytic cookies to analyse how our visitors use our Website and to monitor Website performance. This allows us to provide a high quality experience by customising our offering and quickly identifying and fixing any issues that arise. For example, we might use performance cookies to keep track of which pages are most popular, which method of linking between pages is most effective, and to determine why some pages are receiving error messages. We might also use these cookies to highlight articles or site services that we think will be of interest to you based on your usage of the website. The information collected by these cookies is not associated with your personal information by us or by our contractors.

The Website currently uses the analytic cookies from Google Analytics:

NamePurposeSourceLifetimeFurther Information
_gaUsed to distinguish users.Google Analytics2 years

Any such data will be automatically deleted by Google Analytics after this period.

Click here for Google’s privacy policy in respect of Google Analytics

You may opt out of tracking by Google Analytics by visiting

_gidUsed to distinguish users.Google Analytics24 hours
_ga_<container-id>Used to persist the session state.Google Analytics2 years
_gac_gb_<container-id>Contains campaign related information.Google Analytics90 days

Use of IP addresses and web logs

We may also use your IP address and browser type to help diagnose problems with our server, to administer our Website and to improve the service we offer to you. An IP address is a numeric code that identifies your computer on the internet. Your IP address might also be used to gather broad demographic information.

We may perform IP lookups to determine which domain you are coming from (e.g. to more accurately gauge our users’ demographics.

Cookies policy does not cover third party websites

Please note that this cookies policy does not apply to, and we are not responsible for, the privacy practices of third party websites which may be linked to this Website.

Changes to the Cookies Policy

We may update this cookies policy and we would encourage you to review the policy from time to time to stay informed of how we are using cookies. This cookies policy was last updated on 25th May 2018.