Modified on Wed, 07 Jun 2023 at 11:35 AM


Cookies in CUX

NameSupplierPurposeExpiry date
_cux_pv_ttlcux.ioTime to generate a unique page view identifierSession
_cux_refcux.ioAddress of the traffic referrerSession
_cux_scux.ioUnique session keySession
_cux_ucux.ioUnique user IDPersistent
_cux_vcux.ioUnique visit IDPersistent
_cux_v_ttlcux.ioTime of generating the unique ID of the visitPersistent
_cux_ecux.ioUnique key to exclude the visit from the analysisPersistent
_cux_e_ttlcux.ioTime of generating the visit exclusion key from the analysisPersistent
_cux_lridcux.ioID of the visit key sent to Google AnalyticsPersistent
_cux_ncux.ioUnique key to connect to cux.ioPersistent
_cux_n_ttlcux.ioTime to generate a unique connection keyPersistent
_cux_prcux.ioA unique key to help calculate the page refresh rateSession
_cux_pvcux.ioUnique ID of the page viewSession

Expiry date:

  • Session – until the browser is closed.
  • Persistent – until the cookies history is cleared.

Scope of collected data

For the purposes of the Service, CUX will collect the following information from the browser of the user visiting the Project website, limiting only to the information that the browser makes available to the executed scripts with the user's consent:

  • Device information such as:
    • type (desktop, tablet, mobile, etc),
    • operating system name and version,
    • device manufacturer,
    • screen resolution,
    • screen orientation,
    • IP addressing pool with anonymized non-identifying part (a full IP address is not stored anywhere on the CUX side).
  • Browser information such as:
    • producer,
    • version,
    • viewport,
    • preferred language.
  • Cursor or pointer-related events, such as:
    • click coordinates,
    • cursor movement vector coordinates,
    • xPath of the clicked item,
    • event time.
  • Keyboard-related events such as:
    • type of button pressed without its exact value,
    • event time.
  • Page referring traffic to the Project.
  • Address and time of the view.
  • A number of Project tabs open at the same time.
  • Screenshot of the page preview in text form with automatically anonymized form fields.
  • Screenshot of a preview of dynamic page layout changes in text form with automatically anonymized form fields.

CUX uses localStorage and sessionStorage to store identifiers for combining page views into a single string representing the user's visit. Identifiers are generated on the basis of random strings of characters and do not contain any data allowing the user to be identified.

CUX reserves the right to extend the scope of collected data after informing the Customer at least 7 days in advance.

Visit Recordings

CUX does not record the user's screen but only downloads the HTML code (page preview) that is currently in the user's browser. Then it serializes the code by removing all information from the forms and sends this code back to the CUX servers via an encrypted protocol.

The HTML code is downloaded only from those tabs in the user's browser on which the CUX tracking snippet is implemented. This means that we cannot track other websites that a user is viewing.

Replaying the recording consists in sending a preview CUX snippet inside the application and applying the downloaded HTML code in order to recreate the user's view as credibly as possible. Playing back the “recording” may cause slight distortions or shifts in the view (e.g. lack of appropriate fonts), because it is not a literal recording.

Recording sensitive data, forms & inputs

CUX automatically masks all pages that contain forms and form fields.

In addition, the CUX user has the option of:

  • defining by classy name any element in the system in which the data should be masked,
  • defining xPaths for elements that are to have masked content by configuring the project within the app,
  • use Mock-up Mode (enterprise feature).

The masking process (meaning replacing text with asterisks) takes place at the stage of the user's visit, before sending this data to CUX servers.

Disabling recording

The disabling recording is possible by removing/blocking the CUX tracking snippet for a specific page/service/user.

This can be done, for example, by blocking the tracking of selected segments of users or parts of the website in Google Tag Manager.

Managing your billing

Manage invoice details:

  1. Log in to your CUX account.
  2. Go to Account>Organization.
  3. Select “Edit Details”.

Manage subscription details:

  1. Log in to your CUX account.
  2. Go to Settings>Subscription.
  3. Select “Edit Subscription”.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article