1. BACKGROUND
This Module applies if you use Database Audit (“Feature”). This Module is incorporated into the Data Privacy and Security Agreement located at https://www.tencentcloud.com/document/product/301/17347 (“DPSA”). Terms used but not defined in this Module shall have the meaning given to them in the DPSA. In the event of any conflict between the DPSA and this Module, this Module shall apply to the extent of the inconsistency.
2. PROCESSING
We will process the following data in connection with the Feature:
Personal Information | Use |
Configuration Data (audit policy set by you, the name of the audit policy, resource ID, resource name, region, resource configuration details, your Elasticsearch Service database password) | We only process this data for the purposes of providing the Feature to you in accordance to your specific configuration. Please note that this data is integrated with our TencentDB for MySQL, TencentDB for MongoDB, TDSQL-C features, and stored in our Elasticsearch Service feature. |
Audit Log Data (including SQL statement execution time, thread ID, details of rows, details of processing times, error code of failed SQL statement, audit rule number, client IP, instance name, instance ID, user name (whether created by you or random), database name, audit policy name, SQL statement and SQL statement type) | We only process this data for the purpose of providing the Feature to you, in order to record database operations. Please note that this data is received from target database features, and (other than instance ID) stored in our Elasticsearch Service feature. |
3. SERVICE REGION
As specified in the DPSA.
4. SUB-PROCESSORS
As specified in the DPSA.
5. DATA RETENTION
We will store personal data processed in connection with the Feature as follows:
Personal Information | Retention Policy |
Configuration Data Audit Log Data (other than instance ID, which is not stored) | We retain such data for your chosen data retention time limit. If you do not choose a data retention time limit, we will automatically delete such data 30 days after storage. If you request to delete such data before your data retention time limit has ended, such data will be deleted within 3 days after the deletion request is made. If this Feature is shut down, such data will be retained for 3 days before it is deleted. Where you do not renew service upon service expiration, such data will be automatically deleted 3 days after expiration. |
You can request deletion of such personal data in accordance with the DPSA.
6. SPECIAL CONDITIONS
You must ensure that this Feature is only used by end users who are of at least the minimum age at which an individual can consent to the processing of their personal data. This may be different depending on the jurisdiction in which an end user is located.
Yes
No
Was this page helpful?