- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Connection Guide
- API Documentation
- FAQs
- Service Protocol
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Connection Guide
- API Documentation
- FAQs
- Service Protocol
Terminal Performance Monitoring Privacy Policy
Last updated: 2024-12-03 18:35:34
1.INTRODUCTION
This Module applies if you use Terminal Performance Monitoring (“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:
Personal Information | Use | Legal Basis |
Metric Monitoring and Trace Data: Data relating to the resources or system being monitored by the Feature (such as monitoring object name, collection time, reporting time, filtering dimensions, metric information) Trace data about operations within the Feature (such as start and end times of trace segments, category of monitoring task, filtering dimensions, stages and progress of the operation, return value or state, name of the resources or system where trace is being performed, auto-increment ID, internal ID of the application instance, additional annotations) | We use this information for the purpose of troubleshooting, and to locate and solve problems. Please note that this data is integrated with our Tencent Cloud Virtual Machine (CVM), Tencent Kubernetes Engine (TKE) and Tencent Cloud TCHouse-C (ClickHouse) features for this purpose, and stored in our TencentDB for MySQL (MySQL) and ClickHouse features. | We process this information as it is necessary for us to perform our contract with you to provide the Feature. |
Feature Account, Configuration and Resource Data: Your Feature account data and user data (such as your auto-increment ID, account ID in the database, account/user key and type, primary account ID, APPID, creation time, update time and login time, username, company name, phone number, email address) Your configuration data (such as your auto-increment configuration ID, internal application instance ID, region configuration and country configuration mapping information, reporting configuration information, UIN) Your resources and business system information (such as auto-increment resource ID, resource name, charge type and status, instance status, resource description, data retention period, region configuration ID, cluster ID, owner account ID, creation and update time, APPID, various timestamps, purchase channel, resource region, instance type) Mapping data between various resource identifiers and application instances (such as your resource and sub-resource ID, internal application instance ID, business system name, resource type, remarks, internal application instance key, account ID, creation time, application instance status, and deletion status) Reported user and device whitelist data (such as your auto-increment ID, device ID, internal application instance ID) Traffic control data (such as auto-increment ID, module, internal application instance ID, plugin, SDK version, traffic control amount, enable status, modify time, sample rate) | We use this information to administer the Feature, and manage and maintain the normal operation of the Feature. Please note that this data is integrated with our CVM, TKE and TencentDB for Redis (Redis) features for this purpose, and stored in our MySQL and Redis features. | We process this information as it is necessary for us to perform our contract with you to provide the Feature. |
Order Data and Scheduled Traffic Data: Order data (such as your auto-increment order ID, product information and labels, order ID and number, payment mode, billing region and zone, auto-renewal setting, account ID, APPID, timestamps, resource ID (business system ID)) Scheduled traffic data (such as your auto-increment ID, resource ID, report count (traffic quantity), creation time, APPID) | We use this information to calculate usage and billing for the Feature. Please note that this data is integrated with our CVM and TKE features for this purpose, and stored in our MySQL features. | 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.
6.DATA RETENTION
We will retain personal information in accordance with the following:
Personal Information | Retention Policy |
Metric Monitoring and Trace Data | Stored for 7 days. |
Feature Account, Configuration and Resource Data | We retain such data until you terminate your use of the Feature or otherwise terminate or delete your account, in which case we will delete this data within 7 days thereafter. |
Order Data and Scheduled Traffic Data | We retain such data until you terminate your use of the Feature or otherwise terminate or delete your account, in which case we will delete this data within 7 days thereafter. |
Yes
No
Was this page helpful?