# FinClip SDK Usage List
Effective Date of This Version: July 14, 2021
Last Updated Date of This Version: October 19, 2023
We will periodically update this list to more clearly demonstrate how FinClip cooperates with third parties or uses third-party features to enhance the FinClip product and service experience. We will conduct audits on the integration and usage of SDKs that align with the common capabilities of the internet industry to safeguard your personal information security.
Please also understand that even though we strive to update this list promptly, it may still lag behind the actual usage of FinClip under certain circumstances. Please note that third-party SDKs may have changes in data processing types due to version upgrades, policy adjustments, etc. Please refer to their official announcements for specific details.
What is an SDK
SDK stands for Software Development Kit. It typically refers to a collection of development tools used to create application software for specific software packages, software frameworks, hardware platforms, operating systems, etc.
# 1. Information Collected by the FinClip Mini-Program SDK
Friendly Reminder
When you use FinClip to obtain Mini-Program runtime capabilities, the FinClip Mini-Program SDK may request privacy or data permissions from you based on the Mini-Program business needs. The following is the relevant content regarding the information collected by the FinClip Mini-Program SDK (you can also click here for more details).
| SDK Name | Function Type | Purpose of Use | Data Types Collected | Third-Party Privacy Policy Link |
|---|---|---|---|---|
| FinClip Mini-Program SDK | Mini-Program Container | Providing an independent and secure Mini-Program SDK within the App | Mobile terminal identification information, IP, MAC address; System type, system version, mobile phone manufacturer, mobile phone model | https://super-apps.ai/mop/document/operate/privacy-policy.html |
# 2. SDK Usage List (Web Services)
Friendly Reminder
When you use the FinClip SaaS environment, we may use the following SDKs in the Web端 (www.finclip.com) for data analysis or user experience optimization. The following lists the names of the third-party SDKs and the relevant content of the information they collect.
Please Note
The following environments only exist in the FinClip SaaS environment. The Community Edition and Private Deployment versions you use do not contain the following SDKs.
| SDK Name | Third-Party Vendor Name | Function Type | Purpose of Use | Data Types Collected | Third-Party Privacy Policy Link |
|---|---|---|---|---|---|
| Baidu Tongji | Beijing Baidu Netcom Science Technology Co., Ltd. | Data Statistics & Error Analysis | Using Baidu web and mobile statistics to optimize the FinClip user experience, recording error logs | Device identification information, geographic location, network information | https://tongji.baidu.com/web/help/article?id=330 |
| WeChat Open Platform | Shenzhen Tencent Computer Systems Co., Ltd. | Social Sharing & Third-Party Payment | Sharing content from the application to WeChat friends and Moments, supporting WeChat Pay capabilities | Device identification information | https://support.weixin.qq.com/cgi-bin/mmsupportacctnodeweb-bin/pages/ONwPihxKd82RAkIJ |
| Posthog | PostHog Inc | Data Statistical Analysis | Recording error analysis, optimizing the FinClip user experience | Device identification information, network information | https://posthog.com/privacy |
| Google Analytics | Google LLC | Data Statistical Analysis | Using Google Analytics to optimize the FinClip user experience | Device identification information, geographic location, network information | https://policies.google.com/privacy?hl=zh-CN |
| Hotjar | Hotjar Ltd | Data Statistical Analysis | Using Hotjar to optimize the FinClip user experience | Device identification information, network information | https://www.hotjar.com/legal/policies/privacy/ |
# 3. SDK Usage List (App Products)
Friendly Reminder
When you use the FinClip SaaS environment, we may use the following SDKs in the Mobile端 APP for data analysis or user experience optimization. The following lists the names of the third-party SDKs and the relevant content of the information they collect.
Please Note
The following environments only exist in the FinClip SaaS environment. The Community Edition and Private Deployment versions you use do not contain the following SDKs.
| SDK Name | Third-Party Vendor Name | Function Type | Purpose of Use | Data Types Collected | Third-Party Privacy Policy Link |
|---|---|---|---|---|---|
| Baidu Tongji | Beijing Baidu Netcom Science Technology Co., Ltd. | Data Statistical Analysis | Optimizing the FinClip user experience | Device identification information, geographic location, network information | https://tongji.baidu.com/web/help/article?id=330 |
| WeChat Open Platform | Shenzhen Tencent Computer Systems Co., Ltd. | Social Sharing, Third-Party Payment | Supporting WeChat authorization sharing and WeChat Pay | Device identification information | https://support.weixin.qq.com/cgi-bin/mmsupportacctnodeweb-bin/pages/ONwPihxKd82RAkIJ |
| Number Authentication | Shenzhen Tencent Computer Systems Co., Ltd. | One-Click Login with Phone Number | Optimizing the FinClip APP user experience | Network information | https://cloud.tencent.com/document/product/1415/65372 |
| Mobile Push TPNS | Shenzhen Tencent Computer Systems Co., Ltd. | Mobile Message Push | See Appendix 2.2 content | Device identification information, network information, application information, application data | https://privacy.qq.com/document/preview/8565a4a2d26e480187ed86b0cc81d727 |
| AMap (Gaode Map) | Gaode Software Co., Ltd. | Map Capabilities | Demonstration and invocation of map-related capabilities | Geographic location information | https://lbs.amap.com/pages/privacy/ |
| Baidu Map | Beijing Baidu Netcom Science Technology Co., Ltd. | Map Capabilities | Demonstration and invocation of map-related capabilities | Geographic location information | https://lbsyun.baidu.com/index.php?title=openprivacy |
| Tencent Map | Shenzhen Tencent Computer Systems Co., Ltd. | Map Capabilities | Demonstration and invocation of map-related capabilities | Geographic location information | https://lbs.qq.com/userAgreements/agreements/privacy |
| Agora Interactive Live Streaming | Shanghai Zhaoyan Network Technology Co., Ltd. | Live Streaming Capabilities | Optimizing the FinClip user experience | Device identification information, network information, microphone, camera information | https://doc.shengwang.cn/basics/security/privacy |
| Mobile Authentication | China Mobile (Suzhou) Software Technology Co., Ltd. | One-Click Login | Optimizing the FinClip user experience | Device identification information, network information | https://ecloud.10086.cn/op-help-center/doc/article/27419 |
| Alipay Share SDK | Alipay (China) Network Technology Co., Ltd. | Sharing | Enhancing FinClip functionality | Device identification information, network information | https://opendocs.alipay.com/open/54/104508 |
# 4. Details of Personal Information Obtained by Third-Party SDKs
# 4.1 Personal Information Obtained by the Baidu Tongji SDK
| Information Type | Purpose of Use | Usage Scenario |
|---|---|---|
| Device Information & Log Information | To help developers use statistical and analytical services, enabling them to understand how their end users use their mobile applications. | SDK Direct Collection |
| Application List Information & Device Information | To help developers track the activity of various mobile applications on the end user's device, enabling them to analyze and optimize the functionality and experience of their mobile applications. | SDK Direct Collection |
| Content such as passwords, links, etc., in the Clipboard | To help developers provide end users with information jump and sharing functions, allowing users to share information or receive shared information. | SDK Direct Collection |
# 4.2 Personal Information Obtained by the WeChat Open Platform SDK
| Information Type | Purpose of Use | Usage Scenario |
|---|---|---|
| Images or content actively selected by the user in a third-party application | To allow users to use the Share/Add to Favorites to WeChat function, sharing images and other content to WeChat Moments or WeChat Favorites. | When the user triggers the share function. |
| WeChat avatar and nickname information actively selected by the user | To allow users to log in to third-party applications using their WeChat avatar and nickname. | After user authorization. |
| WeChat Pay order identifier generated by the third-party application when the user initiates a payment, and the status information of whether the payment was successful after the user performs the payment operation. | To allow users to use the WeChat Pay function within third-party applications. | When the user triggers WeChat Pay. |
# 4.3 Personal Information Obtained by the Number Authentication SDK
| Information Type | Purpose of Use | Usage Scenario |
|---|---|---|
| Network Type | Collected to determine whether the current network is Wi-Fi or cellular data, used for precise number retrieval. | Collected when implementing one-click phone number authentication for registration/login. |
| Wi-Fi Type | Collected to determine the current network status, used for specific scenarios in number retrieval. | Collected when implementing one-click phone number authentication for registration/login. |
| Carrier Information | Collected to determine carrier attribution. | Collected when implementing one-click phone number authentication for registration/login. |
| IMSI (Android only) | Required for business logic processing (identifying dual SIM cards and SIM card changes). | Collected when implementing one-click phone number authentication for registration/login. |
| Phone Model | Collected to determine the terminal type, used to determine the terminal adaptation solution for one-click login. | Collected when implementing one-click phone number authentication for registration/login. |
| IP Address | Used when calling the SDK pre-fetch number interface and the get one-click login or verification token interface. | Collected when implementing one-click phone number authentication for registration/login. |
| IDFV (iOS only) | Used for issue localization. | Collected when implementing one-click phone number authentication for registration/login. |
# 4.4 Personal Information Obtained by the Mobile Push TPNS SDK
| Information Type | Purpose of Use | Usage Scenario |
|---|---|---|
| Manufacturer, Model | Used to determine the user's phone type, routing through different manufacturer channels accordingly. | Identifying user channels during push. |
| Android/iOS System Version | Supports third parties in pushing different message content based on different system versions. | Pushing tags. |
| System Language | Supports third parties in pushing content in different languages based on the system language. | Pushing to devices. |
| Device Resolution | Supports pushing different images based on different resolutions. | When performing pushes involving images. |
| Timezone | Supports global push, planning timed pushes for different time zones. | When sending scheduled pushes or pushes to different time zones. |
| Device Boot Time | Determines if the device is powered on for intelligent pushing. Caches messages when the device is off, pushes immediately when the device boots. | When caching messages for offline push. |
| Country Code | Supports pushing different message content to different countries. | When performing regional pushes. |
| Network Type (e.g., Wi-Fi, 3G, 4G) | Supports pushing videos in Wi-Fi environments and text/images in other environments. | During push operations. |
| Device Information (Phone model, kernel parameters, SDCard info, etc.) | a. Used for user device statistics for push and setting SDK cache size to avoid oversized cache affecting push functionality; b. Used to determine if it's a real device, filtering out virtual machines during push to prevent black industry and external malicious attacks. | a. Throughout the SDK operation; b. When establishing a push connection to identify the device. |
| Network Status | Used to determine if the device is online. If online, push immediately; if offline, cache the message. | When establishing a push connection to identify the device. |
| RAM, ROM | a. Used to identify device memory and storage size, selecting the optimal resolution during push to improve push effectiveness; b. Used to determine if it's a real device, filtering out virtual machines during push to prevent black industry and external malicious attacks. | a. During SDK initialization and push delivery; b. When establishing a push connection to identify the device. |
| IDFV | a. Pushing based on IDFV; b. Used to determine if it's a real device, filtering out virtual machines during push to prevent black industry and external malicious attacks. | a. When pushing based on IDFV; b. When establishing a push connection to identify the device. |
| Notification Bar Switch Status | Used to determine the notification bar status; do not push to applications where it is turned off. | Determining whether to push. |
| Third-Party App Version | Supports third parties in pushing different message content based on different versions. | When performing tag pushes and push user statistics. |
| Terminal IP | Used for network link optimization. | Throughout the entire process of terminal user push link access. |
| Carrier Code | Used to determine network type and status, allowing devices to connect nearby, shortening the push path, and improving push efficiency. | Throughout the entire process of terminal user push link access. |
| Data generated during the push process (delivery, click, exposure, etc.) | Used for push statistics and error analysis. | When performing push business data statistics. |
# 4.5 Personal Information Obtained by the AMap (Gaode Map) SDK
| Information Type | Purpose of Use | Usage Scenario |
|---|---|---|
| Location Information (latitude and longitude, precise location, approximate location) | To return the user's location information to the application and allow developers to provide corresponding services based on the user's location; to facilitate the provision of real-time traffic and traffic prediction services, we perform data statistics and analysis on the user's location information and make judgments on traffic congestion based on this. | When the user triggers the location and map function. |
| Device Information (such as IP address, GNSS information, WiFi status, WiFi parameters, WiFi list, SSID, BSSID, base station information, WiFi signal strength information, Bluetooth information, sensor information (vector, acceleration, pressure), device signal strength information, external storage directory) | To help developers provide location and assisted location services to users, achieving more accurate location information for the developer's end users. | When the user triggers the location and map function. |
| Device Identification Information (IDFA, OAID), Current Application Information (application name, application version), Device Parameters and System Information (system properties, device model, operating system, carrier information) | To improve the accuracy and success rate of location services, track, troubleshoot, diagnose, and statistically analyze various issues in the service, ensuring the secure and normal operation of products and services. | When the user triggers the location and map function. |
# 4.6 Personal Information Obtained by the Baidu Map SDK
| Information Type | Purpose of Use | Usage Scenario |
|---|---|---|
| Device Information (including device identification information (Android ID, IDFA, IDFV), system information (operating system version, device brand and model, device configuration) and application information (application name), external storage directory) | To improve the accuracy and success rate of location services, provide continuous location services for specific continuous location scenarios, and provide you with issue tracking, troubleshooting, and diagnosis services, and perform data statistics to ensure the secure and normal operation of products and services. | When the user triggers the location and map function. |
| Location Information (may include latitude and longitude, GNSS information, WiFi gateway address, BSSID, SSID, WiFi signal strength, WiFi status, WiFi parameters, WiFi list, base station ID data information, carrier information, device signal strength information, IP address, Bluetooth information, and sensor information (acceleration, gyroscope, direction, pressure, rotation vector, light, magnetometer)) | To return your precise or approximate location information to the developer's application, helping the developer provide you with related services based on your location information. Sensor information is only used in specific continuous location scenarios like tunnels to provide you with continuous location services. | When the user triggers the location and map function. |
| Network Information (such as mobile network, WiFi network) | To improve the accuracy and success rate of location services, provide you with issue tracking, troubleshooting, and diagnosis services, and perform data statistics to ensure the secure and normal operation of products and services. | When the user triggers the location and map function. |
# 4.7 Personal Information Obtained by the Tencent Map SDK
| Information Type | Purpose of Use | Usage Scenario |
|---|---|---|
| OAID | User positioning, handling user feedback on positioning issues and anti-cheating. | User positioning. |
| IDFV | User positioning, handling user feedback on positioning issues and anti-cheating. | User positioning. |
| System Properties | Handling positioning strategies for different system properties. | User positioning, adapting to the processing strategies of positioning raw information by different phone manufacturers, preventing SDK crashes and significant drops in positioning accuracy due to incompatible system properties, ensuring the SDK works normally on all models. |
| Operating System and Version | Handling positioning strategies for different system versions. | User positioning, determining the system version to avoid SDK crashes and significant drops in positioning accuracy due to different system interfaces, ensuring the SDK works normally on all systems. |
| System Settings | Handling positioning strategies based on whether the user's location service switch is turned on. | User positioning, preventing system crashes due to incompatible SDK integration versions, while providing more reasonable positioning capabilities under different settings, troubleshooting positioning failure issues. |
| Device Model | Compatible with positioning strategies of different phone manufacturers. | User positioning, adapting to the processing strategies of positioning raw information by different phone manufacturers, preventing SDK crashes and significant drops in positioning accuracy due to incompatible integration models, ensuring the SDK works normally on all models. |
| Carrier Base Station Information (Cell id) | Providing location services to users. | User positioning. |
| WiFi Information (WiFi status, WiFi parameters, nearby WiFi list, connected WiFi) | Providing location services to users. | User positioning. |
| Sensor Information (gravity sensor, gyroscope sensor, acceleration sensor, magnetic field sensor, rotation vector sensor) | Auxiliary positioning function, deducing and predicting location points when positioning is lost. The rotation vector sensor is used to obtain screen orientation. | User positioning. |
| Bluetooth Information | Providing location services to users. | User positioning. |
| Device Motion Data | Provides device posture data, used to determine the position and attitude of the phone in the current space. | Positioning optimization for outdoor sports scenarios like walking and cycling. |
| Precise Location Information (GPS Information) | Providing location services to users. | User positioning. |
| BSSID | Providing location services to users. | User positioning. |
| SSID | Providing location services to users. | User positioning. |
| SIM Card Status | Providing location services to users. | Used to determine if the user can use base station positioning, thereby providing correct positioning results. |
| Location Service Access | Providing location services to users. | User positioning, continuously obtaining user location. |
| Phone State Access | Providing location services to users. | User positioning, used to obtain changes in base station status, obtaining base station positioning. |
| Network Carrier Name | Providing location services to users. | User positioning, handling user feedback related to carrier type positioning issues. |
| Phone Type | Providing location services to users. | User positioning, handling user feedback related to phone signal type positioning issues. |
# 4.8 Personal Information Obtained by the Agora Interactive Live Streaming SDK
- The audio and video data generated by users in the Agora Interactive Live Streaming (real-time streaming data) SDK is not stored by Agora;
- Service/operation-related data, such as service logs, network logs, performance data, functional data, etc., are deleted by Agora every 30 days.
# 4.9 Personal Information Obtained by the Mobile Authentication SDK
| Information Type | Purpose of Use | Usage Scenario |
|---|---|---|
| Cellular Network Permission | Performance analysis, categorized into 2G, 3G, 4G; analyzing the impact of different network environments on the success rate and latency of number retrieval for targeted optimization. | When calling the pre-fetch number interface. |
| IDFV | Used for issue localization (to identify the cause of number retrieval failure). | Used when the App is installed for the first time and the SDK runs for the first time. |
| Network Type | Performance analysis, categorized into cellular data only, Wi-Fi only, cellular data + Wi-Fi; analyzing the impact of different network environments on the success rate and latency of number retrieval for targeted optimization. | Used when calling the SDK pre-fetch number interface, get one-click login or verification token interface. |
| Network Access Permission | Determine whether the current network is Wi-Fi or cellular data for precise number retrieval. | Used during normal requests, reported by the SDK. |
| Carrier Information | Determine carrier attribution. | Used during SDK initialization. |
| Wi-Fi Status | Check if Wi-Fi is enabled before making a request. | Pre-check before calling functional interfaces. |
| Network Channel Switching | Switch network channels. | Required when both Wi-Fi and cellular networks are enabled to switch to the cellular network channel. |
| Phone Model | Determine the terminal type to determine the terminal adaptation solution for one-click login. | Used when calling the SDK pre-fetch number interface, get one-click login or verification token interface. |
| IP Address | Information necessary for SDK functionality. | Used when calling the SDK pre-fetch number interface, get one-click login or verification token interface. |
# 4.10 Personal Information Obtained by the Alipay Share SDK
| Information Type | Purpose of Use | Usage Scenario |
|---|---|---|
| Read Clipboard | Provide sharing functionality. | When the user clicks "Share to Alipay". |