- Release Notes and Announcements
- User Tutorial
- Product Introduction
- Purchase Guide
- Free Demo
- SDK Download
- Integration (UI Included)
- TUIKit Overview
- Audio/Video Call
- Audio/Video Conference
- Interactive Live Audio Streaming
- Interactive Video Streaming
- Online Karaoke
- Integration (No UI)
- Advanced Features
- Relay to CDN
- Enabling Advanced Permission Control
- RTMP Streaming with TRTC
- Testing Hardware Devices
- Testing Network Quality
- On-Cloud Recording
- Custom Capturing and Rendering
- Custom Audio Capturing and Playback
- Sending and Receiving Messages
- Event Callbacks
- Content Moderation
- Access Management
- How to push stream to TRTC room with OBS WHIP
- Sample Code
- Client APIs
- Server APIs
- Console Guide
- FAQs
- Legacy Documentation
- Service Level Agreement
- TRTC Policy
- Glossary
- Release Notes and Announcements
- User Tutorial
- Product Introduction
- Purchase Guide
- Free Demo
- SDK Download
- Integration (UI Included)
- TUIKit Overview
- Audio/Video Call
- Audio/Video Conference
- Interactive Live Audio Streaming
- Interactive Video Streaming
- Online Karaoke
- Integration (No UI)
- Advanced Features
- Relay to CDN
- Enabling Advanced Permission Control
- RTMP Streaming with TRTC
- Testing Hardware Devices
- Testing Network Quality
- On-Cloud Recording
- Custom Capturing and Rendering
- Custom Audio Capturing and Playback
- Sending and Receiving Messages
- Event Callbacks
- Content Moderation
- Access Management
- How to push stream to TRTC room with OBS WHIP
- Sample Code
- Client APIs
- Server APIs
- Console Guide
- FAQs
- Legacy Documentation
- Service Level Agreement
- TRTC Policy
- Glossary
1. INTRODUCTION
This Module applies if you use the Tencent Real-Time Communication feature (“Feature”). This Module is incorporated into the privacy policy located at (“Privacy Policy"). Terms used but not defined in this Module shall have the meaning given to them in the Privacy Policy. In the event of any conflict between the Privacy Policy and this Module, this Module shall apply to the extent of the inconsistency.
2. CONTROLLERSHIP
The controller of the personal information described in this Module is as specified in the Privacy Policy.
3. AVAILABILITY
This Feature is available to users globally.
4. HOW WE USE PERSONAL INFORMATION
We will use the information in the following ways and in accordance with the following legal bases:
Personal Information | Use | Legal Basis |
Console Configuration Data: TRTC application ID, application name, whether recording is open, whether the bypass function is enabled or not, selected billing method | We use this information to determine your use of the Feature, for billing purposes. Please note that this data is stored in our Elasticsearch Service (ES) feature. | We process this information as it’s necessary for us to perform our contract with you to provide the Feature. |
Backend Log Data: User ID relating to any participants of the live streaming event, room number, client IP relating to any participants of the live streaming event, client SDK version, OS type relating to any participants of the live streaming event | We use this information to ensure the Feature functions as required, and for troubleshooting. Please note that this data is stored in our ES feature. | We process this information as it’s necessary for us to perform our contract with you to provide the Feature. |
Dashboard Information: Information about audio and video quality during calls: end user's APPID, data regarding functions controlled by the end-user (enable video, disable video, enable audio, disable audio), enter room, leave room, room ID, mute function, CPU usage, memory usage, network latency, packet loss, resolution, bitrate, frame rate, volume | We use this information to ensure the Feature functions as required, and for troubleshooting. Please note that this data is stored in our ES feature. | We process this information as it’s necessary for us to perform our contract with you to provide the Feature. |
SDK Log Data (of end user): User ID, room number, client SDK version number, OS type of the TRTC room | We use this information to ensure the Feature functions as required, and for troubleshooting. Please note that this data is stored in our ES feature. | We process this information as it’s necessary for us to perform our contract with you to provide the Feature. |
UIN | We use this information to identify your usage of the Feature. Please note that this data is stored in our ES feature. | We process this information as it’s necessary for us to perform our contract with you to provide the Feature. |
SDK APPID (created with your UIN for different applications) | We use this information to identify the usage of your applications as part of the Feature. Please note that this data is stored in our ES feature. | We process this information as it’s necessary for us to perform our contract with you to provide the Feature. |
Troubleshooting Data: End user's APPID, data regarding functions controlled by the end-user (enable video, disable video, enable audio, disable audio), enter room, leave room, mute function, room ID, CPU usage, memory usage, network latency, packet loss, resolution, bitrate, frame rate, volume | We use this information to detect and locate problems experienced by end users, for troubleshooting. Please note that this data is stored in our ES feature. | We process this information as it’s necessary for us to perform our contract with you to provide the Feature. |
5. HOW WE STORE AND SHARE PERSONAL INFORMATION
As specified in the Privacy Policy.
6. DATA RETENTION
We will retain personal information in accordance with the following:
Personal Information | Retention Policy |
Console Configuration Data | We retain such data for as long as you use the Feature. When your use of the Feature is terminated or when your account is deleted, we will delete this data within 7 days. |
Backend Log | Stored for 14 days. |
Dashboard Information | |
SDK Log Data | |
UIN | |
SDK APPID | |
Troubleshooting Data | |
Yes
No
Was this page helpful?