Freshdesk

Overview

Freshdesk, part of the Freshworks product suite, is a customer support platform that provides helpdesk ticketing, live chat, and knowledge base functionality. On third-party websites, Freshdesk's primary presence is the Freshchat widget (also branded as Freshworks Messaging) — an embedded chat interface that allows visitors to initiate support conversations, browse help articles, and submit tickets. The widget is widely deployed across SaaS, e-commerce, and service-oriented websites as a real-time support channel.

What This Script Does

Freshdesk's widget loads from wchat.freshchat.com or fw-cdn.com and initializes the chat interface on the host page.

Functionality:

• Renders a persistent chat bubble that expands into a full messaging interface
• Supports real-time messaging with support agents and chatbot-driven flows
• Displays contextual help articles from the connected Freshdesk knowledge base
• Tracks the visitor's current page and navigation history to provide context to support agents
• Supports file attachments and screenshot sharing within the chat

Cookies set:

• fc_uid — persistent cookie identifying the visitor across chat sessions so agents can see conversation history
• fc_session — session cookie for the active chat session
• fc_campaign — cookie tracking whether the visitor has seen or dismissed proactive chat campaigns
• Cookies scoped to freshchat.com domain for maintaining the chat session state

Data collected:

• Chat messages and file attachments submitted by the visitor
• Current page URL and navigation path (displayed to agents for support context)
• Visitor identity when provided (name, email) or when pre-populated via the host application
• Browser and device information for troubleshooting

The page history tracking serves a support context purpose — agents see what pages the visitor browsed to understand the issue without asking. This is standard practice for support chat tools but does involve passive data collection beyond what the visitor explicitly submits.

Consent & Compliance

Freshdesk falls under the functional consent category. Under GDPR, the chat session cookies serve the functional purpose of enabling a service (customer support) that the visitor initiates by clicking the chat widget. The persistent visitor identification cookie (fc_uid) maintains conversation history across sessions, which is a functional feature but involves storing a persistent identifier.

The proactive chat campaign cookie (fc_campaign) manages whether triggered chat prompts have been shown, which some DPAs may view as requiring consent since the proactive messages are not user-initiated.

Under CCPA/CPRA, the data collected through support interactions is user-directed and does not constitute a "sale" of personal information. Freshdesk should be disclosed as a data processor in the privacy policy.

Should You Block This Without Consent?

No. Freshdesk's chat widget serves a functional support purpose. The core chat functionality and session cookies are tied to a service visitors explicitly engage with. If you use proactive chat campaigns (auto-triggered messages), consider whether those require consent in your jurisdiction, as they involve behavioral monitoring before the visitor initiates contact.