Does your website use third-party services? Get GDPR compliant in minutes.
Try FlowConsentFree plan · 10-min setup
DialogShift is a German AI chatbot platform used mainly by hotels and service businesses to answer guest questions and capture leads. It loads a conversation widget that can store identifiers and message history in the browser, so it falls under the GDPR and the ePrivacy consent rules.
DialogShift is an artificial intelligence chatbot platform developed in Germany and used widely by hotels, clinics, and service businesses to automate guest and customer conversations. The widget loads on the website, answers common questions, and can hand over to a human agent, processing the messages visitors send along with technical session data.
DialogShift stores a session identifier in a cookie or local storage so a conversation stays coherent, and it may keep the message history and any contact details a visitor provides. In a booking or enquiry context this can include names, dates, and request details, which are personal data under the GDPR.
Writing identifiers to the visitor device is governed by Article 5(3) of the ePrivacy Directive. Storage that is strictly necessary to handle a conversation the visitor started can be exempt, but analytics, persistent recognition, or marketing features need consent. The website operator remains the controller and must disclose the automated processing.
Get GDPR compliant in 10 minutes
Free plan available · No credit card required
If the widget loads automatically and writes non essential storage, gate it behind consent. A clean pattern loads a launcher by default and starts the full assistant once the visitor opens the chat or accepts the relevant category. Provide a link to the privacy notice inside the chat window.
Because DialogShift hosts data in the European Union, transfers are usually not an issue, but you should still sign a data processing agreement, set a retention period for transcripts, and document the lawful basis. List its cookies in your policy and explain that an automated assistant handles the first response.
Websites using DialogShift must obtain user consent under GDPR regulations.
DPIA considerations
A DPIA is not normally required for a standard service chatbot, but consider one if DialogShift handles health or other sensitive enquiries, profiles guests, or processes large volumes. Document the conversation data flows and retention regardless.
Sample consent text
We use DialogShift to answer your questions with an automated assistant. The chat only stores non essential information if you accept it.
Third-party domains contacted
dialogshift.comcdn.dialogshift.comCookies placed
| Name | Type | Duration | Purpose |
|---|---|---|---|
| ds_session | Functional | Session | Keeps the chatbot conversation consistent during a visit |
| ds_visitor | Functional | 6 months | Recognises a returning visitor to restore a previous conversation |
| ds_analytics | Analytics | 1 year | Measures how visitors interact with the chat widget |
DialogShift uses cookies for user preferences — inform visitors with a consent banner.
DialogShift stores a session identifier in a cookie or local storage to keep the conversation consistent, and depending on settings may add analytics cookies. The session storage supports the chat itself, while any analytics storage is non essential.
If the widget loads automatically and sets non essential cookies, you need prior consent. If it only stores what is strictly necessary once a visitor opens the chat, that part can rely on the ePrivacy exemption, but a notice is still required.
The core chat function can rely on legitimate interest or, where it supports a booking or contract, on Article 6(1)(b). Analytics and recognition cookies rely on consent under Article 6(1)(a) of the GDPR and Article 5(3) ePrivacy.
DialogShift hosts conversation data in the European Union, so transfers are usually not an issue. Confirm the hosting location in your data processing agreement and document any non EU integration you enable.
A DPIA is not normally required for a standard service chatbot, but consider one if it handles sensitive enquiries, profiles guests, or processes large volumes. Document the data flows and retention in any case.
Load only a launcher by default, start the full assistant after the visitor opens the chat or grants consent, sign a data processing agreement, and set a transcript retention period. List its cookies and disclose the automated processing in your privacy notice.
Other EU hosted chat and chatbot tools offer comparable features. Whatever you choose, the consent and transparency duties are the same once the widget stores non essential data or profiles visitors.
Add the DialogShift session and analytics cookies with their purpose and duration, mention the automated conversation processing, and update the entry whenever the widget changes how it stores data.