Set up your bannerConfigure Your ToolsLive Chat and Messaging

LiveChat

How to configure LiveChat at different risk levels and map it in the Consenter Manager.

This work is licensed under CC BY-SA 4.0

Typical processing purposes: Unlock additional website features

Overview

This guide explains how to reflect the LiveChat widget in the Consenter Manager. LiveChat does not document privacy settings that change the widget's cookies, so this guide uses a single fixed-behaviour table.

  1. Implement the service as described below.
  2. Map the implementation in the Consenter Manager.
  3. Update your privacy policy to reflect the actual implementation.

The mapping is an example, not a guarantee of legal compliance. Verify it against your implementation and current provider documentation.

At a glance

Scope. The LiveChat chat widget (Text group).

What the service does in this scope. LiveChat sets two primary cookies, lc_cid (customer ID) and lc_cst (customer secure token), which it describes as necessary for widget operation; they maintain chat sessions, reconnect visitors with previous agents and remember conversations over multiple visits. The Text group's GDPR FAQ names Text, Inc., Boston, United States, as the processing entity.

⚠ Recommendation — "necessary" classification. LiveChat classifies its cookies as necessary for the widget, but the cookies persist across visits to recognise returning visitors. Whether that is strictly necessary for a chat the visitor has not opened is not established by the sources. Load the widget after Consenter consent, or only after the visitor clicks a chat placeholder, unless your DPO or independent counsel confirms otherwise.

Step 1 — Implement LiveChat

Configuration areaFixed behaviour / required action
Processing purposesUnlock additional website features
LoadingConsenter script blocking, or click-to-load placeholder
Cookieslc_cid, lc_cst
ContractDPA with the Text group

Step 2 — Map the configuration in the Consenter Manager

Consenter Manager fieldValue to selectBasis and conditions
Processing purposesUnlock additional website featuresLive chat
Tracking methodFirst party tracking (cross-session)Visitor recognised across visits
IdentifierDevice identifierslc_cid
Data categoriesBrowsing and interaction data, Device characteristics, Device identifiers, IP address, User-provided dataChat context and messages
Legal role of data recipientProcessorProvider on behalf of the operator
Personalisation modelNo personalisation—
Maximum storage durationPer cookie inspectionNot documented
Processing locationUnited StatesText, Inc.; the US CLOUD Act

How is this guide?

Shape Consenter Together

Consenter is built on an open and participatory process that grows through community collaboration. Whether you share feedback, improve the documentation, or contribute to the Risk Configuration Guides or Technical Integration Guides, your expertise helps make Consenter more privacy-friendly, interoperable, and useful for everyone—including your own users and services: Get finally your benefits and control the risks when sharing personal data.

Need Help?

Last updated on

On this page