Skip to main content

Data privacy in watchRTC

watchRTC collects WebRTC metrics and other relevant data points needed to understand connectivity and quality of experience of your application. Some of the information collected is considered PII (Personally Identifiable Information) - mainly IP addresses.

The information collected is only collected for the purpose of analyzing issues related to the operation of your application and is never shared with third parties. The collection and storage of such information by watchRTC is done using encryption at transiting and at rest: the data is sent to our watchRTC servers encrypted and is stored encrypted as well.

Information collected

watchRTC collects events and metrics relevant to troubleshooting WebRTC and communication related issues. These include:

  • Calls to WebRTC APIs
  • Periodic getStats() metrics
  • Optionally machine information
  • Optionally browser console logs
  • Any custom events and keys provided by the application

PII data is handled with the necessary sensitivity. You can read more about how identifiable information is collected and handled by watchRTC.

As a result, the data collected, once processed and stored, should not include any PII data or information that can later be used to identify the users.


Some things to note regarding storage:
  • Once data is collected, it gets stored by watchRTC as log files. The files get analyzed and the important data points needed for visualization and aggregation get stored into a database.
  • The files and the database are all encrypted at rest.
  • Assuming the application hasn’t passed any PII information of its own within custom keys and console logs, then no PII data will be stored anywhere in the watchRTC backend storage.

Was this article helpful?

0 out of 0 found this helpful