Data Collection

LiveSwitch Cloud collects usage data for billing purposes as well as for providing real-time monitoring and historical information on the LiveSwitch Cloud Console. This data is encrypted and stored on services managed by LiveSwitch. LiveSwitch Cloud does not store any audio/video data unless recording is explicitly enabled, nor do we store any messages sent on the channels. This minimizes the risk of any possible data exposure to our customers.

For data elements we do capture, the only one that is not under the control of the developer is the end user’s IP address. WebRTC requires knowledge of the source IP address of the connecting client, therefore we must collect this information. We also use this information to identify the region the client is connecting from to display on the Unique IPs by Location graph. We do not sell or use this information in any way outside the scope of LiveSwitch Cloud itself.

Developers on LiveSwitch Cloud have some responsibilities when it comes to personal identifiable information (PII) as well. While LiveSwitch Cloud stores everything in an encrypted fashion, to be compliant with local regulations, you may need to anonymize certain parts of the information that is sent to LiveSwitch Cloud when you are building your application.

Here are the events that we capture and store:

• Client Registered
• Client Unregistered
• Client Updated
• Client Joined Channel
• Client Left Channel
• Channel Activated
• Channel Deactivated
• Channel RTMP Started
• Channel RTMP Stopped
• Connection Initializing
• Connection Connecting
• Connection Connected
• Connection Closing
• Connection Failing
• Connection Closed
• Connection Failed
• Connection Updated
• Connection Stats

Here are the data elements in these events that are available to developers using the LiveSwitch Cloud SDK or on the LiveSwitch Cloud Console which may potentially need to be anonymized by the developer using the LiveSwitch SDK if, for some reason, they need to include PII in them:

• Client Properties
  • user_id
  • user_alias
  • device_id
  • device_alias
  • external_id
  • tag
  • roles
  • region
• Channel Properties
  • id
  • tag
• Connection Properties
  • tag

Numerous mechanisms can be used by developers on LiveSwitch Cloud to anonymize this data, from UUIDs to encryption, the exact method is up to the developer of the application, provided they require such steps to be taken.

Also, please note that most data is not PII and, therefore, does not matter as far as all the above comments are concerned. Typical use cases for tags, for example, would be information on meeting state, which is not PII. Just be careful that you don’t use, for example, a channel name like “/my-cancer-doctor/my-full-name”.