What is the fc_uid cookie?
The fc_uid cookie is placed by Freshchat, the live chat and customer messaging solution from Freshworks Inc. It appears on a website when the site owner has integrated the Freshchat widget for customer support or sales conversations.
It is generated automatically by the Freshchat script, typically on the first load of the widget in the visitor's browser, whether or not the visitor starts a chat.
What data it stores
The cookie stores a unique identifier (UID) associated with the visitor or chat session, in the form of an alphanumeric string generated by Freshchat. It does not typically contain direct identifying information such as a name or email address.
The value is sent to Freshchat/Freshworks servers to recognize the visitor when they return to the site and to resume the conversation where it left off.
What it is used for
Its main purpose is to maintain continuity of chat conversations: if a visitor closes the window or returns later, Freshchat can display the previous conversation history using this identifier.
For the site owner, the cookie supports a coherent support experience, avoiding the need for visitors to repeat information already provided in an earlier conversation.
Does it require consent?
CookieFix classifies fc_uid under the preferences (functional) category. Since it is not strictly necessary for the site's core operation but relates to an added feature (live chat), setting it requires the visitor's prior consent under the ePrivacy Directive (2002/58/EC, transposed in Romania via Law 506/2004) and GDPR principles.
The site owner must disclose this cookie in the cookie policy, place it in the appropriate consent banner category, and configure the CMP so the Freshchat widget only loads after the relevant category is accepted.
How to block or delete fc_uid
Visitors can delete or block fc_uid from browser settings (Chrome, Firefox, Edge, Safari) under per-site cookie management, or use private/incognito browsing.
- Clearing browser cookies removes the identifier, and Freshchat will generate a new one on the next visit.
- Blocking third-party scripts in the browser may prevent the chat widget from loading.
For compliance, the site owner should automatically block the Freshchat script from loading until consent is given. A CMP platform like CookieFix can do this automatically, preventing the cookie from being set before the visitor accepts the preferences category.
Frequently asked questions
No, it is a technical identifier used to maintain chat conversation continuity and typically does not contain direct personal data such as a name or email.
The typical duration is 1 year, after which it expires automatically, though the actual lifespan may vary depending on Freshchat's configuration.
Yes, since it is classified as a preferences/functional cookie, it requires the visitor's prior consent under ePrivacy and GDPR rules applicable in the EU.
The Freshchat widget should not load or set the cookie, and the visitor will not benefit from conversation continuity when returning to the site.