Skip to main content

Search

Advice and answers from the ClickCease team

CHEQ Cookies

In This Article:

Paid Marketing: 

What is a Server-Side Cookie:

A server-side cookie is an identifier that can only be accessed by the dropping domain. This cookie is only accessible through an HTTP header, and cannot be accessed by JavaScript.

Example #1:

  • CHEQ is opening up an iframe on example.com
  • This iframe’s domain is cheq.com
  • CHEQ drops a cookie (or reads the cookie value if already exists) when the client (the web browser that renders the page) makes the request to cheq.com

Result:

As CHEQ is the owner of the cheq.com servers - only CHEQ can read this identifier value.

The great value of server-side cookies is that the identifier will be the same across all the internet.

Example #2:

  • CHEQ is opening up an iframe on example.com
  • This iframe’s domain is cheq.com
  • The cookie value is 1234
  • CHEQ is opening up an iframe on another-domain.com 
  • This iframe’s domain is cheq.com

Result:

The cookie value is still 1234.

The fact that the cookie value stayed the same, enables CHEQ to track the same profile across the web.

What is a Client-Side Cookie:

Client-side cookies make sure that a user returning to a site, such as example.com, will have the same value.

Example #1

  • CHEQ is using a client-side cookie on example.com
  • The cookie value is 1234
  • A user refreshes

Result:

The cookie value is still 1234

Example #2

  • CHEQ is using a client-side cookie on another-domain.com
  • The cookie value is 7890
  • A user refreshes

Result:

The cookie value is still 7890

Client-side Cookie Importance:

Safari and Firefox stopped supporting third-party cookies a while back, while Google is now starting to fade out the use of such cookies.

Therefore, a client-side cookie is important for identifying cybercrime and blocking ad fraud.

CHEQ uses first-party cookies (client-side) to track fraudulent users or bots, and the use of first-party cookies facilitates our ability to do so, even with the limitations imposed on server-side cookies by the browsers aforementioned.

Privacy & Security Policy:

CHEQ has not changed what we collect with the usage of client-side cookies. Cookies dropped by CHEQ are solely used to detect illegal fraudulent behavior, and in this specific case, allow us to detect when the same device is used in separate browser sessions. No personal information, such as user identity, is transmitted or collected.

CHEQ's Cookies:

Customer Actions

The only difference is that CHEQ now drops client-side cookies, which may require you to update your cookie policy with the list of all CHEQ's cookies, both server-side and client-side.

Name Duration Description Host Value HTTP Only Secure
cg_uuid up to 365 days CHEQ's cookie is used to detect when the same device is used in separate browser sessions. No personal information such as user identity is transmitted or collected. cheqzone.com Random Hash Yes Yes
_cq_duid 3 months Same as above on domain resolution Top-level domain [version].[creation timestamp].[16 random chars] NA NA
_cq_suid Session Same as above on browser session resolution Top-level domain [version].[creation timestamp].[16 random chars] NA NA
_cq_tuid Tab session sessionStorage, same as above on tab resolution Top-level domain [version].[creation timestamp].[16 random chars] NA NA
_cq_check deleted immediately after insertion A cookie is used to detect whether a device supports cookies Top-level domain 1 NA NA

See the external article Cookies, the GDPR, and the ePrivacy Directive to learn more.