- Release Notes
- Product Introduction
- Purchase Guide
- Getting Started
- Console Guide
- Practical Tutorial
- SDK Documentation
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- User APIs
- Application Management APIs
- CreateApplication
- CreateApplicationSnapshot
- CreateApplicationVersion
- DeleteApplication
- DeleteApplicationVersion
- DescribeApplicationList
- DescribeApplicationPathList
- DescribeApplicationStatus
- DescribeApplicationVersion
- DescribeCosCredential
- ModifyApplicationBaseInfo
- ModifyApplicationVersion
- SetApplicationVersionOnline
- DescribeApplicationFileInfo
- ModifyMobileApplicationInfo
- Project Management APIs
- Concurrency Management APIs
- Stream Push Service APIs
- Data Types
- Error Codes
- FAQs
- Service Level Agreement
- CAR Policy
- Contact Us
- Release Notes
- Product Introduction
- Purchase Guide
- Getting Started
- Console Guide
- Practical Tutorial
- SDK Documentation
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- User APIs
- Application Management APIs
- CreateApplication
- CreateApplicationSnapshot
- CreateApplicationVersion
- DeleteApplication
- DeleteApplicationVersion
- DescribeApplicationList
- DescribeApplicationPathList
- DescribeApplicationStatus
- DescribeApplicationVersion
- DescribeCosCredential
- ModifyApplicationBaseInfo
- ModifyApplicationVersion
- SetApplicationVersionOnline
- DescribeApplicationFileInfo
- ModifyMobileApplicationInfo
- Project Management APIs
- Concurrency Management APIs
- Stream Push Service APIs
- Data Types
- Error Codes
- FAQs
- Service Level Agreement
- CAR Policy
- Contact Us
1. INTRODUCTION
This Module applies if you use the Cloud Application Rendering 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 |
Operation and Maintenance Data: AppID, request time, your IP, accessed domain name, URL, node IP, ConcurrentRegion, connect_fd | We use this information to ensure the Feature functions as required, and to analyze the reasons for errors or failures and troubleshoot such problems. Please note this data is stored and backed up in our TencentDB for MongoDB feature. | We process this information as it is necessary for us to perform our contract with you to provide the Feature. |
WebRTC Operation Log Data (when your end user accesses the Feature’s SDK): request ID, device ID, SDK version, platform (H5, Android, iOS), browser, SDK build time, SDK commit hash, APPID, package name, concurrency instance's details (cpu chip name, cpu platform, cpu core, memory (GB)), end user’s device brand, end user’s device model, application ID, server IP, server version, region, instance type, audio packet lost/received/sent, fps (frame rate), delay, render frame rate, receive frame rate, decoded frame rate, target delay, decode ms, max decode ms, render delay ms, min playout delay ms, first frame to decoded ms, interframe delay max ms, stun ping request and response, nack, cpu, gpu, jitter buffer, input delay, round trip time (rtt), raw rtt, freeze count, freeze duration, frame decoded, frame dropped, frame received, picture lost count, full intra skip count, network type, network operator, remote sdp failed, local sdp failed, played time, disconnection, reconnection, application start, application stop, foreground change, first video packet received, first audio packet received, load cost time, first frame | We use this information to ensure the Feature functions as required, and to analyze the reasons for errors or failures and troubleshoot such problems. Please note this data is stored and backed up in our TencentDB for MongoDB feature. Additionally, this data is stored in the concurrency instance of our Cloud Virtual Machine (“CVM”) feature until the end user ceases access to the Feature’s SDK or the access period expires (whichever is earlier). | We process this information as it is necessary for us to perform our contract with you to provide the Feature. |
SDK Log Data: end user ID, application ID, end user IP address | We use this information to ensure the Feature functions as required, and to analyze the reasons for errors or failures and troubleshoot such problems. Please note this data is stored and backed up in our TencentDB for MongoDB feature. Additionally, this data is stored in the concurrency instance of our CVM feature until the end user ceases access to the Feature’s SDK or the access period expires (whichever is earlier). | We process this information as it is necessary for us to perform our contract with you to provide the Feature. |
Operating Data: AppID, application ID, application name, application status, application type, application configuration information, project ID, create time, concurrent ID, concurrent type, concurrent region, concurrent status, UIN, billing status | We use this information for internal statistical purposes to improve and administer our Feature, and for troubleshooting. Please note this information is stored and backed up in our TencentDB for MongoDB feature. | We process this information as it is necessary for us to perform our contract with you to provide the Feature. |
Billing Data: monthly bill amounts | We use this information to calculate usage and billing for the Feature. Please note this information is stored and backed up in our TencentDB for MongoDB feature. | We process this information as it is 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, including Aceville Pte Ltd.. Additionally, your AppID and UIN will be stored and backed up in our TencentDB for MongoDB feature.
6. DATA RETENTION
We will retain personal information in accordance with the following:
Personal Information | Retention Policy |
Operation and Maintenance Data | Stored until you remove this data from the Feature or you terminate your use of the Feature (whichever is earlier). |
WebRTC Operation Log Data | Stored by us for 15 days after (a) your end user ceases access to the Feature’s SDK or (b) the access period expires (whichever is earlier).Additionally, stored in the concurrency instance of CVM feature until your end user ceases access to the Feature’s SDK or the access period expires (whichever is earlier). |
SDK Log Data | |
Operating Data | Stored until you manually delete this data from the Feature or you terminate your use of the Feature (whichever is earlier). |
Billing Data | Stored for 12 months following the date that you terminate your use of the Feature. |
Yes
No
Was this page helpful?