The following statement is hereby made for this document:1. This document is intended to provide an overview of Tencent Cloud's security measures for Tencent Real-Time Communication (TRTC). It explains how to manage information and protect the security of your and end users' data. If you have any mandatory requirements, we recommend you enter into a service level agreement (SLA) with Tencent Cloud. Tencent Cloud disclaims any express or implied undertakings and warranties as to the content of this document.2. This document only involves "part of" the technical security features among the wide range of security features.3. This document is not intended as a reference document for national or industry-specific information security standards or requirements.4. This document has been adapted for readability. In the event of any ambiguity or inaccuracy, refer to Item 1.5. Tencent Cloud reserves the right to interpret this document.
Personal Information | Purpose | Legal Basis |
Data configured in the console: The TRTC application ID and name, whether recording and relayed push are enabled, and the selected billing mode | For billing purposes, we use this information to determine your usage of the corresponding feature. Note that such data is stored in our Elasticsearch Service (ES) feature. | We will process this information as necessary to make the corresponding feature available to you as part of our performance of the contract entered into with you. |
Backend log data: The user ID, room ID, client IP and SDK version, and OS type of any participants in live streaming events | We use this information to ensure that corresponding features run as required and to perform troubleshooting. Note that such data is stored in our ES feature. | We will process this information as necessary to make the corresponding feature available to you as part of our performance of the contract entered into with you. |
Dashboard information: Audio/Video quality information during call: The end user's APPID , data about the features controlled by the end user (enabling/disabling audio/video), room entry/exit, room ID, muting feature, CPU utilization, memory usage, network latency, data packet loss, resolution, bitrate, frame rate, and volume level | We use this information to ensure that corresponding features run as required and to perform troubleshooting. Note that such data is stored in our ES feature. | We will process this information as necessary to make the corresponding feature available to you as part of our performance of the contract entered into with you. |
SDK log data (of the end user): The user ID, room ID, client SDK version number, and the OS type of the TRTC room | We use this information to ensure that corresponding features run as required and to perform troubleshooting. Note that such data is stored in our ES feature. | We will process this information as necessary to make the corresponding feature available to you as part of our performance of the contract entered into with you. |
UIN | We use this information to determine your usage of the corresponding feature. Note that such data is stored in our ES feature. | We will process this information as necessary to make the corresponding feature available to you as part of our performance of the contract entered into with you. |
SDK APPID (created for different applications with your UIN) | As part of the corresponding feature, we use this information to determine the usage of your application. Note that such data is stored in our ES feature. | We will process this information as necessary to make the corresponding feature available to you as part of our performance of the contract entered into with you. |
Troubleshooting data: The end user's APPID , data about the features controlled by the end user (enabling/disabling audio and video), room entry/exit, room ID, CPU utilization, memory usage, network latency, data packet loss, resolution, bitrate, frame rate, and volume level | We use this information to detect and locate the issues encountered by the end user for troubleshooting. Note that such data is stored in our ES feature. | We will process this information as necessary to make the corresponding feature available to you as part of our performance of the contract entered into with you. |
Personal Information | Retention Policy |
Your temporary key information: The SDK APPID , username, and private key | We retain this data during your use of the corresponding feature. If your use of the feature is terminated or your account is deleted, we will delete this data within seven days. |
Application-related customer log data: The SDK APPID , application name, tag, service status, creation time, and operation | We retain this data during your use of the corresponding feature. If your use of the feature is terminated or your account is deleted, we will delete this data within seven days. |
Was this page helpful?