Home > Third-Party SDK List

Sdk list

List of third-party SDK

When providing services to users, Saada will also use the following SDK technologies. When you view the web pages created by third parties or use applications developed by third parties, these third parties may put their own cookies or use other technical means. These cookies or other technical means are not under our control and their use is not subject to this policy. In order to ensure your information security to the greatest extent, we recommend that you check the privacy terms of any third-party SDK service before using it. In order to protect your legitimate rights and interests, if you find that there are risks in such SDK or other similar applications, we suggest that you immediately stop relevant operations and contact us in time.

In order to provide you with more services, continuously optimize the stability of our services, improve service quality or upgrade related functions, we may adjust the third-party SDK we access and update the SDK directory. We will strictly abide by relevant laws, regulations and regulatory requirements, and evaluate the legality, legitimacy and necessity of third-party SDK to collect your personal information before accessing SDK, so as to protect your personal information. You can view the data usage and protection rules of third parties through related links. Please note that the third-party SDK may change its personal information processing type due to version upgrade, policy adjustment and other reasons. Please refer to its official description. The following is the specific information of the third-party SDK:

HXPhotoPicker

Personal information: visiting photo albums and saving pictures to photo albums.

Purpose: The video/picture selector that users need to use when uploading pictures/videos.

Usage scenarios: uploading the head portrait, uploading the background map of the hall, sending pictures in private message conversations, and uploading pictures when the news is released.

Client: IOS

Collection method: SDK collects by itself.

Official website Link: https://github.com/SilenceLove/HXPhotoPicker

AgoraRtcEngine_Special_iOS

Personal information: information related to terminal personal user equipment and network collected by customers, including microphone information, CPU status, memory status, battery status, system version, mobile phone model, mobile phone signal level, received signal strength indicator (RSSI), network type, user attributes, channel attributes, Bluetooth and call status.

Purpose: users can use it when serving wheat.

Usage scenario: Push the wheat when it is served.

Client: IOS

Collection method: SDK collects by itself.

Official website Link: https://doc.shengwang.cn/basics/security/information

TXLiteAVSDK_TRTC

Personal information: information related to terminal personal user equipment and network collected by customers, including microphone information, CPU status, memory status, battery status, system version, mobile phone model, mobile phone signal level, received signal strength indicator (RSSI), network type, user attributes and room attributes.

Purpose: users can use it when serving wheat.

Usage scenario: Push the wheat when it is served.

Client: Android

Collection method: SDK collects by itself.

Official website Link: https://cloud.tencent.com/document/product/647/86362

Firebase/Analytics

Personal information: mobile advertisement ID, IDFV, Android ID, Firebase installation ID and analysis application instance ID.

Purpose: Use these data to provide analysis and attribution information.

Usage scenario: During the user's use of the APP.

Client: Android, IOS

Collection method: SDK collects by itself.

Official website Link: https://firebase.google.com/support/privacy? hl=zh-cn

Firebase/Performance

Personal information: Firebase installation ID and IP address.

Purpose: Use the Firebase installation ID to calculate the number of unique Firebase installations accessing network resources, so as to ensure that the access mode is completely anonymous. It also uses the Firebase installation ID with Firebase Remote Config to manage the reporting rate of performance events. In addition, it uses IP addresses to map performance events to their countries of origin.

Usage scenario: During the user's use of the APP.

Client: Android, IOS

Collection method: SDK collects by itself.

Official website Link: https://firebase.google.com/support/privacy? hl=zh-cn

Firebase/Messaging

Personal information: Firebase installation ID.

Purpose: Use the Firebase installation ID to determine which devices to send messages to.

Usage scenario: used when sending messages to devices.

Client: Android, IOS

Collection method: SDK collects by itself.

Official website Link: https://firebase.google.com/support/privacy? hl=zh-cn

Firebase/Crashlytics

Personal information: Crashlytics installation UUID, Firebase installation ID, crash trajectory, data in the format of Breakpad mini dump (NDK crash only).

Purpose: Use the crash stack trajectory to associate the crash with the project, send e-mail reminders to project members and display this information in the Firebase console to help Firebase customers debug the crash. It uses Crashlytics to install UUID to measure the number of users affected by the crash, and uses small dump data to handle the NDK crash. The system stores the minidump data when the crashed session is processed, and discards it after processing. In the future, the system will use the Firebase installation ID to enable the upcoming crash reporting and crash management service enhancements.

Usage scenario: used when the application crashes.

Client: Android, IOS

Collection method: SDK collects by itself.

Official website Link: https://firebase.google.com/support/privacy? hl=zh-cn

Firebase/Auth

Personal information: e-mail address, password, telephone number, user agent, IP address.

Purpose: Use these data to enable end-user authentication and help end-user account management. It also uses user agent strings and IP addresses to improve security and prevent abuse during registration and authentication.

Usage scenario: used when authenticating users.

Client: Android, IOS

Collection method: SDK collects by itself.

Official website Link: https://firebase.google.com/support/privacy? hl=zh-cn

Adjust

Personal information: traffic data, geographical location, service log, IP address, operating system, cookie, information collected by network identification and other tracking technologies, and GAID.

Purpose: identify user identity information.

Usage scenario: used when authenticating users.

Client: Android, IOS

Collection method: SDK collects by itself.

Official website Link: https://www.adjust.com/terms/privacy-policy/

ForterSDK

Personal information: IP address, device type, geographical location and information about the user's operating system and language preference.

Purpose: guarantee products and services.

Usage scenario: During the user's use of the APP.

Client: Android, IOS

Collection method: SDK collects by itself.

Official website Link: https://www.forter.com/privacy-policy/

GoogleSignIn

Personal information: device ID, IMEI, MEID, device type, operating system, mobile network information (including operator's name and telephone number) and application version number, and information related to the interaction between the application and Google service, including IP address, crash report, system activity, date and time of corresponding request and URL of referral source.

Purpose: to provide registration/login services.

Usage scenario: used during registration/login.

Client: Android, IOS

Collection method: SDK collects by itself.

Official website Link: https://policies.google.com/privacy? gl=CN&hl=zh-CN#infocollect

Google Pay

Personal information: device ID, IMEI, MEID, device type, operating system, mobile network information (including operator's name and telephone number) and application version number, and information related to the interaction between the application and Google service, including IP address, crash report, system activity, date and time of corresponding request, referral source URL and GAID.

Purpose: to provide registration/login services.

Usage scenario: used during registration/login.

Client: Android, IOS

Collection method: SDK collects by itself.

Official website Link: https://policies.google.com/privacy? gl=CN&hl=zh-CN#infocollect

FBSDKLoginKit

Personal information: device attributes (including operating system, hardware and software versions, battery capacity, signal strength, available storage space, names and types of applications and files), device operations (including information about operations performed on services and pages visited), device ID, IMEI, MEID, network and connection, name, language, time zone, mobile phone number, IP address and service provider. Information about other devices nearby or on the network, and information about Wi-Fi hotspots connected by users use our services, Cookie data, Cookies stored on user devices and other similar technologies, including Cookie ID and settings, and GAID.

Purpose: to provide registration/login services.

Usage scenario: used during registration/login.

Client: Android, IOS

Collection method: SDK collects by itself.

Official website Link: https://opensource.fb.com/legal/privacy/

TikTokOpenSDKCore

Personal information: Information of IP address, country/region, language and application program.

Purpose: to provide registration/login services.

Usage scenario: used during registration/login.

Client: Android, IOS

Collection method: SDK collects by itself.

Official website link: https://ads.tiktok.com/i18n/official/policy/business-products-terms.

TikTokOpenAuthSDK

Personal information: Information of IP address, country/region, language and application program.

Purpose: to provide registration/login services.

Usage scenario: used during registration/login.

Client: Android, IOS

Collection method: SDK collects by itself.

Official website link: https://ads.tiktok.com/i18n/official/policy/business-products-terms.

GeeGuardSDK

Personal information: equipment system, equipment model, equipment brand, equipment screen size, IDFA, IDFV and location information, jailbreak logo, simulator logo, debugging logo, package name, etc.

Purpose: to generate user equipment identification id.

Usage scenario: used when authenticating users.

Client: Android, iOS

Collection method: SDK collects by itself.

@2020 FUNI PTE.LTD
Privacy PolicyTerms of Service