What are cookies?
Cookies are small files that are stored on your computer. They are designed to hold a small amount of specific data about your viewing of our site.
Cookies help improve your visit to our website:
● They remember the settings, so you don’t have to record them again each time you visit a new page.
● They memorize the information you have specified (e.g. your postal code), so you don’t need to enter it again.
● They allow you to evaluate how you use the website, which allows us to ensure that it meets your needs.
Please note that cookies cannot damage your computer and we don’t store any information that identifies you in the cookies we use on this website.
The cookies we use:
This website is developed using Java web technologies. We use the built-in session cookie (JSP.SessionID) to manage your session. When you access the site, the server establishes a single session that is maintained for the duration of your visit. Our website also checks your login information if you have a HaierClub account.
Evaluation of the use of the website: Google Analytics
The following table shows the type of information obtained through Google Analytics cookies and used in Analytics reports.
Description of the cookie
Definition of the scope of the site’s content
Since access to read / write cookies is limited by a combination of cookie names and their domain, default visitor tracking by Google Analytics is limited to the domain of the page where the tracking code is installed. For the most common scenario where the tracking code is installed on a single domain (and no other subdomain), the generic setup is correct. In other cases, if you want to track content in domains or subdomains, or limit tracking to a smaller section of a single domain, you use other ga.js tracking code functions to define the scope of the content. For more details, see the Domains & Directories section in the API Collection document.
Determination of visitor session
Google Analytics tracking for ga.js uses two cookies to establish a session. In the absence of either of these two cookies, any other activity of the user triggers the start of a new session. For a detailed definition and a list of end-of-session scenarios, see the Session (Session) article in the Help Center. You can customize the duration of the default session with the _setSessionCookieTimeout () function.
This description is specific to the ga.js tracking code for web pages. If you use Analytics tracking for other environments (such as Flash or mobile), you should check the documentation for those environments to find out how sessions are calculated or established.
Identification of single browser
Every single browser visiting a page on your site has a unique ID with the __utma cookie. Subsequent visits to your website by the same browser are thus recorded as being performed by the same (single) visitor. Therefore, if someone were interacting with your website using Firefox and Internet Explorer, the Analytics report would track this activity under two unique visitors. Similarly, if the same browser were used by two different visitors, each with a separate computer account, the activity would be recorded under the identities of two unique visitors. In addition, if the browser is used by two different people sharing the same computer account, the identity of a single visitor is recorded, even if two unique individuals have accessed the site.
Tracking traffic sources and navigation
When visitors access your site through the result of a search engine, a direct link, or an ad linking to your page, Google Analytics stores the type of reference information in a cookie. The parameters of the cookie value string are parsed and sent in the GIF request (in the utmcc variable). This cookie is updated each time the page is subsequently consulted on your site; therefore, it is used to analyze visitor navigation on your site.
You can define your own segments for reporting on your particular data. When you use the _setCustomVar () function in your tracking code to define custom variables, Google Analytics uses this cookie to track and report information. In typical use, you can use this method to segment visitors to your website with demographic information they select on your site (income, age range, product preferences).
You can use Google Analytics with Google Website Optimizer (GWO). This tool helps determine the most effective design for your site. When a site optimizer script runs on your page, a _utmx cookie is created on your browser and its value is sent to Google Analytics. For more information, see the Website Optimizer Help Center.
Once cookies are created / updated on the web browser, the data they contain, which is needed for reporting, is sent to the Analytics servers in the GIF Request URL using the utmcc parameter.
Google Analytics creates the following cookies, described in the table below. The default configuration and the use of Google Analytics only create the first 4 cookies described in the table.
This cookie is usually created on the browser from the first visit of your site from this web browser. If the cookie has been removed by the browser user and the browser subsequently visits your site, a new __utma cookie is created with a different unique ID. This cookie is used to determine unique visitors to your site and is updated whenever a page is viewed. In addition, this cookie has a unique identification used by Google Analytics to ensure the validity and accessibility of the cookie as an additional security measure.
2 years from creation / update
This cookie is used to establish and continue a user session with your site. When a user views a page on your site, the Google Analytics code attempts to update that cookie. If it does not find the cookie, a new cookie is created and a new session is established. Whenever a user visits a different page on your site, this cookie is updated and expires 30 minutes later, continuing a single session as long as the user's activity continues, every 30 minutes. This cookie expires when a user stops on a page in your site for more than 30 minutes. You can change the default length of a user session with the _setSessionCookieTimeout () function.
30 minutes from creation / update
This cookie is no longer used by the tracking code ga.js to determine the state of the session.
In the past, this cookie worked with the __utmb cookie to determine whether or not to establish a new session for the user. For backward compatibility with sites still using the urchin.js tracking code, this cookie will always be created and will expire when the user leaves the browser. However, if you are developing tracking for your site and you are using the tracking code ga.js, you should not interpret the existence of this cookie as a sign of a new session or a completed session.
This cookie stores the type of means used by the visitor to access your site, whether directly, through a referral link, a search for websites or a campaign (announcement or email link). It is used to evaluate search engine traffic, ad campaigns, and page navigation on your own site. This cookie is updated whenever a page of your site is viewed.
6 months from creation /update
In general, this cookie is not present in a default configuration of the tracking code. The __utmv cookie passes the information provided by the _setVar () function, which you use to create a custom user segment. This string is then passed to the Analytics servers in the GIF request URL using the utmcc parameter. This cookie is only created if you have added the _setVar () function for the tracking code on your website page.
2 years from creation /update
This cookie is used by Website Optimizer and is only created when the Website Optimizer tracking code is installed and properly configured for your pages. When the optimizer script runs, this cookie stores the variation that this visitor is submitted for each experiment. As a result, the visitor experience on your site is constant. For more information, see the Website Optimizer Help Center.
2 years from creation /update
Other third-party cookies that we sometimes use
When you visit our website, you may notice that some cookies collect information for other websites. For example, if you are viewing a page with video content, cookies from YouTube may be transmitted. We do not control the setting up of these cookies. We advise you to visit the third party websites for further information.
You will find below a list of third-party cookies that you can find on this website as well as links to specific information:
Paid on Results
How to control or delete cookies?
If cookies are not enabled on your computer, your use of our website will not be optimal and some parts and / or functions of the site will not be accessible. However, if you wish, you can control or
You will find information on deleting cookies or controlling cookies on www.aboutCookies.org.
Haier is a Chinese multinational consumer electronics and home appliances company. It designs, develops, manufactures and sells products including air conditioners, mobile phones, computers, microwave ovens, washing machines, refrigerators, and televisions.
The headquarter is located in China but there are several Haier entities located in the European Union.
Haier is particularly committed to conduct its business in accordance with the privacy and the protection of personal data of individuals whether they are its own employees or external individuals such as clients, customers, partners, job applicants, providers etc.
The purpose of this Data Protection Policy (the “Policy”) is to inform you about the commitments made by Haier to ensure that your personal data are processed in compliance with the applicable relevant laws.
This Policy may evolve according to the legal and regulatory context and the doctrine of supervisory authorities.
“Controller”: The Haier legal entity which determines the purposes and means of the Processing of Personal Data.
“Data Subject”: Any natural person, including you, whose Personal Data are processed by Haier.
“Personal Data”: All information on an identified or identifiable natural person. A person is deemed to be identifiable if he or she can be directly or indirectly identified for example by reference to an IP number, identity number or by at least one factor specific to that person’s social, cultural, physical or economic identity.
“Processing”: Any operation or set of operations which is performed on Personal Data, whether or not by automated means, such as collection, recording, organization, structuring, storage, adaption or alteration, retrieval, consultation, use, disclosure by transmission, dissemination or otherwise making available, alignment or combination, restriction, erasure or destruction.
“Processor”: The natural or legal person which processes Personal Data on behalf of the Haier legal entity.
In order to provide legal certainty and transparency for economic operators, the European Union adopted the Regulation 2016/679 on the protection of natural persons with regard to the Processing of Personal Data and on the free movement of such data (General Data Protection Regulation or ‘GDPR’). The GDPR enters into force on 25 May 2018.
The local laws of each Member State remains relevant in the limits allowed by the GDPR.
The Policy is subject to the GDPR and the relevant local laws of the concerned Haier legal entity.
Principles for processing Personal Data
Haier commits to ensure that Personal Data are:
Haier ensures that all its Processings are performed in accordance with the applicable laws.
Management is responsible for defining and structuring all processes where Personal Data can be collected, processed and/or used, that they comply with this Policy.
In particular, the following tasks are falling in the responsibility scope of the management:
Each Haier’s employee has the duty to process the Personal Data he/she has access to in the course of its employment as strictly confidential.
Each Haier’s employee can collect, use and/or process Personal Data pursuant to the defined process within Haier but only in the extent as necessary to fulfil his/her duty.
Where required by law, each Haier legal entity shall appoint a data protection officer who is in charge to ensure compliance with relevant data protection and privacy law and the provisions of this Policy.
How do we process Personal Data?
By being contacted by customers, suppliers and/or other persons via our website, phone, email or any other mean;
Each Data Subject is informed by the Haier legal entity which is collecting the Personal Data that his/her Personal Data are collected, used and/or processed and how his/her Personal Data are being handled by Haier.
In particular, each Data Subject is informed (i) of which types of Personal Data will be subject to Processing; (ii) for which specific purpose(s); (iii) to whom such Personal Data might be transmitted; and (iv) how the Data Subject can exercise its rights.
Personal Data are subject to data secrecy. Haier apply the following rules in order to prevent any unauthorized collection, processing or use of such data by its employees:
Haier ensures that Personal Data are accurate and, where necessary, kept up to date, by applying the following rules:
Haier is aware that periods for which the Personal Data are stored must be limited to a strict minimum.
To ensure safely storage, Haier applies the following rules:
Rights of Data Subjects
According to the GDPR, each Data Subject has the following rights:
Right of access (article 15 GDPR): In certain cases, the Data Subject has the right to obtain confirmation as to whether or not Personal Data concerning him or her are being processed, and, where that is the case, access to the Personal Data.
Right to data portability (article 20 GDPR): in certain cases, the Data Subject has the right to receive the Personal Data concerning him or her, which he or she has provided to a Controller, in a structured, commonly used and machine-readable format and have the right to transmit those data to another controller.
Right to object (article 21 GDPR): in certain cases, the Data Subject has the right to object, on grounds relating to his or her particular situation, at any time to processing of Personal Data concerning him or her.
In order to fulfill efficiently these requests and securely transmit the Personal Data to the Data Subject, Haier has set up an internal process to handle Data Subject requests.
Transfer of Personal Data
As Haier is a multinational group, Personal Data may be transferred to countries located outside the EEA. In this case, Haier ensures that the country has an adequate level of data protection in compliance with articles 44 to 50 of GDPR.
The transfers of Personal Data within Haier group are subject to appropriate safeguards thanks to an interaffiliate agreement which refers to the standard data protection clauses adopted by the European Commission (2004 Clauses Controller to Controller and 2010 Clauses Controller to Processor).
The transfers of Personal Data outside Haier group are managed on a case-by-case basis. In this case, Haier ensures that such transfers are (i) performed on the basis of an adequacy decision of the European Commission or (ii) are subject to appropriate safeguards.
Haier has implemented appropriate technical and organizational measures to ensure a level of security appropriate to the risk of each Processing.
These measures are detailed in the different security and IT policies of Haier.
In case of a data breach, Haier has implemented an internal process in order to prevent, detect and stop Personal Data breach as well to notify the relevant supervisory authority and, if applicable, the Data Subjects, in time.
Done in Thailand, on August 15, 2019