目录

Personal information must be handled with care. To meet this end, you should ensure compliance with applicable laws and regulations, fulfill obligations to protect personal information, and follow principles of lawful, proper, necessary, and fair processing. This includes but is not limited to Personal Information Protection Law of the People's Republic of China, Cybersecurity Law of the People's Republic of China, Data Security Law of the People's Republic of China, Measures for Identification of Illegal Collection and Use of Personal Information by Apps, Notice on Launching Further Special Rectification Campaign on the Infringement of User Rights and Interests by Apps, Information Security Technology — Personal Information Security Specification, Measurement Specifications for App Users' Rights and Interests Protection, Notice of the Ministry of Industry and Information Technology on Launching Actions for Improvements to the Perception of Information and Communications Services, Notice of the Ministry of Industry and Information Technology on Further Improving Mobile Internet Application Service Capabilities, Provisions on the Administration of Algorithm-based Recommendations for Internet Information Services, Provisions on the Scope of Necessary Personal Information for Common Types of Mobile Internet Apps, Regulations on Network Protection of Children's Personal Information, Notice on Further Improving Mobile Internet Application Service Capabilities, and other applicable laws and regulations.

Privacy Policy

7.1 You must provide a link to the privacy policy in AppGallery Connect and within your atomic service. The privacy policy must be open and transparent, consistent with how your atomic service processes users' personal information during its operation. Ensure the link is always functional.

7.2 The privacy policy link provided by your atomic service must redirect users to the privacy policy that includes the purpose, method, and scope of personal data collection and use by your atomic service (including entrusted third parties or embedded third-party code and plugins).

7.3 The privacy policy within your atomic service must include information on how users can exercise their rights as the personal information subjects, such as how to withdraw consent and/or request data deletion, how to access and copy their personal information, and how to give their feedback about any privacy-related issues. If your atomic service has an account system, ensure that users are provided with easy-to-use options to delete non-account information, remove their data, and delete their accounts, with clear indications of what will be deleted. Ensure there are no unreasonable barriers to the above-mentioned actions, and the deletion requests are completed within 15 working days.

7.4 Your atomic service must obtain user consent or comply with applicable laws and regulations when accessing, collecting, using, or disclosing any personal information.

User Consent

7.5 Your atomic service must present the privacy policy in a clear and noticeable way. Before collecting and processing users' personal information, obtain user consent in a manner that allows users to voluntarily and explicitly give their consent, fully understanding what they are agreeing to.

7.6 Your atomic service must provide users with simple, understandable, and easy-to-operate methods to withdraw consent.

7.7 If your atomic service uses personal information for personalized advertising or precision marketing, this must be clearly stated in the privacy policy. Additionally, an independent option to disable or opt out of such activities should be provided within the atomic service.

7.8 Your atomic service must obtain user consent for processing sensitive personal information, and inform users of the necessity and the impact on their rights and interests.

7.9 Your atomic service must not auto-launch or trigger the launch of other apps or atomic services, nor engage in wake-up, invocation, or update actions unless required or justified by a reasonable scenario. Before triggering an associated launch, your atomic service must clearly inform users of the app to be launched, or the redirection must be initiated by the users themselves.

Collection and Use

7.10 Your atomic service must follow the principle of data minimization in collecting and using personal information, using the least intrusive methods necessary to achieve the processing purpose.

7.11 Your atomic service must not secretly collect and use personal information or collect information beyond what is necessary for the service or without a reasonable scenario.

7.12 Your atomic service must use secure methods, such as encryption (for example, HTTPS), to process all personal information.

7.13 The privacy policy of your atomic service must specify the content, purpose, and recipient of any disclosed personal information.

7.14 Your atomic service must not sell users' personal information.

7.15 Any third party to whom personal information is disclosed must provide personal information protection measures that are equivalent to or the same as those required by your atomic service's privacy policy and the guidelines.

7.16 Your atomic service must not use sensitive personal information, such as call records, SMS messages, biometric data, health data, or tracking data, for purposes like service improvement, advertising, marketing, or other non-core features.

7.17 Your atomic service must follow the principle of permission minimization, requesting permissions dynamically only when the related feature needs to be activated. It must not refuse to provide products or services on the basis that users do not provide consent or have withdrawn their consent.

7.18 Your atomic service must provide a clear, reasonable scenario and feature description when requesting permissions. Inducing or misleading users into granting permissions is prohibited, and the permission used must align with the permission requested. Your atomic service must simultaneously inform users of the purpose when requesting any sensitive permissions. Changes to permission granting status without user consent are prohibited.

7.19Your atomic service must not repeatedly request permissions. In the case that a user has refused to grant a permission, unless required by specific features, the permission should not be re-requested.
Note: If a user denies a permission request, and the permission prompt reappears without the user actively triggering the relevant service, it is considered excessive. 

7.20 Your atomic service must process personal information for clear and legitimate purposes, and should not require consent beyond the scope of the service or unrelated to the service scenario, under the guise of service experience, product R&D, algorithm recommendations, or risk control. If a user refuses to provide personal information that is not essential for a service, access to the service's basic features should not be impacted.

7.21 Your atomic service must use platform capabilities appropriately and comply with user privacy requirements when requesting personal information, such as mobile numbers associated with their HUAWEI IDs.