Use of Cookies

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


What are Cookies?

Cookies are small pieces of information stored on your hard drive, not on Freshcaller. 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 or functionality to be provided on or through the website (e.g. like 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

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


Provider
Cookies
Description
Google analytics

_ga_<someid>

_ga

_gid

web analytics service provided by Google. Google Analytics uses cookies to track user interactions and gather information about how visitors use a website

Google ads

_gcl_au

The "_gcl_au" cookie plays a role in measuring ad campaign performance and optimizing the delivery of ads to users

Facebook pixel

_fbp

The "_fbp" cookie is used to store and track information related to Facebook advertising campaigns.

Adobe Experience Cloud (Adobe Target)

_cq_suid
_cq_duid

The "_cq_suid" cookie is a visitor identification cookie used by Adobe Target for tracking and personalization purposes.

Beamer

landing

refUrl

_BEAMER_LAST_UPDATE_<someid>

_BEAMER_LAST_POST_SHOWN_<someid>

_BEAMER_USER_ID_<someid>

_BEAMER_USER_ID_<someid>

_BEAMER_FIRST_VISIT_<someid>

_BEAMER_FIRST_VISIT_<someid>

_BEAMER_BOOSTED_ANNOUNCEMENT_DATE_<someid>

Help website owners and businesses communicate and engage with their users through in-app notifications, announcements, and updates

VWO

zarget_visitor_info
zarget_user_id

VWO allows website owners to create experiments where different variations of a webpage are shown to different visitors.


Clearbit

cb_anonymous_id

cb_user_id
cb_group_id

This identifier allows Clearbit to track the user's interactions and behavior on the website over time.

Heap analytics

_hp2_ses_props.<randomdigits> 

_hp2_id.<randomdigits>

Heap Analytics is a tool that automatically captures and tracks user interactions on websites for the purpose of web analytics and user behavior analysis

Freshcaller cookies
  • capability_token
  • _fcs
  • fw-session-id
  • _session_id
  • _x_m cookie

  • capability_token - Freshcaller agent uses capability token to connect to Twilio. We might deprecate it as we do not rely on this coolie any more rather then we use local storage.
  • _fcs- Used by devise gem for authentication purpose, 

    We are configuring dummy values in the emails.

  • fw-session-id - Freshid V2 session identifier.
  • _session_id - Ruby Session Identifier
  • _x_m cookie - Helps in canary deployment. Reference: Canary Deployment

FreshID

freshid_session_state

freshid_session_token


Optimizely

optimizelyEndUserId


Mixpanel

_mt_sp_id



 

You can visit the Freshworks Cookie Policy page for more information.