Third-Party SDK Collection and Use of Information

Version: V1.1

Updated: August 18, 2026

Effective: August 18, 2026

To ensure the stable operation of the Blooming Talk (hereinafter referred to as "this Product") client and the realization of its features, and to enable you to use and enjoy more services and functions, we embed software development kits (SDKs) or similar application programming interfaces from authorized partners in the App. We will exercise due care and conduct strict security monitoring of SDKs that obtain information from partners, in order to protect data security. The third-party SDKs we integrate mainly serve you and other users. Therefore, when new service needs arise or business functions change, we may adjust the third-party SDKs we integrate, and we will promptly disclose the latest information about such integrations. The third-party SDKs integrated into this Product are listed below:

This description forms part of the Privacy Policy. If this description is inconsistent with the Privacy Policy, the latest versions of this description and the Privacy Policy shall prevail.

  1. Tencent Cloud IM Push (timpush 8.3.6498) + tuicore

    Operator: Tencent Cloud Computing (Beijing) Co., Ltd.

    Purpose: Push notifications

    Use case: When sending in-app instant messages and notifications to users

    Collection method: Collected by the SDK itself

    Types of personal information collected: Network connection status, device model, system version

    Privacy policy: View

  2. Huawei Push SDK (HMS Push 6.12.0.300)

    Operator: Huawei Software Technologies Co., Ltd.

    Purpose: Push notifications

    Use case: When sending push messages to users of Huawei devices

    Collection method: Collected by the SDK itself

    Types of personal information collected: Device-related information (HMS Core openId), application Token, Topic subscription relationships, cached messages, message delivery records, PushToken, AAID (app anonymous identifier), Token application records, display/click/close analytics records, application ID, application package name, server public IP address

    Privacy policy: View

  3. Xiaomi Push SDK

    Operator: Beijing Xiaomi Mobile Software Co., Ltd.

    Purpose: Push notifications

    Use case: When sending push messages to users of Xiaomi devices

    Collection method: Collected by the SDK itself

    Types of personal information collected: Device-related information (including IMEI, OAID (for Android Q and above), IMEI MD5, MEIDMD5, Android ID, VAID, AAID, user MID (for MIUI systems), device model, etc.)

    Privacy policy: View

  4. OPPO Push SDK

    Operator: Guangdong HeyTap Technology Co., Ltd.

    Purpose: Push notifications

    Use case: When sending push messages to users of OPPO devices

    Collection method: Collected by the SDK itself

    Types of personal information collected: Device-related information (such as IMEI, Serial Number, IMSI, User ID, Android ID, Google Advertising ID, phone Region settings, device model, battery level, mobile OS version and language, etc.), information about apps using the push service, push SDK version number, network-related information, message sending results

    Privacy policy: View

  5. vivo Push SDK

    Operator: Vivo Mobile Communication Co., Ltd.

    Purpose: Push notifications

    Use case: When sending push messages to users of vivo devices

    Collection method: Collected by the SDK itself

    Types of personal information collected: Device identifier information (such as IMEI), phone model, system type, system version

    Privacy policy: View

  6. Honor Push SDK

    Operator: Honor Device Co., Ltd.

    Purpose: Push notifications

    Use case: When sending push messages to users of Honor devices

    Collection method: Collected by the SDK itself

    Types of personal information collected: Device identifiers (AAID, PushToken, OAID), push message content

    Privacy policy: View

  7. Apple Push Notification service (iOS only)

    Operator: Apple Inc.

    Purpose: Push notifications

    Use case: When sending push messages to users of iOS devices

    Collection method: Collected by the SDK itself

    Types of personal information collected: Device token (e.g. device token), phone model, system version

    Privacy policy: View

  8. Alipay SDK 15.8.35

    Operator: Alipay.com Co., Ltd.

    Purpose: Subscription payments

    Use case: When the user completes a subscription payment with Alipay

    Collection method: Collected by the SDK when the user initiates a payment

    Types of personal information collected: Order information, device information

    Privacy policy: View

  9. WeChat Open SDK 6.8.34

    Operator: Shenzhen Tencent Computer Systems Company Limited

    Purpose: Subscription payments and sharing

    Use case: When the user completes a subscription payment with WeChat Pay, or shares content to WeChat

    Collection method: Collected by the SDK when the user initiates a payment or share

    Types of personal information collected: Order information, device information

    Privacy policy: View

  10. PictureSelector v3.11.2 (including compress / ucrop)

    Provider: Open-source project (lucksiege)

    Purpose: Photo selection, cropping, and compression

    Use case: When the user selects photos from the album, or crops or compresses images

    Collection method: Processed locally on the device after the user selects photos

    Types of personal information collected: Photos actively selected by the user. This is an open-source component processed locally on the device only; personal information is not transmitted to the SDK provider

    Official link: View

  11. Sentry Android 8.16.0

    Operator: Functional Software, Inc. (Sentry)

    Purpose: Crash and error diagnostics

    Use case: When the App crashes or encounters an exception that requires diagnosis

    Collection method: Collected by the SDK itself

    Types of personal information collected: Device information, IP address, error logs

    Privacy policy: View

  12. Firebase Messaging / Analytics / Auth / Dynamic Links, Play Services Auth 21.2.0

    Operator: Google LLC

    Purpose: Push notifications, usage analytics, third-party login

    Use case: During push notifications, usage analytics, and third-party account login

    Collection method: Collected by the SDK itself

    Types of personal information collected: Unique device identifiers, device type and settings, operating system, mobile network information, app version number, IP address, crash reports, system activity and the date, time and referrer URL of corresponding requests, carrier name, apps you have installed, other information about how you use Android devices (depending on your device settings), usage logs, account identifiers

    Privacy policy: View View

  13. Google Play Billing 9.1.0

    Operator: Google LLC

    Purpose: Google-channel payments

    Use case: When the user initiates a subscription payment through the Google channel

    Collection method: Collected by the SDK when the user initiates a payment

    Types of personal information collected: Order information

    Privacy policy: View

  14. Google Play Services Location 21.3.0

    Operator: Google LLC

    Purpose: Location services

    Use case: When using location-based services in the App

    Collection method: Collected by the SDK itself

    Types of personal information collected: Location information

    Privacy policy: View

  15. Silero VAD / ExoPlayer / FFmpeg / LightCompressor / Glide / Lottie and other open-source components

    Provider: Open-source projects

    Purpose: Local media processing (playback, compression, animation)

    Use case: When playing, compressing, or displaying audio/video or animations locally on the device

    Collection method: Processed only on the device

    Types of personal information collected: No personal information collected. These are open-source components processed locally on the device only; personal information is not transmitted to our servers or third parties, nor to the SDK providers