Why does opentok-network-test-js create a cookie during a network test?

opentok-network-test-js library has a dependency to opentok-solutions-logging, which creates a cookie during a network test.

This cookie stores a randomly generated unique ID (UUID), which can be used to identify reconnecting clients, which is needed for seamless operation of video calls. The UUID is the same that is visible in OpenTok Inspector tool as guid.

Since the UUID is randomly generated for each call, it does not contain personal information.

Vonage can identify only that the same client tries to reconnect to a session with this UUID, which is needed for operations. Vonage does never know who the user is. Other use of the cookie is only for support purposes and debugging calls with Inspector.

Below are the common questions asked about this cookie:

Is there PII data in the cookie? - No.

Does Vonage know the person behind the unique id? - No.

What is the cookie used for? - user reconnects, error logging, session inspector, support issues

Where is the information from the cookie transmitted and stored? - The unique id from the cookie is part of the non-personal information that is transferred to Vonage log servers in the EU or US (non-personal, operational machine data).

How long is the cookie stored? - In the browser, this depends on the user browser settings. In Vonage logs, up to 21 days.

Is the cookie information shared with third parties? - No.

Have more questions? Submit a request