Third Party SDK Service Agreement
1. Third-party information sharing list
I. Third-party voice services
Purpose of use: Support voice control of the device through third-party speakers.
Baidu (Xiaodu)
Name of third-party entity: Beijing Baidu Netcom Technology Co., Ltd.
Information collection details: device unique identifier (device_id), category, device name, device model name, device manufacturer name
Ali (Tmall Elf)
Name of third party: Zhejiang Maojing Artificial Intelligence Technology Co., Ltd.
Information collection details: device unique identifier (device_id), category, device name, device model name, device manufacturer name, product icon, device location (optional, no value is currently passed)
Xiaomi (Xiaoai)
Name of third party: Xiaomi Communication Technology Co., Ltd.
Information collection details: device unique identifier (device_id), category, device name
JD.com (Ding Dong)
Name of third-party entity: Beijing Linglong Technology Co., Ltd.
Information collection details: device unique identifier (device_id), category, device name
Privacy Policy (API docking) address:https://open.linglongtech.com/openweb/docs/index
Tencent (Cloud Xiaowei)
Name of third-party entity: Shenzhen Tencent Computer Systems Co., Ltd.
Information collection details: device unique identifier (device_id), category, device name, device model name, device manufacturer name, device version number
Privacy Policy Address:https://dingdang.qq.com/doc/page/440
JD.com (Little Jingyu)
Name of third-party entity: Beijing Jingdong Sanbailu Shidu E-Commerce Co., Ltd.
Information collection details: device unique identifier (device_id), category, device name, device model name, device manufacturer name, device version number
Privacy policy address (product docking):https://iot.jdcloud.com/Docs/skillManager#tianxiejibenxinxi
Spichi
Name of third party: Suzhou Spichi Information Technology Co., Ltd.
Information collection details: device unique identifier (device_id), voice information, device location information
Ruoqi (Ruoqi)
Name of third party: Taro Technology (Hangzhou) Co., Ltd.
Information collection details: device unique identifier (device_id), category, device name, device manufacturer name
Amazon Alexa
Name of the entity: Amazon.com
Data collection details: device id, product category, device name, device model name, name of device manufacturer, device version
Google Assistant
Name of entity: Google Group
Data collection details: device id, product category, device name, device model name, name of device manufacturer, device version
GiGA Genie
Name of entity: KT(Korea)
Data collection details: device id, product category, device name, device model name, name of device manufacturer, device version
SmartThings
Name of entity: Samsung Electronics Co., Ltd.
Data collection details: device id, product category, device name, device model name, name of device manufacturer, device version
HomeAssistant
Developer: Home Assistant Core Team and Community
Data collection details: device id, product category, device name, product icon to relevant device
ii. Cloud service provider
Alibaba cloud service
Name of third-party entity: Alibaba Cloud Computing Co., Ltd.
Purpose of use: Provide infrastructure forQT App, including network, server and virtualization services
Type of function: website hosting, data analysis, payment and credit card processing, infrastructure provision, IT services, customer support services, email delivery services and other similar services
Information collection details: All information will be stored on Alibaba Cloud. For details, please check the
AWS cloud service
Name of third-party entity: Amazon Web Services, Inc.
Purpose of use: Provide infrastructure forQT App, including network, server and virtualization services
Type of function: website hosting, data analysis, payment and credit card processing, infrastructure provision, IT services, customer support services, email delivery services and other similar services
Information collection details: All information will be stored on AWS Cloud. For details, please check thePrivacy Policy Address:https://aws.amazon.com/compliance/data-privacy/
Azure cloud service
Name of third-party entity: Microsoft Azure
Purpose of use: Provide infrastructure forQT App, including network, server and virtualization services
Type of function: website hosting, data analysis, payment and credit card processing, infrastructure provision, IT services, customer support services, email delivery services and other similar services
Information collection details: All information will be stored on Azure Cloud. For details, please check thePrivacy Policy Address:https://privacy.microsoft.com/privacystatement
iii.Software service provider
Software development services support
Name of third party: Hangzhou Tuya Information Technology Co., Ltd.
Purpose of use: To provide software development services, technical support, data analysis, customer support services, email sending services and other similar services
Function type: software development services, technical support
Information collection details:
· Account system: Account or profile data: such as user email address, phone number, username and login credentials, nickname, avatar, country code, language preference and time zone information;
· Feedback function: This may include user email address, mobile phone number and feedback content.
· Family system: When creating or using home devices, customized user family name, device name, device ID, and device location information;
· Device related: Device information includes the device's MAC address, IP address, wireless connection information, operating system type and version, application version number, push notification identifier, log file and mobile network information, and device location information;
· Log data: SDK performance data, such as MQTT connection rate, Socket connection rate and other desensitized business data.
iv. Health indicator partners
apple health
Third-party entity name: Apple (China) Co., Ltd.
Purpose of use: Users choose to synchronize health data to Apple Health so that users can have more health management software choices to achieve unified management of personal health.
Function type: Health data three-party synchronization service
Information collection details: height, weight, body fat percentage, bmi
Apple Health
Name of entity: Apple Inc.;
Purpose of processing: Users may proactively consent to synchronize health data to Apple Health, so that users can use more health management services and manage/check health related data;
Function: synchronize service to Apple Health;
Data collection details: height, weight, body fat rate, BMI;
GoogleFit
Name of entity: Google Group.;
Purpose of processing: Users may proactively consent to synchronize health data to GoogleFit, so that users can use more health management services and manage/check health related data;
Function:  synchronize service to GoogleFit;
Fitbit
Third party entity name: Fitbit LLC
Purpose of use: Users choose to synchronize health data to Fitbit so that users can provide more health management software choices to achieve unified management of personal health.
Function type: Health data three-party synchronization service
Information collection details: weight, body fat percentage
Fitbit
Name of entity: Fitbit LLC.;
Purpose of processing: Users may proactively consent to synchronize health data to Fitbit, so that users can use more health management services and manage/check health related data;
Function: synchronize service to Fitbit;
Data collection details: weight and body fat rate;
Strava
Third party entity name: Strava, Inc.
Purpose of use: Synchronize movement records to Strava, and be able to see the movement data generated by the Tuya device on Strava
Function type: Three-party synchronization service of sports data
Information collection details: steps, calories, exercise records
Strava
Name of entity: Strava, Inc.
Purpose of processing: Users may proactively consent to synchronize health data to Strava, so that users can use more health management services and manage/check health related data;
Function: synchronize service to Strava;
Data collection details: steps, calories, record of sports;
v. Third-party payment
Alipay payment
Third-party entity: Alipay (China) Network Technology Co., Ltd.
Purpose of use: Provide payment functions, and sensor information is used to generate device fingerprints to ensure user payment security.
Function type: payment
Information Collection Details: Rotation Vector Sensor Information
WeChat Pay
Third-party entity: Shenzhen Tencent Computer Systems Co., Ltd.
Purpose of use: Provide payment function
Function type: payment
Information collection details: None
2. App third-party SDK service list
In order to ensure the stable operation of QT App services or implement related functions, we may access software development kits (sdk) provided by third parties to ensure the sustainable development and maintenance of the products and services we provide to you. We will conduct strict security testing on the software tool development kits (sdk) used by authorized partners to obtain relevant information. You can learn how third parties will handle your personal information through the relevant information listed in this list. We will also strictly restrict the behavior of third parties in obtaining personal information to protect the security of your personal information.
The third-party SDK we access is mainly used for the services you request. When you do not use the relevant functions or services, the third party cannot obtain your information. When meeting new service requirements and changes in business functions, we may adjust the third-party SDKs we access. We will promptly disclose to you the latest status of accessing third-party SDKs in this description.
The situation of Tuya connecting to third-party SDK is as follows:
QQ LOGIN SDK
Third-party entity: Shenzhen Tencent Computer Systems Co., Ltd.
Purpose of use: Log in with QQ account
Usage scenario: when logging in
Information collection details: Device information: device model, operating system version, unique device identifier, battery, signal strength information, IP address; software information: software version number, browser type. To ensure the security of the operating environment or to provide services, we will collect information about the mobile applications and other software you use; location information: obtain your geographical location information through IP address, GPS, WLAN (Wi Fi) or base station.
Wechat login sdk
Third-party entity: Shenzhen Tencent Computer Systems Co., Ltd.
Purpose of use: Log in using WeChat account
Usage scenario: when logging in
Information collection details: Device information: device model, operating system, unique device identifier (referring to a string of characters programmed into the device by the device manufacturer, which can be used to uniquely identify the corresponding device), login IP address, access Network mode, type and status, network quality data, device accelerator (gravity sensing device); software information: WeChat software version number, operation log, service log information
China Mobile one-click login sdk
Third-party entity: China Mobile Internet Co., Ltd.
Purpose of use: Automatically read mobile phone number and log in with one click
Usage scenario: when logging in
Information collection details: Network type: performance analysis, divided into three situations: data traffic only, Wi Fi only, and data traffic + Wi Fi; analyze the impact of different network environments on the success rate and delay of number retrieval, and perform targeted optimization; network standard : Performance analysis, divided into three situations: 2G, 3G, and 4G; analyze the impact of different network environments on the success rate and delay of number retrieval, and carry out targeted optimization; equipment type and system: performance analysis, collection model and system Information for model adaptation and optimization; idfv (i OS only): used for problem location
QQ Sharing SDK
Third-party entity: Shenzhen Tencent Computer Systems Co., Ltd.
Purpose of use: Use qq to send family invitations
Usage scenario: When adding family members
Information collection details: mobile device information, IP address
WeChat share sdk
Third-party entity: Shenzhen Tencent Computer Systems Co., Ltd.
Purpose of use: Use WeChat to send family invitations
Usage scenario: When adding family members
Information collection details: mobile device information, IP address
Xiaomi pushes sdk (android)
Third-party entity: Beijing Xiaomi Mobile Software Co., Ltd.
Purpose of use: push messages to the mobile phone system notification bar
Usage scenario: When receiving alarm, family, and notification messages in the message center
Information collection details: your OAID (applicable to Android Q and above systems), MEIDMD5, Android ID, VAID, AAID, as well as your MID (applicable to MIUI system), device model information.
Huawei pushes sdk (android)
Third-party entity: Huawei Terminal Co., Ltd.
Purpose of use: push messages to the mobile phone system notification bar
Usage scenario: When receiving alarm, family, and notification messages in the message center
Information collection details: your ID, application ID, application package name, server public IP address. If you create a message push task on the App Gallery Connect website, we will collect information about the frequency of use of each Huawei push function, task name, message content, and push scope (application token, or topic name, or audience group name)
OPPO push SDK(Android)
Third-party entity: OPPO Guangdong Mobile Communications Co., Ltd.
Purpose of use: push messages to the mobile phone system notification bar
Usage scenario: When receiving alarm, family, and notification messages in the message center
Information collection details: your device related information (Serial Number, User ID, Android ID, Google Advertising ID, mobile phone Region settings, device model, mobile phone battery, mobile phone operating system version and language), application information using push services (APP package name and version number, running status), push SDK version number, network-related information (IP or domain name connection results, current network type), message sending results, notification bar status (notification bar permissions, user click behavior), lock screen status ( Whether to lock the screen, whether to allow the screen to be locked)
VIVO push SDK(Android)
Third-party entity: Vivo Mobile Communications Co., Ltd.
Purpose of use: push messages to the mobile phone system notification bar
Usage scenario: When receiving alarm, family, and notification messages in the message center
Information collection details: Device and application information: including operating system version number, application information, device identifier (SIM, mobile country code and mobile network number of vivo Android device), mobile operator when you use vivo devices and services , Usage Language, System Settings System, Device and Application Data
Amap SDK
Third-party entity: AutoNavi Software Co., Ltd.
Purpose of use: In order to provide corresponding services, provide you with problem tracking, troubleshooting, diagnosis services and perform data statistics to ensure the normal operation of products and services, AutoNavi will process your device information, including location information (latitude and longitude, precise location, rough location); including processing device information through technology [such as IP address, GNSS information, Wi Fi status, Wi Fi parameters, Wi Fi list, SSID, BSSID, base station information, Wi Fi signal strength information, Bluetooth information, sensor information ( vector, acceleration, pressure), device signal strength information, external storage directory] for positioning; device identification information (IDFA, OAID), current application information (application name, application version number), device parameters and system information (system properties, device Model, operating system, operator information), based on different devices and systems (Android/i OS) and system versions, the device information collected will be different. In particular, when you use the following AutoNavi SDK related functions and services, the device information collected will be different. For details, please check the contents of the positioning SDK, map SDK, search SDK and navigation SDK.
Usage scenarios: intelligent scenarios based on location changes, weather services based on location information
Locate sdk
Detailed information collection:
· Location information: The purpose of use is to return user location information to the application, and for developers to provide corresponding services based on the user's location information; in order to facilitate the provision of real-time traffic conditions and traffic prediction services, we will perform data statistics and analysis on the user's location information. And based on this, the traffic congestion situation is judged.
· Collect device information: The purpose of use is to provide services, track, troubleshoot, diagnose, and collect statistics on various problems in services, and ensure the normal operation of products and services. Device information [such as IP address, GNSS information, Wi Fi status, Wi Fi parameters, Wi Fi list, base station information, signal strength information, Bluetooth information, sensor information (vector, acceleration, pressure), device signal strength information].
· Collect device identification information: The purpose of use is to provide positioning service accuracy and success rate, track, troubleshoot, diagnose, and collect statistics on various problems in the service, and ensure the safe and normal operation of products and services. Device identification information (IDFA, OAID), current application information (application name, application version number), device parameters and system information (system attributes, device model, operating system, operator information)
map sdk
Detailed information collection:
· Location information: The purpose of use is to return the user's location information to the application when the developer turns on the positioning small blue dot function, display the user's location on the map, and provide the developer with corresponding services based on the user's location information.
· Collect device information: The purpose of use is to provide services, track, troubleshoot, diagnose, and collect statistics on various problems in services, and ensure the normal operation of products and services. Device information [such as IP address, GNSS information, Wi Fi status, Wi Fi parameters, Wi Fi list, base station information, signal strength information, Bluetooth information, sensor information (vector, acceleration, pressure), device signal strength information, external storage Table of contents】.
· Collect device identification information: The purpose of use is to provide positioning service accuracy and success rate, track, troubleshoot, diagnose, and collect statistics on various problems in the service, and ensure the safe and normal operation of products and services. Device identification information (IDFA, OAID), current application information (application name, application version number), device parameters and system information (system attributes, device model, operating system, operator information)
Search SDK
Detailed information collection:
· Mobile device information: The purpose of use is to provide services, track, troubleshoot, diagnose, and collect statistics on various problems in services, and ensure the normal operation of products and services.
Privacy Policy Address:https://lbs.amap.com/pages/privacy/
Shangyun P2P SDK
Third-party entity: Shenzhen Shangyun Internet Technology Co., Ltd.
Purpose of use: To realize the video preview function of IPC equipment
Usage scenario: When connecting to an IPC device to use the preview function
Shared information: camera device ID, network information (IP, current network type and name)
Sharing method: SDK local collection, background interface transmission
Information collection details: No personal information is collected
Official website link: http://www.cs2-network.com/
Yitong SDK
Third-party entity: Chengdu Yitong Technology Co., Ltd.
Purpose of use: To implement the fisheye camera rendering function
Usage scenario: When using fisheye camera
Information collection details: No personal information is collected
Official website address: https://www.eapil.com/
Yitong CamTells camera privacy agreement (not App SDK): https://cftweb.3g.qq.com/privacy/agreement?appid=54248880
QQ Dingdang Speaker SDK (IOS)
Third-party entity: Shenzhen Tencent Computer Systems Co., Ltd.
Purpose of use: Use Dingdang Speaker to play QQ music under an authorized account
Usage scenario: When authorizing qq music account login in the Dingdang audio panel
Information collection details: login credential information, device information, IP address
Privacy Policy Address:https://dingdang.qq.com/doc/page/440
Tencent Cloud Xiaowei SDK (android)
Third-party entity: Shenzhen Tencent Computer Systems Co., Ltd.
Purpose of use: Use Dingdang Speaker to play QQ music under an authorized account
Usage scenario: When authorizing qq music account login in the Dingdang audio panel
Information collection details: network status, system time, voice information (provided by third-party developers), device unique identification code (provided by third-party developers), end-user account (provided by third-party developers), voice information, images information
Privacy Policy Address:https://dingdang.qq.com/doc/page/440
Tencent Lighthouse SDK (android)
Third-party entity: Shenzhen Tencent Computer Systems Co., Ltd.
Purpose of use: Use Dingdang speakers to play QQ music under authorized accounts
Usage scenario: When authorizing qq music account login in the Dingdang audio panel
Information collection details: Device related information.
Huawei unified code scanning SDK (Android)
Third-party entity: Huawei Software Technology Co., Ltd.
Purpose of use: Scan the code to bind the project code to log in, scan the code to add equipment, scan and identify the QR code
Usage scenario: when scanning QR code
Details of collected information: data you actively submit (pictures, text), sensor information (acceleration sensor, light sensor), network information, application information, device information, operator information (name of operator), system information (system settings, System properties, device model, operating system) and Wi-Fi information (Wi-Fi status).
Google MAP SDK
third party entity:Google LLC
purpose of usage:Google may use different types of location information to make certain services and products more useful to you, depending on the product you use and the settings you choose. This location information includes:
· GPS and other sensor data from your device
· IP address
· Activity across Google services, such as your searches or places you've marked (such as your home or work address)
· Information about things surrounding your device, such as Wi-Fi access points, base stations, and Bluetooth-enabled devices
scenes to be used:In order to return the user's location information to the application, display the user's location on the map, and provide developers with corresponding services based on the user's location information.
Mapbox SDK
third party entity:Mapbox
purpose of usage:In order to provide corresponding services, we provide you with problem tracking, troubleshooting, diagnosis services and perform data statistics to ensure the normal operation of products and services.
scenes to be used:
· Location information: Such as, the location of an event where an individual signed up to receive communication or interact with Mapbox.
· Internet or other network or device activity: When visiting any Mapbox websites, Mapbox automatically receives certain information such as: (a) browser and device type, (b) operating system, and (c) referring web pages including the pages visited on such sites. And information such as, IP address, data collected via strictly necessary and accepted website cookies / similar technologies. For information about cookies on Mapbox’s website, settings, and how to change browser cookie settings, please visit Mapbox’s website.
FCM SDK
third party entity:Google LLC
purpose of usage:Push messages to the phone system notification bar
scenes to be used:IP address(How to help: Cloud Functions uses IP addresses to execute event handlers and HTTP functions based on end-user actions;Retention: Cloud Functions temporarily stores IP addresses solely for the purpose of providing the service.)Firebase Cloud Messaging(Firebase Cloud Messaging uses Firebase installation IDs to determine which devices to send messages to.)
Twitter login SDK
third party entity:Twitter Inc.
purpose of usage:login
scenes to be used:login
information collected:Device information: device model, operating system, unique device identifier (referring to a string of characters programmed into the device by the device manufacturer, which can be used to uniquely identify the corresponding device), login IP address, method of accessing the network, Type and status, network quality data, device accelerator (gravity sensing device)
Privacy Policy Link:https://twitter.com/en/privacy
Google login SDK
third party entity:Google LLC
purpose of usage:login
scenes to be used:login
information collected:Device information: device model, operating system, unique device identifier (referring to a string of characters programmed into the device by the device manufacturer, which can be used to uniquely identify the corresponding device), login IP address, method of accessing the network, Type and status, network quality data, device accelerator (gravity sensing device)
Facebook login SDK
third party entity:Meta Platforms, Inc.
purpose of usage:login
scenes to be used:login
information collected:Device information: device model, operating system, unique device identifier (referring to a string of characters programmed into the device by the device manufacturer, which can be used to uniquely identify the corresponding device), login IP address, method of accessing the network, Type and status, network quality data, device accelerator (gravity sensing device)
Health Connect SDK
Third party:Google LLC
Purpose of use: Users choose to synchronize health data to Fitbit so that users can be provided with more health management software choices to achieve unified management of personal health.
Function type: When synchronizing health data to Fitbit
Information collection details: Height, weight, body fat rate, body metabolic rate, body water content, bone mass, lean body mass, heart rate, blood pressure, blood oxygen, calories, body temperature    
Privacy policy address: https://policies.google.com/privacy
Line login SDK
Third party:LINE Corporation
purpose of usage:login
scenes to be used:login
information collected:Device information: device model, operating system, unique device identifier (referring to a string of characters programmed into the device by the device manufacturer, which can be used to uniquely identify the corresponding device), login IP address, method of accessing the network, Type and status, network quality data, device accelerator (gravity sensing device)
Tiktok Share SDK
Third party:TikTok Pte. Ltd.
purpose of usage:Share specific messages
scenes to be used:Sharing
information collected:User content, Messages