Why does opentok-network-test-js create a cookie during a network test?
Why does the opentok-network-test-js create a cookie during a network test?
- Network Test
The 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 Vonage Video 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.
There is no PII data in the cookie. The cookie is used to identify user reconnects, error logging, session inspector, and support issues. 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 the cookie is stored depends on the user browser settings. In Vonage logs, it is stored up to 21 days. This information is not shared with third parties.
Article is closed for comments.