严重违规的APP可能会被断网！规范移动应用全链条生态，工信部新规逐条看
Seriously Non-Compliant APPs May Be Disconnected from the Network! A Detailed Analysis of MIIT's New Regulations Governing the Full-Chain Ecosystem of Mobile Applications
严重违规的APP可能会被断网！规范移动应用全链条生态，工信部新规逐条看
Seriously Non-Compliant APPs May Be Disconnected from the Network! A Detailed Analysis of MIIT's New Regulations Governing the Full-Chain Ecosystem of Mobile Applications
简要归纳
工信部于今年2月份印发通知，为应对目前移动互联网应用服务的现状，提升行业服务能力与用户体验，共提出26条措施再次加强规范移动互联网应用服务提供商。
与以往仅提及应用开发商和平台不同，本次通知进一步深入到了整个移动互联网产业的上下游，包含了从APP开发运营者、分发平台、SDK（软件开发工具）、终端和接入企业全生命链条的规范。同时加强了违规限制，从下架进一步提升到了“按照电信监管部门要求，依法对违规APP、SDK采取停止接入等必要措施”。
本文将依据通知全文进行简单分析。
*本文内容不代表任何法律建议。
工业和信息化部关于进一步提升移动互联网应用服务能力的通知
工信部信管函〔2023〕26号
近年来，工业和信息化部大力推动提升移动互联网应用服务质量，切实维护用户合法权益，取得积极社会成效，但部分企业服务行为不规范、相关环节责任落实不到位等问题仍时有发生。为优化服务供给，改善用户体验，维护良好的信息消费环境，促进行业高质量发展，依据《个人信息保护法》《电信条例》《规范互联网信息服务市场秩序若干规定》《电信和互联网用户个人信息保护规定》等相关法律法规规章，现就有关事项通知如下：
一、 提升全流程服务感知，保护用户合法权益
（一）规范安装卸载行为
- 确保知情同意安装。向用户推荐下载APP应遵循公开、透明原则，真实、准确、完整地明示开发运营者、产品功能、隐私政策、权限列表等必要信息，并同步提供明显的取消选项，经用户确认同意后方可下载安装，切实保障用户知情权、选择权。不得通过“偷梁换柱”“强制捆绑”“静默下载”等方式欺骗误导用户下载安装。
分析
本条是针对平台、买量宣传网页等环境所做出的限制。
当向用户推荐下载游戏时，必须在页面列明相关的必要信息，同时要确保“所见即所得”。
最重要是必须用户点击同意才能下载安装，不能直接自动或在页面停留几秒后就自动下载（例如通过JavaScript制作定时器（Timer）自动下载脚本）。
- 规范网页推荐下载行为。在用户浏览页面内容时，未经用户同意或主动选择，不得自动或强制下载APP，或以折叠显示、主动弹窗、频繁提示等方式强迫用户下载、打开APP，影响用户正常浏览信息。无正当理由，不得将下载APP与阅读网页内容相绑定。
分析
本条更偏向于同时提供网页和移动端阅读的应用。以往常见的网页隐藏一半文章然后提示“下载/打开某某某APP阅读余下内容”、看到一半弹窗提示“下载/打开某某某APP阅读余下内容”等推广行为将会被认定违规。
有相关设计的网页建议尽快更换设计。
- 实现便捷卸载。除基本功能软件外，APP应当可便捷卸载，不得以空白名称、透明图标、后台隐藏等方式恶意阻挠用户卸载。
分析
去年已有媒体报道过类似的空白图标行为。
有某些不良软件会以空白png图标和隐藏APP名称的方式，增加用户删除的困难。本次通知正式把此类行为定性为违规。
建议不要采取此类方式制作“隐藏式”推广程序。
（二）优化服务体验
- 窗口关闭用户可选。开屏和弹窗信息窗口提供清晰有效的关闭按钮，保证用户可以便捷关闭；不得频繁弹窗干扰用户正常使用，或利用“全屏热力图”、高灵敏度“摇一摇”等易造成误触发的方式诱导用户操作。
分析
再次针对开屏广告弹窗的方式进行规范。
如游戏公司要打造自己下载平台的，需要留意开屏广告跳转的设计，避免采用上述的违规方式。
- 服务事项提前告知。清晰明示产品功能权益及资费等内容，存在开通会员、收费等附加条件的，应当显著提示。未经明示，不得在提供产品服务过程中擅自添加限制性条件，并以此为由终止用户正常使用的产品功能和服务，或降低服务体验。
分析
针对前些时间纷纷扰扰的“投屏限制”投诉，本条出来之后，在投诉时就可以有理可循了。
在游戏产品中，如果涉及到“月卡”“通行证”等类似常见的“会员”收费性服务时，也可能会涉及到本条内容。因此，针对已经“销售”的产品，在到期前均不能进行任何降低用户权益的行为。
针对日后销售的产品，如预计确实需要变更功能和服务内容的，需在销售页面（最低限度用户协议且需要玩家重新签署）中，【明示】可能根据时间和实际变化，并在实际变化后【明示】告知玩家。
- 启动运行场景合理。在非服务所必需或无合理场景下，不得自启动和关联启动其它APP，或进行唤醒、调用、更新等行为。
分析
再次强调了对自启动和连锁启动的限制，甚至增加了限制“更新”的内容。
对于游戏平台，需增加用户允许后台更新游戏的设置；
对于游戏本身，应避免自我唤醒（哪怕要更新）。
- 服务续期及时提醒。采取自动续订、自动续费方式提供服务的，应当征得用户同意，不得默认勾选、强制捆绑开通。在自动续订、自动续费前5日以短信、消息推送等显著方式提醒用户，服务期间提供便捷的随时退订方式和自动续订、自动续费取消途径。
分析
不允许默认勾选和强制捆绑已算是老生常谈了，本次通知主要确定了自动续期的提醒时效。
如果游戏设计了“自动续费”“自动续期”等类似功能的，需要新增在到期（续费）前5日进行短信或推送的功能。
注意：短信通知或推送功能依据以往的法规也需要用户同意，因此需要在玩家确定“自动续费”时就要通过用户协议勾选或类似的方式让玩家同意相关推送通知功能。
（三）加强个人信息保护
- 坚持合法正当必要原则。从事个人信息处理活动，应具有明确合理的目的，不得仅以服务体验、产品研发、算法推荐、风险控制等为由，强制要求用户同意超范围或者与服务场景无关的个人信息处理行为。用户拒绝提供非当前服务所必需的个人信息时，不得影响用户使用该服务的基本功能。
分析
再次新增了不允许“超范围”收集的“理由”，游戏公司需要按照上述内容调整用户协议。
再次强调了玩家不提供非必要个人信息（权限）也可使用基本功能。针对游戏这一类型，【当前服务所必需的个人信息】只为手机号码以及身份证实名信息。
- 明示个人信息处理规则。通过简洁、清晰、易懂的方式告知用户个人信息处理规则，如发生变动，应及时告知用户最新情况。突出显示敏感个人信息的处理目的、方式和范围，建立已收集个人信息清单，不得采用默认勾选、缩小文字、冗长文本等方式诱导用户同意个人信息处理规则。
分析
简单来说就是：
（1）用户协议、隐私协议变更时需要通知玩家；
（2）涉及敏感个人信息处理的内容要【加粗】、【增大字体】、【加框】等方式突出显示；
（3）不能默认勾选同意框，不能用超长的文本描述收集内容（多分段）。
- 合理申请使用权限。在对应业务功能启动时，动态申请所需权限，不得要求用户一揽子同意多个非本业务功能的必要权限。在调用终端相册、通讯录、位置等权限时，同步告知用户申请该权限的目的。未经用户同意，不得更改用户未授权权限状态。
分析
再次强调要动态申请权限。
实务中就是，除非玩家点到那个功能，否则不能在进入游戏时把全部权限允许框一股脑展示给玩家。
同时申请权限时，要把获取的目的提供给玩家，不能单纯只弹权限申请。
（四）响应用户诉求
- 设立客服热线。鼓励互联网企业建立客服热线，主要互联网企业在网站、APP显著位置公示客服热线电话号码，简化人工服务转接程序。鼓励提高客服热线响应能力，月均响应时限最长为30秒，人工服务应答率超过85％。
分析
考虑到目前只是【鼓励】，只需要了解即可。
要求中的响应时限30秒、应答率超过85%，可见整体成本会较高，目前非强制阶段可以先了解准备，未来强制执行或有足够能力实施后再执行即可。
- 妥善处理用户投诉。公布有效联系方式，接受用户投诉。按照规范要求答复互联网信息服务投诉平台上的投诉，确保15日内处理完成，提高投诉处理满意率。鼓励在APP中设置用户满意度测评链接，引导用户参与测评。
分析
明确确认了12345等投诉工单的处理时限，需在收到工单后15日内处理完毕（考虑到转交的时间问题，建议以玩家投诉之日算起15日内比较合适）。
同时可考虑在网站或游戏中设置满意度调查问卷（虽然也是鼓励，但这项成本比电话客服低），方便处理投诉，也满足本通知的要求。
二、 提升全链条管理能力，营造健康服务生态
（一）落实APP开发运营者主体责任
- 完善内部管理机制。明确用户服务和权益保护的牵头管理部门和负责人，建立全生命周期个人信息保护机制，健全考核问责制度，将相关法规政策要求落实到产品研发、推广和运营各环节，不断提高合规水平。定期对个人信息保护措施及执行情况等进行合规审计，有效防范风险隐患。
分析
要求明确客户服务和保障的部门和负责人（以便配合工作和处理追责）。同时要求研发、推广、运营的各个环节都必须落实各项法律法规政策，还需要定期进行合规审计，防范风险隐患。
目前新推出的各项法律法规均在不断强调用户个人信息保护等内容，并逐渐加重违规的惩罚程度，做到全流程合规将是每家企业必须考虑到的内容。
考虑到法律法规数量多、范围广，可考虑寻找合适的专业机构或团队，提供全方位、专业化的个人信息保护方案，为企业在竞争激烈的市场中赢得合规优势，增强企业品牌形象和公信力，避免因合规风险而错失市场。
- 增强技术保障能力。采取访问控制、技术加密、去标识化等安全技术措施，加强前端和后端安全防护。主动监测发现个人信息泄露、窃取、篡改、毁损、丢失、非法使用等风险威胁，及时响应处置要求。
分析
加钱买保障，加强技术能力，及时打安全补丁。
要从技术上尽量避免个人信息泄露的风险。
3.加强软件开发工具（SDK）使用管理。使用SDK前对其进行个人信息保护能力评估，通过合同等形式明确约定各方权利和义务，确保个人信息处理依法合规。集中展示并及时更新嵌入的SDK名称、功能及其处理个人信息的规则。共同处理用户个人信息，侵害用户权益造成损害的，依法承担相应责任。
分析
明确提出应对SDK也要进行合规管理，需要进行风险评估、合同约束，还要在用户协议/隐私协议中列明接入SDK的相关信息。
本条还提到，如果两方共同处理用户个人信息的，在侵犯到用户权益时，要依法承担相应责任。因此前期风险评估以及合同条款的拟定将会成为企业避免被第三方合规风险拖累的重要途径。
（二）强化平台分发管理
- 严格APP上架审核。准确登记并核验APP开发运营者的真实身份和联系方式、APP的主要功能及用途等基本信息，并对拟上架APP进行技术检测。相关审核应明确负责人，并留存审核日志记录，不符合要求的不予上架。全量公示在架APP，并在显著位置标明APP名称及功能、开发运营者、版本号、所需获取的用户终端权限列表及用途、个人信息处理规则等信息。尚未建立分发明示界面的，应将APP下载链接到应用商店，引导用户从正规渠道下载所分发的APP。
分析
可以分三段理解这条内容:
（1）分发平台要严格审核拟上架APP并明确审查负责人和审查日志，存在事后追责的可能性。意味着以后上架分发平台/应用商店将可能越发严格；
（2）分发平台要全量公示在架的APP，并明确显示APP的相关信息；
（3）如果没法做到上面这一条的，只能跳转到各大应用商店，不能提供下载功能（意味着不合规就不给做分发下载）。
- 强化在架APP巡查。加强对APP的动态巡查，确保公示信息真实准确。对与公示信息不一致，或采用“热更新、热切换”等方式擅自更改APP主要功能、申请的权限、个人信息收集使用的场景和范围等违规APP，应当停止提供服务。
分析
分发平台要对在架APP加强巡查，很多游戏（尤其买量游戏）以往采取“先上架再热更新、热切换”的方式将会视为违规，会被要求【应当】停止服务（下架）。
- 完善分发管理机制。建立APP开发运营者信用评价、风险提示等机制，鼓励对分发APP进行电子签名认证，实现上架应用、分发行为全流程可溯源。加强与面向移动互联网应用程序的检测及认证公共服务平台联动，做好信息上报、监测溯源、信息共享、响应处置工作。
分析
分发平台要为上架APP以及其开发商建立信用评级和风险提示的功能（绿黄红牌等，需要要较为明显的提示）。
考虑采用电子签等方式确认APP溯源（可能不利于换皮换名买量），并与相关公共服务平台联动，配合有关部门的监管工作。
（三）规范SDK应用服务
- 建立信息公示机制。公开明示SDK名称、开发者、版本号、主要功能、使用说明等基本信息，以及个人信息处理规则。SDK独立采集、传输、存储个人信息的，应当单独作出说明。鼓励发挥SDK管理服务平台作用，引导APP开发运营者使用合规的SDK。
分析
在提供SDK分发功能的界面及其他明显的位置要提供相应的信息，并建议制作通用的SDK信息文档供APP开发运营商使用（粘贴到他们的隐私协议中）。
- 优化功能配置。遵循最小必要原则，根据不同应用场景或用途，明确SDK功能和对应的个人信息收集范围，并向APP开发运营者提供功能模块及个人信息收集的配置选项，不得一揽子过度收集个人信息。
分析
与前文APP开发者一样的收集限制，同样必须“用到才要权限”，不能“一揽子获取”。
- 加强服务协同。在产品使用全生命周期过程中，通过明确易懂的方式主动向APP开发运营者提供合规使用指南，引导APP开发运营者正确合理使用，共同提高合规水平。当个人信息处理规则变更或发现风险时，及时更新并告知APP开发运营者。
分析
暗示了SDK提供商有比APP开发运营者更多的合规义务。
SDK提供商要为APP开发者提供合规指南，指导对方如何合规使用，并且在规则变更和发现风险时要及时告知APP开发者。
考虑到这是【义务性】规范，SDK提供商必须准备好相关的文档和提示风险功能，减少被认定“监管不力”的风险。
（四）筑牢终端安全防线
这部分涉及的是终端（手机、平板等设备）提供商的规范，通常和软件相关开发者无关，但也可以了解一下即将会来的监管内容，提前做好准备。
- 强化APP运行管理。为用户提供APP自启动和关联启动的关闭功能，以及便捷的相关设备识别码重置选项，加强对APP静默下载、热更新的监测，防范未经用户同意私自启动、下载、安装等行为。
分析
本条最重要的内容是终端要研发【设备识别码重置】功能和【热更新】监测功能。
前者意味着追踪用户更加困难，后者意味着各种补丁的更新都可能会被提示。
- 加强APP行为记录提醒。增强对权限调用行为的记录能力，为用户查询权限调用情况提供便利。建立通讯录、麦克风、相机、位置、剪切板等权限在用状态的明显提示机制，保障用户及时准确了解个人信息收集状态。
分析
考虑到目前主流手机系统都有相关功能，本条属于再次强调。
- 提高APP风险预警能力。推动开展APP电子签名认证，并向用户进行预警提示，提高对仿冒、不良、违规等风险APP的识别能力。
分析
目前主流手机系统都有相关功能，通常只是提示风险，但后续是否将会对未经过签名验证的软件进行其他限制，需要我们留意。
（五）夯实接入企业责任
- 准确登记信息。在为APP、SDK提供网络接入服务时，登记并核验APP、SDK开发运营者的真实身份、联系方式等信息，提高溯源能力。
分析
接入开发商时需要实名认证，目前主流分发平台和APP应用商店基本均已做到，属于再次强调要求。
- 确保有效处置。按照电信监管部门要求，依法对违规APP、SDK采取停止接入等必要措施，有效阻止其侵害用户权益的违规行为。
分析
从【下架】（但仍能运营）变成了【停止接入】（停运），违规成本显著性提高，合规工作必须放在重要位置。
三、 工作要求
（一）抓好组织落实。各单位要坚持以人民为中心的发展思想，提高政治站位，强化责任担当，细化分解任务，认真抓好本通知的贯彻实施，确保取得实效。相关企业要落实主体责任，对照本通知要求开展自查自纠，切实维护用户合法权益。同时，健全长效机制，创新模式方法，不断提升移动互联网应用服务水平，不断增强用户的获得感、幸福感、安全感。
分析
考虑到本通知发布即生效，各大企业自查自纠的工作需尽快开展，以尽快合规。
并需要建立长效的合规机制，在以后的各个产品中进行审查，避免产生不必要的风险。
（二）加强指导监督。工业和信息化部健全完善测评、通报、排名、公示机制，推动工作扎实有序开展，及时总结、推广优秀案例和经验做法。各地通信管理局要加强监督检查，指导督促属地企业落实本通知各项要求。对落实不到位或出现违规行为的，依法采取责令限期整改、向社会公告、组织下架等措施，严肃问责查处。
分析
监管机构增加了【通讯管理局】，对于落实不到位的机构也要进行问责。
本条也规定了具体的惩罚行为：限期整改、向社会公告、下架（以及上文提及的，由电信部门组织的停止接入）。
（三）强化技术运用。中国信息通信研究院要组织产业力量，综合运用人工智能、大数据等新技术新手段，升级打造面向移动互联网应用程序的全国检测及认证公共服务平台，持续完善平台功能，做好技术检测、监测服务和监管支撑工作。积极推广应用电子签名认证等可溯源技术手段，促进提高服务管理能力。
分析
官方即将推出应用电子签名认证等技术服务，以后版号申请可能会增加【接入电子签名认证】的相关内容。
同时考虑到官方对于“换名包”的态度，以后没有版号的包可能无法获得电子签名而被终端提示风险。
（四）推动行业自律。鼓励行业协会及相关机构制定行业自律公约、技术标准、服务规范，加强评估认证和人才培养。进一步畅通渠道倾听群众意见，促进各方交流互动，引导企业依法合规经营，不断优化改进服务，营造争先创优、互促共进的良好环境，以高质量服务促进高质量发展。
分析
表达了官方的态度，要“依法合规经营，不断优化改进服务，营造争先创优、互促共进的良好环境，以高质量服务促进高质量发展”。
2023年2月6日
总结
本次通知的发布，比以往的通知更“接地气”，跟“贴合业务实际”，足以可见官方已经逐渐摸清了移动互联网业务的各链条的情况。
随着新一代群体开始任职相关部门，可预见监管工作将越来越细致，越来越“懂”，以前野蛮生长时代的各种“手段”都会被发现，以后新出现的手段也会越快被阻止，不合规的推广手段可能会成为一把“双刃剑”，在获利的同时也会带来风险。
【合规】审查，将会成为未来移动互联网软件开发过程中的一个重要的工序，也会是上线运营的前提。
Brief Summary:
In February this year, the Ministry of Industry and Information Technology (MIIT) issued a notice to address the current state of mobile internet application services, enhance industry service capabilities and user experience, and proposed 26 measures to further regulate mobile internet application service providers.
Unlike previous regulations that only mentioned app developers and platforms, this notice further delves into the upstream and downstream of the entire mobile internet industry, including regulation of the full life cycle of APP developers and operators, distribution platforms, SDKs (Software Development Kits), terminals, and access enterprises. At the same time, it strengthens penalties for violations, going beyond removal from app stores to “in accordance with the requirements of telecommunications regulatory authorities, lawfully taking necessary measures such as stopping access for non-compliant APPs and SDKs.”
This article provides a simple analysis based on the full text of the notice.
This article does not represent any legal advice.
Ministry of Industry and Information Technology Notice on Further Improving Mobile Internet Application Service Capabilities
MIIT Xin Guan Han [2023] No. 26
In recent years, the Ministry of Industry and Information Technology has vigorously promoted the improvement of mobile internet application service quality and effectively safeguarded users’ legitimate rights and interests, achieving positive social effects. However, problems such as non-standardized service behaviors of some enterprises and inadequate implementation of responsibilities in related areas still occur from time to time. In order to optimize service supply, improve user experience, maintain a good information consumption environment, and promote high-quality development of the industry, and in accordance with relevant laws, regulations, and rules such as the “Personal Information Protection Law,” “Telecom Regulations,” “Provisions on Standardizing the Order of the Internet Information Services Market,” and “Provisions on the Protection of Telecommunications and Internet User Personal Information,” the relevant matters are hereby notified as follows:
I. Improving Full-Process Service Perception and Protecting Users’ Legitimate Rights and Interests
(I) Standardizing Installation and Uninstallation Behaviors
- Ensure informed consent for installation. When recommending APP downloads to users, the principles of openness and transparency should be followed, and necessary information such as the developer and operator’s name, product functions, privacy policies, and permission lists should be truthfully, accurately, and completely indicated, with obvious cancellation options provided simultaneously. Downloads and installations should only proceed after user confirmation and consent, effectively protecting users’ rights to know and choose. Users must not be deceived or misled into downloading and installing through methods such as “substitution,” “forced bundling,” or “silent downloads.”
Analysis:
This article addresses restrictions on platforms and promotional webpages for downloads.
When recommending game downloads to users, the necessary information must be listed on the page, and it must be ensured that “what you see is what you get.”
Most importantly, user consent must be obtained through clicking before download and installation can proceed. Automatic downloads or downloads triggered after a page停留 (dwell) time without user action (for example, using JavaScript to制作 (create) timer automatic download scripts) are not permitted.
- Standardize webpage recommendation download behaviors. When users are browsing page content, apps should not be automatically or forcefully downloaded without user consent or active selection, nor should users be forced to download or open apps through methods such as folded displays, active pop-ups, or frequent prompts. Without justified reasons, downloading an app should not be tied to reading webpage content.
Analysis:
This article is more oriented toward applications that provide both webpage and mobile reading. Previous common practices such as hiding half an article on a webpage and then prompting “Download/Open [App Name] to read the rest” or showing a pop-up prompting “Download/Open [App Name] to read the rest” halfway through reading will be deemed non-compliant.
Webpages with such designs are advised to revise their designs as soon as possible.
- Achieve convenient uninstallation. Except for basic function software, apps should be conveniently uninstallable and should not maliciously obstruct users from uninstalling through methods such as blank names, transparent icons, or background hiding.
Analysis:
Similar blank icon behaviors were reported in the media last year.
Some unscrupulous software increases the difficulty for users to delete by using blank PNG icons and hiding app names. This notice officially characterizes such behaviors as non-compliant.
It is advised not to adopt such methods to create “hidden” promotional programs.
(II) Optimizing Service Experience
- Window closing is user-optional. Pop-up information windows such as splash screens and pop-ups should provide clear and effective close buttons so that users can conveniently close them; frequent pop-ups should not interfere with users’ normal use, nor should users be induced to perform operations through easily-mistriggered methods such as “full-screen heatmaps” or highly sensitive “shake to activate.”
Analysis:
This再次 (again) addresses standardization of splash screen ad pop-up methods.
For game companies building their own download platforms, attention should be paid to splash screen ad redirect designs, avoiding the aforementioned non-compliant methods.
- Service matters should be clearly informed in advance. Product function rights and charges should be clearly indicated. If there are附加 (additional) conditions such as membership activation or charges, they should be prominently indicated. Without clear indication, restrictive conditions should not be added in the process of providing products and services, nor should users’ normal use of product functions and services be terminated, or service experience be reduced on this basis.
Analysis:
Regarding the “screen casting restrictions” complaints that have been buzzing around recently, this article provides a basis for complaints.
For game products, if “monthly cards,” “battle passes,” and similar common “membership” chargeable services are involved, this article may also apply. Therefore, for products already “sold,” no actions that reduce user rights may be taken before expiration.
For products sold in the future, if product functions and service content are expected to need changes, they must be [clearly indicated] on the sales page (at minimum the user agreement, and players need to re-sign) that changes may occur based on time and actual circumstances, and players must be [clearly informed] after actual changes.
- Startup and running scenarios should be reasonable. Without services being necessarily required or in unreasonable scenarios, apps should not self-start and associate-start other apps, nor perform behaviors such as waking up, calling, or updating.
Analysis:
This再次 (again) emphasizes restrictions on self-starting and chained starting, even adding restrictions on “updating.”
For game platforms, settings allowing users to permit background game updates need to be added;
For games themselves, self-waking should be avoided (even for updates).
- Timely reminders for service renewals. For services provided through automatic renewal or automatic subscription methods, user consent should be obtained. Default selections should not be checked, nor should membership be forcibly bundled. Users should be reminded 5 days before automatic renewal or automatic subscription through prominent methods such as SMS or push notifications. During the service period, convenient unsubscription methods and automatic renewal or subscription cancellation channels should be provided.
Analysis:
Non-compliant default selection and forced bundling have been老生常谈 (a common topic) for a long time. This notice mainly confirms the reminder timing for automatic renewals.
If games have designed functions such as “automatic renewal” or “automatic subscription,” a function for SMS or push notifications 5 days before expiration (renewal) needs to be added.
Note: SMS notification or push notification functions also require user consent according to previous regulations. Therefore, when users confirm “automatic renewal,” they must also obtain user consent for related push notification functions through user agreement checkboxes or similar methods.
(III) Strengthening Personal Information Protection
- Adhere to the principles of legality,正当 (legitimacy), and necessity. Personal information processing activities should have clear and reasonable purposes. Users should not be required to consent to personal information processing behaviors beyond scope or unrelated to service scenarios solely on the grounds of service experience, product research and development, algorithm recommendations, or risk control. When users refuse to provide non-essential personal information for current services, the basic functions of those services should not be affected.
Analysis:
It再次 (again) adds that “beyond scope” collection is not permitted as a reason. Game companies need to adjust user agreements according to the above.
It再次 (again) emphasizes that players can use basic functions without providing non-essential personal information (permissions). For the type of games, [personal information essential for current services] only includes mobile phone numbers and ID card real-name information.
- Clearly indicate personal information processing rules. Users should be informed of personal information processing rules through concise, clear, and easy-to-understand methods. If changes occur, users should be promptly informed of the latest situation. Processing purposes, methods, and scope of sensitive personal information should be prominently displayed. An inventory of collected personal information should be established. User consent to personal information processing rules should not be obtained through default checkboxes,缩小 (shrinking) text, or冗长 (lengthy) text.
Analysis:
In simple terms:
(1) When user agreements or privacy policies change, players need to be notified;
(2) Content involving sensitive personal information processing needs to be [bolded], [enlarged], or [boxed] for prominent display;
(3) Default consent checkboxes cannot be used, and lengthy text describing collection content cannot be used (break it into more paragraphs).
- Reasonably apply for and use permissions. Required permissions should be dynamically applied when corresponding business functions are started. Users should not be required to give blanket consent to multiple permissions not essential for the current business function. When calling terminal photo albums, address books, locations, etc., users should同步 (simultaneously) be informed of the purpose of applying for that permission. Without user consent, the status of unauthorized permissions should not be changed.
Analysis:
It再次 (again) emphasizes dynamic permission application.
In practice, unless a player clicks on that function, all permission allow boxes cannot be displayed to players when entering a game.
At the same time, when applying for permissions, the purpose of obtaining them must be provided to players. Permission application dialogs alone are not sufficient.
(IV) Responding to User Requests
- Establish customer service hotlines. Internet enterprises are encouraged to establish customer service hotlines. Major internet enterprises should post customer service hotline numbers in prominent positions on their websites and apps, and simplify procedures for transferring to human services. Encouraging improvement of customer service hotline response capabilities, with average monthly response time not exceeding 30 seconds and human service response rate exceeding 85%.
Analysis:
Considering that this is currently only [encouraged], only understanding is needed.
The response time of 30 seconds and response rate exceeding 85% in the requirements可见 (show) overall costs will be relatively high. At the current non-mandatory stage, one can first understand and prepare. When mandatory implementation occurs or sufficient capabilities are available, implementation can proceed.
- Properly handle user complaints. Effective contact methods should be published to accept user complaints. Complaints on the internet information services complaint platform should be answered according to standards, ensuring processing is completed within 15 days and improving complaint handling satisfaction rates. Encouraging setting satisfaction survey links in apps to guide users to participate in surveys.
Analysis:
It clearly confirms the processing time limit for complaints such as 12345 work orders—processing must be completed within 15 days of receiving the work order (considering transfer time, it is recommended to calculate from the date of player complaint for 15 days).
At the same time, one can consider setting satisfaction surveys on websites or in games (though this is also encouraged and has lower costs than hotline customer service), facilitating complaint handling and meeting the notice’s requirements.
II. Improving Full-Chain Management Capabilities and Creating a Healthy Service Ecosystem
(I) Implementing APP Developer and Operator Subject Responsibility
- Improve internal management mechanisms. Clearly designate leading management departments and responsible persons for user services and rights protection, establish personal information protection mechanisms for the full life cycle, improve assessment and accountability systems, implement relevant laws, regulations, and policy requirements in all aspects of product research and development, promotion, and operation, and continuously improve compliance levels. Regular compliance audits of personal information protection measures and implementation should be conducted to effectively prevent risk hazards.
Analysis:
It requires clearly designating departments and responsible persons for customer service and protection (so as to cooperate with work and handle accountability). At the same time, it requires that all laws, regulations, and policies must be implemented at all stages of research, promotion, and operation, and regular compliance audits are needed to prevent risk hazards.
The various new laws and regulations recently introduced continuously emphasize personal information protection and gradually increase penalties for violations. Full-process compliance will be something every enterprise must consider.
Considering the large number and wide scope of laws and regulations, one may consider seeking suitable professional institutions or teams to provide comprehensive and professional personal information protection solutions, gaining compliance advantages in the competitive market, enhancing corporate image and credibility, and avoiding missing markets due to compliance risks.
- Enhance technical guarantee capabilities. Adopt security technical measures such as access control, technical encryption, and去标识化 (de-identification), and strengthen front-end and back-end security protection. Proactively monitor and detect risks such as personal information leakage,窃取 (theft), tampering, destruction, loss, and illegal use, and promptly respond to and handle requirements.
Analysis:
Spend money to buy protection, strengthen technical capabilities, and promptly apply security patches.
Technically minimize the risk of personal information leakage.
- Strengthen SDK usage management. Conduct personal information protection capability assessments of SDKs before use. Clearly stipulate respective rights and obligations through contracts and other forms to ensure lawful and compliant personal information processing. Concentratedly display and promptly update the names, functions, and personal information processing rules of embedded SDKs. When jointly processing users’ personal information and causing damage to users’ rights, bear corresponding legal responsibility in accordance with the law.
Analysis:
It clearly proposes that SDK compliance management is also required, including risk assessment, contract constraints, and indication of related SDK information in user agreements/privacy policies.
This article also mentions that if two parties jointly process users’ personal information and infringe upon users’ rights, they must bear corresponding legal responsibility. Therefore, advance risk assessment and contract clause drafting will become important ways for enterprises to avoid being dragged down by third-party compliance risks.
(II) Strengthening Platform Distribution Management
- Strictly review APP上架 (listing). Accurately register and verify basic information such as the true identity and contact information of APP developers and operators, main functions and purposes of APPs, and conduct technical testing of apps planned for listing. Relevant reviews should clearly designate responsible persons and retain review log records. Those not meeting requirements should not be listed. Fully publicly display apps on shelves, and indicate APP names and functions, developers and operators, version numbers, required user terminal permission lists and purposes, personal information processing rules, and other information in prominent positions. Those that have not yet established a distribution display interface should redirect APP download links to app stores, guiding users to download distributed apps from official channels.
Analysis:
This can be understood in three parts:
(1) Distribution platforms must strictly review apps planned for listing and clearly designate review responsible persons and review logs—there is the possibility of post-hoc accountability. This means listing on distribution platforms/app stores may become increasingly strict in the future;
(2) Distribution platforms must fully display listed apps and clearly show related app information;
(3) If the above cannot be achieved, one can only redirect to major app stores without providing download functions (meaning non-compliance means no distribution downloads).
- Strengthen巡查 (inspection) of listed apps. Strengthen dynamic inspection of apps to ensure publicly displayed information is truthful and accurate. For non-compliant apps whose publicly displayed information is inconsistent, or that擅自 (unauthorized) change main app functions, applied permissions, personal information collection and usage scenarios and scope through methods such as “hot updates” and “hot switching,” distribution of services should be stopped.
Analysis:
Distribution platforms must strengthen inspections of listed apps. Many games (especially user acquisition games) that previously adopted the approach of “listing first, hot updating, and hot switching later” will be deemed non-compliant and will be required to [stop] providing services (remove from shelves).
- Improve distribution management mechanisms. Establish mechanisms such as APP developer and operator credit evaluation and risk alerts, encourage electronic signature certification for distributed apps, and achieve full-process traceability of listed applications and distribution behaviors. Strengthen linkage with public service platforms for testing and certification of mobile internet applications, and do well in information reporting, monitoring and traceability, information sharing, and response and disposal.
Analysis:
Distribution platforms need to establish credit ratings and risk alerts for listed apps and their developers (green, yellow, red cards, etc.—need relatively obvious prompts).
Consider adopting electronic signatures and other methods to confirm APP traceability (which may not be conducive to repackaged and renamed user acquisition). Link with related public service platforms to cooperate with regulatory work.
(III) Standardizing SDK Application Services
- Establish information disclosure mechanisms. Publicly indicate basic information such as SDK names, developers, version numbers, main functions, usage instructions, and personal information processing rules. If SDKs independently collect, transmit, or store personal information, separate explanations should be provided. Encourage leveraging SDK management service platforms to guide APP developers and operators to use compliant SDKs.
Analysis:
Provide corresponding information on interfaces providing SDK distribution functions and other prominent positions, and it is advised to制作 (produce) general SDK information documents for APP developers and operators to use (paste into their privacy policies).
- Optimize function configurations. Adhere to the minimum necessary principle. According to different application scenarios or purposes, clarify SDK functions and corresponding personal information collection scope, and provide APP developers and operators with configuration options for function modules and personal information collection. Do not collect personal information in a bundled manner.
Analysis:
Same collection restrictions as for APP developers above—permissions should only be requested when needed, and “bundled collection” is not permitted.
- Strengthen service coordination. During the entire product usage life cycle, proactively provide APP developers and operators with compliant usage guides through clear and understandable methods, guide APP developers and operators to correctly and reasonably use them, and jointly improve compliance levels. When personal information processing rules change or risks are discovered, promptly update and inform APP developers and operators.
Analysis:
This implies that SDK providers have more compliance obligations than APP developers.
SDK providers must provide APP developers with compliance guides, guide them on how to use compliance, and promptly inform APP developers when rules change and risks are discovered.
Since this is an [obligatory] regulation, SDK providers must prepare related documents and risk notification functions to reduce the risk of being found “lax in regulation.”
(IV) Building Terminal Security Defense Lines
This part involves regulations for terminal (mobile phones, tablets, etc.) providers and is usually unrelated to software-related developers. However, one can understand the upcoming regulatory content to prepare in advance.
- Strengthen APP operation management. Provide users with functions to close APP self-starting and associated starting, as well as convenient options to reset device identification codes. Strengthen monitoring of app silent downloads and hot updates, and prevent behaviors such as unauthorized starting, downloading, or installing.
Analysis:
The most important content of this article is that terminals need to develop [device identification code reset] functions and [hot update] monitoring functions.
The former means user tracking is more difficult. The latter means various patch updates may be prompted.
- Strengthen APP behavior record reminders. Enhance the capability to record permission call behaviors and provide convenience for users to query permission call situations. Establish obvious reminder mechanisms for the in-use status of permissions such as address books, microphones, cameras, locations, and clipboards, ensuring users can timely and accurately understand personal information collection status.
Analysis:
Considering that current mainstream mobile operating systems already have related functions, this article is mainly reiterating.
- Improve APP risk early warning capabilities. Promote the development of APP electronic signature certification and early warning notifications to users, and improve the capability to identify counterfeit, non-compliant, and violative apps.
Analysis:
Current mainstream mobile operating systems already have related functions, usually only prompting risks. Whether subsequent restrictions will be imposed on software that has not undergone signature verification requires our attention.
(V) Consolidating Access Enterprise Responsibilities
- Accurately register information. When providing network access services for APPs and SDKs, register and verify the true identity, contact information, and other information of APP and SDK developers and operators to improve traceability.
Analysis:
Identity verification is required when accessing developers. Current mainstream distribution platforms and APP stores have basically already done this—it is mainly reiterating requirements.
- Ensure effective disposal. In accordance with the requirements of telecommunications regulatory authorities, lawfully take necessary measures such as stopping access for non-compliant APPs and SDKs, and effectively prevent their non-compliant behaviors that harm users’ rights.
Analysis:
This changes from [removal from shelves] (but still operational) to [stopping access] (ceasing operations). The cost of violations significantly increases—compliance work must be placed in an important position.
III. Work Requirements
(1) Organize and implement well. All units should adhere to the people-centered development philosophy, improve political stance, strengthen responsibility, refine and decompose tasks, earnestly implement this notice, and ensure results are achieved. Relevant enterprises should implement subject responsibility, conduct self-inspection and self-correction according to this notice’s requirements, and effectively protect users’ legitimate rights and interests. At the same time, establish long-term mechanisms, innovate models and methods, continuously improve mobile internet application service levels, and continuously enhance users’ sense of gain, happiness, and security.
Analysis:
Considering this notice is effective upon issuance, all enterprises need to carry out self-inspection and self-correction as soon as possible to achieve compliance as quickly as possible.
Long-term compliance mechanisms need to be established and reviews conducted for subsequent products to avoid unnecessary risks.
(2) Strengthen guidance and supervision. The Ministry of Industry and Information Technology should improve and perfect evaluation, notification, ranking, and public disclosure mechanisms, promote solid and orderly work, promptly summarize and promote excellent cases and experiences. Local communications management bureaus should strengthen supervision and inspection, and guide and supervise enterprises within their jurisdictions to implement this notice’s various requirements. For those implementing poorly or committing violations, lawfully take measures such as ordering deadline corrections, social announcements, and organizational removals, and strictly investigate and punish.
Analysis:
Regulatory authorities add [Communications Management Bureaus], which also need to be held accountable for institutions implementing poorly.
This article also specifies concrete punishment behaviors: deadline corrections, social announcements, removal from shelves (and stopping access organized by telecommunications authorities as mentioned above).
(3) Strengthen technology application. The China Academy of Information and Communications Technology should organize industrial forces, comprehensively apply new technologies such as artificial intelligence and big data, upgrade and build a national public service platform for mobile internet application testing and certification, continuously improve platform functions, and do well in technical testing, monitoring services, and regulatory support work. Actively promote and apply traceable technical methods such as electronic signature certification to promote improved service management capabilities.
Analysis:
The government will launch APP electronic signature certification and other technical services. Future game版号 (approval) applications may add related content for [accessing electronic signature certification].
At the same time, considering the government’s attitude toward “renamed packages,” packages without版号 may not be able to obtain electronic signatures and thus be prompted with risks by terminals.
(4) Promote industry self-discipline. Encourage industry associations and related institutions to formulate industry self-discipline conventions, technical standards, and service norms, and strengthen assessment, certification, and talent cultivation. Further streamline channels to listen to public opinions, promote exchange and interaction among all parties, guide enterprises to operate lawfully and compliantly, continuously optimize and improve services, create a good environment for striving for excellence and mutual promotion, and promote high-quality development with high-quality services.
Analysis:
It expresses the government’s attitude: “operate lawfully and compliantly, continuously optimize and improve services, create a good environment for striving for excellence and mutual promotion, and promote high-quality development with high-quality services.”
February 6, 2023
Summary:
The issuance of this notice is more “grounded” and “aligned with business reality” than previous notices, clearly showing that the government has gradually gotten to the bottom of the mobile internet business’s various chains.
As the new generation begins serving in relevant departments, it can be foreseen that regulatory work will become increasingly detailed and increasingly “knowledgeable.” Various “tactics” from the era of blind growth will all be discovered, and newly emerging tactics will also be stopped more quickly. Non-compliant promotion methods may become a “double-edged sword”—bringing profits while also bringing risks.
[Compliance] review will become an important procedure in the future mobile internet software development process, as well as a prerequisite for going live and operating.