IoT Hub
- Release Notes and Announcements
- Product Introduction
- Getting Started
- Scenario 1: Device Interconnection
- Scenario 2: Device Status Reporting and Setting
- Console Guide
- Product Management
- Rule Engine
- Sub-account Access to IoT Hub
- Developer Manual
- Device Authentication
- Device Connection Protocol
- MQTT-Based Device Connection
- Gateway Subdevice
- Message Communication
- Device Shadow
- Device Connection Manual
- Connection Based on SDK for C
- SDK for C Cross-Platform Porting
- Connection Based on SDK for Android
- Connection Based on SDK for Java
- Connection Based on SDK for Python
- API Documentation
- Making API Requests
- CA Certificate APIs
- Device APIs
- Product APIs
- Device Shadow APIs
- IoT Hub Policy
Data Privacy And Security Agreement
Last updated: 2022-03-08 11:47:26
1.BACKGROUND
This Module applies if you use IoT Hub (“Feature”). This Module is incorporated into the Data Privacy and Security Agreement located at (“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 |
Log Data:device log (if you enable collection of this data) | We only process this data according to your configuration to facilitate debugging or troubleshooting by you.Please note that this data is stored and backed up with our Elasticsearch Service feature. Additionally, you may also use our Cloud Log Dump feature to store and analyze the data. |
Configuration Data: settings of products (product name, product ID), devices (device name, device key/certificate) and rules (SQL statement) | We only process this data to facilitate product and/or device identification and management by you.Please note that this data is stored and backed up with our TencentDB for MySQL feature. |
Monitoring Data: statistics of online devices, device messages, device shadows, rule engine and firmware | We only process this data to provide you with statistics of your use of the Feature.Please note that this data is stored with and managed by our Cloud Monitor feature. This data is backed up with our TencentDB for MySQL feature. |
Resource Data:resources related to platforms and devices uploaded by you (if you include personal data in such resources) | We only process this data to enable you to provide such data to your end users.Please note that this data is stored and backed up with our Cloud Object Storage feature. |
Published Device Data: type of device, state of device, rules and commands for controlling the device by SQL statement | We only process this data for device verification and message forwarding as instructed by you.Please note that we have no access to this data. This data is transferred to other service(s) as instructed by you. |
Subscriber Device Data :device command message | We only process this data to facilitate control of device(s) by your end users.Please note that we have no access to this data. This data is transferred to other service(s) as instructed by you. |
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 |
Log Data | Stored for 7 days with our Elasticsearch Service feature.Additionally, you may also store the data with our Cloud Log Dump feature for a period determined by you. |
Configuration Data | Stored until you request for account deletion, upon which such data will be deleted within 30 days. Where you do not request for deletion, such data will be deleted within 30 days of the earlier of the date that overdue amounts become payable on your account, termination of your use of this Feature, or shutdown of this Feature. |
Resource Data | Stored until you request for account deletion, upon which such data will be deleted within 30 days. Where you do not request for deletion, such data will be deleted within 30 days of the earlier of the date that overdue amounts become payable on your account, termination of your use of this Feature, expiration of your Feature subscription, or shutdown of this Feature. |
Monitoring Data | Stored for 7 days. |
Published Device Data | Not stored. |
Subscriber Device Data | Not stored. |
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.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No