LiveChat

LiveChat sets first party cookies on the publisher domain (__lc_cid, __lc_cst, __lc2_cid, __lc2_cst) and third party cookies on livechatinc.com (__livechat, __lc_visitor_id, AWSALB session affinity). They store the visitor identifier, the chat continuity token and the agent routing state.

The widget sets __lc_cid (visitor identifier, 2 years), __lc_cst (session secret, 2 years), __livechat_lastvisit and __livechat as first party cookies under the publisher domain. The conversation state is also kept in localStorage.

Persistent LiveChat cookies (visitor identification, history retrieval) are not strictly necessary and require consent under article 5(3) ePrivacy. A minimal session only chat that does not store identifiers can be loaded without consent.

Yes. The widget cookies are non strictly necessary because they are dropped before any visitor interaction. Prior, freely given, specific, informed and unambiguous consent under Article 5(3) ePrivacy is required before the LiveChat loader executes.

Performance of a contract for the chat conversation itself. Legitimate interest for limited fraud prevention. Consent for persistent cookies, marketing follow up and integration with CRM lead enrichment.

Widget cookies rely on Article 6(1)(a) GDPR consent. The agent inbox processing relies on Article 6(1)(b) GDPR (contract) for the customer relationship and Article 6(1)(f) GDPR (legitimate interest) for fraud prevention and service operations.

LiveChat hosts customer data on AWS in Frankfurt and Dublin. EU customer data normally stays in the EEA. Some sub processors may operate under EU SCCs. Verify the Text S.A. sub processor list before assuming pure EU residency.

Not by default. Text S.A. is established in Poland (EEA) and processes data on AWS infrastructure with European primary regions. The Text S.A. DPA confirms EEA data residency. Occasional support engagement may involve US subcontractors, covered by Standard Contractual Clauses.

A DPIA is recommended for AI chatbot deployments, when transcripts are retained beyond 12 months, when chat data feeds a US based CRM, or when the chat handles sensitive topics (health, legal, financial advice).

A DPIA is not generally required for LiveChat because data stays inside the EEA and the volume of personal data per chat is small. It becomes recommended when pre chat surveys collect sensitive data, when LiveChat is paired with ChatBot for automated triage, or in regulated sectors.

Decide between persistent and session only chat. Block persistent cookies behind your CMP. Define a transcript retention policy and document it. Sign the Text S.A. DPA with EU SCCs for non EU sub processors. Use the Personal Data Eraser to honour Erasure requests.

Sign the Text S.A. DPA, gate the LiveChat widget behind a consent management platform, list __lc_cid, __lc_cst and __livechat cookies in the cookie policy, document the EEA processing, configure transcript retention, mask sensitive pre chat fields and apply the LC_API consent gate.

European live chat alternatives include Crisp (France), Userlike (Germany), LiveAgent (Slovakia), Tidio (Poland, same regulatory environment), HelpCrunch (EU regions), Smartsupp (Czech Republic) and self hosted alternatives such as Chatwoot.

Crisp (Nantes, EU), Userlike (Cologne, EU), Tidio (Polish, similar profile), Chatwoot (open source self hosted), Smartsupp (Czech), Front (US), Intercom (US), Zendesk (US) or Help Scout (US) for higher feature counts at the cost of more complex transfers.

List the __lc_cid, __lc_cst, __lc2_cid, __lc2_cst first party cookies and the third party cookies on livechatinc.com with domain, duration and purpose. Identify Text S.A. as processor in the privacy notice. Note the EU hosting and describe any sub processor transfers.

List __lc_cid, __lc_cst, __livechat_lastvisit and __livechat with name, domain, duration and purpose. State the EEA data residency, identify Text S.A. as the processor, document the localStorage usage and link to the LiveChat privacy notice.