Data protection
Data protection
1. This Agreement governs the download and use of Miele software and information. By downloading, the user agrees to be bound by these terms.
2. In general, downloads are available 24 hours a day, seven days a week. Miele accepts no responsibility, however, for uninterrupted service based on the state of the internet and computer systems.
3. Miele exercises due diligence to keep downloads up-to-date. Miele reserves the right, however, to change information and software at any time, in particular concerning further technical or economical developments or altered conditions of service and general conditions, also taking into account pricing/commercial issues, without having to announce or notify of the change.
Rights and responsibilities of use
1. The contents are legally protected, and particularly copyright protected, for the benefit of Miele and third parties. Usage, in particular, any copying, distribution, performance, screening, broadcast, providing public access and other reproductions as well as adaptations and transformations are only permitted with the express written consent from Miele or the respective rights holder.
2. Miele software may not be copied, resold, loaned or given to unauthorised third parties. Miele software contains trade secrets. For this reason, the software may not be reverse-engineered, decompiled, disassembled or manipulated in other usable forms.
3. If copyright law determines that approval is not absolutely required for use under certain preconditions as an exception, then the limitations of the usage rights in the preceding points do not preclude this.
4. Miele grants the user basic, non-exclusive, non-transferable rights that may be revoked at any time to use the downloads to support business purposes within the scope of existing business agreements with Miele. Possible copyright and comparable notices must be adopted without change.
5. Miele points out the fact that data transfer over the internet is unsecured. It is not impossible for unauthorised persons to see the data, or for the data to be falsified.
Liability
1. No guarantees or assertions are made through the content and downloads made available or via this Agreement. Likewise, no warranty claims shall arise from it.
2. Miele accepts no liability for the accuracy, completeness, quality and reliability of the information nor for results that may be achieved through the use of that information. Miele accepts no liability for any consequential loss from use of the downloads, such as interruption of service, lost earnings, loss of information and data. Decisions as to the use of software made available by Miele as downloads should be made by the user in consultation with Miele.
3. Miele accepts no liability for damages, regardless of the legal basis, that arise from the use, inability to use, possible hardware or software errors or incorrect system settings created by the user. Download usage is at your own risk. Miele accepts no liability for software and information, particularly regarding their usability, accuracy, completeness and virus-free state.
4. Miele's liability is further excluded for damages caused by viruses, Trojan horses, hoax viruses or similar programming, as well as for programmes, programme parts or codes which cause similar impairment, destruction or failure of systems or parts. The user shall take their own measures to protect against viruses and other destructive data.
5. Miele's accepts no liability for the incorrect transfer of data from Miele, the manipulation of this data by third parties, particularly through unauthorised access to Miele's networks and systems, insofar such access is not advocated by Miele.
6. Liability is not excluded, provided liability must be assumed, for example, if caused intentionally or through culpable negligence, for guarantees of quality or due to violation of material contractual obligations, in the event of loss of life, limb or health as well as if liable in accordance with product liability law. Compensation due to violation of material contractual obligations, however, is limited to damages that are foreseeable and typical of the contract, provided there is no intent or culpable negligence involved. This does not imply a change in the burden of proof to the detriment of the user.
Contacting Us
To ensure sufficient data protection when transmitting internet forms (e.g. signing up for a newsletter) we use the Google ReCAPTCHA service from Google Inc. This is used for working out if input was made by a person, or unintentionally by automated, machine processing. The service accesses your IP address and other data that may be required by Google for the reCAPTCHA service and passes it to Google. The data protection policies from Google Inc. apply.
For further information about Data protection with Google Inc. please go to https://www.google.com/intl/de/policies/privacy/
Qualtrics
On our website, we use the services of Qualtrics LLC, 333 W. River Park Drive, Provo UT 84604, USA for customer-, product-, and brandsurveys in order to regularly improve our products and services. When you are taking a survey, only log data (date and timestamp / information to your browser and browser settings / information to your device / usage date) will be processed. You are free to decide whether you like to participate on a survey. If you do not want to participate, you can just close the survey pop-up by using the “X”-button on the top right corner of the survey pop-up. The legal basis for the data processing is your consent, Art. 6(1)(a) GDPR. You can revoke your consent with effect for the future at any time.
In the context of the use of Qualtrics services, we also use Qualtrics cookies, mainly to help keep track of survey sessions or to maintain survey sessions. Please find more information to our use of Qualtrics cookies in our cookie notice. For more information about Qualtrics LLC and use of personal data by Qualtrics please visit https://www.qualtrics.com/privacy-statement/.
Viewing pdf files
Adobe Acrobat Reader is required to view pdf files.
Viewing CAD data
Planning data allows simple, quick and secure planning in two- and, sometimes, three-dimensional front and floor plan views. Data relating to planning, such as measurements, connection points and the necessary on-site installations is highlighted.
As a rule, special software is required to view CAD files. The CAD data from Miele is available in different formats and is compatible with current CAD programmes:
3DS: http://en.wikipedia.org/wiki/.3ds
DWG: http://en.wikipedia.org/wiki/.dwg
OBJ: http://en.wikipedia.org/wiki/Wavefront_.obj_file
STEP: http://en.wikipedia.org/wiki/ISO_10303-21
The design files for the appliances are indicated with the heating type “EL” (electric), “D” (steam) or “G” (gas) as appropriate. The additional "D", "S", "V" or "R" stand for the top, side, front or rear view of the appliances.
The recipient accepts responsibility for the correct choice and the consequences of use of the data as well as the intended or achieved results. Liability for damages or consequential loss is excluded.
Liability is not excluded, provided liability must be assumed, for example, if caused intentionally or through culpable negligence, for guarantees of quality or due to violation of material contractual obligations, in the event of loss of life, limb or health as well as if liable in accordance with product liability law. Compensation due to violation of material contractual obligations, however, is limited to damages that are foreseeable and typical of the contract, provided there is no intent or culpable negligence involved. This does not imply a change in the burden of proof to the detriment of the user.
We will be happy to answer any questions you may have:
Click here for the contact form
Data security
Information on data security at Miele
Miele on data security
Miele, as a manufacturer of high-quality and durable products, demands the highest data and cyber security of its networked devices, apps and web applications. Although, we try very hard to detect and eliminate weaknesses in advance, to eliminate 100% of security threats is almost impossible to achieve.
For this reason, Miele is interested in any information from you that relates to possible or discovered data security risks affecting our networked products, apps or web applications.
For reporting vulnerabilities and information about cyber security at Miele, please use our international page:
https://www.miele.com/en/com/cybersicherheit-5047.htm
Even if you're not quite sure: We will follow up your request and contact you if we have any further questions.
Cookie Notice
You have the right to withdraw your consent at any time by returning to this cookie policy and changing the settings above.
1. General Explanation
Cookies are small text files that are stored on your computer or end device when you use our websites. When you visit the Miele website, a cookie may be stored on your system. This contains an individual string of characters that can be used to identify your browser the next time you visit the website. There are two basic types of cookies:
- - Temporary cookies: These cookies, also called session cookies, are temporarily stored on your computer or terminal device during your visit to our website and then deleted.
- - Persistent cookies: These cookies remain on your computer for a longer period of time.
In general, Miele uses various Internet technologies (e.g. cookies, Java-Script) to make it easier for you to use the Miele Internet applications and to optimise them. This means that they are used to:
- - Identify you when you log in to our web shop and to ensure that valid security standards, optimized for you, are observed.
- - Help us remember products that you have added to your shopping cart or notepad.
- - Show you the quantity of products you have added to your shopping cart or notepad on the website.
- - Remind us of your chosen language during the session, so that you can navigate our pages more easily.
- - Analyse data, such as the evaluation of the number of visitors to our website or the most frequently visited websites. We use the analysis results for the purpose of optimizing our website.
- - We also use so-called marketing cookies from third parties for the purpose of retargeting/remarketing and the placement of personalised online advertisements.
Please note that Miele needs you to express your preferences regarding the use of cookies, on its own interface, but by changing the cookie settings of your Internet browser, you can also deactivate or restrict the transmission of cookies. You can delete already stored cookies at any time. Further browser specific information on how to delete cookies can be found here:
- - Microsoft Edge: https://support.microsoft.com/en-us/microsoft-edge/delete-cookies-in-microsoft-edge-63947406-40ac-c3b8-57b9-2a946a29ae09
- - For Mozilla Firefox: https://support.mozilla.org/en-US/kb/clear-cookies-and-site-data-firefox
- - For Google Chrome: https://support.google.com/chrome/answer/95647?hl=en
- - For Safari: https://help.apple.com/safari/mac/8.0/#/sfri11471
Please note, however, that if you deactivate cookies, you may no longer be able to use all the functions of the website. In the menu of most browsers you will find setting options for the use of cookies. Typically, a browser has the following setting options:
- - View cookies,
- - Allow cookies,
- - Disable all or certain cookies,
- - Disable all cookies when closing the browser,
- - Blocking cookies,
- - Notify when a cookie is to be set,
- - Objection to tracking web analysis (opt-out).
When you visit our website, a banner informs you about the use of cookies and asks for your consent to cookies requiring consent. You can withdraw your consent at any time with effect for the future, which we explain in detail in this cookie policy.
2. Google Tag Manager
On our website, we use the tag management service named Google Tag Manager provided by Google Ireland Ltd., Gordon House, Barrow Street, Dublin (“Google”). Google Tag Manager allows websites to quickly and easily update measurement codes and related code fragments collectively known as tags on their websites or mobile apps. Once the small segment of Tag Manager code has been added to a project, the website can safely and easily deploy analytics and measurement tag configurations from a web-based user interface.
The Google Tag Manager helps us to implement and manage cookies and tracking tags. The Google Tag Manager does not use any of its own cookies, but the Google Tag Manager triggers other cookies and tracking tags if and insofar you have explicitly agreed to the use of such cookies and tracking tags. You will find detailed information to each of such cookies and tracking tags in our cookie notice. In the context of the use of the Google Tag Manager, we and Google process your ip-address and an unique identifier. It might be possible that your data will be processed outside the territory of the European Union. In order to ensure an appropriate level of data protection, Google and we have agreed on the standard contractual clauses published by the European Commission. The legal basis for the use of the Google Tag Manager and related data processing activities is our legitimate interest, Art. 6 (1) (f) GDPR. That legitimate interest is the assistance Google Tag Manager provides us in implementing and managing our use of cookies and tracking tags.
3. Technically necessary cookies (essential cookies)
Essential cookies are required for navigation of the websites and for the use of their functions, such as access to the registration part of the website or the use of our chat tool. Without these cookies certain functions of the website are not possible.
The legal basis for the processing of personal data using technically necessary cookies is legitimate interests Article 6(1) (f) GDPR. The legitimate interest is that this processing is required for navigation of the websites and for the use of their functions. The data collected by technically necessary cookies is not used to create user profiles.
Essential cookies cannot be deactivated. The essential cookies we use are generally so-called session cookies, which are generally automatically deleted after the browser session has ended.
Some essential cookies are provided and/or accessed by third parties. Details of the third parties and their tools that we use essential cookies for are explained below.
3.1 SAP Customer Data Cloud (formerly Gigya)
On our website we use various cookies for essential purposes that are provided and/or used by SAP Deutschland SE & Co. KG, Hasso-Plattner-Ring 7, 69190 Walldorf, Germany (“SAP”). We use a series of necessary cookies, which are provided and / or used by SAP and which are necessary for the proper functioning of the website. SAP provides a platform for managing customer identity management, including customer profiles, preferences, opt-ins, and consent settings. Further information about the SAP Customer Data Cloud can be found here.
3.2 Chatbot e-bot7
On our website, we use the Digital Miele Assistant, a so-called chatbot, provided by our technical service provider, e-bot7 GmbH, Perusastraße 7, 80333 Munich (“e-bot7”). In order to provide you with our chatbot function, we must use technologies named “Session storage” and “Local storage”, in particular, for technical authentication, restoring the chat history and analytics/quality assurance purposes. Without such technologies, the chatbot service is not useable. These technologies will only be used if you actively request to use the chatbot service. Please find more detailed information to e-bot7 and data processing activities related to the use of the chatbot function in our privacy notice. Further information about e-bot7 GmbH can be found here.
3.3. Go Instore – SYM-SYS Ltd.
On our website we use the Go Instore services provided by Sym-Sys Ltd (t/a Go Instore), 1 Phipp St., London, EC2A 4PS, United Kingdom. Sym-Sys Ltd. uses cookies and similar technologies like “Session Storage” and “Local Storage” in order to provide the services. Without such technologies, the Go Instorie service is not useable. These technologies will only be used if you actively request to use the of the Go Instore service. Please find more information to Sym-Sys Ltd and the Go Instore service on www.goinstore.com.
3.4 Neocom.ai – Buyers Guide
On our website, we use the Guided-Selling-service, a so-called Buyers Guide, provided by our service provider, Neo Commerce GmbH, Max-Bill-Str. 8, 80807 Munich, Germany („Neocom“). In order to provide you with our Guided-Selling-service, we must use a technology named “Session storage” in order to group multiple uses of the Guided-Selling-service in one browser session. Without such technology, the Guided-Selling-service is not useable. This technology will only be used if you actively request to use the Guided-Selling-service. Please find more detailed information about Neocom and data processing activities related to the use of the Guided-Selling-service in our privacy notice.
3.5 Further Details
Further details about the essential cookies that we use can be found in the following table:
Name |
Third Party/Cookie Host |
Purpose (Further details are explained above) |
Retention Period |
ASLBSA | sst.miele.co.uk | This cookie is used for Azure Software Load Balancer Session Affinity. | Session |
ASLBSACORS | sst.miele.co.uk | This cookie is used for Azure Software Load Balancer Session Affinity Cross Origin Resource Sharing. | Session |
Ebot7/webchat/env (Session Storage) |
e-bot7 |
General: Digital Miele Assistant
Specific: Information regarding the Deployment Environment of the chat application |
Session |
Ebot7/webchat/config (Session Storage) |
General: Digital Miele Assistant
Specific: Information about the version of the chat application |
Session |
|
Chat-jwt (Local Storage) |
General: Digital Miele Assistant
Specific: Session Token for technical authentication of the user (anonymized ID) |
Unlimited (but the authentication token is invalid after 24 hours) |
|
convId_ (Local Storage) |
General: Digital Miele Assistant
Specific: Conversation ID to restore the chat history (anonymous ID) |
Unlimited (but the authentication token is invalid after 24 hours) |
|
Eb7UUID: (Local Storage) |
General: Digital Miele Assistant
Specific: Analytics ID to track the opening, loading and closing of the chat window (anonymous ID) |
Unlimited (but the authentication token is invalid after 24 hours) |
|
shop_domestic_gb |
Site domain (miele.co.uk) |
The cookie is used to display the name of a logged in user and for better segmentation of users to perform more granular analyses. |
Session |
cookieUse |
The cookie is used for cookie consent management. |
6 months
|
|
LoginToken
|
The cookie is used to remember login status. |
7 days |
|
newsletterEmail (Local Storage) |
The cookie is used to store Newsletter subscription consent. |
Persistent |
|
gig_bootstrap_<apiKey> |
Internal cookie for the Web SDK and is used for log in. |
12 months |
|
mielestorefrontRememberMe |
Based on this cookie the user is automatically logged in (based on the credentials set in Backoffice). |
6 months |
|
JSESSIONID |
The cookie is used to maintain an anonymous user session by the server. |
Session
|
|
ROUTE |
The cookie is used to preserve the customer on the same node (traffic management). |
Session |
|
acceleratorSecureGUID |
This cookie brings the information the customer is logged in. |
Session |
|
miele-gb-cart |
The cookie is storing a unique ID to remember what was added to the cart. |
1000 hours |
|
recentSearches |
The cookie helps to remember the recent search on the Miele domain. |
100 days |
|
gig_canary |
General: SAP Customer Data Cloud strictly necessary cookies
Specific: Indicates whether the client is using the canary version of the WebSDK. |
1 year (only active ~3 days) |
|
gig_canary_ver |
General: SAP Customer Data Cloud strictly necessary cookies
Specific: The version name of the WebSDK's canary version. |
1 year (only active ~3 days) |
|
miele_globals (Session Storage) |
General: SAP Customer Data Cloud strictly necessary cookies |
Persistent |
|
mnfly/c/<____.htm> |
General: SAP Customer Data Cloud strictly necessary cookies
Specific: Used to render the header. |
Persistent |
|
compare-product-data |
Miele (miele.com) |
This cookie stores the selected products and their categories to prepare the compare page. |
30 days |
mdl-notification-banner |
This cookie detects if a notification banner got previously closed. |
180 days |
|
Gmid |
SAP (gigya.com) |
General: SAP Customer Data Cloud strictly necessary cookies
Specific: Used to identify the logged in user |
12 months |
Gig_hasGmid |
General: SAP Customer Data Cloud strictly necessary cookies
Specific: Internal Cookie for the Web SDK and is used for log in. |
12 months |
|
ds-session-id |
General: SAP Customer Data Cloud strictly necessary cookies
Specific: A unique number that a Web site's server assigns a specific user for the duration of that user's visit. |
Session
|
|
apiDomain_<apiKey> |
General: SAP Customer Data Cloud strictly necessary cookies
Specific: The shared domain API calls for all sites in a group should be sent to. |
12 months |
|
_gig_comments_nickname |
General: SAP Customer Data Cloud strictly necessary cookies
Specific: Comments guest nickname. |
12 months |
|
_gig_comments_email |
General: SAP Customer Data Cloud strictly necessary cookies
Specific: Comments guest email. |
12 months |
|
_gig_comments_cb_<provider> |
General: SAP Customer Data Cloud strictly necessary cookies
Specific: Remembers if a provider checkbox was checked by the user. |
12 months |
|
_gig_comments_selected_<provider> |
General: SAP Customer Data Cloud strictly necessary cookies
Specific: Remembers if a provider checkbox was checked by the user. |
12 months |
|
_gig_comments_selected_providers |
General: SAP Customer Data Cloud strictly necessary cookies
Specific: Last selected share providers. |
12 months |
|
_gig_comments_locked |
General: SAP Customer Data Cloud strictly necessary cookies
Specific: Remembers if a guest user has posted at least one comment. |
12 months |
|
_gig_comments_sort |
General: SAP Customer Data Cloud strictly necessary cookies
Specific: Last selected user sort. |
12 months |
|
_gig_comments_is_guest |
General: SAP Customer Data Cloud strictly necessary cookies
Specific: Indicates that the user is commenting as guest user. |
12 months |
|
gig-comments (Local Storage) |
General: SAP Customer Data Cloud strictly necessary cookies
Specific: IDs of comments flagged by the user. |
Persistent |
|
gig_debug |
General: SAP Customer Data Cloud strictly necessary cookies
Specific: Used to trigger the debug UI. |
2 seconds |
|
_gig_dbgConsole_log |
General: SAP Customer Data Cloud strictly necessary cookies
Specific: Used to trigger logging for debugging. |
3 seconds |
|
_gig_email |
General: SAP Customer Data Cloud strictly necessary cookies
Specific: Last used email address in share (when sending email). |
12 months |
|
_gig_gmidt (Local Storage) |
General: SAP Customer Data Cloud strictly necessary cookies
Specific: User cookie. |
30 minutes |
|
_gig_llu |
General: SAP Customer Data Cloud strictly necessary cookies
Specific: Last login provider username for Login "Welcome back" screen. |
12 months |
|
_gig_llp |
General: SAP Customer Data Cloud strictly necessary cookies
Specific: Last login provider name for Login "Welcome back" screen. |
12 months |
|
_gig_lt / glt_<APIKey> |
General: SAP Customer Data Cloud strictly necessary cookies
Specific: Login Token for authentication. |
3600 seconds |
|
gig_last_ver_<APIKey> |
General: SAP Customer Data Cloud strictly necessary cookies
Specific: Last time of verification of the session when the site is using the verifyLoginInterval property of global CONF in order to trigger reverification. |
12 months |
|
gig_loginToken_<APIKey> |
General: SAP Customer Data Cloud strictly necessary cookies
Specific: Gigya's Single Sign On (SSO) group login token. |
12 months |
|
gig_loginToken_<APIKey>_exp |
General: SAP Customer Data Cloud strictly necessary cookies
Specific: SSO expiration. |
12 months |
|
gig_loginToken_<API_KEY>_revoked_tokens |
General: SAP Customer Data Cloud strictly necessary cookies
Specific: Revoked login tokens in an SSO group. In SSO scenarios, indicates to the Web SDK that the current token was revoked, so as to log the user out. |
12 months |
|
gig_loginToken_<APIKey>_session |
General: SAP Customer Data Cloud strictly necessary cookies
Specific: Indicates if the group login token session is still activated. |
Session |
|
gig_loginToken_<APIKey>_visited |
General: SAP Customer Data Cloud strictly necessary cookies
Specific: Used to keep track of visited sites within the same SSO group. |
12 months |
|
_gig_shareUI_cb_<provider name> |
General: SAP Customer Data Cloud strictly necessary cookies
Specific: Remembers if a provider checkbox was checked by the user. |
12 months |
|
_gig_shareUI_lastUID |
General: SAP Customer Data Cloud strictly necessary cookies
Specific: Last logged in UID. |
12 months |
|
_gigRefUid_<APIKey> |
General: SAP Customer Data Cloud strictly necessary cookies
Specific: Last referrer User ID. |
12 Months |
|
_gig_ssoToken_<apikey> (Local Storage) |
General: SAP Customer Data Cloud strictly necessary cookies
Specific: SSO Token by API. |
Persistent |
|
_gig_ssoToken (Local Storage) |
General: SAP Customer Data Cloud strictly necessary cookies
Specific: SSO Token. |
Persistent |
|
gig_toggles |
General: SAP Customer Data Cloud strictly necessary cookies
Specific: This value is sent to Gigya in order to identify toggles that the back-end behavior depends on to process the specified toggle. |
Session |
|
gig3pc |
General: SAP Customer Data Cloud strictly necessary cookies
Specific: Remembers if 3rd party cookies are blocked to avoid checking every time. |
48 hours |
|
gig3pctest (when using bypassCookiePolicy in the globalConf) |
General: SAP Customer Data Cloud strictly necessary cookies
Specific: A temp cookie used to check if 3rd party cookies are blocked. |
1 second |
|
gigyaSettings (Local Storage) |
General: SAP Customer Data Cloud strictly necessary cookies
Specific: Saves user Share settings locally. |
Persistent |
|
glnk |
General: SAP Customer Data Cloud strictly necessary cookies
Specific: Ticket for 2nd phase of login. |
1 day |
|
gmSettings (Local Storage) |
General: SAP Customer Data Cloud strictly necessary cookies
Specific: Locally stored Loyalty settings. |
Persistent |
|
gst |
General: SAP Customer Data Cloud strictly necessary cookies
Specific: Server ticket for 2nd phase of login. |
30 minutes |
|
GSLM_<siteID> |
General: SAP Customer Data Cloud strictly necessary cookies
Specific: Session magic cookie. |
Session |
|
hasGmid |
General: SAP Customer Data Cloud strictly necessary cookies
Specific: Internal cookie for the Web SDK |
13 months |
|
reactionState-down_<barId> (Local Storage) |
General: SAP Customer Data Cloud strictly necessary cookies
Specific: Per Reaction and barID - The Last reactions that were made by the user. |
Persistent |
|
SAML_<SiteId>_<ExternalIdp.Name> |
General: SAP Customer Data Cloud strictly necessary cookies
Specific: This cookie is saved by SAML SP to manage the SAML session information and, specifically, the parameters needed for logout. |
12 months |
|
gltexp_<apikey> |
General: SAP Customer Data Cloud strictly necessary cookies
Specific: Login Token Expiration. |
Session |
|
_gig_<id>_cb |
General: SAP Customer Data Cloud strictly necessary cookies
Specific: Callback for listener. |
12 months |
|
__gigAPIAdapterSettings_<apikey>_<build> (Local Storage) |
General: SAP Customer Data Cloud strictly necessary cookies
Specific: WebSDk settings. |
Persistent |
|
Gmid (Local Storage) |
General: SAP Customer Data Cloud strictly necessary cookies
Specific: User cookie. |
Persistent |
|
ucid |
General: SAP Customer Data Cloud strictly necessary cookies
Specific: Unique computer identifier used for generating reports, and used by the Web SDK to get saved response. |
13 months |
|
Ucid (Local storage) |
General: SAP Customer Data Cloud strictly necessary cookies
Specific: Unique computer identifier for unique user reporting purposes. |
Persistent |
|
SESSION_ID |
Neocom |
General: Neocom.ai – Buyers Guide
Specific: Neocom stores an anonymous session identifier in the session storage in order to group multiple uses of the service in one browser session. |
Session |
gis_visit (Local Storage) |
SYM-SYS Ltd. |
The cookie is used to determine if a user is using the service for the first time. |
Session |
viewed-broadcast-uuid (Local Storage) |
The cookie is used to measure broadcast view duration. |
Session |
|
viewed-broadcast-type (Local Storage) |
The cookie is used to measure time in a call. |
Session |
|
gis-chat-user-name (Local Storage) |
The cookie is used to store the chat name during an application. |
Session |
|
ctaAutoPlayDismissed (Local Storage) |
The cookie is used to remember the time at which CTA autoplay was last dismissed. |
Session |
|
ctaAutoPlayMaximisedShown (Local Storage) |
The cookie is used to remember the time at which CTA autoplay was last shown. |
Session |
|
broadcast-contact-capture (Local Storage) |
The cookie prevents multiple requests for contact details following broadcast view. |
Session |
|
show-available-clerk (Local Storage) |
The cookie for A/B control to show available clerk profile images on connect screen. |
Session |
|
cta-awareness-message-closed (Local Storage) |
The cookie is used to control redisplay of CTA message engagement. |
Session |
|
pollingStartTimeStamp (Local Storage) |
The cookie is used to control the query for availability following customer interaction with unavailable CTA. |
Session |
|
oneToOneEngagement (Local Storage) |
The cookie is used to control the display of the Service Intro Video. |
Session |
|
cta-roundel-closed (Local Storage) |
The cookie is used to control reshowing of the CTA following closure by customer. |
Session |
|
gis-broadcast-preview-display (Local Storage) |
This cookie is a Legacy value used to control the gif engagement. |
Session |
|
video-viewed (Local Storage) |
This cookie is used to keep record of the videos viewed by the user. |
Session |
4. Analytics cookies
In addition, we use cookies on our website which enable an analysis of your usage behaviour (so-called analysis cookies). With these cookies we collect and store the following data:
- - Frequency of page visits
- - Search Keywords
- - Use of website functions
Your data collected by means of the cookies is pseudonymised, so that it is no longer possible to assign the data to the respective user without additional data.
This processing enables us to improve the quality of our website and its content. The legal basis for this processing of data is consent under Article 6(1) (a) GDPR. You can revoke your consent at any time with effect for the future, by managing your settings at the very top of this Policy.
Some analytics cookies are provided and/or accessed by third parties. Details of the third parties and their tools that we use analytics cookies for are explained below.
The analysis cookies we use include:
4.1 Google
On our website we use various cookies for analysis purposes that are provided and/or used by Google Ireland Limited ("Google"), a company incorporated and regulated under Irish law (registration number: 368047) with its registered office at Gordon House, Barrow Street, Dublin 4, Ireland ("Google"). Further information about these Google Services can be found below and at https://www.google.com/privacy/ads/. The details table below contains cookie names with variable identifiers, where <wpid> is web property ID or the measurement ID for Google Analytics 4, consisting of 10 characters (numbers and letters), [_<customname>] and <property-id> are property IDs in Google Analytics 3 (Universal Analytics), consisting of digits in the following pattern: UA-XXXXXXXX-X.
4.1.1 Google Analytics
Our website uses Google Analytics to design and improve the website in line with demand. Google Analytics uses so-called cookies, which are stored on your end device and which enable an analysis of your use of the website. The information generated by the cookie is usually transferred to a Google server in the USA and stored there. On this website, we use the extension of IP masking (so-called IP masking), i.e. your IP address is shortened by Google within member states of the European Union or in other contracting states of the Agreement on the European Economic Area before being transferred to, and stored in, the USA. Only in exceptional cases will the full IP address be transferred to a Google server in the USA and shortened there.
On behalf of the operator of this website, Google will use this information to evaluate your use of the website, to compile reports on the website activities and to provide further services to the website operator in connection with the use of the website and the Internet.
If you are a Google account holder and have consented to the personalization of advertising ("Ads Personalization") then Google's services also include reports on the effectiveness of our advertising measures (including cross-device reports), demographics and the interests of our users, as well as functions for cross-device delivery of online advertising. In this case, the legal basis for data processing is your consent to Google (Art. 6(1)(a) GDPR).
You can object to the collection or evaluation of your data by Google Analytics by downloading and installing the browser plugin available at the following link: https://tools.google.com/dlpage/gaoptout.
The data sent by us and linked to cookies, user IDs or advertising IDs are automatically deleted after 14 months.
4.2 Go Instore – SYM-SYS Ltd. – Sales Attribution
In the event you agree to the use of analytics cookies, we will use the data of your interaction with our Go Instore services and your corresponding use of our webshop for sales attribution purposes. The data will be anonymized and would not allow any reidentification of a specific userPlease find more information to Sym-Sys Ltd and the Go Instore service on www.goinstore.com
4.3 Optimizely
On our website we use an A/B testing tool provided by our technical service provider Optimizely AB, Torsgatan 11, Box 7007, 103 86 Stockholm, Sweden. Optimizely allows us to compare two versions of our website and then determine which version results in better performance. For this purpose, we must use Cookies and similar technologies named “Session storage” and “Local storage”, in particular, for identifying visitors, tracking their actions, and delivering consistent experiences across page loads. We collect a Visitor ID and an IP Address, which is anonymized by default.
For a small portion of our website visitors (less than 10%), Optimizely Web Experimentation and Optimizely Performance Edge will attempt to collect performance and product usage telemetry; no personal data is collected. Cookies on the browsers of visitors who are sampled for this telemetry data are dropped from domain rum.optimizely.com.
For more information about Optimizely, please visit https://www.optimizely.com/trust-center/privacy/.
4.4 Hotjar
On our website we use cookies for analysis purposes that are provided and/or used by Hotjar Ltd (“Hotjar”), Dragonara Business Centre, 5th floor, Dragonara Road, Paceville St Julian’s STJ 3141 Malta.
Hotjar cookies are used to process information including standard internet log information and details of the visitor’s behavioral patterns upon visiting our site. This is done to operate our site and provide visitors to our site with a better experience by providing us with insights on how visitors use our site. For further details, please see Hotjar’s support site.
You can control the use of cookies and tracking technologies through your browser settings.
4.5 Further Details
You can deactivate analysis cookies. Further details about all of the individual analytics cookies we use can be found in the following table:
Name |
Third Party/Cookie Host |
Purpose |
Retention Period |
GA_OPT_OUT |
|
Used by: Google Analytics
Cookie set to remember that the user opted out from the use of Google Analytics. |
10 Nov 2030 (all cookies) |
NID |
Used by: Google Ads
The cookie contains a unique ID Google uses to remember user preferences and other information, such as preferred language, how many search results the user wishes to have shown per page and whether or not the user wishes to have Google’s SafeSearch filter turned on. |
6 months |
|
AID |
Used by: Campaign Manager, Display & Video 360, Google Ads, Search Ads 360
This cookie links user’s activities on other devices the user has previously logged into using their Google account. Based on this, the ads the user sees on their devices are coordinated and conversion events are measured. |
13 months EEA UK / 540 days elsewhere |
|
TAID |
Used by: Campaign Manager, Display & Video 360, Google Ads, Search Ads 360
The cookie us used for cross device association of the user’s actions. |
14 days |
|
_ga |
Google,Used by: Google Analytics |
Used by: Google Analytics Purpose of the cookie is to store and count pageviews, as well as to distinguish users. |
2 years |
_gac_<wpid> |
Used by: Google Analytics This cookie contains campaign related information for the user. |
90 days |
|
FPID |
FPID is Server Managed and secure HttpOnly cookie that is used as a new Client ID. It replaces the JavaScript Managed and JavaScript accessible cookie which uses the GA4 Client ID. |
2 years | |
FPLC |
Used by: Google Analytics This cookie is the cross-domain linker cookie hashed from the FPID cookie. |
20 hours | |
_gat[_<customname>] |
Used by: Google Analytics
Purpose of the cookie is to throttle the request rate |
1 minute |
|
_gid |
Used by: Google Analytics
Purpose of the cookie is to store and count pageviews, as well as to distinguish users. |
24 hours |
|
__utma |
Used by: Google Analytics
The cookie is used to distinguish users and sessions. This cookie keeps track of the number of times a visitor has been to the site pertaining to the cookie, when their first visit was, and when their last visit occurred. Google Analytics uses the information from this cookie to calculate things like Days and Visits to purchase. |
2 years |
|
__utmb |
Used by: Google Analytics
The cookie is used to determine new sessions/visits. |
30 minutes |
|
__utmc |
Used by: Google Analytics
This cookie operates in conjunction with the __utmb cookie to determine whether the user is in a new session/visit. |
Session |
|
__utmt |
Used by: Google Analytics
The cookie is set to throttle request rate. |
10 minutes |
|
__utmz |
Used by: Google Analytics
The cookie stores the traffic source or campaign that explains how the user reached the site. |
6 months |
|
__utmv |
Used by: Google Analytics
The cookie is used to store visitor-level custom variable data. |
2 years |
|
AMP_TOKEN |
Used by: Google Analytics
The cookie contains a token that can be used to retrieve a Client ID from AMP Client ID service. Other possible values indicate opt-out, inflight request or an error retrieving a Client ID from AMP Client ID service. |
30 seconds to 1 year |
|
_ga_<wpid> |
Used by: Google Analytics
The cookie is used to persist session state. |
2 years |
|
_dc_gtm_<property-id> |
Used by: Google Analytics
The cookie contains a token that can be used to retrieve a Client ID from AMP Client ID service. |
1 minute |
|
FPAU |
Used by: Campaign Manager, Display & Video 360, Google Ads, Search Ads 360
The cookie is used for analytics and advertising.
|
90 days |
|
FPGCLDC |
Used by: Campaign Manager, Display & Video 360, Search Ads 360
The cookie is used to help advertisers determine how many times users who click on their ads end up taking an action on their site |
90 days |
|
_gcl_dc |
Used by: Campaign Manager, Display & Video 360, Search Ads 360
The cookie is set to store and track conversions. |
90 days |
|
_gcl_au |
Used by: Campaign Manager, Display & Video 360, Google Ads, Search Ads 360
The cookie is used for "Conversion Linker" functionality. |
90 days |
|
FPGCLGB |
Used by: Google Ads
The cookie is used for analytics and advertising. |
90 days |
|
_gcl_gb |
Used by: Google Ads
The cookie is assisting in "Conversion Linker" functionality - it takes information in ad clicks and stores it in a first-party cookie so that conversions can be attributed outside the landing page. |
90 days |
|
_gac_gb_<wpid> |
Used by: Google Ads
The cookie contains campaign related information. |
90 days |
|
_gcl_aw |
Used by: Google Ads
The cookie is assisting in "Conversion Linker" functionality - it takes information in ad clicks and stores it in a first-party cookie so that conversions can be attributed outside the landing page. |
90 days |
|
DSID |
Doubleclick, Google
|
Used by: Campaign Manager, Google Ad Manager, Google Analytics, Display & Video 360, Search Ads 360
The cookie is set to store user preferences. |
2 weeks |
test_cookie |
Used by: Campaign Manager, Google Ad Manager, Google Analytics, Display & Video 360, Search Ads 360
This cookie is used by Google DoubleClick to check that cookies can be set. |
15 minutes |
|
IDE |
Used by: Campaign Manager, Display & Video 360, Google Ad Manager, Google Analytics, Search Ads 360
The cookie is used for serving targeted advertisements that are relevant to users across the web.
|
13 months EEA UK / 24 months elsewhere |
|
gis-chat-call-user-uuid (Local Storage) |
SYM-SYS Ltd. |
Used to identify a customer anonymously for sales attribution. |
Session |
optimizelyEndUserId |
Optimizely, however dropped from Miele domain |
Stores a visitor's unique Optimizely Experimentation identifier. | 6 months |
optimizelyRedirectData |
Optimizely, however dropped from Miele domain |
After Optimizely Experimentation has executed a redirect experiment, it stores various data from the original page so that Optimizely Experimentation still has access to it on the new page. | 5 seconds |
optimizelyDomainTestCookie |
Optimizely, however dropped from Miele domain |
When Optimizely Experimentation loads a URL, the snippet places the cookie to get the current domain for determining whether cross-domain syncing is possible. If successful, the cookie is immediately removed. | 6 months |
optimizelyOptOut |
Optimizely, however dropped from Miele domain |
Stores a boolean indicating whether the visitor has opted out of participating in Optimizely Experimentation-powered experimentation. | 10 years |
AWSELB | rum.optimizely.com | Enables "sticky sessions", which is a requirement of our RUM service. | Session |
optimizelyRumLB | rum.optimizely.com | Controls the AWSELB cookie's attributes (e.g., SameSite and Secure). | Session |
_hjSessionUser_{site_id} |
Hotjar, however set from Miele domain |
This cookie is set when a user first lands on a page. Persists the Hotjar User ID which is unique to that site. Hotjar does not track users across different sites. Ensures data from subsequent visits to the same site are attributed to the same user ID. JSON data type. |
365 days |
_hjid |
This is an old cookie that Hotjar does not set anymore, but if a user has it unexpired in their browser, Hotjar will reuse its value and migrate to _hjSessionUser_{site_id}. Set when a user first lands on a page. Persists the Hotjar User ID which is unique to that site. Ensures data from subsequent visits to the same site are attributed to the same user ID. UUID data type. |
365 days | |
_hjFirstSeen |
This cookie identifies a new user’s first session. Used by Recording filters to identify new user sessions. Boolean true/false data type. |
30 minutes, extended on user activity | |
_hjHasCachedUserAttributes (Local Storage) |
This cookie enables us to know whether the data set in _hjUserAttributes Local Storage item is up to date or not. Boolean true/false data type. |
Session | |
_hjUserAttributes (Local Storage) |
This cookie stores User Attributes sent through the Hotjar Identify API. Base64 encoded JSON data type. |
Persistent | |
hjViewportId (Local Storage) |
This cookie stores user viewport details such as size and dimensions. UUID data type. |
Session | |
hjActiveViewportIds (Local Storage) |
This cookie stores user active viewports IDs. Stores an expirationTimestamp that is used to validate active viewports on script initialization. JSON data type. |
Persistent | |
_hjSession_{site_id} |
This cookie holds current session data. Ensures subsequent requests in the session window are attributed to the same session. JSON data type. |
30 minutes duration, extended on user activity. |
|
_hjSessionTooLarge |
This cookie causes Hotjar to stop collecting data if a session becomes too large. Determined automatically by a signal from the server if the session size exceeds the limit. Boolean true/false data type. |
1 hour | |
_hjSessionResumed |
This cookie is set when a session/recording is reconnected to Hotjar servers after a break in connection. Boolean true/false data type. |
Session | |
_hjCookieTest |
This cookie checks to see if the Hotjar Tracking Code can use cookies. If it can, a value of 1 is set. Deleted almost immediately after it is created. Boolean true/false data type. |
Under 100ms duration, cookie expiration time set to session duration. |
|
_hjLocalStorageTest |
This cookie checks if the Hotjar Tracking Code can use Local Storage. Data stored in _hjLocalStorageTest has no expiration time, but it is deleted almost immediately after it is created. Boolean true/false data type. |
Under 100ms duration. |
|
_hjSessionStorageTest |
This cookie checks if the Hotjar Tracking Code can use Session Storage. If it can, a value of 1 is set. Data stored in _hjSessionStorageTest has no expiration time, but it is deleted almost immediately after it is created. Boolean true/false data type. |
Under 100ms duration. |
|
_hjIncludedInPageviewSample |
This cookie is set to determine if a user is included in the data sampling defined by your site's pageview limit. Boolean true/false data type. |
2 minutes duration, extended every 30 seconds. |
|
_hjIncludedInSessionSample_{site_id} |
This cookie is set to determine if a user is included in the data sampling defined by your site's daily session limit. Boolean true/false data type. |
2 minutes duration, extended every 30 seconds. |
|
_hjAbsoluteSessionInProgress |
This cookie is used to detect the first pageview session of a user. Boolean true/false data type. |
30 minutes duration, extended on user activity | |
_hjTLDTest |
We try to store the _hjTLDTest cookie for different URL substring alternatives until it fails. Enables us to try to determine the most generic cookie path to use, instead of page hostname. It means that cookies can be shared across subdomains (where applicable). After this check, the cookie is removed. Boolean true/false data type. |
Session | |
_hjRecordingEnabled (Session Storage) |
This cookie is set when a Recording starts. Read when the Recording module is initialized to see if the user is already in a recording in a particular session. Boolean true/false data type. |
Session | |
_hjRecordingLastActivity (Session Storage) |
This cookie is updated when a user recording starts and when data is sent to the server (the user performs an action that Hotjar records). Numerical value (timestamp) data type. |
Session | |
_hjClosedSurveyInvites |
This cookie is set when a user interacts with a Link Survey invitation modal. Ensures the same invite does not reappear if it has already been shown. List of Survey IDs, URL encoded. |
365 days | |
_hjDonePolls |
This cookie is set when a user completes an on-site Survey. Ensures the same Survey does not reappear if it has already been filled in. List of Survey IDs, URL encoded. |
365 days | |
_hjMinimizedPolls |
This cookie is set when a user minimizes an on-site Survey. Ensures that the Survey stays minimized when the user navigates through your site. List of Survey IDs, URL encoded. |
365 days | |
_hjShownFeedbackMessage |
This cookie is set when a user minimizes or completes a Feedback widget. This cookie ensures the Feedback widget will load as minimized if the user navigates to another page where it is set to show. Boolean true/false data type. |
1 day |
5. Marketing cookies
For the purpose of retargeting/remarketing and for the placement of online advertisements we use so-called marketing cookies from third parties.
Retargeting or remarketing refers to technologies that allow users who have previously visited a certain website to see suitable advertisements even after they have left the website. For this purpose, it is necessary to recognize Internet users beyond their own website, for which cookies from the corresponding service providers are used. In addition, the previous usage behaviour is taken into account. For example, if a user looks at certain products, these or similar products can later be displayed as advertisements on other websites. These are personalised advertisements that are adapted to the needs of individual users. For this personalised advertising, it is not necessary for the user to be identified beyond recognition. The data used for retargeting or remarketing is therefore not merged with other data.
Marketing cookies may also track user engagement with the ads ultimately shown. This is in order to avoid unwanted duplicate advertising and to track the amount of times ads result in some form of ad conversion (e.g. an ad being clicked on or an actual sale).
The legal basis for the processing of personal data through marketing cookies is consent (Article 6(1)(a) GDPR), You can revoke your consent at any time with effect for the future, by managing your settings at the very top of this Policy.
We use such technologies for the placement of online advertisements. For the placement of the advertisements we use third party providers. Details of the third parties (and their tools) who provide and/or access marketing and targeted cookies are explained below.
5.1 Facebook / Meta
On our website we use marketing cookie(s) provided and/or used by Meta, Inc., 1 Hacker Way, Menlo Park, CA 94025, USA (“Facebook” or “Meta”).
Facebook cookies are used if you have a Facebook account, use the Facebook Products, including the Facebook website and apps, or visit other websites and apps that use the Facebook Products (including the Like button or other Facebook Technologies). The Facebook cookies allow us to track your activities on our website in order analyse the effectiveness of our conversion funnel and to regularly improve our website. Furthermore, the Facebook cookies allow us to use the “Custom Audiences” remarketing feature of Facebook. This allows users of the website to be shown interest-based advertisements ("Facebook Ads") as part of their visit to the social network Facebook or other websites that also use the process. Please find more information to Facebook Conversion Tracking, Facebook Custom Audiences and related data processing activities in our privacy notice.
In addition, the Facebook cookies enable Facebook to offer the Facebook Products to you and to understand the information they receive about you, including information about your use of other websites and apps, whether or not you are registered or logged in.
The Facebook cookies receives the following types of data: Http Headers, Pixel specific Data, Button Click Data, Optional Values and Form Field Names. Further information about Facebook's cookies can be found here.
5.2 Google
As already outlined above, on our website we use various cookies for analytics and/or marketing purposes that are provided and/or used by Google. Further information about Google's privacy practices can be found at https://www.google.com/privacy/ads/. The further details table contains cookie names with variable identifiers, where <wpid> is web property ID or the measurement ID for Google Analytics 4, consisting of 10 characters (numbers and letters), [_<customname>] and <property-id> are property IDs in Google Analytics 3 (Universal Analytics), consisting of digits in the following pattern: UA-XXXXXXXX-X.
5.2.1 Google Ads
Google Ads is an online advertising platform developed by Google, where advertisers pay to display brief advertisements, service offerings, product listings, video content, and generate mobile application installs within the Google ad network to web users.It can place ads both in the results of search engines like Google Search and on non-search websites, mobile apps, and videos.
Further information about Google Ads can be found here.
5.2.2 Google Remarketing function
Google's remarketing function allows us to serve ads to our users on other sites within the Google Ads network (called "Google ads" or ads on other sites) based on their interests. To this end, we analyse user interaction on our website in order to be able to display targeted advertising to users on other sites even after they have visited our website. For this purpose, Google stores a number in the browsers of users who visit certain Google services or websites in the Google display network. This number, known as a "cookie," is used to track the visits of these users. This number is used to uniquely identify a web browser on a particular computer, not to identify an individual, and no personal data is stored.
You can deactivate the use of cookies by Google by installing the plug-in provided under the following link: www.google.com/settings/ads/plugin.
5.2.3 Google Conversion Tracking
We also use Google's conversion tracking in this context. When you click on an ad placed by Google, a 30-day conversion tracking cookie is placed on your device. This cookie is not used for personal identification. The information collected using the conversion cookie is used to compile conversion statistics for Google Ads customers.You can disable interest-based Google ads on Google in your browser by clicking the "Off" button at https://adssettings.google.de/authenticated or by opting out at http://www.aboutads.info/choices/.
5.2.4 Other Google Marketing Platform services (Campaign Manager 360, Display & Video 360, Search Ads 360)
Our website also uses other services of the Google Marketing Platform (formerly "Google Doubleclick"). Campaign Manager 360 allows us to run ad campaigns and measure their performance. Display & Video 360 helps us manage display and video campaigns. Search Ads 360 is utilized to manage search campaigns across various search engines. These services use cookies to deliver ads that are relevant to users, to improve campaign performance reports, or to prevent a user from receiving ads more than once. Google uses a cookie ID to determine which ads are served in which browser and can thus prevent them from being shown more than once. Google may also use cookie IDs to track conversions, which is whether a user sees an ad and later visits the advertiser's website to make a purchase. These cookies contain no personal information. Your browser automatically establishes a direct connection with the Google server. According to Google, the integration of these services provides Google with the information that you have viewed the corresponding part of our website or clicked on an advertisement from us. If you are registered with a Google service, Google can assign the visit to your user account. Even if you are not registered with Google or have not logged in, it is possible that the provider will find out your IP address and save it. In addition, cookies enable us to understand whether you perform certain actions on our website after you have viewed or clicked on one of our ads on Google or on another platform (conversion tracking) ("floodlight"). Google uses this cookie to understand the content that you have interacted with on our sites so that we can later send you targeted advertising. You can prevent tracking by changing your browser software settings (e.g., disabling third party cookies), disabling conversion tracking cookies by blocking cookies from the http://www.google.com/settings/ads/ domain in your browser settings, with respect to interest-based ads from providers that are part of the About Ads self-regulatory campaign, by clicking on the http://www.aboutads.info/choices link or by clicking on the www.googleadservices.com link. We would like to point out that in this case you may not be able to use all functions of the website to their full extent.
Further information about the Google Marketing Platform is available at https://marketingplatform.google.com/. You can also find further information at the Network Advertising Initiative (NAI) at http://www.networkadvertising.org/.
5.3. Microsoft Ads Remarketing and Conversion Tracking
On our website, we use various marketing cookies that are provided and/or used by Microsoft Corporation, One Microsoft Way, Redmond, WA 98052-6399, US ("Mircosoft"). Microsoft sets cookies on your device if you have reached our website via a Microsoft Bing ad. This enables Microsoft and us to recognize that someone has clicked on an ad and has been redirected to our website and to track your actions in order analyze the effectiveness of our conversion. We only learn the total number of users. Microsoft collects, processes and uses information via the cookies, from which usage profiles are created using pseudonyms. These usage profiles are used to analyze visitor behavior and to display advertisements.
For more information, visit Microsoft Privacy Statement – Microsoft privacy and choice.microsoft.com/en/opt-out.
5.4 Qualtrics
We use the services of Qualtrics LLC, 333 W. River Park Drive, Provo UT 84604, USA in order to conduct customer-, product-, and brandsurveys on our website. When you are taking a survey, we use Qualtrics cookies with ID values, mainly to help keep track of survey sessions or to maintain survey sessions. For more information about Qualtrics LLC please visit www.qualtrics.com.
5.5 Bloomreach Engagement
We use the Bloomreach Engagement solution from the provider BloomReach, Inc., 82 Pioneer Way Mountain View, CA 94041, USA on our website for personalized advertisement. Through the use of cookies and other tracking technologies, we collect information about your user behaviour on the website. The cookies contain a specific ID and can thus be assigned to your user profile. We save the information collected via the cookies - insofar as we are entitled to do so on the basis of a separate consent - to your user profile (personal) in order to better tailor the content that we display to you via various channels (website, app, etc.) to your personal interests. In this context, we collect the following usage data:
- - Viewed products (incl. product category);
- - Products in the shopping cart;
- - Registration;
- - Login;
- - Newsletter subscription;
- - Checkout;
- - Respected product information (e.g. energy label);
- - Viewed product data sheet; and
- - Updating the wish list.
We only link this usage data to your (personal) user profile if you have separately consented to this. Otherwise, this data will not be linked to your (personal) user profile, but will only be processed without a corresponding link in order to display interest-related online advertising.
It is possible that your data will be processed outside the European Union. In this case, we take all necessary measures within the meaning of Article 46(2) of the GDPR to protect your data, for example by concluding the EU standard contractual clauses for the transfer of data between the EU and non-EU countries. You can access the EU standard contractual clauses here Standard Contractual Clauses (SCC) | European Commission (europa.eu).
We store this information (extended personalisation) for this purpose for 2 years. The legal basis for this processing is your consent.
5.6 Teads
On our website, we use various marketing and advertising cookies that are provided and/or used by Teads SA with registered office at 5 rue de la Boucherie, L12 17 Luxembourg (“Teads”) in order to optimize our advertising campaigns. Teads tracking technology collects information regarding the URL address, the types of device, browser and operating system information you currently use, and your IP address. Teads provides aggregated data reports on the performance of the campaign.
For more information visit: https://privacy-policy.teads.com/
5.7 Rakuten Marketing LLC dba Rakuten Advertising
On our website, we use various marketing cookies that are provided and/or used by Rakuten Marketing LLC dba Rakuten Advertising, 800 Concar Drive Suite 175, San Mateo, CA 94402, US, (“Rakuten Advertising”). Rakuten Advertising is an online digital advertising company that provides services to a network of publishers and advertisers. Those services include affiliate marketing, performance marketing, personalized advertising and optimization, measurement and reporting, facilitation of advertising-related transactions between network participants, and other online advertising tools and technologies. Rakuten Advertising sets cookies on your device if you have reached our website by interacting with a Rakuten advertising program. The cookies contain a unique identifier that can be used to track your activity. This enables Rakuten Advertising and us to track referrals and to attribute conversions to corresponding affiliates. The tracking is required to identify the affiliate responsible for a referral, so that the affiliate can be properly credited for the conversion. You can find more information about the individual cookies we use for Rakuten Advertising and the purposes for which we use them in the table below.
For more information, visit https://go.rakutenadvertising.com/hubfs/Services-Privacy-Policy-English.pdf, https://go.rakutenadvertising.com/hubfs/Cookie-Policy.pdf, and https://rakutenadvertising.com/legal-notices/. You can exercise your rights with regard to cookies Rakuten Advertising uses for their services directly via this link: https://go.rakutenmarketing.com/hubfs/legal-notices/Data-Subject-Rights-Request-Confirmation-of-Identify.pdf
5.8 Further Details
You can deactivate marketing cookies by changing your settings at the top of this policy. Further details about all of the individual marketing cookies we use can be found in the following table:
Name |
Third Party/Cookie Host |
Purpose (further explanation above) |
Retention Period |
_fbp |
Meta / Facebook, however set from Miele domain
|
General: Facebook Marketing Specific: cookie is used to identify browsers for the purposes of providing advertising and site analytics |
90 days |
_fbc |
Meta / Facebook
|
General: Facebook Marketing Specific: cookie is used to store the Facebook Click ID in order to match website access and clicks on Facebook Ads |
90 days |
fr |
General: Facebook Marketing
Specific: cookie is used to deliver, measure and improve the relevancy of Facebook Ads |
7 days |
|
wd |
General: Facebook Marketing
General: cookie is used to deliver an optimal experience for your device’s screen |
2 years |
|
datr |
General: Facebook Marketing
General: cookie is used to identify the web browser being used to connect to Facebook independent of the logged in user |
700 days |
|
c_user |
General: Facebook Marketing
Specific: cookie is used for authenticating the identity to Facebook |
90 days |
|
locale |
General: Facebook Marketing
Specific: cookie is used for the "Share" button |
7 days |
|
presence |
General: Facebook Marketing
Specific: cookie is used to enable website features and services, such as use of messenger chat windows |
Session |
|
sb |
General: Facebook Marketing Specific: cookie is used to identify the browser for login authentication purposes |
700 Days |
|
spin |
General: Facebook Marketing |
Session |
|
xs |
General: Facebook Marketing Specific: cookie is used for authenticating the identity to Facebook |
The lifetime of this cookie is dependent on the status of the ‘keep me logged in’ checkbox. If the ‘keep me logged in’ checkbox is set, the cookie expires after 90 days of inactivity. If the ‘keep me logged in’ checkbox is not set, the cookie is a session cookie. |
|
oo |
General: Facebook Marketing Specific: cookie is used by Facebook to remember that the user has opt out of seeing ads from Meta based on activity on third-party websites |
5 years |
|
dpr |
General: Facebook Marketing
Specific: cookie is used for optimization of the screen display |
7 days |
|
dbln |
General: Facebook Marketing
Specific: cookie is used to save browser details and Facebook account security information |
2 years |
|
act |
General: Facebook Marketing
Specific: cookie is used This cookie is used to distinguish between two sessions for the same user, created at different times
|
The lifetime of this cookie is dependent on the status of the ‘keep me logged in’ checkbox. If the ‘keep me logged in’ checkbox is set, the cookie expires after 90 days of inactivity. If the ‘keep me logged in’ checkbox is not set, the cookie is a session cookie. |
|
1P_JAR |
|
Used by: Google Ads
This cookie carries out information about how the user uses the website and any advertising that the user may have seen before visiting the said website. |
30 days |
Conversion |
Used by: Google Ads
The cookie is used for advertising. |
90 days |
|
ANID |
Used by: Campaign Manager, Display & Video 360, Google Ads, Search Ads 360
This cookie links user’s activities on other devices they have previously logged into using their Google account. Based on this, the ads the user sees on their devices are coordinated and conversion events are measured. |
13 months EEA UK / 24 months elsewhere |
|
AID |
Used by: Campaign Manager, Display & Video 360, Google Ads, Search Ads 360
This cookie links user’s activities on other devices the user has previously logged into using their Google account. Based on this, the ads the user sees on their devices are coordinated and conversion events are measured. |
13 months EEA UK / 540 days elsewhere |
|
TAID |
Used by: Campaign Manager, Display & Video 360, Google Ads, Search Ads 360
The cookie us used for cross device association of the user’s actions. |
14 days |
|
NID |
Used by: Google Ads
The cookie contains a unique ID Google uses to remember user preferences and other information, such as preferred language, how many search results the user wishes to have shown per page and whether or not the user wishes to have Google’s SafeSearch filter turned on. |
6 months |
|
FPAU |
Google, however set from Miele domain |
Used by: Campaign Manager, Display & Video 360, Google Ads, Search Ads 360
The cookie is used for analytics and advertising. |
90 days |
FPGCLAW |
Used by: Google Ads This cookie replicates the pre-existing Google Ads cookies in that it writes the Google Ads Click ID into a first-party cookie |
90 days | |
FPGCLGB |
Used by: Google Ads
The cookie is used for analytics and advertising. |
90 days |
|
_gcl_gb |
Used by: Google Ads
The cookie is assisting in "Conversion Linker" functionality - it takes information in ad clicks and stores it in a first-party cookie so that conversions can be attributed outside the landing page. |
90 days |
|
_gac_gb_<wpid> |
Used by: Google Ads
The cookie contains campaign related information. |
90 days |
|
_gcl_aw |
Used by: Google Ads
The cookie is assisting in "Conversion Linker" functionality - it takes information in ad clicks and stores it in a first-party cookie so that conversions can be attributed outside the landing page. |
90 days |
|
FPGCLDC |
Used by: Campaign Manager, Display & Video 360, Search Ads 360
The cookie is used to help advertisers determine how many times users who click on their ads end up taking an action on their site |
90 days |
|
_gcl_dc |
Used by: Campaign Manager, Display & Video 360, Search Ads 360
to store and track conversions. |
90 days |
|
_gcl_au |
Used by: Campaign Manager, Display & Video 360, Google Ads, Search Ads 360
The cookie is used for "Conversion Linker" functionality. |
90 days |
|
__gpi |
Used by: Google Ad Manager
The cookie collects information on user behaviour on multiple websites. This information is used in order to optimize the relevance of advertisement on the website. |
13 months |
|
__gpi_optout |
Used by: Google Ad Manager
This cookie is used to deliver advertisements on the website. |
13 months |
|
__gads |
Used by: Display & Video 360, Google Ad Manager, Google Ads
The cookie is used to register what ads have been displayed to the user. |
13 months |
|
_gac_<wpid>
|
Used by: Google Analytics
This cookie contains campaign related information for the user. |
90 days
|
|
pm_sess |
Doubleclick, Google
|
Used by: Campaign Manager, Display & Video 360, Google Ads, Search Ads 360
The cookie is set to prevent malicious sites acting without a user’s knowledge and as if they were that user. |
30 minutes |
pm_sess_NNN |
Used by: Campaign Manager, Display & Video 360, Google Ads, Search Ads 360
The cookie is set to prevent malicious sites acting without a user’s knowledge and as if they were that user. |
30 minutes |
|
aboutads_sessNNN |
Used by: Campaign Manager, Display & Video 360, Google Ads, Search Ads 360
The cookie allows users to interact with a service or site to access features that are fundamental to that service. Used to authenticate users, prevent fraud, and protect users as they interact with a service. |
30 minutes |
|
DSID |
Used by: Campaign Manager, Google Ad Manager, Google Analytics, Display & Video 360, Search Ads 360
The cookie is used to identify a signed-in user on non-Google sites and to remember whether the user has agreed to ad personalization. |
2 weeks |
|
test_cookie |
Used by: Campaign Manager, Google Ad Manager, Google Analytics, Display & Video 360, Search Ads 360
This cookie is used by Google DoubleClick to check that cookies can be set. |
15 minutes |
|
id |
Used by: Campaign Manager, Display & Video 360, Google Ad Manager, Search Ads 360
The cookie is used by Google for advertising, including serving and rendering ads, personalizing ads, limiting the number of times an ad is shown to a user, muting ads they have chosen to stop seeing, and measuring the effectiveness of ads. |
OPT_OUT: fixed expiration (year 2030/11/09), non-OPT_OUT: 13 months EEA UK / 24 months elsewhere |
|
FLC |
Used by: Campaign Manager, Display & Video 360, Search Ads 360
This cookie is used to link user’s activity across devices and to coordinate the ads the user sees across devices and measure conversion events. |
10 seconds |
|
RUL
|
Used by: Display & Video 360, Google Ads
The cookie is used to determine whether website advertisement has been properly displayed. |
12 months |
|
IDE |
Used by: Campaign Manager, Display & Video 360, Google Ad Manager, Google Analytics, Search Ads 360
The cookie is used for serving targeted advertisements that are relevant to users across the web.
|
13 months EEA UK / 24 months elsewhere |
|
MUID, MSFPC, MC1
|
Microsoft |
These cookies are used to identify browsers for the purposes of providing advertising and site analytics. |
13 months |
MUIDB |
390 days |
||
_uestsid |
This cookie is used to gather information on how visitors are using our website. |
30 minutes |
|
_uetvid |
This cookie is used to store and track visits across websites. |
13 months |
|
_uetmsclkid |
This is the Microsoft Click ID, which is used to improve the accuracy of conversion tracking. |
Session |
|
SRCHHPGUSR |
This cookie allows us to track the effectiveness of campaigns. |
2 years |
|
_RwBf |
This cookie is used is set for advertisement tracking purposes. |
1 year |
|
ipv6 |
This cookie tracks Bing web visits. |
Session |
|
BCP |
This cookie is used for advertisement tracking purposes. |
1 year |
|
SUID |
This cookie is an analytics service that connects data from the Bing advertising network with actions performed on the website. |
1 day |
|
SRCHD |
This cookie is an analytics service that connects data from the Bing advertising network with actions performed on the website. |
9 months |
|
SRCHUID |
The cookie contains a unique Bing-User-ID. |
9 months |
|
SRCHUSR |
This cookie is an analytics service that connects data from the Bing advertising network with actions performed on the website. |
2 years |
|
SRCHS |
This cookie is an analytics service that connects data from the Bing advertising network with actions performed on the website. |
Session |
|
_EDGE_S |
This cookie is used to retarget website visitors via Bing. |
Session |
|
_EDGE_V |
This cookie is set when a user requests Bing Maps services. |
390 days |
|
_SS |
This cookie indicates if the page viewed is the first in a session. |
Session |
|
_tarLang |
This cookie is used for saving and counting page views. |
1 year |
|
USRLOC |
This cookie is used to understand user interaction with the website. |
390 days |
|
ABDEF |
This cookie is used by the Bing advertising network for advertising tracking purposes. |
390 days |
|
_UR |
This cookie is used by the Bing advertising network for advertising tracking purposes. |
390 days |
|
_HPVN |
This cookie is used by the Bing advertising network for advertising tracking purposes. |
390 days |
|
ANIMIA |
This cookie is used by the Bing advertising network for advertising tracking purposes. |
22 days |
|
_TTSS_OUT |
This cookie is an analysis cookie from Bing. |
1 year |
|
_TTSS_IN |
This cookie is an analysis cookie from Bing. |
1 year |
|
dsc |
This cookie is used by the Bing advertising network for advertising tracking purposes. |
Session |
|
ANON |
This is a Microsoft MSN 1st party cookie to enable user-based content. |
2 months |
|
MS0 |
This cookie identifies a specific session. |
13 months |
|
MR |
This cookie is used by Microsoft to reset or refresh the MUID cookie. |
3 months |
|
MSCC |
This cookie contains user choices for most Microsoft properties. |
6 months |
|
MC0 |
This cookie detects whether cookies are enabled in the browser. |
13 months |
|
NAP |
This cookie contains an encrypted version of your country, postal code, age, gender, language and occupation, if known, based on your Microsoft account profile.
The cookie is only set if a user has accepted cookies from Microsoft Bing, has created a Microsoft profile and has provided Microsoft with this information. |
13 months |
|
OIDI |
This cookie is used by the Bing advertising network for advertising tracking purposes. |
1 year |
|
MH |
This cookie appears on co-branded sites where Microsoft is partnering with an advertiser. This cookie identifies the advertiser, so the right ad is selected. |
13 months |
|
PPAuth, MSPAuth, MSNRPSAuth, KievRPSAuth, WLSSC, MSPProf |
These cookies help to authenticate a user when they sign in their Microsoft account. |
13 months |
|
x-ms-gateway-slice |
This cookie identifies a gateway for load balancing. |
13 months |
|
TOptOut |
This cookie records the decision not to receive interest-based advertising delivered by Microsoft. Where required, Microsoft places this cookie by default and removes it when a user consents to interest-based advertising. |
5 years |
|
CSRFCookie |
This cookie is used by the Bing advertising network for advertising tracking purposes. |
Session |
|
_uetsid_exp (local storage)
|
This cookie is used to gather information on how visitors are using our website. |
Persistent |
|
_uetvid_exp (local storage) |
This cookie is used to store and track visits across websites. |
Persistent |
|
Survey ID |
Qualtrics LLC |
Cookie is used to identify the survey user and to store the survey history of the user to keep track of survey session or to maintain survey session. |
6 Months |
Hash of the sessionID and query parameters that maps to a sessionID |
Cookie is used to record the hash of the session ID and url of the user's response so that if save and continue is on the survey user will be able to come back to their response to continue |
Up to 1 year or when the session is complete |
|
QST |
Cookie is used to record the survey taken and prevent the survey user from taking the survey again. |
6 Months |
|
<surveyid><statedata>-reloadSession |
This cookie is for surveys using an SSO Authenticator and is used to inform Qualtrics what session to reload after the respondent leaves and comes back. |
15 Minutes |
|
A hash of the url that may be appended with ‘-singleReload’ |
Cookie is used to record the survey taken and prevent the survey user from taking the survey again. |
6 Months |
|
__exponea_etc__ |
Bloomreach |
General: Bloomreach Engagement
Specific: this cookie is used to store a unique user ID.
|
7 days - 3 years (depending on browser) |
xnpe_[project-token] |
General: Bloomreach Engagement
Specific: this cookie helps to keep the user's identity for browsers that have shorter expiration for client-side cookies such as Safari. |
3 years |
|
__exponea_time2__ |
General: Bloomreach Engagement
Specific: timestamp offset between browser and server time. |
60 minutes |
|
__exponea_ab_[ABTestName]__ |
General: Bloomreach Engagement
Specific: variant name returned for an A/B test. |
7 days - 3 years (depending on browser) |
|
__exponea_experiment_event[EXPERIMENT_ID]_last_show__ - Local storage |
Bloomreach Engagement |
Persistent |
|
__exponea_experiment_event[EXPERIMENT_ID]_last_interaction_- Local storage |
Persistent |
||
__exponea_safari_push_subscribed__ - Local storage |
Persistent |
||
__exponea_last_session_ping_timestamp__ - Local storage |
Persistent |
||
__exponea_last_session_start_timestamp__ - Local storage |
Persistent |
||
__exponea_banner_event__[BANNER_ID]_last_show - Local storage |
Persistent |
||
__exponea_banner_event__[BANNER_ID]_last_interaction - Local storage |
Persistent |
||
__exponea__sync_modifications__- Local storage |
Persistent |
||
_exponea_tracking_definition__ - Session storage |
Persistent |
||
tfpai |
Teads |
Teads First Party Auction ID that allows the correlation of a click on an ad by a user with the visit on a website by this user. The CLICK ID (AuctID) is transferred to the site via URL decoration, and its value stored in a cookie. |
30 days |
tfpsi |
|
Teads First Party Session ID that allows correlating all events of a user to form a session, regardless of whether the user arrived through a Teads ad or not. This cookie allows a more precise and more reliable measure, and helps to improve traffic metrics (qualified visits rate, pages viewed, etc.). |
30 minutes It is auto-generated and can be renewed for 30 minutes. |
tt_viewer |
Teads |
The cookie is used to deliver, measure and improve the relevance of Teads Traffic Acquisition ads. The cookie is dropped and used across all domains a user is visiting. |
365 days |
tt_liveramp |
Teads |
Avoid calling to Liveramp. This avoids unnecessary calls to Liveramp. |
1 day
|
tt_salesforce |
Teads |
Avoid calling to Salesforce. This avoids unnecessary calls to Salesforce. |
1 day |
__rmco_jsv (Local Storage) | Rakuten |
The element is used to store the consent of the user. This refers to cases where client has a consent management platform (CMP) and CMP has obtained certain consents for identified legal purposes. This framework is usually used in reference to the Transparency and Consent Framwork (TCF). If it’s applicable we recognize and abide by the purposes for which consent has been obtained. |
Persistent |
rmuid | Rakuten | Rakuten Advertising ID on Rakuten Advertising domain. The cookie is used to identify which publisher drove the sale and attribute the commission back to the right publisher. | 1 year |
lsclick_midNNNNN (NNNNN is the MID for the advertiser that the click belongs to) |
Rakuten | This cookie contains information on click date and advertisement publisher ID. | 730 days |
6. Changes to this Cookie Policy
We may change this Cookie Policy from time to time to reflect changes to the cookies we use or for other operational, legal or regulatory reasons. Please therefore re-visit this Cookie Policy regularly to stay informed about our use of cookies and related technologies. You can see when this Cookie Policy was last updated by checking the “last updated” date displayed at the top of this Cookie Policy.
7. To get further information
If you have any questions or comments about this Cookie Policy, contact us at info@miele.co.uk.