What is the __lc_cid cookie?
Necessary for the functionality of the website's chat-box function.
Our October 2026 scan found it on 6 sites (0% of the 2,450 we scanned), set before any consent.
- Purpose
- Functional
- Belongs to
- Livechat
- Set as
- Third-party (under another company's domain)
- Typical lifetime
- 13 months (vendor says: 3 years) — shorter than the vendor documents
Sites that set __lc_cid before consent
The highest-ranked 6 of 6 sites.
- synology.com1 tracking company
- directnic.com3 tracking companies
- ning.com10 tracking companies
- livechat.com6 tracking companies
- aaa.com1 tracking company
- remotepc.com1 tracking company
Related cookies
Other cookies from Livechat.
- __lc_cst6 sites
- __oauth_redirect_detector6 sites
How to stop it
Declining non-essential cookies in a site's consent banner should stop __lc_cid being set on later visits. Blocking third-party cookies in your browser settings stops the third-party kind everywhere, and clearing cookies for a site removes any it already set.
Description from the Open Cookie Database (Apache 2.0).
Understanding this page
- How cookie lifetimes work, and why a 13-month _ga matters
What a cookie's "expires" field actually controls, why Google Analytics ships a 2-year default that many sites cut down to 13 months, and how Safari's 7-day cap on script-set cookies changes the picture.
- First-party vs third-party cookies (and why "first-party" still tracks you)
What the distinction actually means technically, why browsers only block one of the two, and how CNAME cloaking, server-side tagging and cookies like _ga let sites keep tracking under their own domain.
- How to block or limit trackers
Browser privacy settings, content blockers, Global Privacy Control and clearing cookies compared honestly — what each one actually stops, what it doesn't, and what it costs you in return.