Definition
Under EU ePrivacy rules and the GDPR, a chat widget needs the visitor's consent before storing non-essential cookies or identifiers in their browser.
Chat widgets often store an identifier so the visitor's conversation persists across pages and visits, and some also set analytics or marketing cookies. Under the EU ePrivacy Directive, storing or reading information on a visitor's device needs consent unless it is strictly necessary for a service the visitor explicitly requested.
A common interpretation is that storage needed to run a chat the visitor actively starts can be strictly necessary, while tracking, analytics, session replay, and proactive targeting are not. National regulators differ in detail, so check the guidance in your markets.
Practical options: load the widget only after consent, load a minimal version until consent is given, or classify each widget feature correctly in your consent tool. This page is general information, not legal advice.
Example
A website's consent banner lists the chat widget under "Functional" for the conversation itself and under "Analytics" for its visitor tracking, and only enables tracking after the visitor accepts analytics.
How Yaplet helps
Yaplet's widget can be added to sites that use a consent manager, and Yaplet is EU-hosted.