10660
This Cookie Policy (“Policy”) outlines the general policy, practices, and types of cookies that HappyFox, Inc. (“HappyFox,” “we,” “us,” or “our”) may be used to improve our Services and your experience when visiting our Sites. For the purposes of this Policy, capitalized terms used but not defined in this Policy have the meanings given in our Privacy Policy.
What is a Cookie?
Cookies are small pieces of text used to store information on web browsers. They are used by many websites to store and receive identifiers and other information on devices, such as a handheld phone or computer. You can learn more about cookies and their functions generally by visiting an information website such as allaboutcookies.org.
How does HappyFox use cookies?
Our Sites and Services use cookies and other similar technologies (collectively in this Policy, "cookies"), in order to provide a better service to you, to help keep your account safe, and to generally improve our Sites and Services. Cookies perform essential functions, such as ensuring a webpage loads correctly and securely. They also help us provide you with a consistent and efficient experience. For example, we may use cookies to remember which language you prefer, to remember that you are a repeat visitor so we can direct you to the appropriate part of our Sites, or to present you with services that are matched to your preferences. This Cookie Policy (“Policy”) outlines the general policy, practices, and types of cookies that HappyFox, Inc. (“HappyFox,” “we,” “us,” or “our”) may be used to improve our Services and your experience when visiting our Sites. For the purposes of this Policy, capitalized terms used but not defined in this Policy have the meanings given in our Privacy Policy.
We also may include tracking pixels, or pixel tags, which are small graphic images, in our marketing communications to determine engagement. These cookies may be set by us or by third-parties with whom we have partnered to assist in our marketing efforts.
Most web browsers are set to accept cookies by default, however, you may be able to delete cookies yourself through your browser’s cookie manager. To do so, please follow the instructions provided by your web browser. Please note that disabling cookies will reset your session, disable auto-login, and may adversely affect the availability and functionality of our Sites and the services we can provide to you.
Types of cookies
There are generally three categories of cookies: “Strictly Necessary,” “Analytics," and “Targeting.” We routinely use all three categories of cookies on the Service. You can find out more about each cookie category, and the cookies used on our Sites, below.
Strictly Necessary Cookies.:
These cookies are essential, as they enable you to move around the Services and use its features, such as accessing logged in or secure areas. Because these cookies are essential, they cannot be disabled.
Analytics Cookies:
These cookies collect information about how you have used the Services, for example, information related to the unique username you have provided, so that less strain is placed on our backend infrastructure. These cookies may also be used to allow us to know that you have logged in so that we can serve you fresher content than a user who has never logged in. We also use cookies to track aggregate Services usage in an anonymized fashion and experiment with new features and changes on the Services. The information collected is used to improve how the Services work.
Targeting Cookies:
Us, our advertising partners or other third-party partners may use these types of cookies to deliver advertising that is relevant to your interests. These cookies can remember that your device has visited a site or service, and may also be able to track your device’s browsing activity on other sites or services other than ours. This information may be shared with organizations outside of ours, such as advertisers and/or advertising networks to deliver the advertising, and to help measure the effectiveness of an advertising campaign, or other business partners for the purpose of providing aggregate Service usage statistics and aggregate Service testing.
Cookies we set
When you utilize our products, we may set the following cookies on your browser:
|
Cookie |
Lifespan |
Domain |
Type |
Description |
Product Associated |
|---|---|---|---|---|---|
|
staff-sessionid |
Session |
HF/ Custom domain |
Necessary |
Staff session will be stored |
Helpdesk |
|
brand-sessionid |
Session |
HF/ Custom domain |
Necessary |
Contact session will be stored |
Helpdesk |
|
brand{}-sessionid |
Session |
HF/ Custom domain |
Necessary |
Contact session for multi brand will be stored |
Helpdesk |
|
csrftoken |
Session |
HF/ Custom domain |
Necessary |
CSRF token for staff session |
Helpdesk |
|
pbrand-csrftoken |
Session |
HF/ Custom domain |
Necessary |
CSRF token for contact session in primary brand |
Helpdesk |
|
mbrand-csrftoken |
Session |
HF/ Custom domain |
Necessary |
CSRF token for contact session in multi brand |
Helpdesk |
|
messages |
Session |
HF/ Custom domain |
Necessary |
Used by the django framework |
Helpdesk |
|
sc_language |
Session |
HF/ Custom domain |
Necessary |
Used in support center to store the user language code for better user experience by remembering the language chosen for KB articles |
Helpdesk |
|
kb_language |
Session |
HF/ Custom domain |
Necessary |
Used in support center to store the user language code for better user experience by remembering the language chosen for KB articles |
Helpdesk |
|
_dd_s |
4 hours Maximum |
HF/ Custom domain |
Tracking / Necessary |
Set by datadog to group all events generated from a unique user session |
Helpdesk |
|
_GRECAPTCHA |
6 months |
Necessary |
reCAPTCHA sets a necessary cookie (_GRECAPTCHA) when executed for the purpose of providing its risk analysis. |
Helpdesk |
|
|
hf_brand_domain |
Session |
HF/ Custom domain |
Necessary |
To store the brand domain which can be referred in SAML callback |
Helpdesk |
|
password_authorization_expiry |
1 hour |
HF/ Custom domain |
Necessary |
To check whether staff provided the password before doing critical manage actions in the app |
Helpdesk |
|
{subdomain}_token |
Session |
Necessary |
Required for real time data/ real time actions like proactive agent collision |
Helpdesk |
|
|
{subdomain}_token_legacy |
Session |
Necessary |
Required for real time data/ real time actions like proactive agent collision |
Helpdesk |
|
|
io |
Session |
Necessary |
Required for real time data/ real time actions like proactive agent collision |
Helpdesk |
|
|
top_banner_{id} |
Session |
HF/ Custom domain |
Necessary |
Used in support center to store id to decide whether banner needs to be shown or not |
Helpdesk |
|
hf-token |
Session |
HF/ Custom domain |
Necessary |
To store the temporary token generated while resetting password. Instead of having the token in the URL, we are redirecting to an intermediate page by removing the token in the URL and setting the same in cookie |
Helpdesk |
|
x-hfc-auth |
Till the agent session is active |
Necessary |
Agent session will be stored |
Chat |
|
|
x-hfc-csrf |
Till the agent session is active |
Necessary |
Stores CSRF token to prevent csrf attacks |
Chat |
|
|
__stripe_mid |
1 year |
Necessary |
Used for billing subscriptions |
Chat |
|
|
__stripe_sid |
30 minutes |
Necessary |
Used for billing subscriptions |
Chat |
|
|
_ga |
1 year, 1 month, 4 days |
Analytics |
Used for analytics |
Chat |
|
|
_gid |
1 year, 1 month, 4 days |
Analytics |
Used for analytics |
Chat |
|
|
hfbAuth |
Till the agent session is active |
Necessary |
Agent session will be stored |
Chatbot |
|
|
sessionid |
14 days |
Necessary |
User session id will be stored |
Assist AI |
|
|
csrftoken |
1 year |
This will be removed as part of next production release |
Assist AI |
||
|
sessionid |
14 Days |
Necessary |
User session will be stored |
Workflows |
|
|
sessionid |
14 days |
Necessary |
User session id will be stored |
BI |
|
|
csrftoken |
1 year |
Necessary |
CSRF token for user session will be stored |
BI |
