1. Third-Party Information Sharing List
Third-Party Voice Service
Purpose: To support voice control of the device through third-party speakers.
Baidu (Xiaodu)
Third-Party Entity: Beijing Baidu Netcom Technology Co., Ltd.
Use Scenario: When using Xiaodu speakers to control devices
Information Collected: Unique device identifier (device_id), category, device name, model name, manufacturer name
Alibaba (Tmall Genie)
Third-Party Entity: Zhejiang Maojing Artificial Intelligence Technology Co., Ltd.
Use Scenario: When using Tmall Genie to control devices
Information Collected: Unique device identifier (device_id), category, device name, model name, manufacturer name, product icon, device location (optional, currently not passed)
JD.com (Dingdong)
Third-Party Entity: Beijing Linglong Technology Co., Ltd.
Use Scenario: When using Dingdong to control devices
Information Collected: Device unique identifier (device_id), product category, device name
Tencent (Yunxiaowei)
Third-Party Entity: Shenzhen Tencent Computer Systems Co., Ltd.
Use Scenario: When using Yunxiaowei to control devices
Information Collected: Device unique identifier (device_id), product category, device name, device model name, device manufacturer name, device version number
Cloud Service Provider
Tencent Cloud Services
Third-Party Entity: Shenzhen Tencent Computer Systems Co., Ltd.
Purpose: Provides infrastructure for Tuya, including network, server, and virtualization services.
Use Scenarios: Website hosting, data analysis, payment and credit card processing, infrastructure provision, IT services, customer support, email delivery, and other similar services.
Information Collection Details: All information will be stored on Tencent Cloud. For details, please see the Privacy Policy. Health Metrics Partner
Apple Health
Third-Party Entity: Apple (China) Co., Ltd.
Purpose: Users choose to sync their health data to Apple Health, providing them with a wider selection of health management apps for unified management of their personal health.
Use Scenario: When syncing health data to Apple Health
Information Collected: Height, weight, body fat percentage, BMI, weight
Third-Party Payment
Alipay
Third-party entity: Alipay (China) Network Technology Co., Ltd.
Purpose of use: Provide payment functionality
Usage scenarios: When using Alipay to pay for phone or SMS notifications or other payment scenarios
Information collected: Rotational vector sensor information, which is used to generate device fingerprints to ensure user payment security.
WeChat Pay
Third-Party Entity: Shenzhen Tencent Computer Systems Co., Ltd.
Purpose: Provide payment functionality
Function Type: Activate phone or SMS notification services or use WeChat Pay for other payment scenarios
Information Collection Details: None
2. App Third-Party SDK Service List
To ensure the stable operation of Tuya services or implement related features, we may integrate software development kits (SDKs) provided by third parties to ensure the sustainable development and maintenance of the products and services we provide to you. We conduct rigorous security testing on the SDKs that our authorized partners use to access relevant information. You can use the information listed in this list to understand how third parties handle your personal information. We also strictly restrict third parties from accessing your personal information to protect the security of your personal information.
The third-party SDKs we integrate are primarily used for the services you request. If you are not using the relevant features or services, third parties will not be able to access your information. We may adjust the third-party SDKs we integrate to meet new service requirements or due to changes in business functions. We will promptly disclose the latest updates on the integration of third-party SDKs in this notice.
Tuya integrates third-party SDKs in the following situations:
QQ Login SDK (supported only on Android and iOS)
Third-Party Entity: Shenzhen Tencent Computer Systems Co., Ltd.
Purpose: Log in using a QQ account
Usage Scenario: During login
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 may collect information about the mobile applications and other software you use; Location Information: Your geographic location is obtained through IP address, GPS, WLAN (Wi-Fi), or cell towers.
WeChat Login SDK (supported only on Android and iOS)
Third-Party Entity: Shenzhen Tencent Computer Systems Co., Ltd.
Purpose: Log in using a WeChat account
Usage Scenario: Login
Information Collected: Device Information: Device model, operating system, unique device identifier (a string of characters embedded in a device by the manufacturer that uniquely identifies it), login IP address, network access method, type, and status, network quality data, device accelerometer (for gravity sensors); Software Information: WeChat software version number, operation logs, and service logs
China Mobile One-Click Login SDK (Android and iOS only)
Third-Party Entity: China Mobile Internet Co., Ltd.
Purpose: Automatically retrieve mobile phone numbers for one-click login
Usage Scenario: Login
Information Collection Details: Network Type: Performance analysis, divided into three scenarios: data traffic only, WiFi only, and data traffic + WiFi; analysis of the impact of different network environments on number retrieval success rate and latency, and targeted optimization; Network Standard: Performance analysis, divided into three scenarios: 2G, 3G, and 4G; analysis of the impact of different network environments on number retrieval success rate and latency, and targeted optimization; Device Type and System: Performance analysis, collecting device model and system information for device adaptation and optimization; idfv (iOS only): Used for problem troubleshooting
QQ Share SDK (supported only on Android and iOS)
Third-Party Entity: Shenzhen Tencent Computer Systems Co., Ltd.
Purpose: Sending family invitations using QQ
Use Scenario: When adding family members
Information collected: Mobile device information, IP address
WeChat Share SDK (supported only on Android and iOS)
Third-Party Entity: Shenzhen Tencent Computer Systems Co., Ltd.
Purpose: Sending family invitations using WeChat
Use Scenario: When adding family members
Information collected: Mobile device information, IP address
Xiaomi Push SDK (Android)
Third-Party Entity: Xiaomi Mobile Software Co., Ltd.
Purpose: Push messages to the phone's system notification bar
Use Scenario: When receiving alarm, family, or notification messages in the Message Center
Information Collected: Your OAID (for Android Q and later), MEIDMD5, Android ID, VAID, AAID, your MID (for MIUI), and device model information.
Huawei Push SDK (Android)
Third-Party Entity: Huawei Device Co., Ltd.
Purpose: Push messages to the phone's system notification bar
Use Scenario: When receiving alarm, family, or notification messages in the Message Center
Information Collected: Your ID, application ID, application package name, and server public IP address. If you create a push notification task on the AppGallery Connect website, we will collect information about the frequency of use of Huawei Push features, the task name, the message content, and the push scope (app token, topic name, or audience group name).
OPPO Push SDK (Android)
Third-Party Entity: Guangdong Huantai Technology Co., Ltd.
Purpose: Push notifications to the phone's system notification bar
Use Scenario: When receiving alarm, family, or notification messages in the Message Center
Information Collection Details: Your device-related information (Serial Number, User ID, Android ID, Google Advertising ID, Phone region settings, device model, phone battery level, phone operating system version and language), information about apps using the push service (app package name and version number, running status), push SDK version number, network-related information (IP or domain connection results, current network type), message delivery results, notification bar status (notification bar permissions, user click behavior), lock screen status (whether the screen is locked, whether lock is allowed)
VIVO Push SDK (Android)
Third-Party Entity: Vivo Mobile Communications Co., Ltd.
Purpose: Push messages to the phone's system notification bar
Use Scenario: Receiving alarm, home, and notification messages in the Message Center
Information Collection Details: Device and Application Information: This includes the operating system version number, application information, device identifiers (SIM card, mobile country code, and vivo ID) during your use of vivo devices and services. (Android device's mobile network ID), mobile operator, language, system settings, device and application data)
AutoNavi SDK
Third-Party Entity: AutoNavi Software Co., Ltd.
Purpose of Use: To provide services, issue tracking, troubleshooting, and diagnostic services, and collect data statistics to ensure the normal operation of our products and services, Amap processes your device information, including location information (latitude and longitude, precise location, and coarse location). This includes positioning through technical processing of device information [such as IP address, GNSS information, WiFi status, WiFi parameters, WiFi list, SSID, BSSID, base station information, WiFi signal strength information, Bluetooth information, sensor information (vector, acceleration, pressure), device signal strength information, and external storage directory]. This includes device identification information (IDFA, OAID), current application information (application name, application version number), device parameters, and system information (system properties, device model, operating system, and carrier information). The device information collected may vary depending on the device, operating system (Android/iOS), and operating system version. In particular, when you use the following Amap SDK-related functions and services, the device information collected may vary. Please refer to the Location SDK, Map SDK, Search SDK, and Navigation SDK for details.
Usage scenarios: Smart scenarios based on location changes, location-based weather services
Positioning SDK
Detailed information collected:
Location information: This information is used to return user location information to applications and enable developers to provide services based on user location information. To facilitate real-time traffic conditions and traffic forecasts, we collect and analyze user location information and use this information to determine traffic congestion.
Device information: This information is used to provide services, track, troubleshoot, diagnose, and collect statistics on service issues, 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), and device signal strength information] is collected.
Device identification information: This information is used to improve the accuracy and success rate of positioning services, track, troubleshoot, diagnose, and collect statistics on service issues, and ensure the safe and normal operation of products and services. Device identification information (IDFA, OAID, GAID), current application information (application name, application version number), device parameters, and system information (system properties, device model, operating system, carrier information).
Map SDK
Detailed information collected:
Location information: This is used when developers enable the blue location dot feature to return user location information to applications, display the user's location on maps, and enable developers to provide services based on user location information.
Device information: This is used to provide services, track, troubleshoot, diagnose, and collect statistics on service issues, and ensure the normal operation of products and services. Device information [such as IP address, GNSS information, WiFi status, WiFi parameters, WiFi list, base station information, signal strength information, Bluetooth information, sensor information (vector, acceleration, pressure), device signal strength information, and external storage directories] is collected.
Device identification information: This is used to improve the accuracy and success rate of positioning services, track, troubleshoot, diagnose, and collect statistics on service issues, and ensure the safe and normal operation of products and services. Device identification information (IDFA, OAID, GAID), current application information (application name, application version number), device parameters, and system information (system properties, device model, operating system, carrier information)
Search SDK
Detailed information collected:
Mobile device information: Used to provide services, track, troubleshoot, diagnose, and collect statistics on service issues, and ensure the normal operation of products and services.
Shangyun P2P SDK
Third-Party Entity: Shenzhen Shangyun Internet Technology Co., Ltd.
Purpose: Implement video preview functionality for IPC devices
Usage scenario: When connecting to an IPC device to use the preview feature
Shared information: Camera device ID, network information (IP address, current network type, and name)
Sharing method: SDK local acquisition, backend interface transmission
Information collection details: No personal information is collected.
Eapil SDK
Third-Party Entity: Chengdu Eapil Technology Co., Ltd.
Purpose: Implementing fisheye camera rendering functionality
Use Scenario: When using a fisheye camera
Information Collection Details: No personal information is collected
QQ Dingdang Speaker SDK (iOS)
Third-Party Entity: Shenzhen Tencent Computer Systems Co., Ltd.
Purpose: Using Dingdang Speaker to play QQ Music music from an authorized account
Use Scenario: When authorizing a QQ Music account to log in via the Dingdang Speaker panel
Information Collection Details: Login credentials, device information, IP address
Tencent Cloud Xiaowei SDK (Android)
Third-Party Entity: Shenzhen Tencent Computer Systems Co., Ltd.
Purpose: Use Dingdang Speaker to play QQ Music music played by an authorized account
Use Scenario: When authorizing a QQ Music account to log in via the Dingdang Speaker panel
Information Collected: Network status, system time, voice information (provided by the third-party developer), device unique identifier (provided by the third-party developer), user account (provided by the third-party developer), voice information, image information
Tencent Lighthouse SDK (Android)
Third-Party Entity: Shenzhen Tencent Computer Systems Co., Ltd.
Purpose: Use Dingdang Speaker to play QQ Music music played by an authorized account
Use Scenario: When authorizing a QQ Music account to log in via the Dingdang Speaker panel
Information Collected: Device-related information
Huawei Unified Scan SDK (Android)
Third-Party Entity: Huawei Software Technologies Co., Ltd.
Purpose: Scan to bind a project code to log in, scan to add a device, and scan to identify a QR code
Usage Scenario: When scanning a code
Information Collected: Data you actively submit (images, text), sensor information (accelerometer, light sensor), network information, application information, device information, carrier information (carrier name), system information (system settings, system properties, device model, operating system), and Wi-Fi information (Wi-Fi status).
Huawei HarmonyOS Push Kit (HarmonyOS)
Third-Party Entity: Huawei Device Co., Ltd.
Purpose: Push messages to the phone's system notification bar
Use Scenario: When receiving alarm, home, or notification messages in the Message Center
Information Collected: Device Identifier (Push Token), Basic App Information, AAID (Application Anonymous Identifier), App Messages
Huawei HarmonyOS Map HarmonyOS Kit
Third-Party Entity: Huawei Device Co., Ltd.
Purpose: Provides positioning services
Use Scenario: Smart scenarios based on location changes, location-based weather services
Information Collected: Coarse or precise location, precise location, IP address, anonymous search keywords, sensor information (including accelerometer, gravity sensor, rotation vector sensor, screen orientation sensor), WiFi status, WiFi parameters, WiFi list, network information, basic application information, carrier information
Huawei HarmonyOS Scan HarmonyOS Kit
Third-Party Entity: Huawei Device Co., Ltd.
Purpose: Scan to bind a project code for login, scan to add a device, scan to identify a QR code
Usage Scenario: Scanning a QR code
Information Collected: Data you actively submit (images, text), sensor information (accelerometer, light sensor)