2 What Information Is Collected and How We Use It?
1.We Collect and Use Your Personal Information
1.1
Account Registration and Login: When you use Kaadas Smart services or manage smart devices, we need to collect the following information from you: mobile phone number, email address, nickname, and profile photo. The purpose of collecting this information is to help you complete account registration and login. To make registration and login more convenient, we also provide "WeChat Login" and "Apple ID Login" features, which additionally collect WeChat account information (and Apple ID for iOS devices) depending on the platform.
If you do not provide this information, you will not be able to use Kaadas Smart services. After logging into your Kaadas account, the Kaadas Smart App will automatically retrieve your account nickname and profile photo and display them within the app.
1.2 Device Networking:
To enable
device binding, device management, network configuration, and device parameter settings, we need to collect the following information:
location information (including domain and country code, city code, mobile network code, mobile country code, cell ID, region name, latitude and longitude, timezone settings, and language settings), Wi-Fi parameters, Wi-Fi status, Wi-Fi name (SSID), Wi-Fi physical address (BSSID), Wi-Fi signal strength, DHCP information, network carrier information (NETWORK), SIM card status, carrier information (SIM), and advertising identifier (GAID).
The purpose of collecting this information is: device discovery, device network configuration, device binding, device management, device parameter settings, network environment detection, security verification, and service stability assurance.
1.3 Mobile Push Notifications: To push device operation records to you in real time, we need to collect the following information: handheld terminal or SIM card-related information:
we may collect information related to the handheld terminal running Kaadas Smart, system version, device manufacturer information, model name, and network carrier. We may also collect information about devices bound to your account, including
MAC address, DID, device network status (IP/network signal), firmware version, Android ID, HarmonyOS (OAID/AAID/ODID/UUID). Mobile application and website-related information, including anonymized identifier technologies, IP address, network request information, running processes, temporary message history, standard system logs, and system crash information.
The purpose of collecting this information is to push device operation records, alarm records, and doorbell ring records to you in real time.
1.4
Face ID / Fingerprint ID Information: To enable secure app login verification, we need to collect the following information:
Fingerprint ID login verification, Face ID login verification. The purpose of collecting this information is to allow you to use Fingerprint ID or Face ID for app account login and complete identity verification on your mobile device. We only receive the verification result and do not collect your actual fingerprint or facial data.
1.5
Installed Application List: To enable WeChat Login, we need to collect the following information: the list of installed applications. The purpose of collecting this information is to determine whether WeChat is installed on your device.
1.6 Statement on Collection of Network and Advertising Identifiers
1.6.1 GAID (Google Advertising ID)
(1)
Type of collected information: Device identifier (GAID)
(2)
Collection scenario: Collected on demand during the initialization of the Getui Push SDK
(3)
Purpose of use: Generate a unique push identifier for each device to distinguish different terminals and enable accurate delivery of notifications, ensuring proper operation of lock alert notifications and operation history pushes. GAID will NOT be used for precise user profiling or ad tracking.
(4)
Data processing method: The GAID is obtained one-time only after you grant privacy consent, with no repeated cyclic collection. You may manually reset the GAID in your mobile system settings; the push identifier will be updated synchronously after reset. No permanent long-term storage of GAID will be performed.
1.6.2 Wi-Fi BSSID and Wi-Fi Signal Strength
(1)
Type of collected information: Network information (Wi-Fi BSSID, Wi-Fi signal strength); device identifiers (OAID, VAID, AAID); device information (device model, operating system version, device type, network type)
(2)
Collection scenario: Temporarily read when entering ad display pages; network environment data is also retrieved during Bluetooth network configuration and Wi-Fi network setup for smart locks.
(3)
Purpose of use① Ad scenarios: Identify the current network environment, count ad impression and click data, and match compliant ad content. Wi-Fi data will not be leveraged to build precise user profiles or conduct location tracking.② Device network configuration scenarios: Evaluate Wi-Fi signal quality to assist smart locks in network authentication and maintain stable online connectivity of devices.
(4)
Data processing method: Data is temporarily collected only while the corresponding service page is active. Reading of Wi-Fi information stops immediately upon exiting the ad or network configuration page. Continuous background Wi-Fi scanning does not occur when the App is idle. Collected data is only cached temporarily and purged promptly once network setup is finished or the ad page is closed, without long-term storage.
1.7 Information Entered for After-Sales Repair Requests
(1)
Type of collected information: Identity and contact data (contact name, phone number, detailed service address for on-site maintenance)、Serial No.(SN)、E‑com Order No.
(2)
Trigger scenario for collection: Information is only collected when you voluntarily access the [One-Click Repair] page, manually fill out and submit a repair ticket. No such data will be gathered if you do not enter the repair page or submit a ticket.
(3)
Purpose of use: Solely to arrange technicians for on-site Kaadas lock troubleshooting, contact you to confirm service times, and locate maintenance addresses. This contact information will never be used for irrelevant purposes including ad push, user profiling, or device binding outside repair services.
(4)
Data processing rules
<1> All information is manually entered at your discretion; you may fill in partial fields or skip them entirely. No entered content will be retained if the repair ticket is not submitted.
<2> After a repair ticket is fully processed, we retain only ticket records for after-sales traceability for a maximum of 3 years. Names, phone numbers and addresses will be automatically desensitized or deleted upon expiration of the retention period.
<3> Your repair contact address and phone number will not be shared with advertising agencies or third-party promotion service providers. Data will only be synchronized to authorized maintenance partners for the single corresponding on-site service, and such partners are prohibited from retaining the information privately after service completion.
(5) Your RightsYou may view your submitted name, phone number and address information contained in repair tickets at any time via the App path [Service – Reservation Records – Installation & Repair]. You may also contact customer service to request full erasure of all stored repair contact information.
1.8
Operation Logs (in accordance with GB 21556‑2008)
To ensure account security and risk traceability, we automatically collect client‑side account‑security operation logs,
including operation time, account identifier, login and logout events, terminal authorization, authorization revocation, security configuration changes, operation IP addresses and operation results. These logs are limited to App‑account‑related activities and do not cover smart lock device operations. Logs are retained on the cloud for no less than six months. As security‑audit records, they cannot be manually deleted and will be automatically purged upon expiry. Such data is used solely for account risk control and will not be disclosed to external parties except as required by law.
1.9
Login Device Management
To secure your account and detect abnormal log‑ins,
we collect information about terminals used to log in to your account, including device brand, device model, login/logout timestamp, terminal identifier and login IP address. You may view logged‑in devices on the App account‑security page and revoke authorization to kick off unfamiliar devices. Data is stored in the cloud for no less than six months, used exclusively for account risk control, and will not be shared with third parties unless compelled by legal requirements.
2.Device Permissions Called
2.1.
Location Permission: To use Wi-Fi LAN for device networking in Kaadas Smart. You need to enable this permission; authorization is requested at first use.
2.2.
Microphone Permission: For voice intercom in the device video feature and audio recording for device voice announcements. You need to enable this permission; authorization is requested at first use.
2.3.
Phone Permission: To call our customer service hotline within Kaadas Smart. You need to enable this permission; authorization is requested at first use.
2.4.
Camera Permission: To scan QR codes for device networking, and to take photos/videos for uploading or changing your profile photo. You need to enable this permission; authorization is requested at first use.
2.5.
Photo Library Permission: To save screenshots and video recordings from device video to your phone, and to upload images. You need to enable this permission; authorization is requested at first use.
2.6.
Storage Permission: To cache generated text and save images and recordings that you actively download. You need to enable this permission; denying this permission will prevent you from using data storage features.
2.7.
Notification Permission: To receive incoming call alerts and device messages (device/app operation records, alarm information, visitor information). You need to enable this permission; denying this permission will prevent you from receiving device messages.
2.8.
Bluetooth Permission: For device discovery and network configuration via Bluetooth in Kaadas Smart. You need to enable this permission; authorization is requested at first use.
2.9.
Alarms and Reminders Permission: To receive device push notifications in Kaadas Smart. You need to enable this permission; denying this permission may affect receipt of device push notifications.
2.10.
Contacts Permission: To auto-fill the phone number of a selected contact when setting up emergency contacts within Kaadas Smart, so you don't need to manually enter the phone number — the app automatically fills in the selected contact's phone number (when a duress code is used to unlock, a phone call/SMS notification is sent to the emergency contact). The app only accesses the phone number and nickname of the selected contact. You need to enable this permission; denying this permission will prevent convenient setup of emergency contacts.（Note: This permission is for iOS systems only.）
2.11.
Tracking Permission: For cross-app and cross-website activity tracking to deliver and measure advertisements.
2.12.
Local Network Permission: To discover, connect to, and control smart home devices (cameras) on your local network in Kaadas Smart. You need to enable this permission; authorization is requested at first use.
2.13.
Calendar Permission: For precise date-based search and display of device activity records in Kaadas Smart, for example selecting a specific date to filter and display records within a time range. You need to enable this permission; authorization is requested at first use.
2.14
Network and Wi‑Fi Permissions: Used for App network access and device network configuration. During network configuration, the App needs to read and switch Wi‑Fi status, and connect the smart lock to your home router via local area network broadcast.
2.15
Audio Settings Permission: Used to control call volume, speaker and microphone status during video intercom.
2.16
Fingerprint and Biometric Recognition Permission: Used for biometric verification for fingerprint / face unlocking. Verification is performed only on‑device; the App does not collect or store any biometric data.
2.17
Vibration and Flashlight Permissions: Used for vibration alerts triggered by doorbell or alarm messages, and flash fill‑in light when scanning QR codes to add devices.
2.18
Get Running Tasks Permission: Used to determine whether the App is in the foreground, so as to govern the jump behavior of push notifications. Jump directly to the target page when the App is in foreground; only display notifications when the App runs in background.
2.19
Keep‑Awake Permission: Used to keep the screen awake during video intercom and video playback to prevent call interruption.
3.Sensitive Permissions Called
3.1.
File Management: To save images and recordings to your phone locally. We need to access this permission; if you deny the relevant system permission, you will not be able to use this feature.
3.2.
Wi-Fi SSID Information: To obtain the currently connected Wi-Fi information for quick and convenient device connection. We need to access this permission; if you deny the relevant system permission, you will not be able to use this feature.
3.3.
Installed Application List: To enable WeChat sharing functionality. We need to check whether WeChat is installed on your phone; we do not detect or access information about other applications on your phone.
3.4.
Device Sensor Information: To adjust screen brightness based on ambient light when scanning QR codes for device networking.
3.5.
sILocal Service: To enable doorbell push notification delivery, we need to detect whether the Kaadas Smart App is running in the background.
3.6.
Vendor Push Service: To enable third-party push notification delivery, we need to detect whether the Kaadas Smart App is running in the background.
3.7.
Device Sensors: To scan QR codes for adding devices, we need to acquire device sensor information.
To ensure the proper implementation of relevant business functions, for specific client permission usage descriptions and scenarios, please refer to the
Personal Information List.
Please note that the above permission features are not enabled by default. They will only be used when implementing specific functions or services with your explicit authorization. You can also go to Kaadas Smart App and tap ["Me" - "My Settings" - "System Permission Management"] to revoke permissions. Importantly, even with your authorization and access to these sensitive data permissions, we will not collect your information when the relevant function or service does not require it. You can adjust the permission settings for Kaadas Smart App features according to your needs.
4.Personal Information Storage
4.1 How and How Long We Store Your Information
We store your information through secure means, including local storage (app data caching), databases, and server logs.
Generally, we only store your personal information for the period necessary to fulfill specific functions or as required by laws and regulations. When the storage period for your information expires, we will promptly delete your personal information or anonymize it.
4.2Where We Store Your Information
In accordance with laws and regulations, we store personal information collected within China on servers located in China.
Currently, we do not transfer or store your personal information across borders. Should cross-border transfer or storage become necessary in the future, we will inform you of the purpose of the data transfer, the recipient, security measures, and security risks, and obtain your consent.
4.3 Termination Processing of Personal Information, User Profiling, Information Aggregation and Fusion
4.3.1 Rules for Personal Information Processing upon Service Discontinuation
In the event of business adjustment, service discontinuation or service decommissioning of this Product/Service, we will notify users in advance through reasonable means such as in‑app announcements and push notifications. After the service is discontinued, we will promptly cease further collection of your personal information.
Following service discontinuation, unless retention is otherwise required by laws and regulations, we will delete or anonymize your personal information within the statutory time limit. For information that must be retained by legal mandate, we will store it in isolation solely for statutory purposes without applying it to other businesses, and permanently delete such information upon expiration of the retention period.
4.4 User Profiling and Behavioral Analysis
To deliver core functions including smart lock device management, unlock event logging and abnormal alerts only, this Product conducts necessary statistics on device usage behaviors. We will not generate user profiles for marketing or advertising purposes based on unlock records and device‑usage data.
Should user profiling be required for future business operations, we will explicitly inform you in advance of the profiling purposes, collected data items and scope of use, and obtain your authorization. You have the right to disable processing related to user profiling. Profiling‑related data will be protected by security measures such as encrypted storage and de‑identification.
4.5 Information Aggregation, Fusion and Protective Measures
To implement business functions such as device management, event alerts and operation log viewing, we aggregate, correlate and fuse data reported by lock devices and APP account operation data. For aggregation and fusion activities, we will carry out a personal information security impact assessment and implement security safeguards based on assessment outcomes. We adopt the following protective measures for personal information after aggregation and fusion:
(1) Implement encrypted storage and de‑identification for aggregated and fused data;
(2) Enforce least‑privilege access control for backend systems; audit logs will be kept for internal staff accessing such data;
(3) Aggregated and fused personal information shall only be used within the business scope disclosed to you and authorized by you, and shall not be diverted for other purposes;
(4) Strictly comply with the minimum‑necessary storage period; corresponding personal information will be automatically cleaned up upon expiry;
(5) Personal information after aggregation and fusion will not be disclosed or shared externally without your consent.
5.How Your Personal Information May Be Used
The purpose of collecting personal information is to provide you with products and/or services and to ensure our compliance with applicable laws. You hereby agree that we may process personal information for the purposes set forth in this Privacy Policy and disclose personal information to our affiliates (involved in communications, social media, technology, and cloud services) and third-party service providers (defined below).
We may use personal information for the following purposes:
(1) To provide, process, maintain, improve, and develop our products and/or services to you, and through devices or services we provide.
(2) To communicate with you regarding your devices, services, or any general inquiries (including updates, device firmware/software upgrades, customer support, relevant information, and notifications).
(3) To analyze and develop statistical information related to the use of our products and services, in order to better improve our products and services.
(4) To store and maintain information related to you for our business operations or to fulfill legal obligations.
(5) To provide local services without communicating with our servers.
Further details on how we use your information (which may include personal information) are provided below:
(6) Creating your Kaadas account. Personal information collected when creating an account through our website or mobile app is used to establish your user account and profile.
(7)
Providing location-based services. When using Kaadas Smart and connecting to our devices, we may use location information to determine the device's time zone, ensuring accurate time display on the device and identifying the service region for login. We may also pre-enable relevant device features based on your preferences. You can disable this feature at any time through device settings or by stopping use of the app.
(8) Device onboarding.
When a device is operated through the App, its authenticity needs to be verified. We do this by validating the factory DID information to confirm the device's legitimate identity. Additionally, when the device requires a network connection, the App is used to configure the device's network settings. During this process, you will need to enter the Wi-Fi name and password, which is used solely for device network configuration. Your Wi-Fi name and password data is encrypted and stored locally on the device and is not uploaded to our servers. You can delete this information from the device at any time. We also need to determine the IP and network signal to select the optimal network connection method for the device, ensuring connection stability.
(9) Device status display. This allows you to remotely view device status so you can monitor device operation at all times.
(10) Setting up automation tasks. Event information reported by your devices (information from devices you have added; the specific configurable information depends on your privacy authorization scope for each device, and each added device provides the device provider's privacy policy terms for your consideration) can be used to create personalized automation tasks.
(11) Provide push notification services. Your account will be used to deliver push notifications for the Kaadas Smart App to send‑device alerts to you. You may disable this function at any time by modifying the preference options under "Message Settings".
(12) Collecting user feedback. Feedback you choose to provide is invaluable in helping us improve our services. To track the feedback you provide, we may use your personal information to contact you and retain records.
(13) Sending notifications. We may periodically use your personal information to send important notifications, including alerts about abnormal device operation, customized device push notifications (depending on the devices you have purchased and added), and changes to our terms, conditions, and policies.
6.About Third-Party SDK Usage and Disclosure
We conduct strict screening of third-party SDKs integrated into our services and promptly disclose the latest information about integrated SDKs. Please refer to the official privacy policies of the respective third-party SDKs for details.
(1) Bugly SDK
SDK Name: Bugly SDK
Third-Party Name: Shenzhen Tencent Computer System Co., Ltd.
Purpose: For crash analysis of the Kaadas app
Third-Party Name: Shenzhen Tencent Computer System Co., Ltd.
Processing Method: De-identification, encrypted transmission and processing
Personal Information Collected: Log information (including developer-custom logs, Logcat logs, and application crash stack traces), device identifier information [IMEI (for Android versions below Q), IMSI, MAC address, Android ID, HarmonyOS (OAID/AAID/ODID/UUID), and IDFV], network information, system name, system version, country code, device serial number, currently running programs
Privacy Policy Link:
https://privacy.qq.com/document/priview/fbd2c3f898df4c1c869925dd49d57827
Contact:
·Online consultation:
https://kf.qq.com/
·Email: Dataprivacy@tencent.com
(2) WeChat Open SDK
SDK Name: WeChat Open SDK
Third-Party Name: Shenzhen Tencent Computer System Co., Ltd.
Purpose: To support WeChat authorization login and sharing
Processing Method: De-identification, encrypted transmission and processing
Personal Information Collected: Device identifier information [IMEI (for Android versions below Q)/OAID, IMSI, MAC address, Android ID, HarmonyOS (OAID/AAID/ODID/UUID)], network information (IP, current network type and name), list of installed applications
Privacy Policy Link:
https://open.weixin.qq.com/cgi-bin/frame?t=news/protocol_developer_tmpl
Contact:
·Online consultation:
https://kf.qq.com/
·Email: Dataprivacy@tencent.com
(3) Xiaomi Push SDK
SDK Name: Xiaomi Push SDK
Third-Party Name: Beijing Xiaomi Mobile Software Co., Ltd.
Purpose: For push notifications on Xiaomi phones
Processing Method: De-identification, encrypted transmission and processing
Personal Information Collected: Device identifiers (OAID, encrypted Android ID, HarmonyOS (OAID/AAID/ODID/UUID)), push message content, device information (device manufacturer, model, region, carrier name, etc.), notification bar settings, list of installed applications
Permissions that may be called: Access network status, obtain device information, write to device storage
Privacy Policy Link:
https://dev.mi.com/distribute/doc/details?pId=1534
Contact:
·Online consultation:
https://privacy.mi.com/support
(4) Huawei Push SDK (includes Huawei Update SDK, Huawei Open SDK)
SDK Name: Huawei Push SDK (Android)
Third-Party Name: Huawei Software Technologies Co., Ltd.
Purpose: For push notifications on Huawei phones
Processing Method: De-identification, encrypted transmission and processing
Personal Information Collected: App information, device information (hardware information, basic system information, and system settings)
Privacy Policy Link:
https://developer.huawei.com/consumer/cn/doc/HMSCore-Guides/sdk-data-security-0000001050042177
Contact:
·Phone: 950800
(5) Getui Push SDK
SDK Name: Getui Push SDK
Third-Party Name: Every Interactive Co., Ltd.
Purpose: To provide Getui push notification service
Processing Method: De-identification, encrypted transmission and processing
Personal Information Collected: Device identifiers (including IMEI, IDFA, Android ID, HarmonyOS (OAID/AAID/ODID/UUID), MAC, OAID, Advertising ID, Serial Number, IMSI, UAID, ICCID), device platform, device manufacturer, device brand, network information (including IP address, Wi-Fi information, base station information), location information, SD card directory creation, SD card file list query, list of installed applications
Privacy Policy Link:
https://docs.getui.com/privacy/
Contact:
·Email: business@getui.com
·Phone: 4006-808-606
·Fax: 0571-86473223
(6) Meizu Push SDK
SDK Name: Meizu Push SDK
Third-Party Name: Zhuhai Meizu Telecom Equipment Co., Ltd.
Purpose: To provide real-time push notifications, push experience optimization, and statistical analysis for Meizu phones
Processing Method: De-identification, encrypted transmission and processing
Personal Information Collected: Device-related information (phone brand, phone model, system version, system language, and device identifier PUSHID), app information, push status
Privacy Policy Link:
https://open.flyme.cn/docs?id=202
Contact:
·Phone: 400-788-3333
(7) OPPO Push SDK
SDK Name: OPUSH SDK
Third-Party Name: Guangdong Huan Technology Co., Ltd.
Purpose: To provide push notification service for OPPO phones
Processing Method: De-identification, encrypted transmission and processing
Personal Information Collected: Basic app information (MCS app package name, app version number, OPUSH SDK version number), in-app device identifiers (RegistraterID, appKey, appSecret), list of installed applications
Privacy Policy Link:
https://open.oppomobile.com/wiki/doc#id=10194
Contact:
·Email: quickapp@oppo.com
(8) vivo Push SDK
SDK Name: vivo Push SDK
Third-Party Name: vivo Mobile Communication Co., Ltd.
Purpose: To provide push notification service for vivo devices and track push SDK API call success rate
Processing Method: De-identification, encrypted transmission and processing
Personal Information Collected: Basic app information, in-app device identifiers, device hardware information, basic system information
Privacy Policy Link:
https://dev.vivo.com.cn/documentCenter/doc/706
Contact:
·Email: privacy@vivo.com
·Phone: 400-678-9688
(9) ZXingLite
Purpose: Google open-source barcode scanning library for generating and scanning QR codes
Processing Method: None
Personal Information Collected: None
Official Website Link:
https://github.com/zxing/zxing
(10) Android Support Library
Purpose: Compatibility for lower-version programs to support higher-version API features
Processing Method: None
Personal Information Collected: None
Official Website Link:
https://developer.android.com/topic/libraries/support-library
(11) AndroidX Library
Purpose: Support for Android libraries, replacing the deprecated Android Support Library
Processing Method: None
Personal Information Collected: None
Official Website Link:
https://developer.android.com/jetpack/androidx?hl=zh-cn
(12) Google Material Design Library
Purpose: Mobile app UI interaction
Processing Method: None
Personal Information Collected: None
Official Website Link:
https://material.io/develop/android/docs/getting-started
(13) Log Service (SLS) SDK
SDK Name: Log Service (SLS) SDK
Third-Party Name: Alibaba Cloud Computing Co., Ltd.
Purpose: To provide log analysis service
Processing Method: Anonymization, de-identification, encrypted transmission and processing
Personal Information Collected: Device information (phone brand, phone OS type), log information
Official Website Link:
https://terms.aliyun.com/legal-agreement/terms/suit_bu1_ali_cloud/suit_bu1_ali_cloud202112131013_69952.html
Contact:
·Phone: 95187-1
(14) Zhongjian Ad SDK
SDK Name: Zhongjian Ad SDK
Third-Party Name: Hangzhou Zhongjian Information Technology Co., Ltd.
Purpose: For ad delivery and ad performance analysis
Processing Method: De-identification, encrypted transmission and processing
Personal Information Collected: Device identifiers (IDFA, OAID); device information (hardware model, OS, system language, screen dimensions, screen orientation); ad data (impressions, click data); user-provided information (name, contact information)
Official Website Link:
https://hzzhongjian.cn/privacy_policy_zhongjian_sdk.html
(15) Octopus SDK
SDK Name: Octopus SDK
Third-Party Name: Beijing Shengying Technology Co., Ltd.
Purpose: App information for ad delivery and ad anti-fraud
Processing Method: De-identification, encrypted transmission and processing
Personal Information Collected: Device identifiers (OAID, GAID, IDFA); device information ((Android+iOS+HarmonyOS) device brand, model, software system version, screen density, screen resolution, device language, device timezone, CPU info, available storage space and other basic information; (Android) AndroidID, OAID; (iOS) phone system reboot time, total disk space, total system memory, IDFV; (HarmonyOS) ODID); network information ((Android+iOS+HarmonyOS) carrier info, Wi-Fi status, network signal strength, IP address; (Android+HarmonyOS) app package name, running process info, version number); ad information (display, click, and conversion interaction data for ads); performance data (such as crash data, performance data)
Official Website Link:
http://doc.adintl.cn/#/zh-cn/guide/UsePrivacy
Contact:
·Email: yaowanyu@adintl.cn
(16) AdScope SDK
SDK Name: AdScope SDK
Third-Party Name: Shanghai Beizi Network Technology Co., Ltd.
Purpose: Device information for ad delivery strategy, statistical analysis, and anti-fraud analysis
Processing Method: De-identification, encrypted transmission and processing
Personal Information Collected: Device identifiers (OAID, device ID (IDFA collected only with user authorization)); device information (device brand, model, timezone, language, system version, UserAgent, screen dimensions, orientation, DPI, system update time, disk space, physical memory); network information ((Android+iOS+HarmonyOS) carrier info, Wi-Fi status, network signal strength, IP address; (Android+HarmonyOS) app package name, running process info, version number; (Android) carrier (mcc&mnc), CPU; (iOS) boot time, device name); ad information (product interaction data, ad data (impressions, clicks, conversions)); diagnostic data (such as crash data, performance data)
Official Website Link:
https://sdkdocv3.beizi.biz/#/zh-cn/guide/UsePrivacy
Contact:
·Email: dev@hubcloud.com.cn
(17) Meishu Aggregated Ad SDK
SDK Name: Meishu Aggregated Ad SDK
Third-Party Name: Beijing Meishu Information Technology Co., Ltd.
Purpose: For commercial performance ad delivery, ad display and monitoring, delivery attribution analysis, anti-fraud verification, ad delivery strategy optimization, reducing app crashes, and providing stable and reliable ad services
Processing Method: De-identification, encrypted transmission and processing
Personal Information Collected: Device identifiers ((Android) Android ID, OAID, IMSI; (iOS) IDFA, IDFV; (HarmonyOS) ODID); device information ((Android+iOS+HarmonyOS) device manufacturer, device model, OS version, device type, device language, screen info (orientation/resolution), network type, boot time, storage capacity); app information (app package name, app version number, SDK version)
Official Website Link:
https://wwww.atdplus.cn/html/sdk-privacy-agreement/
Contact:
·Email: marketing@adxdata.com
·Phone: 010-85907587 / 13522891095
(18) Mobile Security Alliance MSA SDK
SDK Name: Mobile Security Alliance MSA SDK
Third-Party Name: Mobile Security Working Committee of the China Academy of Information and Communications Technology (Mobile Security Alliance MSA)
Purpose: To provide open anonymous device identifiers for different mobile smart terminals, determine virtual machine environments, identify terminal brands, and call interfaces
Processing Method: De-identification, encrypted transmission and processing
Personal Information Collected: Device identifiers (OAID (core), VAID, AAID, device manufacturer information); device information (device model, OS version, device type, network type)
Official Website Link:
https://www.msa-alliance.cn/col.jsp?id=123
Contact:
·Email: msa@caict.ac.cn
·Phone: 010-62300678 (China Academy of ICT main line)
(19) Firebase
Third-Party SDK Name: Firebase
Third-Party Entity: Google LLC
Purpose of Use: Count App crashes, analyze user behavior, and optimize operational stability and functional experience of the product.
Data Processing Method: After users grant privacy consent, data is collected by invoking APIs on demand only when the App runs in the foreground. No silent data collection occurs during background idle state, and the list of installed applications will not be retained long-term.Types of Personal Information Collected: Device identifier (AAID); device information (device model, operating system version, device type, network type); list of installed applications
Official Privacy Policy Link:
https://firebase.google.com/support/privacy
Contact Information: Google Privacy Inquiry Form
https://support.google.com/policies/contact/privacy_policy_feedback
(20) Google Mobile Services (GMS)
Third-Party SDK Name: Google Mobile Services (GMS)Third-Party Entity: Google LLC
Purpose of Use: Support overseas message push and basic account service verification to ensure the normal operation of cross-device core functions.
Data Processing Method: After users grant privacy consent, data is retrieved on demand upon function triggers. There is no continuous background data collection mechanism, and data is only temporarily cached.
Types of Personal Information Collected: Device identifier (AAID); device information (device model, operating system version, device type, network type); list of installed applications
Official Privacy Policy Link:
https://policies.google.com/privacy
Contact Information: Google Privacy Inquiry Form
https://support.google.com/policies/contact/privacy_policy_feedback
(21) adlib Ads SDK (com.zj.adlib)
Third-Party SDK Name: adlib Ads SDKThird-Party Entity: Third-party advertising service provider
Purpose of Use: Identify current network environment, count ad impression and click data, and match compliant ad content. Precise user profiling and location tracking will not be performed based on network information.
Data Processing Method: Wi-Fi information is temporarily read only when users enter the ad page; data collection stops immediately upon exiting the page. No continuous Wi-Fi scanning runs in the background.Types of Personal Information Collected: Device identifiers (OAID, VAID, AAID); device information (device model, operating system version, device type, network type); network information (Wi-Fi BSSID, Wi-Fi signal strength)Official Privacy Policy Link: No independent public official website. All data processing fully complies with the Personal Information Protection Law of the People's Republic of China and the Cybersecurity Law of the People's Republic of China.Contact Information: In-app online customer service channel, which can forward privacy-related requests to the advertising service provider.
(22) Bugly Android (Tencent Crash Monitoring SDK)
Third-Party SDK Name: Bugly AndroidThird-Party Entity: Shenzhen Tencent Computer Systems Co., Ltd.
Purpose of Use: Read local logs when the App suffers flashbacks, stuttering or crashes to help R&D teams troubleshoot faults, fix program defects and improve App stability.
Data Processing Method: Logs are read only once when a crash event is triggered; storage will never be actively scanned when no crash occurs. Only runtime logs are accessed, while private files such as photos and documents will not be read.
Types of Personal Information Collected: Device identifiers (OAID, VAID, AAID, device manufacturer information); device information (device model, operating system version, device type, network type); local SD card runtime logs
Official Privacy Policy Link:
https://bugly.qq.com/v2/privacy
Contact Information: Tencent Bugly Customer Service Portal
https://bugly.qq.com/v2/contact
(23) Getui Basic Push Library (com.getui.gtc)
Third-Party SDK Name: Getui Basic Library getui.gtc
Third-Party Entity: Zhejiang Daily Interactive Co., Ltd.
Purpose of Use: Generate unique push identifiers for devices to realize accurate message delivery, distinguish push channels for different devices, and guarantee the normal operation of push notifications.
Data Processing Method: Identifiers are obtained once during push initialization after users grant privacy consent, with no repeated cyclic collection. Users may manually reset various advertising identifiers in mobile system settings.
Types of Personal Information Collected: Device identifiers (OAID, VAID, AAID, GAID, device manufacturer information); device information (device model, operating system version, device type, network type)
Official Privacy Policy Link:
https://docs.getui.com/privacy/
Contact Information: Getui Privacy Inquiry Email: privacy@getui.com
(24)
GdtAd
Third-Party Name: Shenzhen Tencent Computer Systems Co., Ltd. (Tencent GDT / Youlianghui)
Purpose of Use: Ad serving, ad attribution
Processing Method: De-identification, encrypted transmission
Information Collected: Device information (IMEI/MAC/Android ID/IDFA), device identifiers (OAID/GAID), installed application list, network information, geographic location
Privacy Policy: https://imgcache.qq.com/rain/taf/ad_platform_sdk/privacy.html
Contact: https://www.tencent.com/zh-cn/contacts.html
(25)
React
Third-Party Name: Meta (Facebook, United States)
Purpose of Use: Cross-platform mobile UI rendering framework
Processing Method: Does not actively collect personal information
Information Collected: Does not actively collect; the framework itself does not involve personal data collection
Privacy Policy: https://github.com/facebook/react-native
Contact: https://github.com/facebook/react-native
(26)
Glide
Third-Party Name: Bump Technologies (acquired by Google, United States)
Purpose of Use: Image loading, caching, and display
Processing Method: Does not actively collect personal information
Information Collected: Does not actively collect
Privacy Policy: https://github.com/bumptech/glide
Contact: https://github.com/bumptech/glide
(27)
SmartRefreshLayout
Third-Party Name: scwang90 (Open source, GitHub)
Purpose of Use: Pull-to-refresh and load-more layout component
Processing Method: Does not actively collect personal information
Information Collected: Does not actively collect
Privacy Policy: https://github.com/scwang90/SmartRefreshLayout
Contact: https://github.com/scwang90/SmartRefreshLayout
(28)
FlycoTabLayout
Third-Party Name: flyco (Open source, GitHub)
Purpose of Use: Tab navigation switching component
Processing Method: Does not actively collect personal information
Information Collected: Does not actively collect
Privacy Policy: https://github.com/H07000223/FlycoTabLayout
Contact: https://github.com/H07000223/FlycoTabLayout
(29)
Sqlcipher
Third-Party Name: Zetetic LLC (United States)
Purpose of Use: SQLite database encryption
Processing Method: Does not actively collect personal information; only encrypts local data
Information Collected: Does not actively collect
Privacy Policy: https://www.zetetic.net/sqlcipher/license/
Contact: https://www.zetetic.net/contact/
(30)
ijk Video Player
Third-Party Name: Bilibili (China)
Purpose of Use: Video decoding and playback
Processing Method: Does not actively collect personal information
Information Collected: Does not actively collect
Privacy Policy: https://github.com/bilibili/ijkplayer
Contact: https://github.com/bilibili/ijkplayer
(31)
RxJava-2
Third-Party Name: ReactiveX Organization
Purpose of Use: Asynchronous event processing, reactive programming framework
Processing Method: Does not actively collect personal information
Information Collected: Does not actively collect
Privacy Policy: https://github.com/ReactiveX/RxJava
Contact: https://github.com/ReactiveX/RxJava
(32)
PersistentCookieJar
Third-Party Name: franmontiel (Open source, GitHub)
Purpose of Use: HTTP Cookie persistent storage
Processing Method: Does not actively collect personal information
Information Collected: Stores Cookie data generated by the application
Privacy Policy: https://github.com/franmontiel/PersistentCookieJar
Contact: https://github.com/franmontiel/PersistentCookieJar
(33)
Yalantis
Third-Party Name: Yalantis (Ukraine)
Purpose of Use: UI interaction animation components
Processing Method: Does not actively collect personal information
Information Collected: Does not actively collect
Privacy Policy: https://github.com/Yalantis
Contact: https://yalantis.com
(34)
FileDownloader
Third-Party Name: Liulishuo (China)
Purpose of Use: Multi-threaded file downloading
Processing Method: Does not actively collect personal information
Information Collected: Does not actively collect
Privacy Policy: https://github.com/lingochamp/FileDownloader
Contact: https://github.com/lingochamp/FileDownloader
(35)
ExoPlayer
Third-Party Name: Google LLC (United States)
Purpose of Use: Video decoding and playback
Processing Method: Does not actively collect personal information
Information Collected: Does not actively collect
Privacy Policy: https://github.com/google/ExoPlayer
Contact: https://github.com/google/ExoPlayer
(36)
mp4parser
Third-Party Name: sannies (Open source, GitHub)
Purpose of Use: MP4 file format parsing
Processing Method: Does not actively collect personal information
Information Collected: Does not actively collect
Privacy Policy: https://github.com/sannies/mp4parser
Contact: https://github.com/sannies/mp4parser
(37)
YouthBanner
Third-Party Name: youth5201314 (Open source, GitHub)
Purpose of Use: Carousel banner display component
Processing Method: Does not actively collect personal information
Information Collected: Does not actively collect
Privacy Policy: https://github.com/youth5201314/banner
Contact: https://github.com/youth5201314/banner
(38)
BigkooPickerview
Third-Party Name: gzu-liyujiang (Open source, GitHub)
Purpose of Use: Scrolling picker control (time selection, address selection, etc.)
Processing Method: Does not actively collect personal information
Information Collected: Does not actively collect
Privacy Policy: https://github.com/gzu-liyujiang/AndroidPicker
Contact: https://github.com/gzu-liyujiang/AndroidPicker
(39)
SwipeRecyclerView
Third-Party Name: yanzhenjie (Open source, GitHub)
Purpose of Use: Swipe-action RecyclerView list component
Processing Method: Does not actively collect personal information
Information Collected: Does not actively collect
Privacy Policy: https://github.com/yanzhenjie/SwipeRecyclerView
Contact: https://github.com/yanzhenjie/SwipeRecyclerView
(40)
BouncyCastle
Third-Party Name: Legion of the Bouncy Castle Inc. (Australia)
Purpose of Use: Cryptographic algorithm library (AES/RSA/SHA, etc.)
Processing Method: Does not actively collect personal information
Information Collected: Does not actively collect
Privacy Policy: https://www.bouncycastle.org
Contact: https://www.bouncycastle.org
(41)
greenrobot-common
Third-Party Name: greenrobot Organization (Germany)
Purpose of Use: Event publish/subscribe communication bus (EventBus)
Processing Method: Does not actively collect personal information
Information Collected: Does not actively collect
Privacy Policy: https://github.com/greenrobot/EventBus
Contact: https://github.com/greenrobot/EventBus
(42)
Bolts
Third-Party Name: Parse Platform / Facebook (United States)
Purpose of Use: Asynchronous task management, chained task framework
Processing Method: Does not actively collect personal information
Information Collected: Does not actively collect
Privacy Policy: https://github.com/BoltsFramework/Bolts-Android
Contact: https://github.com/BoltsFramework/Bolts-Android
(43)
Okio
Third-Party Name: Square, Inc. (United States)
Purpose of Use: Java I/O data reading and writing framework
Processing Method: Does not actively collect personal information
Information Collected: Does not actively collect
Privacy Policy: https://github.com/square/okio
Contact: https://github.com/square/okio
(44)
Airbnb Lottie
Third-Party Name: Airbnb, Inc. (United States)
Purpose of Use: After Effects animation playback
Processing Method: Does not actively collect personal information
Information Collected: Does not actively collect
Privacy Policy: https://github.com/airbnb/lottie-android
Contact: https://github.com/airbnb/lottie-android
(45)
OkHttp3
Third-Party Name: Square, Inc. (United States)
Purpose of Use: HTTP network request framework
Processing Method: Does not actively collect personal information (as a network layer framework, transmitted content is determined by the application layer)
Information Collected: Does not actively collect
Privacy Policy: https://square.github.io/okhttp/
Contact: https://github.com/square/okhttp
(46)
Glide Transformations
Third-Party Name: jp.wasabeef (Open source, GitHub)
Purpose of Use: Image transformation processing (rounded corners, blur, filters, etc.)
Processing Method: Does not actively collect personal information
Information Collected: Does not actively collect
Privacy Policy: https://github.com/wasabeef/glide-transformations
Contact: https://github.com/wasabeef/glide-transformations
(47)
DiscreteScrollView
Third-Party Name: yarolegovich (Open source, GitHub)
Purpose of Use: Horizontal scrolling view component
Processing Method: Does not actively collect personal information
Information Collected: Does not actively collect
Privacy Policy: https://github.com/yarolegovich/DiscreteScrollView
Contact: https://github.com/yarolegovich/DiscreteScrollView
(48)
Baidu Mobile Ads SDK
Third-Party Name: Beijing Baidu Netcom Science Technology Co., Ltd.
Purpose of Use: Ad serving, ad attribution
Processing Method: De-identification, encrypted transmission
Information Collected: Device information (IMEI/MAC/Android ID/OAID), installed application list, network information, geographic location
Privacy Policy: https://union.baidu.com/bqt#/legal/policies
Contact: https://union.baidu.com
(49)
Baidu Ad Network
Third-Party Name: Beijing Baidu Netcom Science Technology Co., Ltd.
Purpose of Use: Ad serving, ad attribution, traffic monetization
Processing Method: De-identification, encrypted transmission
Information Collected: Device information (IMEI/MAC/Android ID/OAID), installed application list, network information
Privacy Policy: https://union.baidu.com/bqt#/legal/policies
Contact: https://union.baidu.com
(50)
oCPC SDK
Third-Party Name: Beijing Baidu Netcom Science Technology Co., Ltd.
Purpose of Use: Ad conversion tracking, campaign optimization
Processing Method: De-identification, encrypted transmission
Information Collected: Device information, application information, ad click/conversion data
Privacy Policy: https://union.baidu.com/bqt#/legal/policies
Contact: https://union.baidu.com
(51)
Baidu oCPX Conversion Tracking SDK
Third-Party Name: Beijing Baidu Netcom Science Technology Co., Ltd.
Purpose of Use: Ad conversion tracking, campaign optimization
Processing Method: De-identification, encrypted transmission
Information Collected: Device information, application information, ad click/conversion data
Privacy Policy: https://union.baidu.com/bqt#/legal/policies
Contact: https://union.baidu.com
(52)
Google Mobile Services
Third-Party Name: Google LLC (United States)
Purpose of Use: Google foundational services (Maps/Sign-in/Push channel), Google Play services framework
Processing Method: De-identification, encrypted transmission
Information Collected: Device information (Android ID/GAID), network information, installed application list
Privacy Policy: https://policies.google.com/privacy
Contact: https://support.google.com
(53)
Firebase
Third-Party Name: Google LLC (United States)
Purpose of Use: Analytics, push messaging (FCM)
Processing Method: De-identification, encrypted transmission
Information Collected: Device identifiers (GAID/AAID), Android ID, application information, network information, IP address, installed application list
Privacy Policy: https://firebase.google.com/support/privacy
Contact: https://support.google.com/firebase
(54)
Alibaba Cloud Object Storage Service (OSS)
Third-Party Name: Alibaba Cloud Computing Co., Ltd.
Purpose of Use: Cloud storage for images and videos
Processing Method: Encrypted transmission
Information Collected: Network information, uploaded file content
Privacy Policy: https://help.aliyun.com/document_detail/31852.html
Contact: https://www.aliyun.com/contact
(55)
Alibaba Cloud OSS Android SDK
Third-Party Name: Alibaba Cloud Computing Co., Ltd.
Purpose of Use: Android client SDK for Alibaba Cloud OSS
Processing Method: Encrypted transmission
Information Collected: Network information, uploaded file content
Privacy Policy: https://help.aliyun.com/document_detail/31852.html
Contact: https://www.aliyun.com/contact
(56)
Huawei Open Device ID Interface
Third-Party Name: Huawei Technologies Co., Ltd.
Purpose of Use: Obtain Huawei device OAID (Open Anonymous Device Identifier)
Processing Method: De-identification, encrypted transmission
Information Collected: Device identifier (OAID)
Privacy Policy: https://developer.huawei.com/consumer/cn/doc/HMSCore-Guides/privacy-statement-0000001050041934
Contact: https://developer.huawei.com/consumer/cn/support
(57)
Huawei HMS Core
Third-Party Name: Huawei Technologies Co., Ltd.
Purpose of Use: Huawei Mobile Services core framework, providing foundational capabilities such as push notifications, account services, and maps
Processing Method: Encrypted transmission
Information Collected: Device information, network information
Privacy Policy: https://developer.huawei.com/consumer/cn/doc/HMSCore-Guides/privacy-statement-0000001050041934
Contact: https://developer.huawei.com/consumer/cn/support
(58)
Performance Acceleration Library
Third-Party Name: Huawei Software Technologies Co., Ltd.
Purpose of Use: Performance optimization and acceleration for Huawei devices
Processing Method: Does not actively collect personal information
Information Collected: Does not actively collect
Privacy Policy: https://developer.huawei.com/consumer/cn/doc/HMSCore-Guides/privacy-statement-0000001050041934
Contact: https://developer.huawei.com/consumer/cn/support
(59)
HMS Core Base SDK
Third-Party Name: Huawei Software Technologies Co., Ltd.
Purpose of Use: Huawei Mobile Services base SDK
Processing Method: De-identification, encrypted transmission
Information Collected: Device information, network information
Privacy Policy: https://developer.huawei.com/consumer/cn/doc/HMSCore-Guides/privacy-statement-0000001050041934
Contact: https://developer.huawei.com/consumer/cn/support
(60)
Petal Ads SDK (Jinghong Kinetic Energy)
Third-Party Name: Huawei Software Technologies Co., Ltd.
Purpose of Use: Ad serving and ad attribution on Huawei devices
Processing Method: De-identification, encrypted transmission
Information Collected: Device information (IMEI/Android ID/OAID), installed application list, network information, geographic location
Privacy Policy: https://developer.huawei.com/consumer/cn/doc/development/HMSCore-Guides/privacy-statement-0000001050041934
Contact: https://developer.huawei.com/consumer/cn/support
(61)
Toutiao Pangolin Alliance SDK
Third-Party Name: ByteDance Co., Ltd.
Purpose of Use: Ad serving, ad attribution, traffic monetization
Processing Method: De-identification, encrypted transmission
Information Collected: Device information (IMEI/MAC/Android ID/OAID), installed application list, network information, geographic location, sensor information
Privacy Policy: https://www.pangle.cn/privacy
Contact: https://www.pangle.cn/contact
(62)
Youlianghui Android SDK
Third-Party Name: Shenzhen Tencent Computer Systems Co., Ltd.
Purpose of Use: Ad serving, ad attribution, traffic monetization
Processing Method: De-identification, encrypted transmission
Information Collected: Device information (IMEI/MAC/Android ID/IDFA), device identifiers (OAID/GAID), installed application list, network information, geographic location
Privacy Policy: https://imgcache.qq.com/rain/taf/ad_platform_sdk/privacy.html
Contact: https://www.tencent.com/zh-cn/contacts.html
(63)
Qiqiaoban Universal (Tencent Ads)
Third-Party Name: Shenzhen Tencent Computer Systems Co., Ltd.
Purpose of Use: Ad serving, ad attribution (Tencent Ads platform)
Processing Method: De-identification, encrypted transmission
Information Collected: Device information, device identifiers, installed application list, network information
Privacy Policy: https://imgcache.qq.com/rain/taf/ad_platform_sdk/privacy.html
Contact: https://www.tencent.com/zh-cn/contacts.html
(64)
Qiqiaoban Universal SDK-Android
Third-Party Name: Shenzhen Tencent Computer Systems Co., Ltd.
Purpose of Use: Ad serving, ad attribution (Tencent Ads platform Android SDK)
Processing Method: De-identification, encrypted transmission
Information Collected: Device information, device identifiers, installed application list, network information
Privacy Policy: https://imgcache.qq.com/rain/taf/ad_platform_sdk/privacy.html
Contact: https://www.tencent.com/zh-cn/contacts.html
(65)
AliFastJson
Third-Party Name: Alibaba (China) Network Technology Co., Ltd.
Purpose of Use: JSON serialization/deserialization framework
Processing Method: Does not actively collect personal information
Information Collected: Does not actively collect
Privacy Policy: https://github.com/alibaba/fastjson
Contact: https://github.com/alibaba/fastjson
(66)
Pangolin Ads SDK
Third-Party Name: Beijing Juliang Engine Network Technology Co., Ltd.
Purpose of Use: Ad serving, ad attribution, traffic monetization
Processing Method: De-identification, encrypted transmission
Information Collected: Device information (IMEI/MAC/Android ID/OAID/GAID), installed application list, network information, geographic location, sensor information
Privacy Policy: https://www.pangle.cn/privacy
Contact: https://www.pangle.cn/contact
(67)
GroMore SDK
Third-Party Name: Beijing Juliang Engine Network Technology Co., Ltd.
Purpose of Use: Ad aggregation management, traffic monetization (GroMore Ad Mediation Platform)
Processing Method: De-identification, encrypted transmission
Information Collected: Device information, device identifiers, installed application list, network information
Privacy Policy: https://www.pangle.cn/privacy
Contact: https://www.pangle.cn/contact
(68)
GroMore Android
Third-Party Name: Beijing Juliang Engine Network Technology Co., Ltd.
Purpose of Use: Ad aggregation management Android SDK
Processing Method: De-identification, encrypted transmission
Information Collected: Device information, device identifiers, installed application list, network information
Privacy Policy: https://www.pangle.cn/privacy
Contact: https://www.pangle.cn/contact
(69)
Pangolin Android
Third-Party Name: Beijing Juliang Engine Network Technology Co., Ltd.
Purpose of Use: Ad serving, ad attribution
Processing Method: De-identification, encrypted transmission
Information Collected: Device information (IMEI/MAC/Android ID/OAID), installed application list, network information, geographic location
Privacy Policy: https://www.pangle.cn/privacy
Contact: https://www.pangle.cn/contact
(70)
Fusion SDK Android
Third-Party Name: Beijing Juliang Engine Network Technology Co., Ltd.
Purpose of Use: Pangolin multi-SDK fusion integration, unified ad management
Processing Method: De-identification, encrypted transmission
Information Collected: Device information, device identifiers, installed application list, network information
Privacy Policy: https://www.pangle.cn/privacy
Contact: https://www.pangle.cn/contact
(71)
Kuaishou Ads
Third-Party Name: Beijing Huayihuilong Network Technology Co., Ltd.
Purpose of Use: Ad serving, ad attribution
Processing Method: De-identification, encrypted transmission
Information Collected: Device information (IMEI/MAC/Android ID), device identifiers (OAID/GAID), installed application list, network information
Privacy Policy: https://u.kuaishou.com/home/privacy
Contact: https://u.kuaishou.com
(72)
Sigmob Ads
Third-Party Name: Beijing Chuangzhi Huiju Technology Co., Ltd.
Purpose of Use: Ad serving, ad attribution
Processing Method: De-identification, encrypted transmission
Information Collected: Device information (IMEI/Android ID/MAC), device identifiers (OAID), installed application list, network information
Privacy Policy: https://www.sigmob.com/policy/privacy.html
Contact: https://www.sigmob.com/contact.html
(73)
Douyin Live SDK
Third-Party Name: Beijing Weibo Shijie Technology Co., Ltd.
Purpose of Use: Douyin live streaming integration, live room display
Processing Method: De-identification, encrypted transmission
Information Collected: Device information, device identifiers, network information, audio and video data
Privacy Policy: https://open.douyin.com/platform-docs/doc/developer/common/consent-and-permission
Contact: https://open.douyin.com
(74)
Douyin Live SDK (Android)
Third-Party Name: Beijing Weibo Shijie Technology Co., Ltd.
Purpose of Use: Douyin Live Streaming Android SDK
Processing Method: De-identification, encrypted transmission
Information Collected: Device information, device identifiers, network information, audio and video data
Privacy Policy: https://open.douyin.com/platform-docs/doc/developer/common/consent-and-permission
Contact: https://open.douyin.com
(75)
Douyin SDK (Android)
Third-Party Name: Beijing Weibo Shijie Technology Co., Ltd.
Purpose of Use: Douyin Open Platform base SDK
Processing Method: De-identification, encrypted transmission
Information Collected: Device information, device identifiers, network information
Privacy Policy: https://open.douyin.com/platform-docs/doc/developer/common/consent-and-permission
Contact: https://open.douyin.com
(76)
Toutiao Rewarded Ads
Third-Party Name: Beijing ByteDance Technology Co., Ltd.
Purpose of Use: Rewarded video ad serving, ad monetization
Processing Method: De-identification, encrypted transmission
Information Collected: Device information (IMEI/MAC/Android ID/OAID), installed application list, network information
Privacy Policy: https://www.pangle.cn/privacy
Contact: https://www.pangle.cn/contact
(77)
libGDX Game Engine
Third-Party Name: libGDX Project Team (Open Source Community)
Purpose of Use: 2D/3D game rendering engine
Processing Method: Does not actively collect personal information
Information Collected: Does not actively collect
Privacy Policy: https://github.com/libgdx/libgdx
Contact: https://github.com/libgdx/libgdx
(78)
Google Gson
Third-Party Name: Google LLC (United States)
Purpose of Use: JSON serialization/deserialization framework
Processing Method: Does not actively collect personal information
Information Collected: Does not actively collect
Privacy Policy: https://github.com/google/gson
Contact: https://github.com/google/gson
(79)
OPPO Account
Third-Party Name: Guangdong Huantai Technology Co., Ltd.
Purpose of Use: OPPO device account login, push notification channel
Processing Method: De-identification, encrypted transmission
Information Collected: Device information, network information, account information
Privacy Policy: https://open.oppomobile.com/new/developmentDoc/info?id=10235
Contact: https://open.oppomobile.com
(80)
Sigmob SDK-Android
Third-Party Name: Beijing Chuangzhi Huiju Technology Co., Ltd.
Purpose of Use: Ad serving, ad attribution
Processing Method: De-identification, encrypted transmission
Information Collected: Device information (IMEI/Android ID/MAC), device identifiers (OAID), installed application list, network information
Privacy Policy: https://www.sigmob.com/policy/privacy.html
Contact: https://www.sigmob.com/contact.html
(81)
Sigmob Android SDK
Third-Party Name: Beijing Chuangzhi Huiju Technology Co., Ltd.
Purpose of Use: Ad serving, ad attribution
Processing Method: De-identification, encrypted transmission
Information Collected: Device information (IMEI/Android ID/MAC), device identifiers (OAID), installed application list, network information
Privacy Policy: https://www.sigmob.com/policy/privacy.html
Contact: https://www.sigmob.com/contact.html
(82)
Kuaishou Alliance (Android)
Third-Party Name: Beijing Kuaishou Technology Co., Ltd.
Purpose of Use: Ad serving, ad attribution, traffic monetization
Processing Method: De-identification, encrypted transmission
Information Collected: Device information (IMEI/MAC/Android ID), device identifiers (OAID/GAID), installed application list, network information
Privacy Policy: https://u.kuaishou.com/home/privacy
Contact: https://u.kuaishou.com
(83)
Honor Push SDK
Third-Party Name: Shenzhen Honor Software Technology Co., Ltd.
Purpose of Use: System-level push notifications on Honor devices
Processing Method: De-identification, encrypted transmission
Information Collected: Device information (OAID/device model/OS version), application information, network information
Privacy Policy: https://developer.hihonor.com/cn/doc/guides/100360
Contact: https://developer.hihonor.com/cn/
(84)
Mobile Smart Terminal Supplementary Device Identifier Unified Invocation SDK
Third-Party Name: China Academy of Information and Communications Technology (CAICT / Tel Lab)
Purpose of Use: Obtain OAID (Open Anonymous Device Identifier) as an alternative to IMEI for device identification
Processing Method: De-identification, encrypted transmission
Information Collected: Device identifier (OAID)
Privacy Policy: No standalone privacy policy; must be declared in the App's privacy policy
Contact: http://www.caict.ac.cn
(85)
Qumeng Advertising SDK
Package Name: com.qumeng.advlib
Third-party Entity: Shanghai Yunxi Information Technology Co., Ltd.
Purpose of Use: Used for ad delivery and ad delivery effect analysis.
Processing Method: Processed securely via de-identification and encrypted transmission.
Collected Information: Device brand, model, software system version, screen density, screen resolution, device language, device time zone, available storage space size, CPU serial number, hardware type, OAID, Boot ID, Wi-Fi status, carrier information, application package name, version number, application foreground/background status, application installation list information, accelerometer sensor, gyroscope sensor.
Official Website Link:
https://docs.yunxish.com/privacy/common/privacy-agreement.html
(86)
Shanghai Lingye SDK
Package Name: cj.mobile
Third-party Entity: Shanghai Lingye Information Technology Co., Ltd.
Purpose of Use: Used for ad delivery and ad delivery effect analysis.
Processing Method: Processed securely via de-identification and encrypted transmission.
Collected Information:
Device Information: Device brand, model, network status, operating system version, sensor information (e.g. gravity sensor, accelerometer, orientation sensor, gyroscope, pressure sensor, linear acceleration sensor, light sensor, sensor list); IMEI (Device ID), MAC address, Android_ID, OAID, IDFV, IDFA, resolution and other basic device information.
Application Information: Application name, application package name, application version number, application installation list.
Official Website Link:
https://manage.shanghailingye.cn/privacy
(87)
Fancy SDK
Package Name: com.ptg.adsdk
Third-party Entity: Beijing Fanwei Information Technology Co., Ltd.
Purpose of Use: Used for ad delivery and ad delivery effect analysis.
Processing Method: Processed securely via de-identification and encrypted transmission.
Collected Information:
Device Information:
Mandatory Information: [Both Platforms] Device brand, model, software system version, screen density, screen resolution, SIM card information (MCC & MNC) and other basic information.
[Android Only] AndroidID, OAID
[iOS Only] Mobile system reboot time, total disk space, total system memory space, IDFV
[Both Platforms] Carrier information, Wi-Fi status
[Both Platforms] IP address
[Android Only] Application package name, running process information, version number, foreground/background status of the current application
[iOS Only] Application package name, version number, foreground/background status of the current application
Optional Information:
[Android Only] Device MAC address
[Android Only] Device identifiers (such as IMEI, GAID (GMS service only); specific fields vary by hardware and software version)
[iOS Only] Device identifiers (such as IDFA; specific fields vary by hardware and software version)
[Android Only] Application installation list
[Both Platforms] Available storage space size
[Both Platforms] Accelerometer sensor, gyroscope sensor
[Both Platforms] Precise location information and coarse location information
[Both Platforms] Crash data, performance data
Official Website Link:
https://static.fancyapi.com/fancysdk/privacyagreement/index.html
(88)
iQIYI Advertising SDK
Package Name: com.mcto.sspsdk
Third-party Entity: Beijing iQIYI Technology Co., Ltd.
Purpose of Use: Used for ad delivery and ad delivery effect analysis.
Processing Method: Processed securely via de-identification and encrypted transmission.
Collected Information:
Device Information
[Both Platforms] Device brand, model, system version, MAC address, device language, network type, WiFi name, IP address, battery capacity, physical memory, hard disk capacity, system language, carrier information and other basic information.
[Android Only] CPU type, IMEI, AndroidID
[iOS Only] Carrier information, boot time, system update time, disk capacity, CPU quantity, memory capacity, device name, region name, time zone, OpenUdid, IDFV
Information provided optionally for ad delivery optimization:
[Android Only] OAID
[iOS Only] IDFA
Application Information:
[Android Only]: Application name, package name, version number
[iOS Only]: Application bundleId
Information provided optionally for ad delivery optimization:
[Android Only] Application list information
Official Website Link:
https://union.iqiyi.com/platform/privacyPolicy
(89)
Qingyun Advertising SDK
Package Name: com.qy.sdk
Third-party Entity: Beijing Yunyun Technology Co., Ltd.
Purpose of Use: Used for ad delivery and ad delivery effect analysis.
Processing Method: Processed securely via de-identification and encrypted transmission.
Collected Information:
Device Information
[Both Platforms] Device manufacturer, device model, operating system version, screen resolution, screen orientation, screen DPI, IP address, accelerometer
[Android Only] Magnetic field sensor
[iOS Only] Device name, system startup time, system language, disk space, gyroscope, pressure sensor and other basic information
Coarse Location Information
[Android Only] Base stations, nearby Wi-Fi, connected Wi-Fi.
Information that third-party developers may choose to provide to this SDK:
[Both Platforms] Precise location information
Mandatory Information:
[Both Platforms] Device brand, model, software system version, screen density, screen resolution, device language, device time zone, SIM card information, CPU information, available storage space size and other basic information.
[Android Only] AndroidID, OAID
[iOS Only] Mobile system reboot time, total disk space, total system memory space, IDFV
Optional Information:
[Both Platforms] Wi-Fi SSID name, Wi-Fi router MAC address (BSSID), device MAC address (for iOS only applicable to iOS versions below 3200)
[Android Only] Device identifiers (such as IMEI, IMSI, ICCID, GAID (GMS service only), MEID, device serial number build_serial; specific fields vary by hardware and software version)
[iOS Only] Device identifiers (such as IDFA; specific fields vary by hardware and software version)
Application Information [Both Platforms] Package name and version number of the host application
[Android Only] Process name, running status and suspicious behavior of the host application
Official Website Link:
https://ssp.qyzss.com/privacy.html