TABLE OF CONTENTS


Use of Cookies

This Cookie Statement explains how Freshdesk uses cookies and similar technologies to recognize you when you use our product. It explains what these technologies are and why we use them, as well as your rights to control our use of them.


What are Cookies?

Cookies are small pieces of information stored on your hard drive, not on Freshdesk. Cookies set by the website owner (in this case, Freshworks) are called first-party cookies. Cookies set by parties other than the website owner are called third-party cookies. Third-party cookies enable third-party features/functionality to be provided on or through the website (for example advertising, interactive content, and analytics). The parties that set these third-party cookies can recognize your computer both when it visits the website in question and also when it visits certain other websites.


Why do we use cookies?

We use first-party and third-party cookies for several reasons. Some cookies are required for technical reasons in order for our product to operate, and we refer to these as "essential" or "strictly necessary" cookies. Other cookies also enable us to track and target the interests of our users to enhance the experience of our product. Third parties serve cookies through our product for analytics purposes. This is described in more detail below.


Cookies served through our product on the agent portal

The different cookies served through our product, and their purposes are described in the table below:


Cookie providerList of cookiesDescription
Freshdesk internal cookies
_helpkit_sessionThe secret key for verifying cookie session data integrity. If you change this key, all old sessions become invalid.
helpdesk_node_sessionAn encrypted hash that stores the secret key and ID ofthe login attempt.
return_uri/return_toUsed to return to the page where the app was installed.
falcon_enabledIndicates if falcon_ui is enabled for an account.
session_tokenContains the fresh_id token encrypted hash.
_x_mContains the shard ID at which the account runs.
_x_wContains the state of the shard
tag_sort_keyIndicates the order of the tags used in /admin/tags.
template_show_tabFilter used to show the page view for /admin/ticket_templates page (default value: shared)
scenario_show_tabFilter used to show the page view for /admin/scenario_automations page (default value: shared)
filter_nameUsed to set the name of the filter in the agents' tickets list page for default views and custom views.
order_typeUsed to check if the order is ascending or descending for default ticket filters.
wf_orderUsed to check the order of the tickets filtered for custom ticket filters eg, due_by, agent_responded_at, requester_responded_at, etc.
wf_order_typeUsed to check if the order is ascending or descending for custom ticket filters.
session_stateHash values that are used to check if FreshID V2 is enabled.
orderUsed to check the order of the tickets filtered for default ticket filters eg, due_by, agent_responded_at, requester_responded_at, etc.
Google Analytics__utm*To reduce the retention time of the cookies, go to Google Analytics > Admin > Tracking Info > Data Retention.

Refer to this link for more details.
Websitehelpdesk_urlContains the URL for the Freshdesk L2 dev portal. The default value is freshdeskl2dev.freshdesk.com.
Heap Analytics_hp2_*Cookies used by Heap Analytics to manage data

Refer to this link to know more details.
Beamer notifications_BEAMER_Cookies used by Beamer Notifications to manage their data.
Freshmarketerzarget_*Refer to Freshmarketer cookies.
Cloudflare
__cf_bm
Used to identify and mitigate automated traffic to protect your site from bad bots. Learn more.


Cookies served through our product on the customer portal

The different cookies served through the customer portal and their purposes are described in the table below:


Cookie providerList of cookiesDescription
Freshdesk internal cookies
_fw_crm_vFreshchat/Freshworks cookie (used to track Visitor/User identity and chat sessions performed by the user).
_x_wContains the shard ID on which the account runs.
_x_mContains the state of the shard.
_helpkit_sessionThe secret key for verifying cookie session data integrity. If you change this key, all old sessions become invalid.
helpdesk_node_sessionAn encrypted hash that stores the secret key and id of the login attempt.
user_credentialsUsed for user authentication.
wf_orderUsed to check the order of the tickets filtered for custom ticket filters, eg, due_by, agent_responded_at, requester_responded_at, etc.
wf_order_typeUsed to check if the order is ascending or descending for ticket filters.
wf_filterDenotes which filter is applied for the tickets list.
Cloudflare
__cf_bm
Identifies and mitigates automated traffic.


Enabling the default cookie policy for the customer portal:

You can enable the default cookie consent popup for your support portal in the security settings.

  • Go to Admin > Security

  • Use the toggle to Enable the cookie policy for all your support portals



  • You will be given the option to can also insert your cookie policy 



Once enabled, any new user on your support portals will see a disclaimer (banner) at the bottom of the page informing them about the cookies served.



If they click Click here, they will be presented with the consent popup which explains the cookies being served and their purpose. 



Please note that only the default cookies served through Freshdesk are displayed here. If there is any customization or integration which serves additional cookies, you would need to implement your own cookie consent popup via portal customization. 


Note: Disabling the cookie policy will remove this banner from all your customer portals.


Customization:

If you would like the consent popup to only be available for specific portals, you can edit the individual portal themes and remove this placeholder {{ portal | default_cookie_policy_settings }}.