Does your website use third-party services? Get GDPR compliant in minutes.
Try FlowConsentFree plan · 10-min setup
GetChat is a chat widget that lets visitors start a conversation with a business, often by redirecting them to messaging apps such as WhatsApp. It can set cookies and pass data to third party messaging providers, which brings consent and data transfer duties under the GDPR.
GetChat is a website chat widget that places a contact button on a page and lets visitors start a conversation with a business, frequently by opening a messaging app such as WhatsApp, Messenger, or Telegram. It is used to turn website visits into direct conversations and to capture enquiries from interested visitors.
GetChat can set cookies or local storage to remember that a visitor opened the widget and to attribute the conversation, and when it redirects to a messaging app it shares the page context and identifiers with that provider. The conversation content and any contact details then become personal data handled by both you and the messaging provider.
Setting non essential storage and loading third party scripts fall under Article 5(3) ePrivacy and need consent. Where GetChat routes chats through WhatsApp or Messenger, the messaging provider may process data in the United States, so a transfer mechanism such as the EU US Data Privacy Framework applies and must be disclosed.
Get GDPR compliant in 10 minutes
Free plan available · No credit card required
Load the widget so that it does not set non essential cookies or contact a messaging provider until the visitor opens the chat or accepts the relevant category. A click to chat button that only redirects on user action is easier to justify, but you must still inform users that the conversation continues on a third party platform.
Identify which messaging providers GetChat connects to, sign the relevant agreements, and document the transfers. List its cookies, explain in your privacy notice that conversations may continue on external apps subject to their own policies, and set retention rules for any enquiry data you keep.
Websites using GetChat must obtain user consent under GDPR regulations.
DPIA considerations
GetChat itself is low complexity, but routing conversations to large messaging platforms introduces third party processing and United States transfers. Assess the messaging providers involved, the data shared with them, and the transfer safeguards before deployment.
Sample consent text
We use GetChat to let you contact us, including through messaging apps such as WhatsApp. These features and their cookies are only enabled if you accept them.
Third-party domains contacted
getchat.ioapi.whatsapp.comCookies placed
| Name | Type | Duration | Purpose |
|---|---|---|---|
| gc_open | Functional | 30 days | Remembers that the chat widget was opened or minimised |
| gc_attr | Marketing | 90 days | Attributes the conversation to the page and campaign the visitor came from |
GetChat uses cookies for user preferences — inform visitors with a consent banner.
GetChat can set a functional cookie that remembers the widget was opened and a marketing cookie that attributes the conversation to a page or campaign. The attribution cookie is non essential and needs consent.
Yes, where it sets non essential cookies or loads third party messaging scripts. A pure click to chat link that only acts when the user clicks can rely on the user request, but you must still inform them about the external platform.
A basic contact button can rely on legitimate interest, while attribution cookies and the messaging redirect rely on consent under Article 6(1)(a) of the GDPR and Article 5(3) ePrivacy.
It can, indirectly. When GetChat routes conversations to WhatsApp or Messenger, the provider may process data in the United States, so you must rely on a transfer mechanism such as the EU US Data Privacy Framework and disclose it.
The widget itself is low risk, but the messaging providers it connects to may warrant assessment. Evaluate the data shared with them and the United States transfers, especially if conversations include sensitive details.
Block non essential cookies and the messaging redirect until consent or a user click, sign agreements with the messaging providers, document the transfers, and disclose the external platforms in your privacy notice.
EU hosted chat tools that keep conversations on your own infrastructure avoid the messaging provider transfer. Any widget that sets non essential cookies still requires consent.
List the GetChat cookies with their purpose and duration, state that conversations may continue on messaging apps with their own policies, and note any United States transfer. Update the entry when you change messaging providers.