# FinClip Privacy Policy
Effective Date: September 9, 2026
Version Update Date: September 9, 2026
Issuing Entity: Shenzhen Taiping Technology Co., Ltd. (Wholly-owned subsidiary of Finogeeks)
# Part 1 General Provisions
# I. Scope and Effect
This policy applies to the FinClip Mini-Program Open Platform and related products and services operated by Shenzhen Taiping Technology Co., Ltd. (Wholly-owned subsidiary of Finogeeks, hereinafter referred to as the "Platform" or "we"), including the platform website, FinClip App, Runtime SDK, FinClip IDE, Mini-Program Store, and Management Console (collectively referred to as "FinClip"). For the FinClip Community Edition and Private Deployment versions, where the Platform does not have access to relevant data, the data processing arrangements of the actual deployment environment shall prevail. In the event of any inconsistency between this policy and the FinClip Service Agreement, this policy shall prevail; matters not covered in this policy shall be governed by the FinClip Service Agreement and other platform rules.
# II. Controller Information
Personal Information Controller: Shenzhen Taiping Technology Co., Ltd. (Wholly-owned subsidiary of Finogeeks). Registered Address: Room 1901-1902, 19th Floor, Cuilin Building, No. 10 Kaifeng Road, Maling Community, Meilin Street, Futian District, Shenzhen. Contact email for the Personal Information Protection Officer: contact@finogeeks.com.
# III. Definitions
Terms such as personal information, sensitive personal information, processing, separate consent, and automated decision-making used in this policy shall have the same meanings as defined in the Personal Information Protection Law of the People's Republic of China. "Developer" refers to individuals, enterprises, or organizations that register on FinClip and use platform services. "End User" refers to a natural person who uses an application embedded with the FinClip SDK. "Child" refers to a minor under the age of fourteen.
# IV. Role Allocation
To clarify the boundaries of responsibility, the roles of the Platform and Developers in personal information processing activities are allocated according to the following rules:
(1) Developer account information and application information are processed by the Platform as an independent personal information controller;
(2) In scenarios where developers deploy independently (Community Edition, Private Deployment), data generated by SDK operation only enters the developer's own environment; the Platform does not access or process such data, and the developer is the personal information controller within its environment;
(3) In the Platform SaaS version scenario, the Platform processes log data necessary for its operations in accordance with this policy, while developers bear the responsibility as personal information controllers for their business data;
(4) If a developer integrates the SDK into its application and collects End Users' personal information, the developer shall act as an independent personal information controller, fulfill the obligation to inform and obtain consent from End Users in accordance with the law, and formulate its own privacy policy, which shall not be replaced by this policy.
# Part 2 Collection and Use of Personal Information
# I. Collection List
The Platform collects personal information based on the principle of "minimum necessity." The personal information collected by the Platform (Developer side) is as follows:
Table 1: List of Personal Information Collected by the Platform
| Information Category | Specific Types | Processing Purpose | Collection Scenario | Retention Period |
|---|---|---|---|---|
| Account Information | Mobile phone number, email address, password (encrypted storage) | Registration, login, identity verification, and account security | Registration, login | Permanent |
| Identity Verification Information | Enterprise users provide business licenses, names and identity information of legal representatives (or responsible persons); individual users provide real identity information | Fulfilling legal obligations for real-name verification (Article 21 of the Anti-Telecom and Online Fraud Law) | Registration authentication, enterprise certification, risk re-verification | Retained during account existence and after cancellation as required by law (not less than the statutory period) |
| Developer Profile | Nickname, avatar, contact information | Account display and necessary business communication | Registration, profile completion | Permanent |
| Application Information | Application name, package name, application signature, Mini-Program information | Application management, review, and distribution | Creating applications, submitting for listing | Permanent |
| Log Information | Access time, IP address, operation records, download and invocation records | Service operation and security maintenance, fraud risk monitoring and handling, cooperating with regulatory and judicial authorities as required by law | Throughout the entire use of services | Not less than six months (where laws and regulations require longer, such requirements prevail) |
| Customer Service and Ticket Records | Consultation content, communication records | Handling user requests and complaints | Submitting tickets, contacting customer service | Permanent |
For the rules on the collection and use of End User personal information (device information, permission information, etc.) involving the FinClip SDK during the operation of developer applications, see Part 1, Item IV and Appendix III and Appendix IV; developers who integrate the SDK shall complete compliance configuration in accordance with the SDK Product Compliance Usage Instructions and fulfill the obligation to inform and obtain consent from End Users.
# II. Legal Basis
The legal bases for the Platform's processing of personal information include: obtaining the consent of the individual; where processing is necessary for the conclusion and performance of a contract to which the individual is a party, or is necessary for human resource management implemented in accordance with lawfully formulated labor rules and regulations and lawfully concluded collective contracts; where processing is necessary for the performance of statutory duties or legal obligations; where processing is necessary to respond to public health emergencies or to protect the life, health, and property safety of natural persons in emergency situations; where processing personal information that the individual has made public or that has been otherwise lawfully disclosed, within a reasonable scope in accordance with this Law; and other circumstances provided by laws and administrative regulations.
# III. Separate Consent for Sensitive Personal Information
Where the Platform needs to process sensitive personal information such as precise geolocation or contacts in the SaaS version operation and maintenance scenario, it will inform the individual of the necessity of such processing and its impact on the individual's rights and interests, and obtain the individual's separate consent in advance; where laws and administrative regulations require written consent, such requirements shall prevail. Where developers collect sensitive personal information of End Users through the SDK, the developer shall obtain the separate consent of the End User in accordance with the law.
# IV. Circumstances Where Individual Consent Is Not Required
The Platform does not need to obtain individual consent for processing personal information under any of the following circumstances:
(1) Where processing is necessary for the conclusion and performance of a contract to which the individual is a party, or is necessary for human resource management implemented in accordance with lawfully formulated labor rules and regulations and lawfully concluded collective contracts;
(2) Where processing is necessary for the performance of statutory duties or legal obligations;
(3) Where processing is necessary to respond to public health emergencies or to protect the life, health, and property safety of natural persons in emergency situations;
(4) Where processing personal information that the individual has made public or that has been otherwise lawfully disclosed, within a reasonable scope;
(5) Other circumstances provided by laws and administrative regulations.
# Part 3 Cookies and Similar Technologies
The Platform website uses Cookies and similar technologies to ensure normal operation, remember preferences, and perform statistical analysis. The Platform does not use Cookies for purposes other than those described in this policy. Individuals can manage or delete Cookies through browser settings; deletion may cause some functions to become unavailable.
# Part 4 Use, Entrusted Processing, and Provision of Personal Information to Third Parties
# I. Purpose Limitation and Usage Rules
The Platform only uses personal information to the extent necessary to achieve the processing purposes described in this policy and does not use it beyond such scope; if the processing purpose needs to be changed, the Platform will obtain the individual's consent anew. Information that has been anonymized is no longer personal information, and the Platform may use it for statistical analysis; anonymization is carried out using irreversible technical standards.
# II. Entrusted Processing
Where the Platform entrusts a third party to process personal information, it will agree with the受托方 on the purpose, duration, method of processing, types of personal information, protection measures, and the rights and obligations of both parties, and will supervise the受托方's personal information processing activities.
# III. Sharing
Where the Platform provides personal information to other personal information processors, it will inform the individual of the recipient's name, contact information, processing purpose, processing method, and types of personal information, and obtain the individual's separate consent in advance; the recipient will process the information within the aforementioned scope. The current list of third parties (including affiliated companies) with whom the Platform shares personal information and the links to each third party's privacy policy are subject to the real-time disclosure on the official website's "SDK Usage List" page. The Platform requires recipients to have security capabilities commensurate with the risk; where sensitive personal information is involved, it requires recipients to adopt technical measures such as desensitization and encryption.
# IV. Transfer and Public Disclosure
The Platform will not transfer personal information to any company, organization, or individual, except where separate consent has been obtained in advance, or where transactions such as mergers, acquisitions, or asset transfers are involved and the transferee is required to continue to be bound by this policy (otherwise, consent must be obtained anew). The Platform does not publicly disclose personal information, except where separate consent has been obtained, or where required by law, legal proceedings, litigation, or mandatory requirements of competent government authorities.
# V. Cross-Border Provision
Currently, the Platform stores personal information collected domestically within China and does not provide it abroad. If provision abroad becomes necessary in the future, the Platform will, in accordance with legal provisions, inform the individual of the name and contact information of the overseas recipient, the processing purpose, processing method, types of personal information, and the methods and procedures for the individual to exercise rights against the overseas recipient, obtain the individual's separate consent, and pass the security assessment organized by the national cyberspace administration, obtain certification from professional institutions, or enter into a contract with the overseas recipient in accordance with the standard contract, and conduct a personal information protection impact assessment.
# VI. Circumstances Where Provision to Third Parties Does Not Require Individual Consent
In accordance with laws, regulations, and national standards, where it is necessary for the performance of statutory duties or legal obligations, responding to public health events, or protecting the life, health, and property safety of natural persons, the Platform's sharing, transfer, or public disclosure of personal information does not require prior individual authorization and consent; information that cannot identify a specific individual on its own or in combination with other information is not subject to separate notification and consent requirements for its processing and provision to third parties.
# Part 5 Storage of Personal Information
# I. Storage Method and Duration
The retention period for personal information is the shortest time necessary to achieve the processing purpose, specifically as set out in Table 1; where laws and regulations provide otherwise (e.g., logs for not less than six months, fraud-related clues retained as required by law), such provisions shall prevail. Personal information that exceeds the retention period will be deleted or anonymized by the Platform.
# II. Storage Location
Personal information collected and generated domestically by the Platform is stored within China. Currently, the Platform does not engage in cross-border transmission or storage.
# Part 6 Security of Personal Information
# I. Security Protection Measures
The Platform has implemented security protection measures that meet industry standards (including transmission encryption, access control, de-identification, firewalls, etc.) to protect personal information, prevent unauthorized access, disclosure, use, modification, damage, or loss of data, and continuously strengthens security capabilities in Mini-Program SDK integration scenarios. The Platform has established a personal information security management system and designated responsible personnel, and conducts regular security audits and vulnerability scans.
# II. Handling and Notification of Security Incidents
In the event of a personal information breach, tampering, or loss, or where such an event is likely to occur, the Platform will immediately take remedial measures and notify the department performing personal information protection duties and the individual as required by regulations; the notification content includes the types of information involved in the incident, the cause and potential harm, the remedial measures the Platform has taken, the measures the individual can take to mitigate harm, and the Platform's contact information. If the measures taken by the Platform can effectively prevent harm caused by the breach, tampering, or loss, the Platform may not notify the individual; if the department performing personal information protection duties believes that harm may be caused, it has the right to require the Platform to notify the individual.
# Part 7 User Rights and Exercise Mechanisms
# I. List of Rights
Individuals have the right to know about and decide on the processing of their personal information, and have the right to restrict or refuse others from processing their personal information (except where laws and administrative regulations provide otherwise), and enjoy the following rights:
(1) The right to access and copy their personal information;
(2) The right to request the transfer of personal information to a personal information processor designated by them (where conditions stipulated by the national cyberspace administration are met);
(3) The right to request correction or supplementation of inaccurate or incomplete personal information;
(4) The right to request deletion of personal information under the following circumstances: the processing purpose has been achieved or is no longer necessary, the Platform has ceased providing products or services, the retention period has expired, the individual has withdrawn consent, the Platform has processed personal information in violation of laws, regulations, or agreements, or other circumstances provided by laws and regulations;
(5) The right to withdraw consent (withdrawal does not affect the validity of personal information processing activities already conducted based on consent given prior to withdrawal; after withdrawal, the Platform will cease the corresponding processing);
(6) The right to request explanations from the Platform regarding any doubts about the Platform's processing of personal information. Where a natural person dies, their close relatives may, for their own legitimate and just interests, exercise the rights provided in this chapter regarding the deceased person's relevant personal information, including the rights to access, copy, correct, and delete.
# II. Methods and Time Limits for Exercising Rights
The Platform has established a convenient mechanism for receiving and processing requests from individuals to exercise their rights: individuals can self-service through their platform account settings, or submit a request to the Platform through the contact information in Part 10. The Platform will respond within fifteen working days of receiving the request; if an extension is needed, the Platform will explain the reasons to the individual. If the Platform refuses an individual's request to exercise their rights, it will explain the reasons; the individual may file a lawsuit with the people's court in accordance with the law.
# III. End User Rights on the Developer Side
End Users who wish to exercise rights over their personal information in applications embedded with the SDK should submit requests to the developer (the application operator); the developer shall establish a convenient rights exercise mechanism in accordance with the law. If the Platform receives a direct claim from an End User, it will verify their identity and, depending on the circumstances, assist in handling the matter or forward the request to the developer for processing.
# IV. Account Cancellation
Individuals may cancel their accounts in accordance with the FinClip Account Cancellation Agreement. After account cancellation, the Platform will cease providing services to them and will delete or anonymize their personal information, except for records required to be retained by laws and regulations.
# Part 8 Protection of Minors' Personal Information
The Platform's services are aimed at developers and do not target minors as users. Individuals should be at least eighteen years old, or minors over sixteen years old whose main source of livelihood is their own labor income; natural persons without corresponding civil capacity shall not register. Where the Platform processes personal information of minors under the age of fourteen, it will obtain the consent of their parents or other guardians and formulate specific personal information processing rules; guardians have the right to request correction or deletion of children's personal information processed by the Platform. Where developers process children's personal information, they shall obtain guardian consent and formulate specific rules in accordance with the law. If the Platform collects children's personal information without knowledge, it will delete it promptly, except where retention is required by laws and regulations.
# Part 9 Automated Decision-Making and Personal Information Protection Impact Assessment
# I. Automated Decision-Making
Where the Platform uses personal information for automated decision-making, it will ensure the transparency of decisions and the fairness and impartiality of results, and will not impose unreasonable differential treatment on individuals in terms of transaction conditions such as transaction prices; where automated decision-making is used for information push or commercial marketing to individuals, it will simultaneously provide options that are not targeted at their personal characteristics or provide convenient refusal methods; where automated decision-making is used to make decisions that significantly affect an individual's rights and interests, the individual has the right to request an explanation from the Platform and has the right to refuse decisions made solely through automated decision-making.
# II. Personal Information Protection Impact Assessment
The Platform will conduct a personal information protection impact assessment in advance and record the processing situation under any of the following circumstances:
(1) Processing sensitive personal information;
(2) Using personal information for automated decision-making;
(3) Entrusting the processing of personal information, providing personal information to other personal information processors, or publicly disclosing personal information;
(4) Providing personal information abroad;
(5) Other personal information processing activities that significantly affect an individual's rights and interests.
Impact assessment reports and records of processing situations shall be retained for at least three years.
# Part 10 Updates to This Policy
The Platform may revise this policy from time to time. Under the following circumstances, the Platform will notify through prominent means such as pop-ups, red dot prompts, website announcements, in-site messages, or emails: changes in the purpose, method, or types of processing; significant changes in the recipients to whom personal information is provided or the methods of provision; significant changes in individual rights and the methods of exercising them; changes in the personal information security officer and complaint channels; or the occurrence of major security incidents. For major revisions to this policy, confirmation from individuals will be obtained again. The latest version published on the official website shall prevail.
# Part 11 Contact Us
Individuals who have questions, comments, or suggestions about this policy or personal information processing matters, or who need to exercise their personal information rights, may contact the Platform through the following methods:
- (1) Send an email to contact@finogeeks.com;
- (2) Submit through the online customer service on the official website. The Platform will respond within fifteen working days. Individuals who are dissatisfied with the handling results or believe their personal information rights and interests have been infringed may file complaints or reports with departments performing personal information protection duties, such as the cyberspace administration, or file a lawsuit with the people's court in accordance with the law.
# Appendix I Definitions
The terms used in this appendix shall be determined in accordance with the Personal Information Protection Law of the People's Republic of China and Item III (Definitions) of Part 1 of the main text of this policy; terms already defined in the main text (Developer, End User, Child) will not be repeated. For ease of reading, the following terms are additionally defined:
- We/Platform: refers to Shenzhen Taiping Technology Co., Ltd. (Wholly-owned subsidiary of Finogeeks).
- FinClip Mini-Program SDK Products and/or Services: refers to the SDK products and/or services developed by Shenzhen Taiping Technology Co., Ltd. (Wholly-owned subsidiary of Finogeeks).
- Enterprise User: refers to an enterprise or other organization that authorizes an administrator or directly registers as a FinClip Mini-Program SDK user through its legal representative, and after uploading the enterprise/organization employee directory through the FinClip Management Platform to build the enterprise organizational structure, opens, manages, and uses FinClip Mini-Program SDK services as an administrator on behalf of the enterprise organization. FinClip Mini-Program SDK enterprise/organization users include but are not limited to legal persons, government agencies, other organizations, partnerships, or individual businesses.
- Individual User: refers to a natural person who registers a FinClip Mini-Program SDK account, including individual users with administrator privileges for FinClip Mini-Program SDK enterprise organization users, as well as individual users who are members of the FinClip Mini-Program SDK enterprise organization user directory without administrator privileges.
- App End User: refers to the end user who uses an application embedded with FinClip Mini-Program SDK products and/or services, i.e., the End User as defined in the main text of this policy.
- Application Products and/or Services: refers to products and/or services developed by individual/enterprise users themselves and provided to App End Users through the integration of FinClip Mini-Program SDK products and/or services.
- Personal Information: refers to all kinds of information related to identified or identifiable natural persons recorded electronically or by other means, excluding information that has been anonymized (Article 4 of the Personal Information Protection Law of the People's Republic of China).
- Sensitive Personal Information: refers to personal information that, once leaked or illegally used, may easily lead to infringement of a natural person's personal dignity or harm to personal or property safety, including biometric identification, religious beliefs, specific identities, medical health, financial accounts, whereabouts and trajectory information, as well as personal information of minors under the age of fourteen (Article 28 of the Personal Information Protection Law of the People's Republic of China).
- De-identification: refers to the process by which personal information is processed so that a specific natural person cannot be identified without the aid of additional information (Article 73 of the Personal Information Protection Law of the People's Republic of China).
- Anonymization: refers to the process by which personal information is processed so that a specific natural person cannot be identified and cannot be restored (Article 73 of the Personal Information Protection Law of the People's Republic of China).
- Within the territory of the People's Republic of China: refers to the mainland region of the People's Republic of China, excluding the Hong Kong Special Administrative Region, the Macao Special Administrative Region, and the Taiwan region.
# Appendix II SDK Usage List (Web)
The following are the SDKs currently used by the Platform in the FinClip.com environment and the content related to the information they collect. This list is subject to the date of this policy update; the latest list and detailed information are subject to the public disclosure on the Platform's official website. In case of any inconsistency, the official website disclosure shall prevail.
If you have questions about the personal information collected by third parties through SDKs, please refer to the specific privacy policies of each third party.
| SDK Name | Third-Party Vendor Name | Function Type | Purpose of Use | Types of Data Collected | Third-Party Privacy Policy Link |
|---|---|---|---|---|---|
| Baidu Analytics | Beijing Baidu Netcom Science Technology Co., Ltd. | Data statistics and error analysis | Use Baidu web and mobile analytics to optimize the FinClip user experience and record error logs | Device identifier information, geolocation, network information | https://tongji.baidu.com/web/help/article?id=330 |
| WeChat Open Platform | Shenzhen Tencent Computer Systems Co., Ltd. | Social sharing and third-party payment | Share content from the application to WeChat contacts and Moments, and support WeChat Pay functionality | Device identifier information | https://support.weixin.qq.com/cgi-bin/mmsupportacctnodeweb-bin/pages/ONwPihxKd82RAkIJ |
| Posthog | PostHog Inc | Data statistics and analysis | Record error analysis and optimize the FinClip user experience | Device identifier information, network information | https://posthog.com/privacy |
| Google Analytics | Google LLC | Data statistics and analysis | Use Google Analytics to optimize the FinClip user experience | Device identifier information, geolocation, network information | https://policies.google.com/privacy?hl=zh-CN |
| Hotjar | Hotjar Ltd | Data statistics and analysis | Use Hotjar to optimize the FinClip user experience | Device identifier information, network information | https://www.hotjar.com/legal/policies/privacy/ |
# Appendix III SDK Usage List (App)
The following are the SDKs currently used by the Platform in the FinClip App (SaaS and Private Deployment versions) and the content related to the information they collect. This list is subject to the date of this policy update; the latest list and detailed information are subject to the public disclosure on the Platform's official website. In case of any inconsistency, the official website disclosure shall prevail.
If you have questions about the personal information collected by third parties through SDKs, please refer to the specific privacy policies of each third party.
| SDK Name | Third-Party Vendor Name | Function Type | Purpose of Use | Types of Data Collected | Third-Party Privacy Policy Link |
|---|---|---|---|---|---|
| Baidu Analytics | Beijing Baidu Netcom Science Technology Co., Ltd. | Data statistics and analysis | Optimize the FinClip user experience | Device identifier information, geolocation, 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 | Support WeChat authorized sharing and WeChat Pay | Device identifier information | https://support.weixin.qq.com/cgi-bin/mmsupportacctnodeweb-bin/pages/ONwPihxKd82RAkIJ |
| Number Authentication | Shenzhen Tencent Computer Systems Co., Ltd. | One-click login with mobile phone number | Optimize 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 content in section 3.1.4 of this appendix | Device identifier information, network information, application information, application data | https://privacy.qq.com/document/preview/8565a4a2d26e480187ed86b0cc81d727 |
| AMap | Amap Software Co., Ltd. | Map capabilities | Demonstration and invocation of map-related capabilities | Geolocation 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 | Geolocation 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 | Geolocation information | https://lbs.qq.com/userAgreements/agreements/privacy |
| Agora Live | Shanghai Zhaoyan Network Technology Co., Ltd. | Live streaming capabilities | Optimize the FinClip user experience | Device identifier 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 | Optimize the FinClip user experience | Device identifier information, network information | https://ecloud.10086.cn/op-help-center/doc/article/27419 |
| Share to Alipay SDK | Alipay (China) Network Technology Co., Ltd. | Sharing | Improve FinClip functionality | Device identifier information, network information | https://opendocs.alipay.com/common/067y9l |
# 3.1 Details of Personal Information Collected by Third-Party SDKs
# 3.1.1 Personal Information Collected by the Baidu Analytics SDK
| Information Type | Purpose of Use | Usage Scenario |
|---|---|---|
| Device information and log information | To help developers use statistics and analysis services so that developers can understand how their end users use their mobile applications. | Collected directly by the SDK |
| Application list information and device information | To help developers track the activity of various mobile applications on end users' devices, so that developers can analyze and optimize the functionality and experience of their mobile applications. | Collected directly by the SDK |
| Content such as passwords, links, etc. in the clipboard | To help developers provide end users with jump and share functions for information content, so that users can share information or receive shared information | Collected directly by the SDK |
# 3.1.2 Personal Information Collected by the WeChat Open Platform SDK
| Information Type | Purpose of Use | Usage Scenario |
|---|---|---|
| Images or content actively selected by users in third-party applications | To allow users to use the share/collect 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 |
| The WeChat Pay order identifier generated by the third-party application when the user initiates payment, and the status information of whether the payment was successful after the user completes the payment operation | To allow users to use the WeChat Pay function in third-party applications | When the user triggers WeChat Pay |
# 3.1.3 Personal Information Collected 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 accurate number retrieval | Collected during one-click phone number authentication registration and login |
| Wi-Fi type | Collected to determine the current network status, used for number retrieval in specific situations | Collected during one-click phone number authentication registration and login |
| Carrier information | Collected to determine carrier attribution | Collected during one-click phone number authentication registration and login |
| IMSI (Android only) | Required for business logic processing (identifying dual SIM and SIM card changes) | Collected during one-click phone number authentication registration and login |
| Phone model | Collected to determine terminal type, used to determine the terminal adaptation solution for one-click login | Collected during one-click phone number authentication registration and login |
| IP address | Used when calling the SDK pre-retrieval interface, obtaining one-click login or verifying Token interface | Collected during one-click phone number authentication registration and login |
| IDFV (iOS only) | Used for problem diagnosis | Collected during one-click phone number authentication registration and login |
# 3.1.4 Personal Information Collected by the Mobile Push TPNS SDK
| Information Type | Purpose of Use | Usage Scenario |
|---|---|---|
| Manufacturer, device model | Used to determine the user's phone type and route through different vendor channels. | Identifying user channels when pushing |
| Android/iOS system version | Supports third parties in pushing different message content based on different system versions. | Issuing tag-based pushes |
| System language | Supports third parties in pushing different language content based on different system languages. | Pushing to devices |
| Device resolution | Supports pushing different images based on different resolutions. | When pushing content that includes images |
| Time zone | Supports global push, planning scheduled pushes for different time zones. | When issuing scheduled pushes or pushes to different time zones |
| Device boot time | Used for intelligent push by determining whether the device is powered on. Messages are cached when the device is off and pushed immediately when the device is powered on. | When messages are cached offline for 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 and images in other environments. | When pushing |
| Device information (phone model, kernel parameters, SDCard information, etc.) | a. Used for push user device statistics and setting SDK cache size to avoid excessive cache affecting push functionality; b. Used to determine whether it is a real device, allowing virtual machines to be filtered out during push to prevent black market activities and external malicious attacks. | a. Throughout the entire SDK runtime; b. Identifying the device when establishing a push connection. |
| Network status | Used to determine whether the device is online. If the device is online, the message is pushed immediately; if offline, the message is cached. | Identifying the device when establishing a push connection |
| 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 whether it is a real device, allowing virtual machines to be filtered out during push to prevent black market activities and external malicious attacks. | a. During SDK initialization and push delivery; b. Identifying the device when establishing a push connection. |
| IDFV | a. Push based on IDFV; b. Used to determine whether it is a real device, allowing virtual machines to be filtered out during push to prevent black market activities and external malicious attacks. | a. When delivering pushes based on IDFV; b. Identifying the device when establishing a push connection. |
| Notification bar switch status | Used to determine the notification bar switch status; pushes are not delivered to applications that have been disabled. | Determining whether a push needs to be delivered |
| Third-party version | Supports third parties in pushing different message content based on different versions. | When performing tag-based pushes and push user statistics |
| Terminal IP | Used for network link optimization. | The entire process of end user push link access |
| Carrier code | Used to determine network type and status, allowing devices to connect to the nearest node, shortening push delivery paths and improving push efficiency. | The entire process of end user push link access |
| Data generated during the push process, such as delivery, clicks, and impressions | Used for push statistics and error analysis. | When performing push business data statistics |
# Information that may be collected by other third-party SDKs within the Mobile TPNS SDK
The Mobile Push SDK integrates other vendor channel SDKs to improve the reach efficiency of push messages and provides the following information for your reference (please note that the Mobile Push SDK does not collect or share data through the following third-party SDKs).
| Third-Party SDK Name | Third-Party Company Name | Types of Personal Information | Purpose of Using the Third-Party SDK | Usage Scenario of the Third-Party SDK | Third-Party Personal Information Processing Rules |
|---|---|---|---|---|---|
| VIVO PUSH SDK | Vivo Mobile Communication Co., Ltd. | Device identifier information (e.g., IMEI, EmmCID, UFSID, ANDROIDID, GUID, GAID, OPENID, VAID, OAID, RegID, encrypted Android ID), application software information using the push service (such as application package name, version number, AppID, installation, uninstallation, factory reset, running status), device manufacturer, network type, country code, device type, message creation/delivery and click timestamps, message content, push SDK version number, device model, operating system version, current network type, message sending results, notification bar status (such as notification bar permissions, user click behavior), lock screen status (such as whether the screen is locked, whether lock screen notifications are allowed) | Provide push services. Perform association so that VIVO can provide consistent services on these devices. Perform analysis and statistics to improve VIVO products or services. | When using VIVO vendor push | Related Information (opens new window) |
| OPPO PUSH SDK | Guangdong Heytap Technology Co., Ltd. | Message content, device-related information (e.g., IMEI or OAID, Serial Number, IMSI, User ID, Android ID, Google Advertising ID, phone Region settings, device model, battery level, operating system version and language), application information using the push service (e.g., App package name and version number, running status), push SDK version number, network-related information (e.g., IP or domain name connection results, current network type), message sending results, notification bar status (e.g., notification bar permissions, user click behavior), lock screen status (e.g., whether the screen is locked, whether lock screen notifications are allowed), device identification codes (IMEI or OAID), IP addresses, client system, client network type, client time (in some scenarios) collected at the direction of advertisers or developers | Provide push services, including pushing messages, recording message sending results and returning them to developers, and providing functions such as collapsing unimportant notifications. Analyze and develop related statistical information to improve products or services and optimize product performance. Used for business operations or fulfilling legal obligations. Conduct marketing-related activities, some of which involve evaluating marketing effectiveness. | When using OPPO vendor push | Related Information (opens new window) |
| Xiaomi Push SDK | Beijing Xiaomi Mobile Software Co., Ltd. | Android version: Device identifiers (OAID and encrypted Android ID), and application information using the push service such as application package name, version number, and running status. iOS version: IDFV (not collected if IDFV cannot be collected), application package name, version number. Android version: Message creation, delivery, and click times, and temporarily stores message content received from third-party applications and pushed to you. iOS version: Message creation and delivery times, and temporarily stores message content received from third-party applications and pushed to you. Android version: Device-related information such as device manufacturer, device model, device memory, operating system version, Xiaomi Push SDK version, device location (country or region), SIM |