Skip to main content

Hyperproof cookies

Cookies are small text files containing a string of characters sent to your computer when you visit a website. When you visit the site again, the cookie allows that site to recognize your browser. Cookies may store user preferences and other information. For more information, see Hyperproof's cookie policy.

The following required cookies are installed when you log in and use Hyperproof:

Table 1. Auth0 cookies

Name

Definition

Duration

auth0

Used to implement the Auth0 session layer.

1 day



Table 2. Google analytics cookies

Name

Definition

Duration

_ga

Used to distinguish users. Note that this Help Center also uses this cookie.

2 years

_ga_<container-id>

Used to persist session state. Note that this Help Center also uses this cookie.

2 years

_gid

Used for analytics.

24 hours



Table 3. Heap cookies

Name

Definition

Duration

_hp2_ses_props.APP_ID

Stores session properties, such as timestamp and cookie domain/path.

30 minutes

_hp2_props.APP_ID

Stores event properties set by the addEventProperties API.

13 months



Table 4. Hyperproof cookies

Name

Definition

Duration

hp_last_email_address

Used to auto-fill the user name on the login page and to help manage session data.

Session

hp-client-type

Used to help with routing.

Session



Table 5. Hyperproof TPRM cookies

Name

Definition

Duration

prodToken

Stores the authentication token for the logged-in user.

30 days



Table 6. Intercom cookies

Name

Definition

Duration

intercom-id-[app_id]

Anonymous visitor identifier cookie. As people visit Hyperproof site, they get this cookie.

9 months

intercom-session-[app_id]

Keeps track of sessions.

1 week

intercom-device-id-[app_id]

Unique device identifier.

9 months



Table 7. Merge cookies 

Name

Definition

Duration

mergelink_csrftoken

Security protection cookie to protect the site from various well-known attacks.

5 minutes

mergelink_oauth_allowed

Security protection cookie to protect the site from various well-known attacks.

1 minute



Table 8. Planhat cookies

Name

Definition

Duration

-plantrack

Stores user data to help track actions with Planhat analytics.

Session



Table 9. PostHog cookies

Name

Definition

Duration

PostHog - Uses only first-party cookies.

  • The same cookie works across subdomains (e.g., posthog.com and eu.posthog.com)

  • For full GDPR compliance guidance, review the GDPR compliance documentation

ph_<project_api_key>posthog 

Or

ph_ph<project_api_key>_posthog

Stores user identification and session information, including:

  • User's distinct ID

  • Session ID and device ID

  • Active and enabled feature flags

  • Super properties you've defined

  • PostHog configuration options (e.g., whether session recording is enabled)

365 days

_ph_opt_in_out_phc<project_api_key>

Stores the user's tracking consent state (whether they've opted in or out of tracking)

365 days

dmn_chk_<uuid>

Used temporarily during initialization to verify that cookies can be set on the domain.

Expires immediately



Table 10. Segment cookies

Name

Definition

Duration

ajs_anonymous_id

An anonymous ID generated by Analytics.js, is used for Segment calls.

This cookie doesn't have a listed lifespan. It is set to an immediate expiration since the value is set from session data each time the value is used.

Expires immediately

ajs_user_id

A user ID that can be specified by making an identify() call with Analytics.js.

This cookie doesn't have a listed lifespan. It is set to an immediate expiration since the value is set from session data each time the value is used.

Expires immediately



Table 11. Zendesk cookies

Name

Definition

Duration

__zlcmid

Stores a unique chat visitor ID.

365 days



In this section: