Third-party SDK Directory
Google SDK
Third party entity：Google LLC
Location：USA
Purpose of usage：Providing location-based services.
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.
Data Types: 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.
Collection Method: SDK Collection
FCM SDK
Third party entity：Google LLC
Location：USA
Purpose of usage：Push messages to the phone system notification bar
Scenes to be used：Used when delivering or receiving push messages.
Data Types: IP address, Firebase Cloud Messaging.
Collection Method: SDK Collection
Google login SDK
Third party entity：Google LLC
Location：USA
Purpose of usage：To provide third-party account authorization and login services.
Scenes to be used：Triggered when the user initiates the account authorization or sign-in process.
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)
Collection Method: SDK Collection
Health Connect SDK
Third party: Google LLC
Location：USA
Purpose of usage: To synchronize health data with third-party platforms (e.g., Fitbit) for unified personal health management.
Scenes to be used: Triggered when the user explicitly authorizes and enables health data synchronization.
Information collection details: Health metrics and exercise data recorded by the user's health devices.
Collection Method: Transmission via local SDK interface
TikTok Share SDK
Third party: TikTok Pte. Ltd.
Location: Singapore
Purpose of usage: To facilitate the seamless sharing of user-generated content (such as videos, images, or text) from the application directly to the TikTok platform.
Scenes to be used: Triggered when the user initiates a sharing action and explicitly selects TikTok as the destination.
Information collection details: User-selected media content (video/image files), captions, messages, and necessary metadata required for successful upload and attribution.
Collection Method: SDK Collection
Azure Open AI SDK
Third party: Microsoft Corporation
Location：USA
Purpose of usage：Users’ input is sent to an AI model hosted on the Microsoft Azure platform to generate responses or content.
Scenes to be used：When users use “Hey Tuya” intelligent dialogue, AI memo, AI notes, or AI translation
Information collected：Text, audio messages and images sent by users when using specific AI functions
Collection Method: SDK Collection
Gemini SDK
Third party: Google LLC
Location：USA
Purpose of usage：Users’ input is sent to an AI model hosted on the google cloud platform to generate responses or content.
Scenes to be used：When users use AI notes, AI translation, or AI Calories
Information collected：Text, audio messages and images sent by users when using specific AI functions
Collection Method: SDK Collection
Appsflyer SDK
Third party entity：AppsFlyer Inc.
Location：Israel
Purpose of usage：To understand how users find us, we can optimize our products and enhance the service experience more effectively.
Scenes to be used：When Users login
Data Types: Device ID, De-identified ID
Collection Method: SDK Collection
Other Partners & Information Sharing List
Amazon Web Services, Inc.
Location: USA
Purpose of usage: Enable cloud services via IaaS; data storage in data center instances for the data controller.
Scenes to be used: Cloud service, SMS, Emails
Information collected: All data stored through the Cloud, phone number and Email address
Collection Method: API Transmission
Alibaba Cloud (Singapore) Private Limited
Location: Singapore
Purpose of usage: Enable cloud services via IaaS; data storage in data center instances for the data controller.
Scenes to be used: Cloud infrastructure hosting, Data storage, System maintenance
Information collected: All data stored through the Cloud, phone number and Email address
Collection Method: API Transmission
Twilio Inc.
Location: USA
Purpose of usage: Provide verification codes through SMS for account login security verifications.
Scenes to be used: SMS, Phone calls
Information collected: Phone number
Collection Method: API Transmission
Google LLC
Location: USA
Purpose of usage: Notification of App version for update and App function upgrade sent to users; Push and Map services.
Scenes to be used:App update, App function upgrade, Push and Map services
Information collected: App Version, User ID
Collection Method: API Transmission
Apple Inc.
Location: USA
Purpose of Use: User chooses to sync health data to Apple Health to access a wider range of health management software options, achieving unified personal health management.
Scenes to be used: When the user actively selects to sync health data to Apple Health.
Information collected: Health vitals and workout data recorded by the user's health devices.
Collection Method: Transmission via local interface
Hangzhou Tuya Information Technology Co., Ltd.
Location: China
Purpose of usage: To enable Service Provider's technical team to provide technical support, troubleshooting and/or other requested services from App users.
Scenes to be used: Technical support, troubleshooting, data subject requests
Information collected: Applicable user data according to requirement to fulfill users' requests
Collection Method: API Transmission
Microsoft Corporation
Location: USA
Purpose of usage: Input is sent to an AI model hosted on the Microsoft Azure platform to generate responses or content.
Scenes to be used: “Hey Tuya” intelligent dialogue, AI memos, AI notes, AI translation
Information collected: Text and audio messages
Collection Method: API Transmission
Shops and their third-party service providers（For US Users）
Location: USA
Purpose of usage: Fulfill the transaction contract, complete the product packaging and logistics distribution.
Scenes to be used: Transaction fulfillment, Logistics distribution
Information collected: Order ID, product information, recipient's name, shipping address, recipient's mobile phone number, email address
Collection Method: Backend Display