UGREEN NAS APP Center App Review Rules

To ensure the security of the platform ecosystem, protect user rights and interests, and comply with applicable laws and regulations worldwide, the UGREEN NAS APP Center conducts a strict review of all applications for app listing. Developers shall ensure that all materials and app content they submit are true, lawful, complete, and valid, and shall bear legal responsibility for the development, operation, and compliance of their apps in accordance with applicable laws.

The platform only reviews the formal compliance of the materials and apps submitted by developers, and provides no guarantee regarding the actual operations, ongoing compliance status, or legal liabilities arising therefrom. Such legal liabilities shall still be borne by app developers/operators in accordance with the law.

Once an app is listed, the platform will conduct ongoing compliance management through spot checks, complaint investigations, periodic reviews, and other means. If we find that any app does not comply with the rules or legal requirements, the platform reserves the right to take actions such as issuing a warning, requiring rectification within a specified period, or removing the app.

I. Qualification Requirements for Application Listing

All developers applying for app listings shall provide the qualifications and business licensing documents of the intended distribution market during the review process. The platform will verify the qualifications of both the developers and apps in accordance with applicable laws and regulations and industry oversight requirements.

1. Apps Listed in the Chinese Mainland

(1) General Qualification Requirements

When submitting applications for listing, developers shall also provide the following four categories of basic qualification materials:

• Proof of software copyright ownership: One of the following: Computer Software Copyright Registration Certificate, Electronic Copyright Certificate for Applications, or Software Copyright Certificate. If a developer is not the copyright owner, the developer shall provide complete documentation proving the chain of authorization.
• Value-added telecommunications (ICP) license/filing proof: If a developer has obtained an ICP license, the developer shall submit a copy or electronic certificate of the Value-Added Telecommunications Business License. If the developer has only completed ICP filing, the developer shall provide a screenshot of the filing from the government service platform of the Ministry of Industry and Information Technology of the People's Republic of China ("MIIT") together with the filing number.
• App filing proof: A developer shall provide a screenshot showing the app's filing information as displayed on the MIIT government service platform.
• Public security network filing: A developer shall provide a screenshot showing completion of filing on the National Internet Security Management Platform.

(2) Qualification Requirements for Special Types of Apps

If an app falls into one of the following special categories, the developer shall provide the corresponding specialized qualification documents in addition to the basic qualification materials. The platform will strictly review the completeness and consistency of the materials.

Type	Document
Deep synthesis or generative AI services	(1) Content generated by the app shall add explicit and implicit identifiers in accordance with the Measures for Labeling Synthetic Content Generated by Artificial Intelligence. (2) Screenshot and filing number of the Internet information service algorithm filing. Where third-party cooperation is involved, the cooperating party’s algorithm filing information shall also be provided. (3) The Internet Information Service Security Assessment Report and a screenshot of approval on the National Internet Security Management Platform.
Internet map services	The Surveying and Mapping Qualification Certificate shall be provided, with the service scope explicitly including “internet map services”. Where authorization or cooperation is involved, proof of authorization or cooperation from the partner or licensor shall be submitted. In addition, the map review number and the cooperating entity shall be displayed in a prominent position on the map.
Third-party payment	(1) The Payment Business License shall be provided, and the business scope on the business license shall include Internet payment services.
E-commerce platform	(1) EDI license
Audio and video	(1) The Network Culture Business License (2) The License for Dissemination of Audio-Visual Programs through Information Networks (For micro-drama apps, the filing information on the National Online Audio-Visual Platform Information Management System may be provided.) (3) If an app provides instant messaging functions such as bullet comments or private messages, the developer shall provide the Internet Information Service Security Assessment Report and a screenshot of the submission record on the National Internet Security Management Platform. (4) The License for Dissemination of Audio-Visual Programs through Information Networks or Television Program Production and Operation License (required if the app contains self-produced programs or films/TV dramas)
Live streaming	(1) The Network Culture Business License, with the business scope including “performances” or “online performances” (2) The Internet Information Service Security Assessment Report and a screenshot of the submission record on the National Internet Security Management Platform
Commercial performance ticketing	(1) The Commercial Performance License shall be provided. If collaboration is involved, the developer shall provide the collaborating party's Commercial Performance License and the cooperation agreement between the parties.
Publications	(1) The Network Culture Business License shall be provided. If collaboration is involved, the developer shall provide the collaborating party's qualification documents and the cooperation agreement between the parties. The Publication Business License or an Online Publishing Service License shall be provided. If collaboration is involved, the developer shall provide the collaborating party's qualification documents and the cooperation agreement between the parties.
News	(1) The Internet News Information Service License and its appendix shall be provided. If news is sourced from other qualified news entities, relevant cooperation or authorization certificates shall be provided.
Travel agencies	(1) The Travel Agency Business Operation License shall be provided. If outbound tourism services are provided, the business scope shall include outbound tourism services.
Airlines, air ticket sales	(1) The scope of business in the business license shall include ticket sales or ticket agencies.
Accommodation and catering services	(1) The Hygiene License (2) The Catering Service License or Food Business License (3) For accommodation services, additional qualifications such as the Special Industry License and fire safety permits shall also be obtained.
Charity	1. Charitable organizations: (1) The Foundation Legal Person Registration Certificate or Social Organization Legal Person Registration Certificate (for a charitable organization) (2) The Public Fundraising Qualification Certificate 2. Fundraising service platform: (1) Screenshot of the Charitable Organization Internet Fundraising Information Platform Announcement
Crowdfunding platform	(1) If a platform provides online personal assistance fundraising service, the developer shall provide a screenshot of the announcement published by the Ministry of Civil Affairs designating the online personal assistance fundraising platform. If collaboration is involved, the developer shall provide the collaborating party's announcement screenshot and the cooperation agreement between the parties.
Education	(1) Filing with the provincial education administrative department (2) The School Operating License (3) The business license scope shall include education services.
Automobile sales	(1) Manufacturer authorization documents for vehicle sales (2) The business license scope shall include automobile sales.
Online vehicle and driver management services	(1) Official authorization and license from the competent transportation authority
Internet religious information services	(1) Developers shall provide the Internet Religious Information Service License and display the license numbers prominently within apps. (2) The Religious Activity Venue Registration Certificate
Internet telephony Multi-party phone conference Multi-party video conference	(1) The Internet Information Service Security Assessment Report and a screenshot of approval on the National Internet Security Management Platform. (2) The Value-Added Telecommunications Business License covering “domestic multi-party communication services”
Search services (browsers)	(1) The Value-Added Telecommunications Business License shall be provided. If collaboration is involved, the developer shall provide at least one partner's Value-Added Telecommunications Business License and the cooperation agreement between the parties.
Digital collectibles (primary market trading)	(1) Screenshot of blockchain information service filing. If the blockchain service is provided by a third party, the third party’s blockchain service registration with the competent cyberspace administration and the relevant cooperation agreement shall be submitted. (2) The Value-Added Telecommunications Business License shall be provided. For data transmission and transaction/affairs processing: category B21; for NFT minting and issuance services as well as information publication and exchange services: category B25
Gaming	(1) One of the Computer Software Copyright Registration Certificate, Application Electronic Copyright Certificate, or Software Copyright Certification shall be provided. If a developer is not the copyright holder, a copyright authorization letter shall be provided. For individual software copyright authorization, the developer shall provide a copy of the ID card with a red fingerprint, a handwritten signature, and a photo of the individual signing the authorization letter (i.e., a front-facing photo of the person in the process of signing the authorization letter). (2) The Network Game International Standard Book Number (ISBN) Issuance Form or Approval for Publishing and Operating Mobile Network Games (3) If the developer uploading the game is not the operating entity listed on the version number approval document, the developer shall provide a version number authorization letter from the operating entity holding the version number.
Electronic signing	(1) The Electronic Certification Service License shall be provided. If collaboration is involved, the developer shall provide at least one partner's Electronic Certification Service License and the cooperation agreement between the parties.
Courier services	Courier service business license or filing certificate issued by the competent postal administration department

2. Apps Listed Outside the Chinese Mainland (for the Purpose Hereof, Including Hong KongSAR, MacaoSAR, and TaiwanRegion of China)

The APP Center is open toglobaldevelopers.For any app intended to be listed in countries/regions outside the Chinese mainland (for the purpose hereof, including Hong KongSAR, MacaoSAR, and TaiwanRegion of China), the platform will, based on the app type and the nature of the services involved, require its developer to provide the corresponding industry qualification materials, regulatory filings, or equivalent compliance documents.

The following is a guide to common app types and the corresponding qualification categories to help developers determine the supporting documents they may submit. The specific form of documentation shall be subject to the regulatory requirements of the countries or regions where the app is to be listed.

(1) Communication and information service apps

Scenarios: Providing services such as instant messaging, voice/video calls, multi-party conferencing, cloud communications, SMS gateways, and virtual numbers

Qualification requirements:

• Telecommunications operation license or filing
• Communication service provider registration certificate
• Cross-border communication or network service compliance documents (if applicable)

(2) Content and media service apps

Scenarios: audio/video playback, live streaming, short-form dramas, news and information, publication distribution, and user-generated content platforms

Qualification requirements:

• Digital content service license or filing
• Compliance certification for audiovisual content distribution
• News or publication service qualifications

For apps involving paid content or content distribution functions, developers are typically also required to provide telecommunications or online service-related qualification documents.

(3) Gaming and digital entertainment apps

Scenarios:Online games, interactive entertainment, virtual item trading, and online entertainment content platforms

Qualification requirements:

• Game content rating or classification filing
• Compliance certification for game operation or distribution

(4) E-commerce and transaction platform apps

Scenarios: Platforms providing goods or service transactions, third-party storefronts, e-commerce platforms, second-hand trading, ticketing, travel booking, and similar services

Qualification requirements:

• Business operation or platform service license
• Industry-specific operation license (e.g., tourism, auction services)
• Tax or commercial compliance certification

(5) Social and user-scale platform apps

Scenarios:Providing social networking, community platform, and user-generated content services

Qualification requirements:

• App service provider license or filing
• Compliance registration for large-scale platform operations
• Description of content governance and user protection mechanisms

In some app marketplaces, once an app reaches a certain user scale, its developer needs to fulfilladditionalregulatory obligationsto submit supplementary compliance materials.

(6) Map and location service apps

Scenarios:Providing map display, navigation, and geographic information services

Qualification requirements:

• Map service or geographic information service license
• Compliance registration for surveying or location services

3. Notes

(1) If an app is distributed in multiple countries or regions, its developer shall comply with the industry regulatory requirements of each respective distribution market and cannot rely on a single-region qualification to fulfill global compliance obligations.

(2) Specific license names and issuing authorities vary by country and region; the platform accepts foreign qualification documents that hold equivalent legal effect.

(3) For apps with complex business models, unclear regulatory boundaries, or cross-border services, the platform reserves the right to require developers to further clarify their compliance approach and to submit additional equivalent qualification documents or legal opinion statements.

(4) Developers shall ensure that all submitted licenses, registration materials, or certification documents are authentic, valid, and within their effective period. If the qualification status changes or the qualification expires or is revoked, the developer shall promptly update the relevant information.

(5) Generally, qualification reviews are completed within 3-7 working days after complete materials are provided by developers (postponed accordingly duringtheChinese mainland public holidays). The actual timeline is subject to the review progress of the platform.

II. Key Points for App Security and Compliance

In order to provide users with a safe and reliable environment, developers shall ensure that submitted apps do not attempt to abuse or improperly utilize any network or device resources, nor introduce security risks that could interfere with other apps.

The following are key security and compliance points to be observed during app development and submission:

1. Apps shall not contain viruses, Trojans, or backdoors. Any behavior that could encrypt, delete, or leak users’ private information (e.g., photos, videos, work files) is strictly prohibited.

2. We prohibit the consumption of device resources for fraudulent gains.

(1) Prohibition of mining. The use of NAS devices for virtual currency mining is strictly prohibited, as it may cause overheating, excessive electricity consumption, and reduced hardware lifespan.

(2) Prohibition of traffic manipulation: Apps shall not simulate clicks on ads, generate fake traffic, or perform any background actions that consume household bandwidth or degrade network performance.

(3) Prohibition of false subscriptions: Developers shall not induce or deceive users—especially minors and the elderly—into subscribing to paid services. All transactions shall be explicitly confirmed by users with full awareness.

3. Strict Privacy and Data Protection

(1) Explicit disclosure: Apps requesting access to sensitive locations such as “photo library”, “surveillance footage folder”, or “personal file folder” shall clearly inform users of the purpose of access in plainand clearlanguage, and shall not use the data beyond that stated purpose.

(2) Prohibition of unauthorized access: Apps shall not secretly scan or upload users’ file lists, directory structures, or file content. Without explicit user consent, apps shall not collect user behavioral information, except as otherwise required by law.

(3) Local-first principle: Data processing is encouraged to be completed locally on users' NAS devices. If data transmission over a network is necessary, data shall be encrypted, and users shall be clearly informed of where the data is sent and for what purpose.

(4) Apps shall not remotely control NAS devices orsendremote control instructions without authorization, nor engage in any activities that infringe user privacy, misappropriate user assets, or perform other malicious actions.

4. Prohibition of Threats to Device and Network Security

(1) No backdoors: Apps shall not enable remote access ports (such as SSH or web management interfaces) without authorization, which would expose NAS devices tothepublic network.

(2) No internal network attacks: Apps shall not act as a “pivot” to scan or attack other devices within the local network, such as smart TVs, cameras, or mobile devices.

(3) No traffic hijacking: Apps shall not tamper with the network traffic of other devices in the home, inject ads, or conduct phishing activities.

(4) No threat to device stability: Apps shall not cause NAS system crashes or frequent freezes that impair user experience.

5. Secure and Transparent Dynamic Updates

If an app updates its code or upgrades its functionality by any means, such as scripts, plug-ins, or online hotfixes, the developer shall resubmit a complete set of listing materials to the UGREEN NAS App Center, including the app package, update description, and change log, for re-review, and shall clearly inform users of the update content.

6. No Interference with Normal Device Usage

(1) Apps shall not frequently display notifications unrelated to their core functions that interfere with the user’s use of the NAS devices.

(2) Apps shall not monopolize CPU, memory, or hard drive resources for extended periods, resulting in slow performance or failure of tasks such as media playback or downloads on the NAS devices.

(3) App interfaces shall not impersonate the official NAS system settings pages or security warnings to mislead users.

7. Prohibition of Any Form of Ransomware Behavior

Under no circumstances may an app encrypt, lock, hide, or refuse to return users’ NAS data. This is a red line that shall not be crossed.

III. Key Points for Compliance in Personal Information Protection

During app development, operation, and listing, developers shall comply with applicable personal information protection laws and regulations, industry regulatory requirements, and platform rules, and shall also follow the compliance requirements of the countries or regions where apps are distributed.

The following are key personal information protection compliance points that require special attention during app development and listing:

1. Privacy Policy Submission and Content Requirements

(1) Submission requirements: When applying for app distribution, developers shall provide a valid privacy policy link. The link shall use a standard HTTPS format and lead to a directly accessible static page that does not require login, registration, or redirection. The content of the privacy policy shall be consistent with the version displayed within the app and shall be updated synchronously whenever the app is updated. Developers shall not substitute the privacy policy with images, Word documents, blog pages, or any other non-standard web formats.

(2) Content structure and transparency: The privacy policy of an app shall be a standalone document and not incorporated as an ancillary clause into a user agreement. The content of the privacy policy shall be clearly expressed and easy to understand, avoiding obscure legal or technical terminology, and shall cover all personal information processing scenarios involved in the app. The privacy policy shall clearly state the rights that users may exercise and how to exercise them, and provide effective channels for complaints, inquiries, or reports.

(3) Language versions: In principle, the privacy policy of an app shall be provided in the primary language used by the app's target users. For apps distributed in specific countries or regions where local laws impose mandatory language requirements for privacy policies, developers shall provide corresponding language versions.

(4) "Three lists" requirement in the Chinese mainland: If an app is intended for distribution in the Chinese mainland, in addition to the privacy policy, the developer shall also provide a list of collected personal information, a list of personal information shared, and a list of third-party SDKs in the app.

2. Processing of Personal Information Based on the Principles of Legitimacy, Justification, and Minimum Necessity

(1) The collection and use of all personal information shall be based on lawful and explicit purposes, and such activities shall be necessary and limited to the minimum scope required to achieve those purposes. Personal information unrelated to app functions shall not be collected.

(2) Permission request requirements: Apps shall follow the principle of permission minimization by dynamically requesting only the permissions required at the time when specific functions are actually initiated, and clearly explaining the corresponding usage scenarios to users. Apps shall not request multiple permissions unrelated to the current function in a single instance. After a user denies a permission request, the app shall not frequently pop up prompts or obtain authorization through disguised or coercive means.

(3) Management of auto-start and associated launch: Apps shall not automatically start themselves or trigger the launch of other apps without reasonable business necessity or explicit user demand. Where associated launch is required, users shall be clearly informed in advance in a prominent manner, or such actions shall be initiated by users themselves.

3. User Consent

(1) Basic requirements for obtaining consent: Before collecting or processing personal information, an app shall present the privacy policy to users in a clear and understandable manner, and obtain voluntary and explicit consent based on users' full awareness. Upon first launch, the app shall display a privacy policy link or interface.

(2) Withdrawal and refusal: Developers shall provide users with a convenient operation method (such as a switch in the settings menu) so that users may withdraw consent or refuse non-essential processing at any time. Refusal by users to provide non-essential personal information shall not affect the normal use of an app's core functionality, nor can refusal be used as a reason to deny access to essential services.

4. Compliance Review of SDKs and Third-Party Components

(1) Developers shall identify all third-party SDKs or components integrated into apps (e.g., advertising, statistical analytics, push notification services), and ensure that their personal information handling practices are consistent with the privacy policy and applicable laws.

(2) Developers shall clearly disclose the data collection scope, purpose of use, and data transmission scope of third-party SDKs, and shall ensure that no personal information is collected through such SDKs without prior user authorization.

5. Data Security Safeguards

(1) Developers shall implement reasonable technical and organizational measures to protect users' personal information from unauthorized access, disclosure, alteration, or destruction, including data encryption, access control, and audit logging.

(2) If an app involves cross-border transfer of personal information, the developer shall establish compliance mechanisms in accordance with applicable laws (e.g., security assessments, standard contractual clauses, or certifications) and disclose these measures in the privacy policy.

(3) We recommend that developers periodically conduct privacy compliance self-inspections or risk assessments to identify and remediate potential security and compliance risks in a timely manner.

6. Ongoing Updates and Version Iteration Compliance

(1) As business operations or applicable laws and regulations evolve, apps and their privacy policies shall be updated dynamically. Updates shall be communicated to users through prominent channels, such as pop-up notifications or in-app announcements, clearly explaining the changes and their impact.

(2) Any substantial changes to privacy rules that may affect user rights shall be subject to user consent.

We will verify whether apps comply with the applicable laws and regulations of the target countries or regions and platform rules through a combination of technical checks and manual review. If any app is found non-compliant, we reserve the right to require its developer to make corrections within a specified timeframe or to reject the app listing request. Developers are encouraged to perform self-assessments prior to app submission to ensure that their personal information handling practices remain continuously compliant with relevant requirements.

IV. Key Points for App Intellectual Property Compliance

Developers shall ensure that their apps and related content do not infringe upon the legitimate rights and interests of any third party, including copyrights, trademark rights, patent rights, and trade secrets. The platform will conduct intellectual property compliance reviews on all apps listed on the platform. Developers shall pay particular attention to the following requirements:

1. Clear Ownership and Submission Requirements

A developer shall own legitimate, clear, and traceable rights for its app as a whole and all of its elements.

(1) Scope of rights: A developer shall possess legitimate rights for its app as a whole and all of its elements, including but not limited to app code and architecture, app name, logo, UI design, promotional copy, audio, video, images, fonts, animations, templates, and other assets. For non-original content, the developer shall provide complete, valid, and traceable authorization or licensing documents (e.g., authorization agreements, transfer certificates, purchase receipts). If any authorization expires, ownership changes, or the cooperation relationship ends, the developer shall promptly update the materials and resubmit them for review.

(2) Submission and retention of materials: Acceptable proof of rights includes authorization agreements, license letters, transfer certificates, purchase receipts, and similar documents. An authorization document shall clearly specify the authorizing party, scope of authorization, mode of authorization, permitted usage method, term, and territory. We reserve the right to request developers to supplement or resubmit materials during review or subsequent compliance checks.

(3) Consistency of entity: An app shall be submitted by the intellectual property right holder or its legally authorized representative.

(4) Cross-region listing and equivalence principle: Developers shall possess intellectual property proofs that comply with the requirements of the countries or regions where apps are intended to be distributed.

(5) Ownership requirements for special development models: For any app developed through joint development, commissioned development, or outsourced development, the ownership of intellectual property rights shall be clearly defined and documented in a written agreement.

2. Prohibited Conduct

We will focus on reviewing whether any app presents a risk of infringement. The following scenarios constitute grounds for heightened scrutiny or direct violation:

(1) Unauthorized use of third-party intellectual property, including but not limited to copying or closely imitating another app's interface, functional architecture, or interaction design ("shell app" or "cloned app"); using pirated music, videos, images, fonts, plugins, or templates; using third-party trademarks, brand logos, or similar marks without permission; or using a patented technical solution without a license.

(2) Misleading or false intellectual property representations. The app name, description, or screenshots shall not contain false or exaggerated statements regarding authorization, partnership, or certification. Any app shall not mislead users into believing there is an affiliation, partnership, or official relationship with a third-party brand, and shall not use terms such as "official", "solely authorized", or "partner" without authorization, where such terms may cause confusion.

(3) Inadequate control of infringement risks from user-generated content. For apps with functions such as community, comments, uploading, or sharing, developers shall establish reasonable content management mechanisms, including channels for accepting complaints and necessary manual or technical review measures. Apps shall not allow users to continuously upload clearly infringing content without intervention.

(4) Improper use of AI technology or generated content. Developers shall not use others' protected works or data for model training, fine-tuning, or content generation without authorization, nor generate content that substantially copies or imitates expressions protected by third-party copyrights, trademark rights, or other legal rights, thereby infringing upon third-party legitimate rights and interests.

3. Open Source Software and Component Compliance

When developers use open source code or components, they shall comply with all requirements of the corresponding open source licenses.

(1) Developers using open source code or components shall strictly follow the terms of the applicable open source licenses, including but not limited to retaining copyright notices and license texts, fulfilling attribution obligations, and complying with requirements concerning restrictions on commercial use, redistribution, or closed-source distribution.

(2) For open source licenses containing strong copyleft terms, developers shall carefully assess their impact on the disclosure obligations for the overall application code, so as to avoid intellectual property disputes caused by non-compliance with such provisions.

4. Developer Responsibilities and Rights Protection

(1) Self-inspection: A developer shall conduct a basic intellectual property risk assessment before submitting an app for listing, including but not limited to similarity comparison, verification of authorization chains, and open source compliance checks.

(2) Ongoing updates: In the event of license expiration, changes in ownership, or termination of cooperation, a developer shall promptly update the materials and resubmit them for review.

The platform will continuously manage the intellectual property compliance of apps through a combination of technical detection, manual review, and complaint handling. If any developer believes that its intellectual property rights have been infringed by others, the developer may submit supporting evidence through the platform's complaint channels, and we will assist in handling such matters in accordance with applicable laws and regulations.

V. Key Points for the Protection of Minors in Apps

The platform requires developers to systematically implement minor protection mechanisms throughout the design, operation and distribution of their apps and to bear compliance liabilities based on the app category and the applicable provisions of the countries/regions where apps are distributed.

1. Basic Principles and Review Priorities

(1) Compliance with local laws: Developers shall design protection mechanisms for minors in accordance with the legal requirements of the countries or regions where apps are listed or distributed. The platform will verify whether apps comply with local laws based on the actual regions where apps are distributed. If an app is launched in multiple countries or regions, its developer shall meet the applicable standards of each region and shall not replace its overall compliance obligations with the minimum requirements of any single region.

(2) Focus on high-risk sectors: The platform will conduct enhanced reviews of minor protection mechanisms in high-risk sectors such as games, social media, content sharing, live streaming, and interactive communities, including but not limited to content suitability, feature design, payment mechanisms, and interaction security. We encourage developers of the above types of apps to submit dedicated minor protection plans, detailing the specific measures implemented in areas such as content filtering, usage time control, and parental supervision tools.

2. App Age Rating and Suitability

An app's developer shall assign a reasonable age rating to the app, and ensure that the app's content, functional design, and operation methods align with the selected age rating. The description text, screenshots, and demo videos displayed in the app store listing shall truthfully reflect the app's actual functionality, and we do not allow developers to evade our review through a "low rating+high-risk content" approach. The platform will verify the accuracy of age ratings and impose corresponding compliance requirements accordingly.

The following rating standards are for reference only and do not replace any statutory age rating systems established by applicable laws.

Rating	Description
Ages 3+	Apps at this rating level shall not contain any violence, horror, sexual suggestion, inappropriate language, vulgarity, regulated items or activities, simulated gambling, or any other age‑restricted content.
Ages 8+	Apps at this rating level may contain: very little or very mild cartoon or fantasy violence, but no realistic violence; very little or very mild startling elements, but no horror-inducing elements; very little or very mild sexual references, but shall not contain revealing clothing, romantic plots or features, or depictions emphasizing sexual characteristics or reproductive organs; very little or very mild inappropriate language, but no mild profanity or more severe content; and very little or very mild crude or vulgar humor.
Ages 12+	Apps at this rating level may contain: occasional or mild realistic violence against characters or animals, or gory scenes, but no frequent or extensive violent scenes; occasional or mild frightening or terrifying elements, but no frequent or extensive frightening or terrifying elements; occasional or mild sexual references, but no suggestive content, revealing clothing, or nudity; occasional or mild inappropriate language, but no swearing or more severe offensive language; and occasional or mild crude or vulgar humor.
Ages 16+	Apps at this rating level may contain: frequent or more intense depictions of violence and blood, including content involving self-harm guidance, but shall not encourage the most extreme, brutal, or graphic violent behaviors; frequent or more intense startling or horror-inducing elements, but no persistently extreme horror-inducing content; frequent or more intense sexual references, but no sexual acts, sexual suggestions, revealing or provocative clothing, nudity, or intimate contact; simulated gambling, or services such as companion gaming, practice partnering, or in-game leveling; frequent or more intense inappropriate language, but no sex‑related profanity; and depictions of restricted items (e.g., tobacco, alcohol).
Ages 18+	Apps at this rating level may contain: frequent and intense violent content; frequent and intense horror-inducing elements; frequent and intense pornographic content; gambling; sex‑related profanity; and glorification of restricted items (e.g., tobacco, alcohol).

3. Online Information Labeling Functions Concerning Minors

If any app distributed to users under the age of 18 has the function of creating, copying, publishing, or disseminating online information, the app shall provide a prominent prompting function to guide and regulate users to add reminders to relevant information. Specific methods include:

(1) adding text prompts or universally recognized symbol marks at the beginning, end, or appropriate positions within the text, or placing prominent labels on the interactive interface or adjacent to the text content;

(2) adding voice prompts or rhythmic audio cues at the beginning, end, or appropriate positions within the audio, or placing prominent labels on the interactive interface;

(3) adding prominent labels at appropriate positions on an image or on the interactive interface;

(4) adding prominent labels at the beginning of a video and at appropriate positions around the video playback area, or optionally adding prominent labels at the end and at appropriate positions in the middle of a video, or adding prominent labels on the interactive interface;

(5) (In case of a virtual scene) adding prominent labels at an appropriate position on the starting screen or optionally adding prominent label at appropriate positions during the continuous provision of virtual scene services; and

(6) adding prominent labels based on the characteristics of other service scenarios.

4. Parental Supervision Tools and Developer Responsibilities

(1) Supervision function: Developers of apps that are directed at minors or may be widely used by minors shall provide necessary parental supervision tools, including but not limited to usage time management, content filtering, and consumption approval functions.

(2) Self-assessment and changes: During app submission and version updates, developers shall proactively conduct self-assessments of minor protection risks and reassess the adequacy of protection mechanisms when there are material changes to app functionalities.

(3) Complaint handling: Developers shall provide clear and user-friendly reporting channels for minor protection within apps. The platform will prioritize the handling of complaints involving minors.

If the platform identifies any app as posing significant risks in terms of minor protection, we reserve the right to require the developer to rectify the app, restrict certain functionalities, or remove the app from the platform.