- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- FAQs
- Overview
- Permissions
- Pod Startup Fails Because the Envoy Sidecar Is Unready
- Envoy Status Code 431 "Request Header Fields Too Large" Is Returned
- Envoy Converts Headers to Lowercase
- Headless Service-related FAQs
- Istio-init Crashes
- VirtualService Does Not Take Effect
- Inappropriate VirtualService Route Matching Order
- Failed to Access an Ingress Gateway from the Public Network
- Parsing Fails After Smart DNS Is Enabled
- Locality Load Balancing Does Not Take Effect
- Client Status Code 426 "Upgrade Required" Is Returned
- Sidecars Are Not Automatically Injected
- Circuit Breaking Does Not Take Effect
- 404 Is Returned During Access to a StatefulSet's Pod IP Address
- Service Is Abnormal Due to a Retry Policy
- Incomplete Call Tracing Information
- TCM Policy
- Glossary
- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- FAQs
- Overview
- Permissions
- Pod Startup Fails Because the Envoy Sidecar Is Unready
- Envoy Status Code 431 "Request Header Fields Too Large" Is Returned
- Envoy Converts Headers to Lowercase
- Headless Service-related FAQs
- Istio-init Crashes
- VirtualService Does Not Take Effect
- Inappropriate VirtualService Route Matching Order
- Failed to Access an Ingress Gateway from the Public Network
- Parsing Fails After Smart DNS Is Enabled
- Locality Load Balancing Does Not Take Effect
- Client Status Code 426 "Upgrade Required" Is Returned
- Sidecars Are Not Automatically Injected
- Circuit Breaking Does Not Take Effect
- 404 Is Returned During Access to a StatefulSet's Pod IP Address
- Service Is Abnormal Due to a Retry Policy
- Incomplete Call Tracing Information
- TCM Policy
- Glossary
1.INTRODUCTION
This Module applies if you use the Tencent Cloud Mesh 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 |
Administrative Data (mesh basic information): UIN, APPID, mesh version, mesh status, mesh configuration information and Tencent Cloud TAG | We use this information for the purpose of providing this Feature to you, including to provide you with the basic information of your mesh. | 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.
6.DATA RETENTION
We will retain personal information in accordance with the following:
Personal Information | Retention Policy |
Administrative Data | We retain such data until you terminate the service of the Feature, upon which all data will be automatically and immediately deleted. |
Yes
No
Was this page helpful?