<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "journalpublishing.dtd"><article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" dtd-version="2.0" xml:lang="en" article-type="research-article"><front><journal-meta><journal-id journal-id-type="nlm-ta">JMIR Mhealth Uhealth</journal-id><journal-id journal-id-type="publisher-id">mhealth</journal-id><journal-id journal-id-type="index">13</journal-id><journal-title>JMIR mHealth and uHealth</journal-title><abbrev-journal-title>JMIR Mhealth Uhealth</abbrev-journal-title><issn pub-type="epub">2291-5222</issn><publisher><publisher-name>JMIR Publications</publisher-name><publisher-loc>Toronto, Canada</publisher-loc></publisher></journal-meta><article-meta><article-id pub-id-type="publisher-id">v14i1e73651</article-id><article-id pub-id-type="doi">10.2196/73651</article-id><article-categories><subj-group subj-group-type="heading"><subject>Original Paper</subject></subj-group></article-categories><title-group><article-title>Privacy Policy Compliance of Mobile Sports and Health Apps in China: Scale Development, Data Analysis, and Prospects for Regulatory Reform</article-title></title-group><contrib-group><contrib contrib-type="author" equal-contrib="yes"><name name-style="western"><surname>Guo</surname><given-names>Rengui</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff1"/><xref ref-type="fn" rid="equal-contrib1">*</xref></contrib><contrib contrib-type="author" corresp="yes" equal-contrib="yes"><name name-style="western"><surname>Chen</surname><given-names>Fanhong</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff1"/><xref ref-type="fn" rid="equal-contrib1">*</xref></contrib></contrib-group><aff id="aff1"><institution>School of Law, Central South University</institution><addr-line>No.932, Lushan South Road, Yuelu District</addr-line><addr-line>Changsha</addr-line><country>China</country></aff><contrib-group><contrib contrib-type="editor"><name name-style="western"><surname>Buis</surname><given-names>Lorraine</given-names></name></contrib></contrib-group><contrib-group><contrib contrib-type="reviewer"><name name-style="western"><surname>Erickson</surname><given-names>Jacob</given-names></name></contrib><contrib contrib-type="reviewer"><name name-style="western"><surname>Galetsi</surname><given-names>Panagiota</given-names></name></contrib><contrib contrib-type="reviewer"><name name-style="western"><surname>Yu</surname><given-names>Zekai</given-names></name></contrib></contrib-group><author-notes><corresp>Correspondence to Fanhong Chen, PhD, School of Law, Central South University, No.932, Lushan South Road, Yuelu District, Changsha, 410012, China, 86 18810373347; <email>chenzhongxun@foxmail.com</email></corresp><fn fn-type="equal" id="equal-contrib1"><label>*</label><p>all authors contributed equally</p></fn></author-notes><pub-date pub-type="collection"><year>2026</year></pub-date><pub-date pub-type="epub"><day>11</day><month>2</month><year>2026</year></pub-date><volume>14</volume><elocation-id>e73651</elocation-id><history><date date-type="received"><day>09</day><month>03</month><year>2025</year></date><date date-type="rev-recd"><day>13</day><month>11</month><year>2025</year></date><date date-type="accepted"><day>22</day><month>12</month><year>2025</year></date></history><copyright-statement>&#x00A9; Rengui Guo, Fanhong Chen. Originally published in JMIR mHealth and uHealth (<ext-link ext-link-type="uri" xlink:href="https://mhealth.jmir.org">https://mhealth.jmir.org</ext-link>), 11.2.2026. </copyright-statement><copyright-year>2026</copyright-year><license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/"><p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (<ext-link ext-link-type="uri" xlink:href="https://creativecommons.org/licenses/by/4.0/">https://creativecommons.org/licenses/by/4.0/</ext-link>), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIR mHealth and uHealth, is properly cited. The complete bibliographic information, a link to the original publication on <ext-link ext-link-type="uri" xlink:href="https://mhealth.jmir.org/">https://mhealth.jmir.org/</ext-link>, as well as this copyright and license information must be included.</p></license><self-uri xlink:type="simple" xlink:href="https://mhealth.jmir.org/2026/1/e73651"/><abstract><sec><title>Background</title><p>Driven by technological advancements, the proliferation of mobile sports and health apps has revolutionized health management by improving efficiency, cost-effectiveness, and accessibility. While the widespread adoption of these platforms has transformed public health practices and social well-being in China, emerging evidence suggests that inadequacies in their privacy policies may compromise personal information (PI) protection.</p></sec><sec><title>Objective</title><p>This study aimed to conduct a systematic evaluation of privacy policy compliance among 286 mobile sports and health apps in the Chinese Mainland, benchmarking them against the Personal Information Protection Law and associated PI regulatory guidelines.</p></sec><sec sec-type="methods"><title>Methods</title><p>This study develops a privacy policy compliance indicator scale based on the information life cycle and the legal framework for PI protection in the Chinese Mainland. This scale consists of 5 level 1 indicators and 37 level 2 indicators that assess the privacy policy compliance.</p></sec><sec sec-type="results"><title>Results</title><p>The privacy policy compliance of 286 sports and health apps generally performed worse, with only a minimal number (n=11, 3.8%) of apps scoring above 90 points (rated as excellent), nearly half (n=121, 42.3%) of apps scored below 60 points (rated as unqualified). Among the 5 level 1 evaluation indicators for privacy compliance in sports and health apps, the compliance rate for PI collection (mean 74%, SD 25.8%) is the highest, while the compliance rate for PI storage (mean 53.5%, SD 28.4%) is the lowest. The compliance rates for privacy policies across the remaining 3 level 1 evaluation indicators, such as PI usage (mean 54.2%, SD 24.4%), PI entrusted processing, sharing, transferring, and disclosing (mean 62.2%, SD 19.8%), and PI security and feedback (mean 61.7%, SD 21.3%), fall around 60%. Out of 37, 17 level 2 evaluation indicators show a compliance rate below 60%. The compliance rate with privacy policies for 5 level 2 evaluation indicators is exceptionally high, including collection subject (mean 97.2%, SD 16.5%), collection type (mean 99%, SD 10.2%), collection purpose (mean 96.2%, SD 19.3%), reasons for sharing, transferring, and disclosing PI (mean 91.6%, SD 27.8%), and feedback channel (mean 93.4%, SD 24.9%). Notably, 3 indicators exhibit compliance rates below 20%, including sensitive information storage (mean 14%, SD 34.7%), constraints of automatic decision-making (mean 9.4%, SD 29.3%), and deceased user rule (mean 5.2%, SD 22.3%). Authorization for sensitive information (mean 29.4%, SD 45.6%) lagged behind general information (mean 83.6%, SD 37.1%).</p></sec><sec sec-type="conclusions"><title>Conclusions</title><p>Although some apps have established commendable policies, there are gaps that compromise the efficacy of PI protection. Considering this, this paper proposes targeted actions for 3 stakeholders: users, regulators, and legislators. Only through coordinated action can the app ecosystem close the compliance gaps, reduce PI protection risks, and restore user trust in digital services.</p></sec></abstract><kwd-group><kwd>sports and health apps</kwd><kwd>personal data</kwd><kwd>sensitive information</kwd><kwd>privacy policy compliance</kwd><kwd>personal information protection</kwd><kwd>regulatory reform</kwd></kwd-group></article-meta></front><body><sec id="s1" sec-type="intro"><title>Introduction</title><p>With the popularity of mobile phones and people&#x2019;s increasing interests in sports and health management [<xref ref-type="bibr" rid="ref1">1</xref>-<xref ref-type="bibr" rid="ref3">3</xref>], mobile sports and health apps, which are closely related to physical exercise and provide exercise knowledge, assist with physical activities, track workout data, and support health management, have emerged and are constantly growing [<xref ref-type="bibr" rid="ref3">3</xref>-<xref ref-type="bibr" rid="ref7">7</xref>]. Currently, the app stores on the 2 major mobile operating systems, Android (Google) and Apple iOS, offer a vast array of apps related to health monitoring [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref9">9</xref>], calorie management [<xref ref-type="bibr" rid="ref10">10</xref>-<xref ref-type="bibr" rid="ref12">12</xref>], fitness guidance [<xref ref-type="bibr" rid="ref13">13</xref>,<xref ref-type="bibr" rid="ref14">14</xref>], health consultation [<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref16">16</xref>], and other sports and health services [<xref ref-type="bibr" rid="ref17">17</xref>]. These apps have enhanced the efficiency, cost-effectiveness, and accessibility of sports and health management, enabling people who are concerned about health through sports to learn exercise programs in real-time, track their diet, and improve their overall health condition using the apps [<xref ref-type="bibr" rid="ref18">18</xref>-<xref ref-type="bibr" rid="ref21">21</xref>]. It is reported that the extensive usage of these apps has significantly enhanced the social and public health landscape in China [<xref ref-type="bibr" rid="ref22">22</xref>].</p><p>However, the rapid growth of mobile sports and health apps poses a threat to users&#x2019; personal privacy and data security [<xref ref-type="bibr" rid="ref23">23</xref>-<xref ref-type="bibr" rid="ref26">26</xref>]. Streaking privacy, which occurs when sports and health apps collect, process, and use personal exercise and physical health information without authorization, has caused serious legal issues and attracted widespread social attention around the world [<xref ref-type="bibr" rid="ref27">27</xref>-<xref ref-type="bibr" rid="ref29">29</xref>]. For instance, the US Federal Trade Commission ordered the Easy Healthcare Corporation to pay a $100,000 civil penalty for its Premom app collecting and sharing a significant amount of users&#x2019; personal information (PI) with third-party advertisers in violation of privacy protection, eavesdropping, and other applicable laws and regulations [<xref ref-type="bibr" rid="ref30">30</xref>]. A Norwegian nonprofit organization has discovered that 10 of the most popular apps on Google Play Store, including sports and health apps, transmit users&#x2019; sensitive PI to third parties without their permission [<xref ref-type="bibr" rid="ref31">31</xref>]. In China, these challenges are more acute. In December 2018, China&#x2019;s Cyberspace Administration carried out a special regulatory action targeting numerous apps, including those related to sports and health, and discovered that 3496 apps were illegally collecting and using PI [<xref ref-type="bibr" rid="ref32">32</xref>].</p><p>As a response, many countries, including the United States [<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref34">34</xref>] and the European Union [<xref ref-type="bibr" rid="ref35">35</xref>-<xref ref-type="bibr" rid="ref37">37</xref>], have enacted bills to strengthen PI protection [<xref ref-type="bibr" rid="ref38">38</xref>]. The United States has enacted laws such as the Health Insurance Portability and Accountability Act [<xref ref-type="bibr" rid="ref39">39</xref>], the Health Breach Notification Rule [<xref ref-type="bibr" rid="ref40">40</xref>], and the Children&#x2019;s Online Privacy Protection Rule [<xref ref-type="bibr" rid="ref41">41</xref>], which stipulate the obligation of health care organizations to safeguard health data, require health care organizations to establish a consent mechanism for sharing patients&#x2019; health data with third parties, outline the data breach notification mechanism for health care organizations and the legal responsibilities for disclosing patients&#x2019; sensitive data [<xref ref-type="bibr" rid="ref42">42</xref>]. The European Union protects PI and privacy in a unified manner through the General Data Protection Regulation, grants 8 rights to users, and requires data processors to process personal data under the individual consent mechanism [<xref ref-type="bibr" rid="ref43">43</xref>].</p><p>In response to the risks of PI leakage and privacy abuse posed by sports and health apps, China&#x2019;s PI protection legal system adopts an approach [<xref ref-type="bibr" rid="ref44">44</xref>], aiming to protect users&#x2019; privacy data and promote market development [<xref ref-type="bibr" rid="ref27">27</xref>]. In 2019, the Cyberspace Administration of China made policies, such as methods for determining illegal collection and use of personal information by apps and provisions on the scope of necessary personal information for common types of mobile internet applications, to regulate the collection and use of PI by apps [<xref ref-type="bibr" rid="ref45">45</xref>]. In light of the noncoercive nature of these policies and in view of the urgent need for PI protection [<xref ref-type="bibr" rid="ref46">46</xref>], China enacted the Personal Information Protection Law (PIPL) in 2021 [<xref ref-type="bibr" rid="ref47">47</xref>]. While public reports held that the PIPL has established a basic legal framework for PI collection, processing, and usage [<xref ref-type="bibr" rid="ref48">48</xref>-<xref ref-type="bibr" rid="ref50">50</xref>], academic scholars still argue that the PIPL should be significantly improved [<xref ref-type="bibr" rid="ref51">51</xref>-<xref ref-type="bibr" rid="ref54">54</xref>]. Meanwhile, since December 2021, the National Technical Committee 260 on Cybersecurity of Standardization Administration of China has successively made voluntary national standards, such as the Practical Guide to Cybersecurity Standards&#x2014;Guidelines for the Classification and Grading of Network Data [<xref ref-type="bibr" rid="ref55">55</xref>], the Information Security Technology - Personal Information Security Engineering Guidelines (PI Guidelines) [<xref ref-type="bibr" rid="ref56">56</xref>], Information Security Technology&#x2014;Implementation Guidelines for Notices and Consent in Personal Information Processing [<xref ref-type="bibr" rid="ref57">57</xref>], and Information Security Technology&#x2014;Guide for De-identifying Personal Information [<xref ref-type="bibr" rid="ref58">58</xref>] to classify and grade PI for protection. Additionally, the Ministry of Industry and Information Technology of China regularly reports and requires rectification of apps that violate users&#x2019; rights and interests [<xref ref-type="bibr" rid="ref59">59</xref>]. According to public reports, a total of 297 apps were required to rectify their illegal collection of PI in 2024 [<xref ref-type="bibr" rid="ref60">60</xref>].</p><p>Under the above legal requirements, mobile sports and health apps, which collect and use users&#x2019; PI as the premise of their normal operation, need to establish an internal compliance management system for personal privacy and data security [<xref ref-type="bibr" rid="ref44">44</xref>]. In this system, developing privacy policies stands in the foreground, because the formulation and implementation of privacy policies ensures that the apps&#x2019; market operation behavior meets the requirements of laws and regulations, thereby achieving a balance between internal self-discipline and external supervision. As required by PIPL and PI Guidelines, a legitimate and valid privacy policy is comprised of the collection, storage, use, entrusted processing, sharing, transfer, disclosure, consultation, and feedback of PI [<xref ref-type="bibr" rid="ref61">61</xref>,<xref ref-type="bibr" rid="ref62">62</xref>]. Accordingly, this paper attempts to measure these aspects of mobile sports and health apps&#x2019; privacy policy because the degree of PI protection is correlated with how well the app&#x2019;s privacy policy conforms with PIPL and PI Guidelines.</p><p>There is a well-established body of work on privacy policies and PI protection in existing studies. For example, Tangari et al [<xref ref-type="bibr" rid="ref4">4</xref>] explored free fitness apps on the Google Play Store in Australia and found that 88% of the apps will potentially collect user data. Parker et al [<xref ref-type="bibr" rid="ref63">63</xref>] investigated and rated medicine-related apps for the Android mobile platform available in the medical store category of Google Play in the United Kingdom, United States, Canada, and Australia. Grundy et al [<xref ref-type="bibr" rid="ref64">64</xref>] explored the risks posed by rated medicines-related apps when sharing user data. Alfawzan et al [<xref ref-type="bibr" rid="ref65">65</xref>] emphasized the privacy policies of 23 most popular apps on women&#x2019;s health in the Apple operating system and the Android system. Shipp and Blasco [<xref ref-type="bibr" rid="ref66">66</xref>] assessed the privacy practices of a set of 30 Android menstruation-related apps that track users&#x2019; reproductive cycle, sex life, and health. Although research on the privacy policy compliance of mobile health (mHealth) apps is expanding, studies specifically examining the privacy policy compliance of mHealth apps closely related to sports still require further in-depth investigation. Scholars have conducted comparative in-depth research on the privacy policy compliance of China&#x2019;s mHealth apps [<xref ref-type="bibr" rid="ref67">67</xref>-<xref ref-type="bibr" rid="ref69">69</xref>], focusing primarily on mobile mental health [<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref70">70</xref>,<xref ref-type="bibr" rid="ref71">71</xref>], mobile hospitals [<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref72">72</xref>,<xref ref-type="bibr" rid="ref73">73</xref>], contact tracing [<xref ref-type="bibr" rid="ref74">74</xref>,<xref ref-type="bibr" rid="ref75">75</xref>], traditional Chinese medicine treatments [<xref ref-type="bibr" rid="ref76">76</xref>], and chronic disease management [<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref77">77</xref>]. Research on the privacy policy compliance of Chinese mobile sports and health apps remains limited. Current research on privacy policy compliance for mobile sports and health apps is limited to a few jurisdictions, with a significant lack of attention still directed toward the privacy policy compliance issues of Chinese mobile sports and health apps. Currently, China boasts an exceptionally large user base for mobile sports and health apps. These apps collect users&#x2019; PI, particularly sensitive data, such as gender, location, exercise routes, heart rate, workout duration, weight, and exercise frequency. If the PI collected by these mobile sports and health apps is not gathered, used, and shared in a lawful, transparent, and trustworthy manner, it not only jeopardizes users&#x2019; personal privacy and safety but also poses a threat to national data security. Therefore, privacy policy compliance for mobile sports and health apps requires thorough analysis in the Chinese Mainland.</p><p>In order to comprehensively evaluate the compliance rate of privacy policies of sports and health apps in the Chinese Mainland, this paper deploys scenario-based contextual analysis [<xref ref-type="bibr" rid="ref78">78</xref>] and information life cycle theory [<xref ref-type="bibr" rid="ref79">79</xref>]. Nissenbaum [<xref ref-type="bibr" rid="ref78">78</xref>] argued that the contextual integrity theory should serve as the cornerstone of privacy protection, because different contextual frameworks shape the norms of information flow across various scenarios, and these norms determine the legitimacy of information processing. There are typically 2 types of PI protection scenarios. The first type vertically categorizes different types of information based on the varying levels of processing risks, and the other type horizontally focuses on the different stages of information processing. Regarding the former, both domestic and international legislation generally adopt a dichotomy to differentiate between sensitive PI and general PI. This paper also follows this classification to evaluate their respective levels of protection compliance. For the latter, combining with the information life cycle stipulated in the PIPL, this study proposes 5 stages of PI collection, PI storage, PI usage, PI entrusted processing, sharing, transferring, and disclosing, and PI security and feedback, and further uses them as 5 primary indicators in the scale.</p><p>This study uses the legal framework for PI protection to develop a privacy policy compliance indicator scale and evaluate the compliance degree of privacy policies of 286 sports and health apps. In the Methods section, we focus on selecting, collecting, and analyzing sample apps, developing a compliance indicator scale, and designing the scoring process. In the Results section, we examine the level of PI protection of each privacy policy and report the results of the compliance assessment. In the Discussion section, we summarize the overall landscape and existing shortcomings in privacy policy compliance among sports and health apps and propose regulatory reforms to strengthen PI protection.</p><p>This study aims to (1) select, collect, and analyze privacy policies of sports and health apps developed for users in the Chinese Mainland, (2) establish a privacy policy compliance indicator scale based on the PIPL and PI Guidelines [<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref27">27</xref>] (3) evaluate the compliance level of privacy policies of sports and health apps by scoring each indicator, and (4) provide suggestions on how to improve PI protection in the Chinese Mainland. This study enhances the discourse on balancing personal information protection with sustainable innovation in sports and health apps. By underscoring the necessity of enhancing privacy policy compliance and offering improvement suggestions, it offers insights for policymakers, developers, operators, and users across various nations regarding PI protection.</p></sec><sec id="s2" sec-type="methods"><title>Methods</title><sec id="s2-1"><title>Study Design</title><p>We first comprehensively collected 714 apps from the app stores of Google Android and Apple iOS, the 2 mobile phone operating systems in the Chinese Mainland, between August 2 and August 6, 2025. Then we proceeded to examine the program description of apps to review their features and locate their privacy policies on August 6, 2025. Subsequently, we downloaded the privacy policies of the remaining apps, eliminating those that either did not allow a privacy policy download or lacked a privacy policy altogether between August 7 and August 8, 2025. Finally, we analyzed the compliance level of privacy policies of 286 valid sports and health apps with the PIPL and PI Guidelines and further proposed improvement suggestions regarding the gaps identified in the process of compliance evaluation from August 10 to August 20, 2025.</p></sec><sec id="s2-2"><title>Sample Selection and Inclusion Criteria</title><p>This study focused on the privacy policy compliance of sports and health apps. We selected the apps from the app stores of Android and Apple, the 2 popular mobile operating systems in the Chinese mainland. We opened the app stores (Yingyongshangdian in Chinese) section, selected the function of app category (Fenlei in Chinese), and put in keywords &#x201C;sports and health&#x201D; (Yundong Jiankang in Chinese) to filter apps. Through the comprehensive collection and search methods described above, we have gathered the initial sports and health sample apps. Then, we carefully reviewed the feature descriptions of each of the initial sports and health sample apps we collected, while simultaneously downloading their privacy policy documents. The apps included in the sample must meet the following 2 criteria. First, they must be explicitly designed for a diverse user base to offer sport guidance, real-time exercise data tracking, fitness education, and other sports and health services, and second, they must be intended for ordinary individuals rather than for sports and health management organizations or governments. The apps with the following criteria were excluded from the sample. First, the app provides only low-fat food options, recipes, and dietary control recommendations. Second, the app provides only psychological issue diagnosis, stress relief, and emotional support functions. Third, the app provides only sleep aid and sleep quality monitoring functions. Fourth, the app solely collects physical data, analyzes health issues, and provides fitness recommendations. Fifth, the app exclusively offers exercise instruction content and videos, along with coaching services. Sixth, the app solely provides virtual fitness game services. Seventh, the app exclusively offers sports event booking, live streaming, and participation services. Eighth, the app solely provides massage services. Ninth, the app either lacks a privacy policy or its privacy policy web page fails to display effectively. By searching, analyzing, and filtering sports and health apps, we obtained the final number of sample apps used for privacy policy compliance analysis.</p></sec><sec id="s2-3"><title>Development of the Privacy Policy Compliance Indicator Scale</title><p>We constructed a privacy policy compliance indicator scale from the perspective of the scenario-based requirement [<xref ref-type="bibr" rid="ref78">78</xref>] and the information life cycle [<xref ref-type="bibr" rid="ref79">79</xref>] to assess the compliance between the privacy policies of sports and health apps and the PIPL and the PI Guidelines. The process of developing the privacy policy compliance indicator scale is as follows.</p><p>We first comprehensively reviewed the provisions of the PIPL and PI Guidelines and then extracted an appropriate privacy compliance evaluation legal framework applicable to sports and health apps, from which we produce level 1 evaluation indicators. According to the information life cycle, sports and health apps operate through the processes of collection, storage, usage, processing, sharing, transfer, disclosure, information consultation, suggestion, and feedback of PI [<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref27">27</xref>]. In light of this, we argue that the legal framework is comprised of five stages: (1) the collection of PI (Articles 6, 13, 14, 17, 28, 29, and 30 of the PIPL; and Articles 2, 4, and 5 of the PI Guidelines); (2) the storage of PI (Articles 17, 19, 39, and 40 of the PIPL; and Article 6 of the PI Guidelines); (3) the use of PI (Articles 6, 14, 15, 16, 24, 45, 46, 47, 48, 49, and 50 of the PIPL; and Articles 7 and 8 of the PI Guidelines); (4) the entrusted processing, the sharing, the transfer, and the disclosure of PI (Articles 21, 22, 23, 26, 27, 38, and 39 of the PIPL; and Article 9 of the PI Guidelines); (5) the consultation and feedback on PI (Articles 50, 57, and 65 of the PIPL; and Article 10 of the PI Guidelines). In accordance with this legal framework, we set 5 level 1 evaluation indicators: the collection of PI, the storage of PI, the use of PI, the entrusted processing, the sharing, the transfer, and the disclosure of PI, and the consultation and feedback on PI.</p><p>To conduct a more precise evaluation of the privacy policy, we further divide the 5 level 1 evaluation indicators into 37 level 2 evaluation indicators, thus establishing our privacy policy compliance indicator scale (<xref ref-type="table" rid="table1">Table 1</xref>). The level 1 evaluation indicators include PI collection, PI storage, PI usage, PI entrusted processing, sharing, transferring, and disclosing, and PI security and feedback. Specifically, the level 1 evaluation indicator of PI collection comprises 9 level 2 evaluation indicators. They are the collection subject, policy update, app scope, collection type, collection purpose, processing rule, authorization for general information, authorization for sensitive information, and exceptions for explicit authorization. Another level 1 evaluation indicator of PI storage consists of 4 level 2 evaluation indicators: storage time, storage place, PI deidentification, and sensitive information storage. We further break down the level 1 evaluation indicator of PI usage into 14 level 2 evaluation indicators, including PI access control, deidentified display and use, purpose restrictions for PI usage, authorization for the usage purpose change, constraints of automatic decision-making, query right, correction right, deletion right, copy right, account cancelation right, withdraw or change authorization, asking response right, deceased user rule, and complaint mechanism. Concerning the level 1 evaluation indicator of PI entrusted processing, sharing, transferring, and disclosing, we further categorize it into 5 level 2 evaluation indicators: requirements for entrusted controller processing PI, reasons for sharing, transferring, and disclosing PI, security measures of sharing, transferring, and disclosing PI, special circumstances without consent, and cross-border transmission requirements. The last level 1 evaluation indicator is the PI security and feedback, which encompasses 5 level 2 evaluation indicators of security incident response mechanism, security event notification mechanism, feedback channel, feedback period, and external dispute resolution mechanisms.</p><table-wrap id="t1" position="float"><label>Table 1.</label><caption><p>Level 1 and level 2 evaluation indicators of privacy policy compliance of sports and health apps.</p></caption><table id="table1" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Level 1 evaluation indicator</td><td align="left" valign="bottom">Level 2 evaluation indicator</td></tr></thead><tbody><tr><td align="left" valign="top">PI<sup><xref ref-type="table-fn" rid="table1fn1">a</xref></sup> collection</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Collection subject</p></list-item><list-item><p>Policy update</p></list-item><list-item><p>Application scope</p></list-item><list-item><p>Collection type</p></list-item><list-item><p>Collection purpose</p></list-item><list-item><p>Processing rule</p></list-item><list-item><p>Authorization for general information</p></list-item><list-item><p>Authorization for sensitive information</p></list-item><list-item><p>Exceptions for explicit authorization</p></list-item></list></td></tr><tr><td align="left" valign="top">PI storage</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Storage time</p></list-item><list-item><p>Storage place</p></list-item><list-item><p>PI deidentification</p></list-item><list-item><p>Sensitive information storage</p></list-item></list></td></tr><tr><td align="left" valign="top">PI usage</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>PI access control</p></list-item><list-item><p>Deidentified display and use</p></list-item><list-item><p>Purpose restrictions for PI usage</p></list-item><list-item><p>Authorization for the usage purpose change</p></list-item><list-item><p>Constraints of automatic decision-making</p></list-item><list-item><p>Query rightCorrection right</p></list-item><list-item><p>Deletion rightCopy right</p></list-item><list-item><p>Account cancelation right</p></list-item><list-item><p>Withdraw or change authorization</p></list-item><list-item><p>Asking response right</p></list-item><list-item><p>Deceased user rule</p></list-item><list-item><p>Complaint mechanism</p></list-item></list></td></tr><tr><td align="left" valign="top">PI entrusted processing, sharing, transferring, and disclosing</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Requirements for entrusted controller processing PI</p></list-item><list-item><p>Reasons for sharing, transferring, and disclosing PI</p></list-item><list-item><p>Security measures of sharing, transferring, and disclosing PI</p></list-item><list-item><p>Special circumstances without consent</p></list-item><list-item><p>Cross-border transmission requirements</p></list-item></list></td></tr><tr><td align="left" valign="top">PI security and feedback</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Security incident response mechanism</p></list-item><list-item><p>Security event notification mechanism</p></list-item><list-item><p>Feedback channel</p></list-item><list-item><p>Feedback period</p></list-item><list-item><p>External dispute resolution mechanisms</p></list-item></list></td></tr></tbody></table><table-wrap-foot><fn id="table1fn1"><p><sup>a</sup>PI: personal information.</p></fn></table-wrap-foot></table-wrap><p>The PIPL and PI Guidelines are of significant importance for the protection of personal data and privacy. These provisions are legally mandatory rules that must be strictly adhered to. Therefore, we treat all 5 level 1 evaluation indicators equally and assign them a value of 1. It means that if these 37 level 2 evaluation indicators are accurately and effectively stated in the privacy policy of the sports and health app, they are assigned a value of 1, and if not, they are assigned a value of 0.</p><p>After classifying the level 1 evaluation indicators and applying the scoring rule, we got a total score (37 points) for each app&#x2019;s privacy policies. Then, the final score is calculated on a 100-point scale. This means each app&#x2019;s privacy policy score (on a 37-point scale) is converted to a 100-point scale to determine the final score. The evaluation results were further divided into 4 levels: excellent for a compliance score above 90 points, good for a compliance score in the range of 80&#x2010;90 points, qualified for a compliance score in the range of 60&#x2010;79 points, and unqualified for a compliance score below 60 points. The privacy policy compliance tiering of sports and health apps is illustrated in <xref ref-type="table" rid="table2">Table 2</xref>.</p><p>Finally, we calculated and summarized the score of each level 2 evaluation indicator for all sample apps. From August 21 to December 25, 2025, 2 independent raters (RG and FC) participated in the scoring process. This process was divided into 2 stages. To ensure reliability and consistency of the scoring results, in the initial scoring stage, all raters independently evaluated 30 randomly selected apps (10.5% of the total), achieving a correlation coefficient of 0.983 (<italic>P</italic>&#x003C;.001) among different raters within the same group, indicating that the evaluations were closest to consistency. After evaluation, the raters gathered together to discuss the differences and reasons for the initial scoring and ultimately formed an almost consistent scoring standard. In this way, subjectivity in scoring is limited, although not eliminated. In the second scoring stage, we divided the sample apps into 2 groups of 143 each. Each rater randomly selects a group of apps to score independently.</p><table-wrap id="t2" position="float"><label>Table 2.</label><caption><p>The privacy policy compliance tiers of sports and health apps.</p></caption><table id="table2" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Final score for apps</td><td align="left" valign="bottom">Privacy policy compliance tiers</td></tr></thead><tbody><tr><td align="left" valign="top">&#x2265;90</td><td align="left" valign="top">Excellent</td></tr><tr><td align="left" valign="top">80-90</td><td align="left" valign="top">Good</td></tr><tr><td align="left" valign="top">60-80</td><td align="left" valign="top">Qualified</td></tr><tr><td align="left" valign="top">&#x003C;60</td><td align="left" valign="top">Unqualified</td></tr></tbody></table></table-wrap></sec></sec><sec id="s3" sec-type="results"><title>Results</title><sec id="s3-1"><title>Sample Collection</title><p>From August 2, 2025, we conducted the collection, selection, evaluation, and analysis of the privacy policies of the sports and health apps. We gathered an initial set of 714 sports and health apps from the Android App Store and Apple App Store.</p><p>We collected 328 sports and health apps from the Android App Store. After excluding 118 apps due to reasons such as irrelevance to sports and health management services, the final valid count was 210 apps. The reasons and numbers for the 118 excluded apps are as follows: (1) 11 apps were excluded for providing only diet control and fat loss services, (2) 5 apps were excluded for providing only body data collection and testing services, (3) 27 apps were excluded for offering solely exercise instruction and learning services, (4) 17 apps were excluded for providing only virtual gaming services, (5) 35 apps were excluded for offering only sports event booking and live streaming services, (6) 5 apps were excluded for providing only sports venue booking services, (7) 16 apps were excluded for other reasons, and (8) 1 app was excluded because its privacy policy web page could not be accessed.</p><p>We collected 386 sports and health apps from the Apple App Store. After excluding 273 apps unrelated to sports and health management services, 113 valid apps remained. The reasons and quantities for excluding the 113 apps are as follows: (1) 28 apps were excluded for providing only dietary control and fat loss services; (2) 45 apps were excluded for offering solely psychological counseling and mental health guidance; (3) 36 apps were excluded for providing only sleep issue monitoring and sleep aid services; (4) 44 apps were excluded for offering exclusively physical data collection and health monitoring services; (5) 3 apps were excluded for solely providing exercise instruction and learning services; (6) 1 app was excluded for solely providing virtual gaming services; (7) 11 apps were excluded for solely providing massage and relaxation services; (8) 10 apps were excluded for solely providing traditional Chinese medicine consultation and treatment services; (9) 59 apps were excluded for other reasons including menstrual cycle prediction and care, vaccination, parenting, etc; (10) 5 apps were excluded for failing to open their privacy policy webpage; and (11) 31 apps were excluded for lacking a privacy policy. Therefore, we excluded 391 apps whose functions were not centered around sports. The reasons and number of apps excluded are listed in <xref ref-type="table" rid="table3">Table 3</xref>; the names, reasons, and number of apps excluded are presented in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>. Ultimately, we collected 323 valid sports and health apps (the characteristics of the 323 valid sports and health apps are illustrated in <xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref>). The characteristics of the 323 valid sports and health apps are presented in <xref ref-type="table" rid="table4">Table 4</xref>.</p><table-wrap id="t3" position="float"><label>Table 3.</label><caption><p>The reasons and number of apps excluded.</p></caption><table id="table3" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Reasons for apps excluded</td><td align="left" valign="bottom">Apps excluded (n=391), n</td></tr></thead><tbody><tr><td align="left" valign="top">Dietary control</td><td align="left" valign="top">40</td></tr><tr><td align="left" valign="top">Mental health</td><td align="left" valign="top">45</td></tr><tr><td align="left" valign="top">Sleep monitoring</td><td align="left" valign="top">36</td></tr><tr><td align="left" valign="top">Body monitoring</td><td align="left" valign="top">49</td></tr><tr><td align="left" valign="top">Physical education</td><td align="left" valign="top">30</td></tr><tr><td align="left" valign="top">Video games</td><td align="left" valign="top">18</td></tr><tr><td align="left" valign="top">Massage services</td><td align="left" valign="top">11</td></tr><tr><td align="left" valign="top">Traditional Chinese medicine diagnosis and treatment</td><td align="left" valign="top">10</td></tr><tr><td align="left" valign="top">Sports events</td><td align="left" valign="top">35</td></tr><tr><td align="left" valign="top">Venue booking</td><td align="left" valign="top">5</td></tr><tr><td align="left" valign="top">Other reasons (menstrual care, childcare, sports knowledge dissemination, etc)</td><td align="left" valign="top">75</td></tr><tr><td align="left" valign="top">Unable to open the webpage</td><td align="left" valign="top">6</td></tr><tr><td align="left" valign="top">No privacy policy</td><td align="left" valign="top">31</td></tr></tbody></table></table-wrap><table-wrap id="t4" position="float"><label>Table 4.</label><caption><p>The characteristics of the 323 valid sports and health apps.</p></caption><table id="table4" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Characteristics</td><td align="left" valign="bottom">Apps (n=323), n (%)</td></tr></thead><tbody><tr><td align="left" valign="top" colspan="2">Apps source</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Android App Store</td><td align="left" valign="top">210 (65)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Apple App Store</td><td align="left" valign="top">113 (35)</td></tr><tr><td align="left" valign="top" colspan="2">Number of Android apps downloads</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>&#x2264;10,000</td><td align="left" valign="top">46 (21.9)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>10,000-100,000</td><td align="left" valign="top">42 (20)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>100,000-10,00,000</td><td align="left" valign="top">57 (27.1)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>1,000,000-1,00,00,000</td><td align="left" valign="top">43 (20.5)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>10,000,000-1,00,000,000</td><td align="left" valign="top">18 (8.6)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>&#x003E;10,00,00,000</td><td align="left" valign="top">4 (1.9)</td></tr><tr><td align="left" valign="top" colspan="2">Age-based app classification in Android apps</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>&#x2265;3</td><td align="left" valign="top">90 (42.8)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>&#x2265;8</td><td align="left" valign="top">18 (8.6)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>&#x2265;12</td><td align="left" valign="top">30 (14.3)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>&#x2264;16</td><td align="left" valign="top">25 (11.9)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>&#x2265;18</td><td align="left" valign="top">47 (22.4)</td></tr><tr><td align="left" valign="top" colspan="2">Age-based app classification of Apple apps</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>&#x2265;4</td><td align="left" valign="top">76 (67.3)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>&#x2265;9</td><td align="left" valign="top">3 (2.6)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>&#x2265;12</td><td align="left" valign="top">13 (11.5)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>&#x2264;17</td><td align="left" valign="top">21 (18.6)</td></tr><tr><td align="left" valign="top" colspan="2">App rating of Android apps</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>&#x003C;1</td><td align="left" valign="top">60 (28.6)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>1-2</td><td align="left" valign="top">38 (18.1)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>2-3</td><td align="left" valign="top">32 (15.2)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>3&#x2264;n-4</td><td align="left" valign="top">37 (17.6)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>4-5</td><td align="left" valign="top">25 (11.9)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>5</td><td align="left" valign="top">18 (8.6)</td></tr><tr><td align="left" valign="top" colspan="2">App rating of Android apps</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>&#x003C;1</td><td align="left" valign="top">2 (1.8)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>12</td><td align="left" valign="top">2 (1.8)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>23</td><td align="left" valign="top">10 (8.8)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>34</td><td align="left" valign="top">14 (12.4)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>45</td><td align="left" valign="top">81 (71.7)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>5</td><td align="left" valign="top">4 (3.5)</td></tr><tr><td align="left" valign="top" colspan="2">App rating of total apps</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>1</td><td align="left" valign="top">62 (19.2)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>1-2</td><td align="left" valign="top">40 (12.4)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>2-3</td><td align="left" valign="top">42 (13)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>3-4</td><td align="left" valign="top">51 (15.8)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>4-5</td><td align="left" valign="top">106 (32.8)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>5</td><td align="left" valign="top">22 (6.8)</td></tr></tbody></table></table-wrap><p>After carefully verifying the app names and company names of 323 valid sports and health apps, we found that among the 210 valid Android apps and 113 valid Apple iOS apps, 37 apps belonged to the same company and shared identical privacy policies. Therefore, we only need to count the privacy policies of duplicate apps from 1 operating system&#x2019;s app store. Since accessing privacy policies on Apple devices is more user-friendly than on Android devices, the privacy policies for these 37 duplicate apps were collected from the Apple App Store and included in the total count of apps collected from the Apple App Store. We subsequently removed these duplicate apps from the Android App Store, resulting in a final count of 286 apps. The methods and procedures for collecting, selecting, and excluding sample apps are presented in <xref ref-type="fig" rid="figure1">Figure 1</xref>. By entering the introduction pages of 286 sports and health apps one by one, we downloaded the privacy policy texts. After that, we thoroughly and carefully read the privacy policy documents of these apps from August 10 to August 20, 2025.</p><p>This study examined the privacy policies of 286 sports and health apps and assessed whether these privacy policies comply with the PIPL and the PI Guidelines in the Chinese Mainland. The names, compliance indicators, and scores of sports and health apps are presented in <xref ref-type="supplementary-material" rid="app3">Multimedia Appendix 3</xref>. Our findings reveal a complex landscape of privacy policy compliance among sports and health apps. Among 286 sports and health apps examined, we observed a spectrum ranging from commendably high privacy compliance to moderate compliance and to a surprisingly poor compliance rate.</p><fig position="float" id="figure1"><label>Figure 1.</label><caption><p>Flow diagram of the privacy policy collection and identification process.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="mhealth_v14i1e73651_fig01.png"/></fig></sec><sec id="s3-2"><title>Compliance Evaluation</title><p>The privacy policy compliance of 286 sports and health apps exhibits significant variation overall (<xref ref-type="supplementary-material" rid="app3">Multimedia Appendix 3</xref>). The privacy policy compliance rate for level 1 evaluation indicators across these apps exhibits a tiered pattern. Among level 1 evaluation indicators, PI collection had the highest privacy policy compliance rate (mean 74%, SD 25.8%), while PI storage had the lowest compliance rate (mean 53.5%, SD 28.4%). PI usage also scored low in compliance (mean 54.2%, SD 24.4%). PI security and feedback (mean 61.7%, SD 21.3%) and PI entrusted processing, sharing, transferring, and disclosing (mean 62.2%, SD 19.8%) scored relatively higher. The overall privacy policy compliance status of these level 1 evaluation indicators is illustrated in <xref ref-type="fig" rid="figure2">Figure 2</xref>.</p><fig position="float" id="figure2"><label>Figure 2.</label><caption><p>Compliance evaluation results of level 1 evaluation indicators of the apps&#x2019; privacy policies. PI: personal information.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="mhealth_v14i1e73651_fig02.png"/></fig><p>In general, after categorizing the privacy policy compliance scores of 286 sports and health apps into 4 levels (excellent, good, qualified, and unqualified), it was found that 3.8% (n=11) of apps achieved excellent compliance, 41 apps scored good, 113 apps scored qualified, while nearly half (n=121, 42.3%) scored unqualified. Compliance evaluation results on the overall compliance level of the apps&#x2019; privacy policies are illustrated in <xref ref-type="fig" rid="figure3">Figure 3</xref>.</p><fig position="float" id="figure3"><label>Figure 3.</label><caption><p>Compliance evaluation results on the overall compliance level of the apps&#x2019; privacy policies.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="mhealth_v14i1e73651_fig03.png"/></fig><p>From the perspective of the information life cycle [<xref ref-type="bibr" rid="ref58">58</xref>], the privacy policy compliance of sports and health apps exhibits significant diversity in level 2 evaluation indicators for the information life cycle. This reflects significant variations in the implementation of privacy policy compliance among sports and health apps, with some rules being poorly enforced. The level 2 evaluation indicators&#x2019; scores of sports and health apps&#x2019; privacy policy compliance are reflected in <xref ref-type="table" rid="table5">Table 5</xref>.</p><table-wrap id="t5" position="float"><label>Table 5.</label><caption><p>Level 2 evaluation indicators of privacy policy compliance score.</p></caption><table id="table5" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Level 1 and level 2 indicator</td><td align="left" valign="bottom">Mean (SD)</td></tr></thead><tbody><tr><td align="left" valign="top">PI<sup><xref ref-type="table-fn" rid="table5fn1">a</xref></sup> collection</td><td align="left" valign="top">74% (25.8%)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Collection subject</td><td align="left" valign="top">97.2% (16.5%)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Policy update</td><td align="left" valign="top">42.7% (49.5%)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Application scope</td><td align="left" valign="top">82.9% (37.7%)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Collection type</td><td align="left" valign="top">99% (10.2%)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Collection purpose</td><td align="left" valign="top">96.2% (19.3%)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Processing rule</td><td align="left" valign="top">83.2% (37.4%)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Authorization for general information</td><td align="left" valign="top">83.6% (37.1%)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Authorization for sensitive information</td><td align="left" valign="top">29.4% (45.6%)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Exceptions for explicit authorization</td><td align="left" valign="top">52.4% (50%)</td></tr><tr><td align="left" valign="top">PI storage</td><td align="left" valign="top">53.5% (28.4%)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Storage time</td><td align="left" valign="top">69.6% (46.1%)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Storage place</td><td align="left" valign="top">78% (41.5%)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>PI deidentification</td><td align="left" valign="top">52.4% (50%)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Sensitive information storage</td><td align="left" valign="top">14% (34.7%)</td></tr><tr><td align="left" valign="top">PI usage</td><td align="left" valign="top">54.2% (24.4%)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>PI access control</td><td align="left" valign="top">67.5% (46.9%)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>De-identified display and use</td><td align="left" valign="top">34.6% (47.7%)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Purpose restrictions for PI usage</td><td align="left" valign="top">77.6% (41.8%)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Authorization for the usage purpose change</td><td align="left" valign="top">53.5% (50%)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>constraints of automatic decision-making</td><td align="left" valign="top">9.4% (29.3%)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Query right</td><td align="left" valign="top">80.1% (40%)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Correction right</td><td align="left" valign="top">70.6% (45.6%)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Deletion right</td><td align="left" valign="top">79.7% (40.3%)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Copy right</td><td align="left" valign="top">46.5% (50%)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Account cancelation right</td><td align="left" valign="top">61.4% (48.8%)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Withdraw or change authorization</td><td align="left" valign="top">75.2% (43.3%)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Asking response right</td><td align="left" valign="top">45.1% (49.8%)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Deceased user rule</td><td align="left" valign="top">5.2% (22.3%)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Complaint mechanism</td><td align="left" valign="top">51.7% (50.1%)</td></tr><tr><td align="left" valign="top">PI entrusted processing, sharing, transferring, and disclosing</td><td align="left" valign="top">62.2% (19.8%)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Requirements for entrusted controller processing PI</td><td align="left" valign="top">52.4% (50%)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Reasons for sharing, transferring, and disclosing PI</td><td align="left" valign="top">91.6% (27.8%)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Security measures of sharing, transferring, and disclosing PI</td><td align="left" valign="top">63.6% (48.2%)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Special circumstances without consent</td><td align="left" valign="top">65.4% (47.7%)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Cross-border transmission requirements</td><td align="left" valign="top">37.8% (48.6%)</td></tr><tr><td align="left" valign="top">PI security and feedback</td><td align="left" valign="top">61.7% (21.3%)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Security incident response mechanism</td><td align="left" valign="top">68.5% (46.5%)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Security event notification mechanism</td><td align="left" valign="top">55.6% (49.8%)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Feedback channel</td><td align="left" valign="top">93.4% (24.9%)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Feedback period</td><td align="left" valign="top">55.6% (49.8%)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>External dispute resolution mechanisms</td><td align="left" valign="top">35.3% (47.9%)</td></tr></tbody></table><table-wrap-foot><fn id="table5fn1"><p><sup>a</sup>PI: personal information.</p></fn></table-wrap-foot></table-wrap><p>For level 1 evaluation metric PI collection, PI collection demonstrated the highest level of privacy policy compliance (mean 74%, SD 25.8%) (<xref ref-type="fig" rid="figure4">Figure 4</xref>). This indicates that sports and health apps generally prioritize compliance in PI collection, informing users about the methods and purposes of personal information gathering, thereby fundamentally ensuring users&#x2019; right to know regarding the collection of their PI. This promotes users&#x2019; understanding of how their PI is used and enhances the transparency, integrity, and security of personal data usage within sports and health apps. The level 1 evaluation indicators PI collection showed significant differences in privacy policy compliance scores across its 9 level 2 evaluation indicators. Collection type demonstrated the highest privacy policy compliance (mean 99%, SD 10.2%), indicating that sports and health apps place strong emphasis on disclosing the types of PI collected to users, ensuring users are aware that their data, particularly sensitive data, have been gathered. Sports and health apps also exhibit high privacy policy compliance rates for collection subject (mean 97.2%, SD 16.5%) and collection purpose (mean 96.2%, SD 19.3%). This indicates that the vast majority of such apps clearly state the name of the data controller and the purpose of data collection within their privacy policies. Informing users about the collection subject and collection purpose enables them to understand who collects their PI and for what processing activities it is used, thereby assisting users in future legal actions regarding PI breaches. The compliance rate for application scope (mean 82.9%, SD 37.7%), processing rule (mean 83.2%, SD 37.4%), and authorization for general information (mean 83.6%, SD 37.1%) all exceeded 80%. Policy update (mean 42.7%, SD 49.5%) and exceptions for explicit authorization (mean 52.4%, SD 50%) showed lower compliance rates, approaching half. The privacy policy compliance rate for authorization for sensitive information was the lowest (mean 29.4%, SD 45.6%), indicating that the vast majority of sports and health apps lack effective provisions in their privacy policies regarding consent mechanisms for collecting sensitive PI. Since sports and health apps inevitably collect users&#x2019; sensitive PI, the absence of consent mechanisms for such data collection leaves personal sensitive information highly vulnerable and susceptible to leakage.</p><fig position="float" id="figure4"><label>Figure 4.</label><caption><p>Privacy policy compliance evaluation results of personal information collection.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="mhealth_v14i1e73651_fig04.png"/></fig><p>The level 1 evaluation indicator PI entrusted processing, sharing, transferring, and disclosing also demonstrated high privacy policy compliance (mean 62.2%, SD 19.8%) (<xref ref-type="fig" rid="figure5">Figure 5</xref>). Except for cross-border transmission requirements (mean 37.8%, SD 48.6%), the privacy policy compliance rate for level 2 evaluation indicators under level 1 PI entrusted processing, sharing, transferring, and disclosing exceeded 50%. The privacy policy compliance rate for reasons for sharing, transferring, and disclosing PI was the highest (mean 91.6%, SD 27.8%), indicating that sports and health apps highly prioritize explaining these reasons to users. This assists in safeguarding users&#x2019; right to informed consent during the sharing, transferring, and disclosing of PI. The compliance rates of privacy policies for sports and health apps in the requirements for entrusted controller processing PI (mean 52.4%, SD 50%), security measures for sharing, transferring, and disclosing PI (mean 63.6%, SD 48.2%), and special circumstances without consent (mean 65.4%, SD 47.7%) all exceed one-half.</p><fig position="float" id="figure5"><label>Figure 5.</label><caption><p>Privacy policy compliance evaluation results of personal information entrusted processing, sharing, transferring, and disclosing. PI: personal information.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="mhealth_v14i1e73651_fig05.png"/></fig><p>Regarding level 1 evaluation indicators, PI security and feedback, the privacy policy compliance rate of sports and health apps in PI security and feedback exceeds half (mean 61.7%, SD 21.3%) (<xref ref-type="fig" rid="figure6">Figure 6</xref>). The privacy policy compliance score for the level 2 evaluation indicator feedback channel is the highest (mean 93.4%, SD 24.9%), reflecting that sports and health apps pay great attention to providing users with effective feedback channels in case of disputes regarding the collection, use, and processing of PI. In terms of privacy policy compliance, more than half of the sports and health apps meet the level 2 evaluation indicators: security incident response mechanism (mean 68.5%, SD 46.5%), security event notification mechanism (mean 55.6%, SD 49.8%), and feedback period (mean 55.6%, SD 49.85%). This indicates that over 50% of sports and health apps have established PI security protection mechanisms and security incident reporting procedures, ensuring the safety of users&#x2019; PI and their right to be informed in the event of information leakage. The compliance of external dispute resolution mechanisms in privacy policies is very poor, with one-third of sports and health apps not having established external resolution mechanisms for PI disputes, which means they do not clearly inform users that they can sue in court if a dispute occurs.</p><fig position="float" id="figure6"><label>Figure 6.</label><caption><p>Privacy policy compliance evaluation results of personal information security and feedback.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="mhealth_v14i1e73651_fig06.png"/></fig><p>The level 1 evaluation indicator PI usage is relatively low (mean 54.2%, SD 24.4%) for privacy policy compliance. This indicates that nearly half of the sports health apps do not strictly enforce the protective regulations for PI usage (<xref ref-type="fig" rid="figure7">Figure 7</xref>). Sports and health apps generally provide good protection for users&#x2019; PI rights, with the compliance rate for the query right being the highest (mean 80.1%, SD 40.0%). Compliance rates for the correction right (mean 70.6%, SD 45.6%), deletion right (mean 79.7%, SD 40.3%), account cancelation right (mean 61.4%, SD 48.8%), and withdraw or change authorization (mean 75.2%, SD 43.3%) also exceed half, indicating that the vast majority of sports and health apps can effectively protect users&#x2019; basic PI rights. However, in terms of user personal information rights, the privacy compliance rates for copyright (mean 46.5%, SD 50%) and asking response right (mean 45.1%, SD 49.8%) are relatively poor, especially for the deceased user rule, which has the worst privacy compliance (mean 5.2%, SD 22.3%). On the other hand, the privacy compliance rates for level 2 evaluation indicators such as PI access control (mean 67.5%, SD 46.9%) and purpose restrictions for PI usage (mean 77.6%, SD 41.8%) are relatively good. The privacy policy compliance rate for authorization for the usage purpose change (mean 53.5%, SD 50%) and the complaint mechanism (mean 51.7%, SD 50.1%) have both exceeded half. Only one-third of sports and health apps meet privacy policy compliance requirements in deidentified display and use (mean 34.6%, SD 47.7%). It is particularly noteworthy that the compliance rate of privacy policies regarding constraints of automatic decision-making is very low (mean 9.4%, SD 29.3%), indicating that the vast majority of sports and health apps do not have restrictions on the automatic decision-making mechanism. This is detrimental to users&#x2019; ability to decide how their PI is used and processed, leading to negative impacts on the security of PI and users&#x2019; peace of mind [<xref ref-type="bibr" rid="ref80">80</xref>].</p><fig position="float" id="figure7"><label>Figure 7.</label><caption><p>Privacy policy compliance evaluation results of personal information usage. PI: personal information.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="mhealth_v14i1e73651_fig07.png"/></fig><p>The compliance rate of privacy policies for sports and health apps regarding the level 1 evaluation indicator PI storage is the lowest (mean 53.5%, SD 28.4%), with about half of the apps failing to meet the compliance requirements for PI storage (<xref ref-type="fig" rid="figure8">Figure 8</xref>). The compliance rate of privacy policies for sports and health apps regarding the level 2 evaluation indicator storage place is the highest (mean 78%, SD 41.5%), while the compliance extent for storage time (mean 69.6%, SD 46.1%) and PI deidentification (mean 52.4%, SD 50%) also performs relatively well. However, the compliance rate of privacy policies for sensitive information storage is the worst among sports and health apps, indicating that the vast majority of apps do not have specific provisions and settings for the storage of users&#x2019; sensitive PI, which is detrimental to the protection of users&#x2019; sensitive PI and data security.</p><fig position="float" id="figure8"><label>Figure 8.</label><caption><p>Privacy policy compliance evaluation results of personal information storage. PI: personal information.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="mhealth_v14i1e73651_fig08.png"/></fig></sec></sec><sec id="s4" sec-type="discussion"><title>Discussion</title><sec id="s4-1"><title>Principal Findings</title><p>We developed a privacy policy evaluation scale by integrating scenario-based contextual analysis theory and information life cycle theory, grounded in the provisions of the PIPL and PI Guidelines, to assess privacy policies of mobile sports and health apps. Our defined context encompasses scenarios where users use these apps to record physical activity data, exercise routes, and fitness instructions, all directly related to physical exercise.</p><p>This study&#x2019;s findings demonstrate that 286 evaluated apps in the Chinese Mainland are failing to meet core PI protection requirements, with critical gaps in the overall compliance of the 286 apps, policy update, sensitive PI protection, key user rights, PI transferring, and PI security management.</p><p>First, our analysis indicates that the overall compliance level of privacy policies among 286 sports and health apps is not high. The compliance levels varied (mean 61%, SD 24.3%), with a minority of apps demonstrating strong compliance while others showed lower compliance. Sports and health apps with low compliance primarily violate the PIPL and PI Guidelines, which share common principles with many other jurisdictions. Furthermore, low privacy policy compliance of apps can have several direct and indirect negative consequences for users, including security risks, loss of control, and intrusive marketing. This indicates the need to strengthen PI regulatory oversight for sports and health apps and establish standardized, actionable practices.</p><p>Second, data analysis suggests that PI collection has the highest level of compliance. According to Article 14 of the PIPL, if the collection purpose, method, or types are changed, a separate consent shall be obtained from users. However, data analysis indicates that compliance rates regarding privacy policy updates are unsatisfactory, with only 122 out of 286 apps adhering to this requirement. Indeed, many app developers operate under the assumption that continued use equates to user consent, rather than proactively seeking explicit approval. This lack of compliance undermines both user dignity and security, increasing the risk of data misuse and breaches. To address this, we argue that apps should instead secure explicit consent through clear pop-up notifications, much like during the initial sign-up process. Users should be required to actively confirm their agreement; otherwise, access to the app&#x2019;s services should be limited or denied.</p><p>Third, we found that the privacy policies of sports and health apps exhibit significant shortcomings in protecting sensitive PI. It should be noted that the PIPL (especially Chapter II, Section 2) and the Guidelines (especially Article 5.4) provide special protection for the collection of sensitive PI. Substantively, Article 28 of the PIPL specifies the substantive conditions for processing sensitive PI, namely, PI processors can process sensitive PI only when there is a specific purpose and when it is of necessity, under the circumstances where strict protective measures are taken. Procedurally, Articles 29 and 30 of the PIPL and Article 5.4b of the PI Guidelines require that a processor processing sensitive PI shall notify the individual of the necessity of processing their sensitive PI and the impact it has on their rights and interests,&#x201D; and that sensitive PI processors must obtain informed, voluntary, specific, clear, unequivocal, and separate consent from PI subjects. The substantive and procedural requirements have also been highlighted by the Notice of the Ministry of Industry and Information Technology on Further Enhancing the Service Capacity of Mobile Internet Applications [<xref ref-type="bibr" rid="ref81">81</xref>]. However, our data analysis shows that the compliance rate of sensitive PI protection (mean 29.4%, SD 45.6%) is significantly lower than that of general PI protection (mean 83.6%, SD 37.1%). This disparity not only indicates how inadequate the present security measures are for protecting sensitive PI, but it also continuously lowers users&#x2019; awareness of security when providing sensitive PI. Additionally, it is also important to note that although a total of 40 apps referenced sensitive PI storage, none comply with the storage requirements of the PI Guidelines, which mandate encryption (Article 6.3.a) and, in principle, the elimination of original personal biometric data (Article 6.3.c), including samples and photographs. In the 40 apps, one just lists the types of sensitive PI, such as personal identity information and biometric information. The other apps fail to explicitly state the protection measures for sensitive PI; instead, their statements imply that adequate protection measures have been taken and that they would do their best to protect sensitive PI. This reveals a serious security concern, because if sensitive PI is leaked, tampered with, or used illegally, it may endanger the user&#x2019;s personal or property safety.</p><p>Fourth, our analysis indicates that comprehensive compliance with the protection of users&#x2019; PI rights remains weak. In terms of user rights, although most apps effectively list a series of user rights, including query rights, correction rights, deletion rights, withdraw or change authorization rights, and account cancellation rights, less than half of the apps give users the right to obtain a copy of PI and ask for a response. Notably, only 27 of the 286 apps provide users with the right to refuse using automated decision-making mechanisms. Currently, personalized recommendation technologies and artificial intelligence technologies are advancing rapidly. Automated decision-making mechanisms based on algorithms have been widely adopted in the operation of sports and health apps. The vast majority of these apps do not grant users the right to opt out of automated decision-making processes. This results in the infringement of users&#x2019; autonomy over the collection, use, and processing of their personal information, violating the principles of legitimacy and transparency enshrined in PIPL. Consequently, users may be misled in their app usage, experience improper collection of their information, and face frequent disruption from app notifications. Fewer apps have provided deceased user rules, that is, unless otherwise arranged by the deceased before their death, their close relatives have the rights to access, copy, correct, delete, and other rights related to the deceased&#x2019;s relevant PI. This will trigger disputes over the usage and inheritance of deceased individuals&#x2019; digital assets, hindering the normal operation and development of sports and health apps.</p><p>Fifth, our findings reveal that privacy policies for sports and health apps require further refinement regarding regulations on sharing, transferring, and disclosing PI. While most apps state the reasons for sharing, transferring, and disclosing PI, significantly fewer of them will take technical measures to ensure information security and obtain the user&#x2019;s separate consent. Notably, even fewer apps&#x2019; privacy policies specify that when PI is shared or transferred to overseas processors, the user should be separately informed of the purpose of data export and the receiver, and the user&#x2019;s authorization should be separately obtained. This is obviously lower than the standards stipulated in Article 23 of the PIPL and Article 9 of the PI Guidelines, which may damage the users&#x2019; ability to monitor the whole PI processing process, their security awareness of transferring PI, and their trust in apps, and the principle of informed consent.</p><p>Finally, our analysis reveals that sports and health apps do not provide users with clear response times for feedback. User data collection occurs in real time, and this frequent gathering inevitably leads to issues or disputes during usage. At such times, a timely and effective feedback and dispute resolution mechanism becomes crucial for resolving problems, maintaining user retention, and helping apps build a positive reputation. However, many sports and health apps merely provide feedback channels without establishing timelines for addressing concerns. This lack of accountability discourages apps from proactively and effectively resolving feedback issues and disputes. Additionally, many sports and health apps lack robust PI security safeguards and reporting mechanisms, making personal data vulnerable to infringement and posing serious risks of data breaches. This will lead to a decline in users&#x2019; trust in the app&#x2019;s privacy protection, making users more cautious about providing personal information, especially sensitive personal information, and may lead to users uninstalling the app.</p></sec><sec id="s4-2"><title>Recommendations</title><p>The study&#x2019;s findings collectively demonstrate that 286 evaluated apps are failing to meet core PI protection requirements. Critical gaps in PI protection are primarily attributed to 3 factors. First, there is a deficiency of awareness among users regarding PI protection, reducing incentives for app developers to prioritize privacy. Second, existing PI guidelines lack legally binding force, resulting in inconsistent adherence and voluntary compliance. Third, insufficient regulatory oversight and weak enforcement mechanisms fail to deter noncompliant practices. These factors collectively undermine the effectiveness of current PI protection frameworks, highlighting the need for targeted action from 3 stakeholders: users, regulators, and legislators. We argue that only through coordinated action can the app ecosystem close the compliance gaps identified in this study, reduce PI protection risks, and restore user trust in digital services.</p><p>First, to strengthen app privacy compliance, it is essential to enhance users&#x2019; PI rights awareness [<xref ref-type="bibr" rid="ref82">82</xref>]. We argue that interventions can be scenario-embedded and accessible. For example, app developers are encouraged to integrate snapshots of PI rights into app onboarding when users consent to privacy policies, paired with visual resources that translate legal jargon into simple guidance [<xref ref-type="bibr" rid="ref83">83</xref>]. This ensures users learn rights when they interact with PI-related features, not just through disconnected policy texts. Additionally, official complaint channels should be easily accessible to hold apps accountable for noncompliance, which can drive industry-wide improvement [<xref ref-type="bibr" rid="ref84">84</xref>].</p><p>Second, the regulatory mechanism for sports and health apps should be standardized. Under the current legal framework, the regulatory mechanism for apps can be characterized as self-regulation by app operators, with government oversight as a supplementary measure. Moreover, in terms of the institutional framework in the Chinese Mainland, regulators are dispersed across many different government departments, resulting in a lack of enthusiasm for law enforcement and of technical capacity for supervision. As a result, the regulation of apps in practice is inadequate. In this context, we recommend creating a unique data regulator to assess and oversee the privacy protection of apps and raising the industry&#x2019;s entry barrier through the issuance of compliance identification or certifications [<xref ref-type="bibr" rid="ref64">64</xref>]. This regulator can strengthen enforcement of low-compliance areas, such as sensitive PI storage and policy updates, through regular audits and penalties for noncompliance [<xref ref-type="bibr" rid="ref63">63</xref>].</p><p>Finally, laws and regulations for the protection of personal health information should be improved. The Civil Code [<xref ref-type="bibr" rid="ref85">85</xref>], the Cybersecurity Law of China [<xref ref-type="bibr" rid="ref86">86</xref>], the Law of the People&#x2019;s&#x2002;Republic of China on Basic Medical and Health Care&#x2002;and the Promotion of Health [<xref ref-type="bibr" rid="ref87">87</xref>], and the PIPL formulate the legal framework for protecting personal health information. While these laws are comprehensive, the majority of them contain oath and principle clauses that are not applicable in specific cases. Although many of these principles and oath clauses are further crafted in the PI Guidelines, these guidelines do not have the force of law; instead, they are merely recommended standards and are not mandatory by nature. In this regard, we suggest that the legal effect of adopting the PI Guidelines should be clarified in laws and regulations. In this way, the app operator should specify in the first part of the privacy policy whether the PI Guidelines are adopted, and once adopted, they will be legally binding [<xref ref-type="bibr" rid="ref66">66</xref>].</p></sec><sec id="s4-3"><title>Contributions</title><p>This study holds significant implications for both policymakers and scholars. First, based on the principal findings&#x2014;particularly that the privacy protection requirements established by the PIPL demonstrate a higher level of compliance compared with the PI Guidelines&#x2014;we propose that legislation should strengthen the binding force of the PI Guidelines, thereby providing guidance for legislative reform. Second, the current low compliance with privacy policies may be linked to inadequate regulatory enforcement. In response to the fragmented regulatory oversight in practice, we recommend the establishment of an independent regulator to enhance the effectiveness of privacy protection enforcement. Finally, this study addresses a gap in the existing literature. While existing studies have explored the relationship between health apps and privacy protection in Australia [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref88">88</xref>], between mHealth apps and privacy protection [<xref ref-type="bibr" rid="ref89">89</xref>-<xref ref-type="bibr" rid="ref93">93</xref>], and between health code apps and privacy protection in China [<xref ref-type="bibr" rid="ref94">94</xref>,<xref ref-type="bibr" rid="ref95">95</xref>], the legal compliance of sports and health apps with the PIPL and PI Guidelines, as well as China&#x2019;s legislative framework for PI protection, was not thoroughly examined in these studies. This study fills this gap by examining the privacy policies of 286 sports and health apps across 37 evaluation dimensions and assessing whether these privacy policies comply with the PIPL and PI Guidelines.</p></sec><sec id="s4-4"><title>Limitations</title><p>However, this study also has limitations. Although we developed an indicator scale to assess the compliance level of privacy policies of the 286 sports and health apps, this evaluation process does not concern the actual implementation of different technical measures, resulting in the omission of evaluation criteria and the lack of targeted recommendations for improvement from a technical point of view [<xref ref-type="bibr" rid="ref96">96</xref>]. For instance, an app may explicitly state in its policy that it encrypts sensitive PI during storage but may not actually implement consistent encryption protocols in its backend systems. We hope that future research can treat this study as a starting point to further analyze the processing of PI and the design and implementation of PI protection measures in the information system, by using technical methods, such as network traffic analysis or third-party data flow auditing, and adopting the research method of interviewing relevant personnel including product managers, research and development engineers, PI protection officers, legal personnel, system architects, security administrators, operation and maintenance personnel, human resources personnel, system users, and so on.</p></sec><sec id="s4-5"><title>Conclusions</title><p>The extensive usage of sports and health apps is significantly enhancing the social and public health landscape in the Chinese Mainland. Nonetheless, the security threats to PI protection arising from privacy policy compliance have not received adequate attention. This paper&#x2019;s assessment of the overall compliance level of 286 sports and health apps and the individual evaluation of 37 privacy policies reveals a complex picture of PI protection. Although some apps establish commendable compliance policies, there are some shortcomings. These shortcomings not only pose security threats to app users but may also hinder operators in optimizing and developing app functionalities. In light of this, this paper puts forward suggestions for improvement from the perspectives of user awareness, regulatory enforcement, and legislative reforms.</p></sec></sec></body><back><ack><p>We thank Jing Guo, Xiaolan Ji, and Jiamei Xie for assistance with data collection.</p></ack><notes><sec><title>Funding</title><p>This research is funded by the National Social Science Fund Project of China (22CFX073 and 24CFX023) and China National Intellectual Property Administration Soft Science Research Project (SS25-A-05) .</p></sec><sec><title>Data Availability</title><p>All data generated or analyzed during this study are included in this published article and its supplementary information files.</p></sec></notes><fn-group><fn fn-type="con"><p>RG performed the conceptualization, methodology, investigation, data curation, formal analysis, writing&#x2013;original draft, and writing&#x2013;review &#x0026; editing. FC made the conceptualization, methodology, data curation, formal analysis, writing&#x2013;original draft, and writing&#x2013;review &#x0026; editing.</p></fn><fn fn-type="conflict"><p>None declared.</p></fn></fn-group><glossary><title>Abbreviations</title><def-list><def-item><term id="abb1">mHealth</term><def><p>mobile health</p></def></def-item><def-item><term id="abb2">PI</term><def><p>personal information</p></def></def-item><def-item><term id="abb3">PIPL</term><def><p>Personal Information Protection Law</p></def></def-item></def-list></glossary><ref-list><title>References</title><ref id="ref1"><label>1</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Tuitert</surname><given-names>I</given-names> </name><name name-style="western"><surname>Marinus</surname><given-names>JD</given-names> </name><name name-style="western"><surname>Dalenberg</surname><given-names>JR</given-names> </name><name name-style="western"><surname>van &#x2019;t Veer</surname><given-names>JT</given-names> </name></person-group><article-title>Digital health technology use across socioeconomic groups prior to and during the COVID-19 pandemic: panel study</article-title><source>JMIR Public Health Surveill</source><year>2024</year><month>09</month><day>13</day><volume>10</volume><fpage>e55384</fpage><pub-id pub-id-type="doi">10.2196/55384</pub-id><pub-id pub-id-type="medline">39269755</pub-id></nlm-citation></ref><ref id="ref2"><label>2</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Mosa</surname><given-names>ASM</given-names> </name><name name-style="western"><surname>Yoo</surname><given-names>I</given-names> </name><name name-style="western"><surname>Sheets</surname><given-names>L</given-names> </name></person-group><article-title>A systematic review of healthcare applications for smartphones</article-title><source>BMC Med Inform Decis Mak</source><year>2012</year><month>07</month><day>10</day><volume>12</volume><fpage>67</fpage><pub-id pub-id-type="doi">10.1186/1472-6947-12-67</pub-id><pub-id pub-id-type="medline">22781312</pub-id></nlm-citation></ref><ref id="ref3"><label>3</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Weinstein</surname><given-names>RS</given-names> </name><name name-style="western"><surname>Lopez</surname><given-names>AM</given-names> </name><name name-style="western"><surname>Joseph</surname><given-names>BA</given-names> </name><etal/></person-group><article-title>Telemedicine, telehealth, and mobile health applications that work: opportunities and barriers</article-title><source>Am J Med</source><year>2014</year><month>03</month><volume>127</volume><issue>3</issue><fpage>183</fpage><lpage>187</lpage><pub-id pub-id-type="doi">10.1016/j.amjmed.2013.09.032</pub-id><pub-id pub-id-type="medline">24384059</pub-id></nlm-citation></ref><ref id="ref4"><label>4</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Tangari</surname><given-names>G</given-names> </name><name name-style="western"><surname>Ikram</surname><given-names>M</given-names> </name><name name-style="western"><surname>Ijaz</surname><given-names>K</given-names> </name><name name-style="western"><surname>Kaafar</surname><given-names>MA</given-names> </name><name name-style="western"><surname>Berkovsky</surname><given-names>S</given-names> </name></person-group><article-title>Mobile health and privacy: cross sectional study</article-title><source>BMJ</source><year>2021</year><month>06</month><day>16</day><volume>373</volume><fpage>n1248</fpage><pub-id pub-id-type="doi">10.1136/bmj.n1248</pub-id><pub-id pub-id-type="medline">34135009</pub-id></nlm-citation></ref><ref id="ref5"><label>5</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Mart&#x00ED;nez-P&#x00E9;rez</surname><given-names>B</given-names> </name><name name-style="western"><surname>de la Torre-D&#x00ED;ez</surname><given-names>I</given-names> </name><name name-style="western"><surname>L&#x00F3;pez-Coronado</surname><given-names>M</given-names> </name></person-group><article-title>Privacy and security in mobile health apps: a review and recommendations</article-title><source>J Med Syst</source><year>2015</year><month>01</month><volume>39</volume><issue>1</issue><fpage>181</fpage><pub-id pub-id-type="doi">10.1007/s10916-014-0181-3</pub-id><pub-id pub-id-type="medline">25486895</pub-id></nlm-citation></ref><ref id="ref6"><label>6</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Rathbone</surname><given-names>AL</given-names> </name><name name-style="western"><surname>Prescott</surname><given-names>J</given-names> </name></person-group><article-title>The use of mobile apps and SMS messaging as physical and mental health interventions: systematic review</article-title><source>J Med Internet Res</source><year>2017</year><month>08</month><day>24</day><volume>19</volume><issue>8</issue><fpage>e295</fpage><pub-id pub-id-type="doi">10.2196/jmir.7740</pub-id><pub-id pub-id-type="medline">28838887</pub-id></nlm-citation></ref><ref id="ref7"><label>7</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Maa&#x00DF;</surname><given-names>L</given-names> </name><name name-style="western"><surname>Freye</surname><given-names>M</given-names> </name><name name-style="western"><surname>Pan</surname><given-names>CC</given-names> </name><name name-style="western"><surname>Dassow</surname><given-names>HH</given-names> </name><name name-style="western"><surname>Niess</surname><given-names>J</given-names> </name><name name-style="western"><surname>Jahnel</surname><given-names>T</given-names> </name></person-group><article-title>The definitions of health apps and medical apps from the perspective of public health and law: qualitative analysis of an interdisciplinary literature overview</article-title><source>JMIR Mhealth Uhealth</source><year>2022</year><month>10</month><day>31</day><volume>10</volume><issue>10</issue><fpage>e37980</fpage><pub-id pub-id-type="doi">10.2196/37980</pub-id><pub-id pub-id-type="medline">36315221</pub-id></nlm-citation></ref><ref id="ref8"><label>8</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Gamache</surname><given-names>R</given-names> </name><name name-style="western"><surname>Kharrazi</surname><given-names>H</given-names> </name><name name-style="western"><surname>Weiner</surname><given-names>JP</given-names> </name></person-group><article-title>Public and population health informatics: the bridging of big data to benefit communities</article-title><source>Yearb Med Inform</source><year>2018</year><month>08</month><volume>27</volume><issue>1</issue><fpage>199</fpage><lpage>206</lpage><pub-id pub-id-type="doi">10.1055/s-0038-1667081</pub-id><pub-id pub-id-type="medline">30157524</pub-id></nlm-citation></ref><ref id="ref9"><label>9</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Betthauser</surname><given-names>LM</given-names> </name><name name-style="western"><surname>Stearns-Yoder</surname><given-names>KA</given-names> </name><name name-style="western"><surname>McGarity</surname><given-names>S</given-names> </name><name name-style="western"><surname>Smith</surname><given-names>V</given-names> </name><name name-style="western"><surname>Place</surname><given-names>S</given-names> </name><name name-style="western"><surname>Brenner</surname><given-names>LA</given-names> </name></person-group><article-title>Mobile app for mental health monitoring and clinical outreach in veterans: mixed methods feasibility and acceptability study</article-title><source>J Med Internet Res</source><year>2020</year><month>08</month><day>11</day><volume>22</volume><issue>8</issue><fpage>e15506</fpage><pub-id pub-id-type="doi">10.2196/15506</pub-id><pub-id pub-id-type="medline">32779572</pub-id></nlm-citation></ref><ref id="ref10"><label>10</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Hahn</surname><given-names>SL</given-names> </name><name name-style="western"><surname>Kaciroti</surname><given-names>N</given-names> </name><name name-style="western"><surname>Eisenberg</surname><given-names>D</given-names> </name><name name-style="western"><surname>Weeks</surname><given-names>HM</given-names> </name><name name-style="western"><surname>Bauer</surname><given-names>KW</given-names> </name><name name-style="western"><surname>Sonneville</surname><given-names>KR</given-names> </name></person-group><article-title>Introducing dietary self-monitoring to undergraduate women via a calorie counting app has no effect on mental health or health behaviors: results from a randomized controlled trial</article-title><source>J Acad Nutr Diet</source><year>2021</year><month>12</month><volume>121</volume><issue>12</issue><fpage>2377</fpage><lpage>2388</lpage><pub-id pub-id-type="doi">10.1016/j.jand.2021.06.311</pub-id><pub-id pub-id-type="medline">34427188</pub-id></nlm-citation></ref><ref id="ref11"><label>11</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Chew</surname><given-names>HSJ</given-names> </name><name name-style="western"><surname>Koh</surname><given-names>WL</given-names> </name><name name-style="western"><surname>Ng</surname><given-names>J</given-names> </name><name name-style="western"><surname>Tan</surname><given-names>KK</given-names> </name></person-group><article-title>Sustainability of weight loss through smartphone apps: systematic review and meta-analysis on anthropometric, metabolic, and dietary outcomes</article-title><source>J Med Internet Res</source><year>2022</year><month>09</month><day>21</day><volume>24</volume><issue>9</issue><fpage>e40141</fpage><pub-id pub-id-type="doi">10.2196/40141</pub-id><pub-id pub-id-type="medline">36129739</pub-id></nlm-citation></ref><ref id="ref12"><label>12</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Antoun</surname><given-names>J</given-names> </name><name name-style="western"><surname>Itani</surname><given-names>H</given-names> </name><name name-style="western"><surname>Alarab</surname><given-names>N</given-names> </name><name name-style="western"><surname>Elsehmawy</surname><given-names>A</given-names> </name></person-group><article-title>The effectiveness of combining nonmobile interventions with the use of smartphone apps with various features for weight loss: systematic review and meta-analysis</article-title><source>JMIR Mhealth Uhealth</source><year>2022</year><month>04</month><day>8</day><volume>10</volume><issue>4</issue><fpage>e35479</fpage><pub-id pub-id-type="doi">10.2196/35479</pub-id><pub-id pub-id-type="medline">35394443</pub-id></nlm-citation></ref><ref id="ref13"><label>13</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Sakane</surname><given-names>N</given-names> </name><name name-style="western"><surname>Suganuma</surname><given-names>A</given-names> </name><name name-style="western"><surname>Domichi</surname><given-names>M</given-names> </name><etal/></person-group><article-title>The effect of a mHealth app (KENPO-app) for specific health guidance on weight changes in adults with obesity and hypertension: pilot randomized controlled trial</article-title><source>JMIR Mhealth Uhealth</source><year>2023</year><month>04</month><day>12</day><volume>11</volume><fpage>e43236</fpage><pub-id pub-id-type="doi">10.2196/43236</pub-id><pub-id pub-id-type="medline">37043287</pub-id></nlm-citation></ref><ref id="ref14"><label>14</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Lugones-Sanchez</surname><given-names>C</given-names> </name><name name-style="western"><surname>Sanchez-Calavera</surname><given-names>MA</given-names> </name><name name-style="western"><surname>Repiso-Gento</surname><given-names>I</given-names> </name><etal/></person-group><article-title>Effectiveness of an mHealth intervention combining a smartphone app and smart band on body composition in an overweight and obese population: randomized controlled trial (EVIDENT 3 Study)</article-title><source>JMIR Mhealth Uhealth</source><year>2020</year><month>11</month><day>26</day><volume>8</volume><issue>11</issue><fpage>e21771</fpage><pub-id pub-id-type="doi">10.2196/21771</pub-id><pub-id pub-id-type="medline">33242020</pub-id></nlm-citation></ref><ref id="ref15"><label>15</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Mano</surname><given-names>R</given-names> </name></person-group><article-title>Mobile health apps and health management behaviors: cost-benefit modeling analysis</article-title><source>JMIR Hum Factors</source><year>2021</year><month>04</month><day>22</day><volume>8</volume><issue>2</issue><fpage>e21251</fpage><pub-id pub-id-type="doi">10.2196/21251</pub-id><pub-id pub-id-type="medline">33885372</pub-id></nlm-citation></ref><ref id="ref16"><label>16</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Cho</surname><given-names>J</given-names> </name></person-group><article-title>The impact of post-adoption beliefs on the continued use of health apps</article-title><source>Int J Med Inform</source><year>2016</year><month>03</month><volume>87</volume><fpage>75</fpage><lpage>83</lpage><pub-id pub-id-type="doi">10.1016/j.ijmedinf.2015.12.016</pub-id><pub-id pub-id-type="medline">26806714</pub-id></nlm-citation></ref><ref id="ref17"><label>17</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Gordon</surname><given-names>WJ</given-names> </name><name name-style="western"><surname>Landman</surname><given-names>A</given-names> </name><name name-style="western"><surname>Zhang</surname><given-names>H</given-names> </name><name name-style="western"><surname>Bates</surname><given-names>DW</given-names> </name></person-group><article-title>Beyond validation: getting health apps into clinical practice</article-title><source>NPJ Digit Med</source><year>2020</year><volume>3</volume><fpage>14</fpage><pub-id pub-id-type="doi">10.1038/s41746-019-0212-z</pub-id><pub-id pub-id-type="medline">32047860</pub-id></nlm-citation></ref><ref id="ref18"><label>18</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Yerrakalva</surname><given-names>D</given-names> </name><name name-style="western"><surname>Yerrakalva</surname><given-names>D</given-names> </name><name name-style="western"><surname>Hajna</surname><given-names>S</given-names> </name><name name-style="western"><surname>Griffin</surname><given-names>S</given-names> </name></person-group><article-title>Effects of mobile health app interventions on sedentary time, physical activity, and fitness in older adults: systematic review and meta-analysis</article-title><source>J Med Internet Res</source><year>2019</year><month>11</month><day>28</day><volume>21</volume><issue>11</issue><fpage>e14343</fpage><pub-id pub-id-type="doi">10.2196/14343</pub-id><pub-id pub-id-type="medline">31778121</pub-id></nlm-citation></ref><ref id="ref19"><label>19</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Modave</surname><given-names>F</given-names> </name><name name-style="western"><surname>Bian</surname><given-names>J</given-names> </name><name name-style="western"><surname>Leavitt</surname><given-names>T</given-names> </name><name name-style="western"><surname>Bromwell</surname><given-names>J</given-names> </name><name name-style="western"><surname>Harris Iii</surname><given-names>C</given-names> </name><name name-style="western"><surname>Vincent</surname><given-names>H</given-names> </name></person-group><article-title>Low quality of free coaching apps with respect to the American College of Sports Medicine Guidelines: a review of current mobile apps</article-title><source>JMIR Mhealth Uhealth</source><year>2015</year><month>07</month><day>24</day><volume>3</volume><issue>3</issue><fpage>e77</fpage><pub-id pub-id-type="doi">10.2196/mhealth.4669</pub-id><pub-id pub-id-type="medline">26209109</pub-id></nlm-citation></ref><ref id="ref20"><label>20</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Tighe</surname><given-names>J</given-names> </name><name name-style="western"><surname>Shand</surname><given-names>F</given-names> </name><name name-style="western"><surname>Ridani</surname><given-names>R</given-names> </name><name name-style="western"><surname>Mackinnon</surname><given-names>A</given-names> </name><name name-style="western"><surname>De La Mata</surname><given-names>N</given-names> </name><name name-style="western"><surname>Christensen</surname><given-names>H</given-names> </name></person-group><article-title>Ibobbly mobile health intervention for suicide prevention in Australian Indigenous youth: a pilot randomised controlled trial</article-title><source>BMJ Open</source><year>2017</year><month>01</month><day>27</day><volume>7</volume><issue>1</issue><fpage>e013518</fpage><pub-id pub-id-type="doi">10.1136/bmjopen-2016-013518</pub-id><pub-id pub-id-type="medline">28132007</pub-id></nlm-citation></ref><ref id="ref21"><label>21</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Grundy</surname><given-names>Q</given-names> </name></person-group><article-title>A review of the quality and impact of mobile health apps</article-title><source>Annu Rev Public Health</source><year>2022</year><month>04</month><day>5</day><volume>43</volume><fpage>117</fpage><lpage>134</lpage><pub-id pub-id-type="doi">10.1146/annurev-publhealth-052020-103738</pub-id><pub-id pub-id-type="medline">34910582</pub-id></nlm-citation></ref><ref id="ref22"><label>22</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Ni</surname><given-names>Z</given-names> </name><name name-style="western"><surname>Wang</surname><given-names>Y</given-names> </name><name name-style="western"><surname>Qian</surname><given-names>Y</given-names> </name></person-group><article-title>Privacy policy compliance of chronic disease management apps in China: scale development and content evaluation</article-title><source>JMIR Mhealth Uhealth</source><year>2021</year><month>01</month><day>28</day><volume>9</volume><issue>1</issue><fpage>e23409</fpage><pub-id pub-id-type="doi">10.2196/23409</pub-id><pub-id pub-id-type="medline">33507159</pub-id></nlm-citation></ref><ref id="ref23"><label>23</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Rowland</surname><given-names>SP</given-names> </name><name name-style="western"><surname>Fitzgerald</surname><given-names>JE</given-names> </name><name name-style="western"><surname>Holme</surname><given-names>T</given-names> </name><name name-style="western"><surname>Powell</surname><given-names>J</given-names> </name><name name-style="western"><surname>McGregor</surname><given-names>A</given-names> </name></person-group><article-title>What is the clinical value of mHealth for patients?</article-title><source>NPJ Digit Med</source><year>2020</year><volume>3</volume><fpage>4</fpage><pub-id pub-id-type="doi">10.1038/s41746-019-0206-x</pub-id><pub-id pub-id-type="medline">31970289</pub-id></nlm-citation></ref><ref id="ref24"><label>24</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Lupton</surname><given-names>D</given-names> </name><name name-style="western"><surname>Jutel</surname><given-names>A</given-names> </name></person-group><article-title>&#x201C;It&#x2019;s like having a physician in your pocket!&#x201D; A critical analysis of self-diagnosis smartphone apps</article-title><source>Soc Sci Med</source><year>2015</year><month>05</month><volume>133</volume><fpage>128</fpage><lpage>135</lpage><pub-id pub-id-type="doi">10.1016/j.socscimed.2015.04.004</pub-id><pub-id pub-id-type="medline">25864149</pub-id></nlm-citation></ref><ref id="ref25"><label>25</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Flaherty</surname><given-names>JL</given-names> </name></person-group><article-title>Digital diagnosis: privacy and the regulation of mobile phone health applications</article-title><source>Am J Law Med</source><year>2014</year><volume>40</volume><issue>4</issue><fpage>416</fpage><lpage>441</lpage><pub-id pub-id-type="medline">27530051</pub-id></nlm-citation></ref><ref id="ref26"><label>26</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Herriger</surname><given-names>C</given-names> </name><name name-style="western"><surname>Merlo</surname><given-names>O</given-names> </name><name name-style="western"><surname>Eisingerich</surname><given-names>AB</given-names> </name><name name-style="western"><surname>Arigayota</surname><given-names>AR</given-names> </name></person-group><article-title>Context-contingent privacy concerns and exploration of the privacy paradox in the age of AI, augmented reality, big data, and the internet of things: systematic review</article-title><source>J Med Internet Res</source><year>2025</year><month>05</month><day>14</day><volume>27</volume><fpage>e71951</fpage><pub-id pub-id-type="doi">10.2196/71951</pub-id><pub-id pub-id-type="medline">40367513</pub-id></nlm-citation></ref><ref id="ref27"><label>27</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Tovino</surname><given-names>SA</given-names> </name></person-group><article-title>Privacy and security issues with mobile health research applications</article-title><source>J Law Med Ethics</source><year>2020</year><month>03</month><volume>48</volume><issue>1_suppl</issue><fpage>154</fpage><lpage>158</lpage><pub-id pub-id-type="doi">10.1177/1073110520917041</pub-id><pub-id pub-id-type="medline">32342741</pub-id></nlm-citation></ref><ref id="ref28"><label>28</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Jiang</surname><given-names>J</given-names> </name><name name-style="western"><surname>Zheng</surname><given-names>Z</given-names> </name></person-group><article-title>Medical information protection in internet hospital apps in China: scale development and content analysis</article-title><source>JMIR Mhealth Uhealth</source><year>2024</year><month>06</month><day>21</day><volume>12</volume><fpage>e55061</fpage><pub-id pub-id-type="doi">10.2196/55061</pub-id><pub-id pub-id-type="medline">38904994</pub-id></nlm-citation></ref><ref id="ref29"><label>29</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Lin</surname><given-names>X</given-names> </name><name name-style="western"><surname>Wu</surname><given-names>X</given-names> </name><name name-style="western"><surname>Zhu</surname><given-names>Z</given-names> </name><name name-style="western"><surname>Chen</surname><given-names>D</given-names> </name><name name-style="western"><surname>Li</surname><given-names>H</given-names> </name><name name-style="western"><surname>Lin</surname><given-names>R</given-names> </name></person-group><article-title>Quality and privacy policy compliance of mental health care apps in China: cross-sectional evaluation study</article-title><source>J Med Internet Res</source><year>2025</year><month>07</month><day>3</day><volume>27</volume><fpage>e66762</fpage><pub-id pub-id-type="doi">10.2196/66762</pub-id><pub-id pub-id-type="medline">40607739</pub-id></nlm-citation></ref><ref id="ref30"><label>30</label><nlm-citation citation-type="web"><person-group person-group-type="author"><name name-style="western"><surname>McGee</surname><given-names>MK</given-names> </name></person-group><article-title>FTC fines fertility app vendor, bars it from data sharing</article-title><source>Gov Info Security</source><access-date>2024-09-13</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.govinfosecurity.com/ftc-fines-fertility-app-vendor-bars-from-data-sharing-a-22100">https://www.govinfosecurity.com/ftc-fines-fertility-app-vendor-bars-from-data-sharing-a-22100</ext-link></comment></nlm-citation></ref><ref id="ref31"><label>31</label><nlm-citation citation-type="report"><article-title>Out of control-how consumers are exploited by the online advertising industry</article-title><year>2020</year><access-date>2024-09-13</access-date><publisher-name>Forbrukerr&#x00E5;det</publisher-name><comment><ext-link ext-link-type="uri" xlink:href="https://www.forbrukerradet.no/rapporter/out-of-control/">https://www.forbrukerradet.no/rapporter/out-of-control/</ext-link></comment></nlm-citation></ref><ref id="ref32"><label>32</label><nlm-citation citation-type="web"><article-title>The National Cyberspace Administration of China will launch a special campaign to rectify app chaos, and the full process governance will become the norm</article-title><source>Cyberspace Administration of China</source><access-date>2024-12-11</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.cac.gov.cn/2018-12/28/c_1123919199.htm">https://www.cac.gov.cn/2018-12/28/c_1123919199.htm</ext-link></comment></nlm-citation></ref><ref id="ref33"><label>33</label><nlm-citation citation-type="web"><person-group person-group-type="author"><name name-style="western"><surname>Paul</surname><given-names>P</given-names> </name><name name-style="western"><surname>Abdul</surname><given-names>H</given-names> </name></person-group><article-title>Data protection laws and regulations USA 2024-2025</article-title><source>ICLG</source><access-date>2024-11-04</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://iclg.com/practice-areas/data-protection-laws-and-regulations/usa">https://iclg.com/practice-areas/data-protection-laws-and-regulations/usa</ext-link></comment></nlm-citation></ref><ref id="ref34"><label>34</label><nlm-citation citation-type="web"><person-group person-group-type="author"><name name-style="western"><surname>Andrew</surname><given-names>K</given-names> </name><name name-style="western"><surname>Willy</surname><given-names>M</given-names> </name></person-group><article-title>Data privacy and protection in the US: a sign of bipartisan progress</article-title><source>iapp</source><access-date>2024-12-23</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://iapp.org/news/a/data-privacy-and-protection-in-the-us-a-sign-of-bipartisan-progress/">https://iapp.org/news/a/data-privacy-and-protection-in-the-us-a-sign-of-bipartisan-progress/</ext-link></comment></nlm-citation></ref><ref id="ref35"><label>35</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Mulder</surname><given-names>T</given-names> </name></person-group><article-title>Health apps, their privacy policies and the GDPR</article-title><source>Eur J Law Technol</source><year>2019</year><access-date>2026-01-18</access-date><volume>10</volume><issue>1</issue><comment><ext-link ext-link-type="uri" xlink:href="https://papers.ssrn.com/sol3/papers.cfm?abstract_id=3506805">https://papers.ssrn.com/sol3/papers.cfm?abstract_id=3506805</ext-link></comment></nlm-citation></ref><ref id="ref36"><label>36</label><nlm-citation citation-type="report"><person-group person-group-type="author"><name name-style="western"><surname>Lauristin</surname><given-names>M</given-names> </name></person-group><article-title>Draft report on the proposal for a regulation of the European Parliament and of the Council concerning the respect for private life and the protection of personal data in electronic communications and repealing directive 2002/58/EC (regulation on privacy and electronic communications)</article-title><year>2017</year><access-date>2024-12-23</access-date><publisher-name>European Parliament</publisher-name><comment><ext-link ext-link-type="uri" xlink:href="https://www.europarl.europa.eu/doceo/document/LIBE-PR-606011_EN.pdf?redirect">https://www.europarl.europa.eu/doceo/document/LIBE-PR-606011_EN.pdf?redirect</ext-link></comment></nlm-citation></ref><ref id="ref37"><label>37</label><nlm-citation citation-type="web"><article-title>Consolidated text: regulation (EU) 2016/679 of the european parliament and of the council of 27 april 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing directive 95/46/EC (general data protection regulation)</article-title><source>European Union</source><access-date>2024-11-04</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:02016R0679-20160504">https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:02016R0679-20160504</ext-link></comment></nlm-citation></ref><ref id="ref38"><label>38</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Bardus</surname><given-names>M</given-names> </name><name name-style="western"><surname>Al Daccache</surname><given-names>M</given-names> </name><name name-style="western"><surname>Maalouf</surname><given-names>N</given-names> </name><name name-style="western"><surname>Al Sarih</surname><given-names>R</given-names> </name><name name-style="western"><surname>Elhajj</surname><given-names>IH</given-names> </name></person-group><article-title>Data management and privacy policy of COVID-19 contact-tracing apps: systematic review and content analysis</article-title><source>JMIR Mhealth Uhealth</source><year>2022</year><month>07</month><day>12</day><volume>10</volume><issue>7</issue><fpage>e35195</fpage><pub-id pub-id-type="doi">10.2196/35195</pub-id><pub-id pub-id-type="medline">35709334</pub-id></nlm-citation></ref><ref id="ref39"><label>39</label><nlm-citation citation-type="web"><article-title>Health information privacy</article-title><source>US Department of Health &#x0026; Human Services</source><access-date>2024-12-23</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.hhs.gov/hipaa/">https://www.hhs.gov/hipaa/</ext-link></comment></nlm-citation></ref><ref id="ref40"><label>40</label><nlm-citation citation-type="web"><article-title>Health breach notification rule</article-title><source>Federal Trade Commission</source><access-date>2025-01-20</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.ftc.gov/legal-library/browse/rules/health-breach-notification-rule">https://www.ftc.gov/legal-library/browse/rules/health-breach-notification-rule</ext-link></comment></nlm-citation></ref><ref id="ref41"><label>41</label><nlm-citation citation-type="web"><article-title>Children&#x2019;s online privacy protection rule (&#x201C;COPPA&#x201D;)</article-title><source>Federal Trade Commission</source><access-date>2025-01-20</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.ftc.gov/legal-library/browse/rules/childrens-online-privacy-protection-rule-coppa">https://www.ftc.gov/legal-library/browse/rules/childrens-online-privacy-protection-rule-coppa</ext-link></comment></nlm-citation></ref><ref id="ref42"><label>42</label><nlm-citation citation-type="web"><person-group person-group-type="author"><name name-style="western"><surname>Yang</surname><given-names>J</given-names> </name></person-group><article-title>A comprehensive guide to US data protection legislation</article-title><source>Safety internal reference</source><access-date>2025-01-20</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.secrss.com/articles/11839">https://www.secrss.com/articles/11839</ext-link></comment></nlm-citation></ref><ref id="ref43"><label>43</label><nlm-citation citation-type="web"><article-title>General data protection regulation (GDPR)</article-title><source>Intersoft Consulting</source><access-date>2025-01-20</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://gdpr-info.eu/">https://gdpr-info.eu/</ext-link></comment></nlm-citation></ref><ref id="ref44"><label>44</label><nlm-citation citation-type="web"><person-group person-group-type="author"><name name-style="western"><surname>Yin</surname><given-names>K</given-names> </name><name name-style="western"><surname>Zhang</surname><given-names>G</given-names> </name><name name-style="western"><surname>Deng</surname><given-names>S</given-names> </name><name name-style="western"><surname>Li</surname><given-names>H</given-names> </name></person-group><article-title>China&#x2019;s final personal information protection compliance audit rules and faqs</article-title><source>Fangda Partners</source><access-date>2026-01-20</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.fangdalaw.com/en/content/details32_9931.html">https://www.fangdalaw.com/en/content/details32_9931.html</ext-link></comment></nlm-citation></ref><ref id="ref45"><label>45</label><nlm-citation citation-type="web"><article-title>Notification regarding the illegal and irregular collection and use of personal information by 129 apps including Keep</article-title><source>Cyberspace Administration of China</source><access-date>2025-01-20</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.cac.gov.cn/2021-06/11/c_1624994586637626.htm">https://www.cac.gov.cn/2021-06/11/c_1624994586637626.htm</ext-link></comment></nlm-citation></ref><ref id="ref46"><label>46</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Jiang</surname><given-names>J</given-names> </name><name name-style="western"><surname>Zheng</surname><given-names>Z</given-names> </name></person-group><article-title>Personal information protection and privacy policy compliance of health code apps in China: scale development and content analysis</article-title><source>JMIR Mhealth Uhealth</source><year>2023</year><month>11</month><day>14</day><volume>11</volume><fpage>e48714</fpage><pub-id pub-id-type="doi">10.2196/48714</pub-id><pub-id pub-id-type="medline">37990813</pub-id></nlm-citation></ref><ref id="ref47"><label>47</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Calzada</surname><given-names>I</given-names> </name></person-group><article-title>Citizens&#x2019; data privacy in China: the state of the art of the Personal Information Protection Law (PIPL)</article-title><source>Smart Cities</source><year>2022</year><volume>5</volume><issue>3</issue><fpage>1129</fpage><lpage>1150</lpage><pub-id pub-id-type="doi">10.3390/smartcities5030057</pub-id></nlm-citation></ref><ref id="ref48"><label>48</label><nlm-citation citation-type="web"><article-title>The 55th statistical report on the internet development in China</article-title><source>CNNIC</source><access-date>2025-09-05</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.100ec.cn/detail--6646318.html">https://www.100ec.cn/detail--6646318.html</ext-link></comment></nlm-citation></ref><ref id="ref49"><label>49</label><nlm-citation citation-type="web"><article-title>Expert interpretation | personal information protection law: establishing a fundamental law for digital society governance and digital economy development</article-title><source>Cyberspace Administration of China</source><access-date>2025-09-05</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.cac.gov.cn/2021-08/25/c_1631491548474109.htm">https://www.cac.gov.cn/2021-08/25/c_1631491548474109.htm</ext-link></comment></nlm-citation></ref><ref id="ref50"><label>50</label><nlm-citation citation-type="report"><article-title>2023 National Internet Users&#x2019; Satisfaction Survey on Cybersecurity: special report on personal information protection and data security</article-title><year>2024</year><access-date>2026-01-20</access-date><publisher-name>Wuzhen Digital Civilization Research Institute</publisher-name><comment><ext-link ext-link-type="uri" xlink:href="https://www.iscn.org.cn/uploadfile/2024/0829/zhuanti4.pdf">https://www.iscn.org.cn/uploadfile/2024/0829/zhuanti4.pdf</ext-link></comment></nlm-citation></ref><ref id="ref51"><label>51</label><nlm-citation citation-type="web"><person-group person-group-type="author"><name name-style="western"><surname>Liu</surname><given-names>Q</given-names> </name></person-group><article-title>On the impact assessment of personal information protection: focusing on Articles 55 and 56 of Personal Information Protection Act</article-title><year>2022</year><access-date>2026-01-28</access-date><volume>30</volume><issue>5</issue><fpage>40</fpage><lpage>50</lpage><comment><ext-link ext-link-type="uri" xlink:href="https://link.oversea.cnki.net/doi/10.13806/j.cnki.issn1008-7095.2022.05.004">https://link.oversea.cnki.net/doi/10.13806/j.cnki.issn1008-7095.2022.05.004</ext-link></comment></nlm-citation></ref><ref id="ref52"><label>52</label><nlm-citation citation-type="web"><person-group person-group-type="author"><name name-style="western"><surname>Jet</surname><given-names>D</given-names> </name><name name-style="western"><surname>Ken</surname><given-names>D</given-names> </name></person-group><article-title>The comparison between China&#x2019;s PIPL and EU&#x2019;s GDPR: practitioners&#x2019; perspective</article-title><source>Mondaq</source><year>2021</year><access-date>2025-03-01</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.mondaq.com/china/data-protection/1122748/the-comparison-between-chinas-pipl-and-eus-gdpr-practitioners-perspective">https://www.mondaq.com/china/data-protection/1122748/the-comparison-between-chinas-pipl-and-eus-gdpr-practitioners-perspective</ext-link></comment></nlm-citation></ref><ref id="ref53"><label>53</label><nlm-citation citation-type="web"><person-group person-group-type="author"><name name-style="western"><surname>Daniel</surname><given-names>S</given-names> </name></person-group><article-title>China&#x2019;s PIPL vs the GDPR: a comparison</article-title><source>TeachPrivacy</source><access-date>2025-03-01</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://teachprivacy.com/chinas-pipl-vs-gdpr-a-comparison">https://teachprivacy.com/chinas-pipl-vs-gdpr-a-comparison</ext-link></comment></nlm-citation></ref><ref id="ref54"><label>54</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Li</surname><given-names>W</given-names> </name><name name-style="western"><surname>Chen</surname><given-names>J</given-names> </name></person-group><article-title>From brussels effect to gravity assists: understanding the evolution of the GDPR-inspired personal information protection law in China</article-title><source>Computer Law &#x0026; Security Review</source><year>2024</year><month>09</month><volume>54</volume><issue>9</issue><fpage>105994</fpage><pub-id pub-id-type="doi">10.1016/j.clsr.2024.105994</pub-id></nlm-citation></ref><ref id="ref55"><label>55</label><nlm-citation citation-type="report"><article-title>Practical Guide to Cybersecurity Standards-Guidelines for the classification and grading of network data [Article in Chinese]</article-title><year>2021</year><access-date>2025-03-01</access-date><publisher-name>National Information Security Standardization Technical Committee</publisher-name><comment><ext-link ext-link-type="uri" xlink:href="https://www.tc260.org.cn/upload/2021-12-31/1640948142376022576.pdf">https://www.tc260.org.cn/upload/2021-12-31/1640948142376022576.pdf</ext-link></comment></nlm-citation></ref><ref id="ref56"><label>56</label><nlm-citation citation-type="web"><article-title>Information security technology - personal information security engineering guidelines</article-title><source>National Public Service Platform for Standards Information</source><access-date>2025-03-01</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://std.samr.gov.cn/gb/search/gbDetailed?id=EB58F4DA9267B2A2E05397BE0A0A7D33">https://std.samr.gov.cn/gb/search/gbDetailed?id=EB58F4DA9267B2A2E05397BE0A0A7D33</ext-link></comment></nlm-citation></ref><ref id="ref57"><label>57</label><nlm-citation citation-type="web"><article-title>Implementation guidelines for notification and consent in information security technology and personal information processing</article-title><source>National Public Service Platform for Standards Information</source><access-date>2025-03-01</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://std.samr.gov.cn/gb/search/gbDetailed?id=FC816D04FFD262EBE05397BE0A0AD5FA">https://std.samr.gov.cn/gb/search/gbDetailed?id=FC816D04FFD262EBE05397BE0A0AD5FA</ext-link></comment></nlm-citation></ref><ref id="ref58"><label>58</label><nlm-citation citation-type="web"><article-title>Information security technology: guidelines for personal information de-identification</article-title><source>National Public Service Platform for Standards Information</source><access-date>2025-03-01</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://std.samr.gov.cn/gb/search/gbDetailed?id=91890A0DA4AB80C6E05397BE0A0A065D">https://std.samr.gov.cn/gb/search/gbDetailed?id=91890A0DA4AB80C6E05397BE0A0A065D</ext-link></comment></nlm-citation></ref><ref id="ref59"><label>59</label><nlm-citation citation-type="web"><article-title>Notification regarding apps that infringe on user rights (Batch 1 of 2023, Batch 27 in total)</article-title><source>Ministry of Industry and Information Technology of the People&#x2019;s Republic of China</source><access-date>2025-03-01</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://wap.miit.gov.cn/jgsj/xgj/gzdt/art/2023/art_f3c61d42b107479abbc0fa115efffc10.html">https://wap.miit.gov.cn/jgsj/xgj/gzdt/art/2023/art_f3c61d42b107479abbc0fa115efffc10.html</ext-link></comment></nlm-citation></ref><ref id="ref60"><label>60</label><nlm-citation citation-type="web"><article-title>Notification Regarding Apps (SDKS) that Infringe on User Rights (Batch 1 of 2024, Batch 36 in Total)</article-title><source>Ministry of Industry and Information Technology of the People&#x2019;s Republic of China</source><access-date>2025-01-22</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://wap.miit.gov.cn/jgsj/xgj/gzdt/art/2024/art_a6f9db30756c4464804355afb64723ff.html">https://wap.miit.gov.cn/jgsj/xgj/gzdt/art/2024/art_a6f9db30756c4464804355afb64723ff.html</ext-link></comment></nlm-citation></ref><ref id="ref61"><label>61</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Liu</surname><given-names>Y li</given-names> </name><name name-style="western"><surname>Huang</surname><given-names>L</given-names> </name><name name-style="western"><surname>Yan</surname><given-names>W</given-names> </name><name name-style="western"><surname>Wang</surname><given-names>X</given-names> </name><name name-style="western"><surname>Zhang</surname><given-names>R</given-names> </name></person-group><article-title>Privacy in AI and the IoT: the privacy concerns of smart speaker users and the Personal Information Protection Law in China</article-title><source>Telecomm Policy</source><year>2022</year><month>08</month><volume>46</volume><issue>7</issue><fpage>102334</fpage><pub-id pub-id-type="doi">10.1016/j.telpol.2022.102334</pub-id></nlm-citation></ref><ref id="ref62"><label>62</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Tang</surname><given-names>Z</given-names> </name><name name-style="western"><surname>hu</surname><given-names>Y (Jeffrey</given-names> </name><name name-style="western"><surname>smith</surname><given-names>MD</given-names> </name></person-group><article-title>Gaining trust through online privacy protection: self-regulation, mandatory standards, or Caveat Emptor</article-title><source>Journal of Management Information Systems</source><year>2008</year><month>04</month><volume>24</volume><issue>4</issue><fpage>153</fpage><lpage>173</lpage><pub-id pub-id-type="doi">10.2753/MIS0742-1222240406</pub-id></nlm-citation></ref><ref id="ref63"><label>63</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Parker</surname><given-names>L</given-names> </name><name name-style="western"><surname>Halter</surname><given-names>V</given-names> </name><name name-style="western"><surname>Karliychuk</surname><given-names>T</given-names> </name><name name-style="western"><surname>Grundy</surname><given-names>Q</given-names> </name></person-group><article-title>How private is your mental health app data? An empirical study of mental health app privacy policies and practices</article-title><source>Int J Law Psychiatry</source><year>2019</year><month>05</month><volume>64</volume><fpage>198</fpage><lpage>204</lpage><pub-id pub-id-type="doi">10.1016/j.ijlp.2019.04.002</pub-id></nlm-citation></ref><ref id="ref64"><label>64</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Grundy</surname><given-names>Q</given-names> </name><name name-style="western"><surname>Chiu</surname><given-names>K</given-names> </name><name name-style="western"><surname>Held</surname><given-names>F</given-names> </name><name name-style="western"><surname>Continella</surname><given-names>A</given-names> </name><name name-style="western"><surname>Bero</surname><given-names>L</given-names> </name><name name-style="western"><surname>Holz</surname><given-names>R</given-names> </name></person-group><article-title>Data sharing practices of medicines related apps and the mobile ecosystem: traffic, content, and network analysis</article-title><source>BMJ</source><year>2019</year><month>03</month><day>20</day><volume>364</volume><fpage>l920</fpage><pub-id pub-id-type="doi">10.1136/bmj.l920</pub-id><pub-id pub-id-type="medline">30894349</pub-id></nlm-citation></ref><ref id="ref65"><label>65</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Alfawzan</surname><given-names>N</given-names> </name><name name-style="western"><surname>Christen</surname><given-names>M</given-names> </name><name name-style="western"><surname>Spitale</surname><given-names>G</given-names> </name><name name-style="western"><surname>Biller-Andorno</surname><given-names>N</given-names> </name></person-group><article-title>Privacy, data sharing, and data security policies of women&#x2019;s mHealth apps: scoping review and content analysis</article-title><source>JMIR Mhealth Uhealth</source><year>2022</year><month>05</month><day>6</day><volume>10</volume><issue>5</issue><fpage>e33735</fpage><pub-id pub-id-type="doi">10.2196/33735</pub-id><pub-id pub-id-type="medline">35522465</pub-id></nlm-citation></ref><ref id="ref66"><label>66</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Shipp</surname><given-names>L</given-names> </name><name name-style="western"><surname>Blasco</surname><given-names>J</given-names> </name></person-group><article-title>How private is your period?: a systematic analysis of menstrual app privacy policies</article-title><source>Proceedings on Privacy Enhancing Technologies</source><year>2020</year><month>10</month><day>1</day><volume>2020</volume><issue>4</issue><fpage>491</fpage><lpage>510</lpage><pub-id pub-id-type="doi">10.2478/popets-2020-0083</pub-id></nlm-citation></ref><ref id="ref67"><label>67</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Shi</surname><given-names>X</given-names> </name></person-group><article-title>Reducing privacy risks of China&#x2019;s healthcare big data through the policy framework</article-title><source>Front Public Health</source><year>2024</year><volume>12</volume><fpage>1414076</fpage><pub-id pub-id-type="doi">10.3389/fpubh.2024.1414076</pub-id><pub-id pub-id-type="medline">39022418</pub-id></nlm-citation></ref><ref id="ref68"><label>68</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Sun</surname><given-names>L</given-names> </name><name name-style="western"><surname>Buijsen</surname><given-names>M</given-names> </name></person-group><article-title>Mobile health in China: does it meet availability, accessibility, acceptability and quality standards?</article-title><source>Health Policy Technol</source><year>2022</year><month>09</month><volume>11</volume><issue>3</issue><fpage>100660</fpage><pub-id pub-id-type="doi">10.1016/j.hlpt.2022.100660</pub-id></nlm-citation></ref><ref id="ref69"><label>69</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Liu</surname><given-names>K</given-names> </name><name name-style="western"><surname>Xu</surname><given-names>G</given-names> </name><name name-style="western"><surname>Zhang</surname><given-names>X</given-names> </name><name name-style="western"><surname>Xu</surname><given-names>G</given-names> </name><name name-style="western"><surname>Zhao</surname><given-names>Z</given-names> </name></person-group><article-title>Evaluating the privacy policy of Android apps: a privacy policy compliance study for popular apps in China and Europe</article-title><source>Sci Program</source><year>2022</year><month>08</month><day>23</day><volume>2022</volume><fpage>1</fpage><lpage>15</lpage><pub-id pub-id-type="doi">10.1155/2022/2508690</pub-id></nlm-citation></ref><ref id="ref70"><label>70</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Shang</surname><given-names>J</given-names> </name><name name-style="western"><surname>Wei</surname><given-names>S</given-names> </name><name name-style="western"><surname>Jin</surname><given-names>J</given-names> </name><name name-style="western"><surname>Zhang</surname><given-names>P</given-names> </name></person-group><article-title>Mental health apps in China: analysis and quality assessment</article-title><source>JMIR Mhealth Uhealth</source><year>2019</year><month>11</month><day>7</day><volume>7</volume><issue>11</issue><fpage>e13236</fpage><pub-id pub-id-type="doi">10.2196/13236</pub-id><pub-id pub-id-type="medline">31697245</pub-id></nlm-citation></ref><ref id="ref71"><label>71</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Zhang</surname><given-names>X</given-names> </name><name name-style="western"><surname>Lewis</surname><given-names>S</given-names> </name><name name-style="western"><surname>Chen</surname><given-names>X</given-names> </name><name name-style="western"><surname>Berry</surname><given-names>N</given-names> </name><name name-style="western"><surname>Bucci</surname><given-names>S</given-names> </name></person-group><article-title>Technology use and attitudes towards digital mental health in people with severe mental health problems: a survey study in China</article-title><source>Front Psychiatry</source><year>2023</year><volume>14</volume><fpage>1261795</fpage><pub-id pub-id-type="doi">10.3389/fpsyt.2023.1261795</pub-id><pub-id pub-id-type="medline">38076680</pub-id></nlm-citation></ref><ref id="ref72"><label>72</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Wang</surname><given-names>Y</given-names> </name><name name-style="western"><surname>Liu</surname><given-names>Y</given-names> </name><name name-style="western"><surname>Shi</surname><given-names>Y</given-names> </name><name name-style="western"><surname>Yu</surname><given-names>Y</given-names> </name><name name-style="western"><surname>Yang</surname><given-names>J</given-names> </name></person-group><article-title>User perceptions of virtual hospital apps in China: systematic search</article-title><source>JMIR Mhealth Uhealth</source><year>2020</year><month>08</month><day>12</day><volume>8</volume><issue>8</issue><fpage>e19487</fpage><pub-id pub-id-type="doi">10.2196/19487</pub-id><pub-id pub-id-type="medline">32687480</pub-id></nlm-citation></ref><ref id="ref73"><label>73</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Lian</surname><given-names>L</given-names> </name><name name-style="western"><surname>Feng</surname><given-names>Y</given-names> </name><name name-style="western"><surname>Zhao</surname><given-names>Y</given-names> </name><name name-style="western"><surname>Lei</surname><given-names>L</given-names> </name><name name-style="western"><surname>Daying</surname><given-names>F</given-names> </name><name name-style="western"><surname>Xiaohua</surname><given-names>W</given-names> </name></person-group><article-title>Ethical dilemmas and solutions for patient privacy protection in internet hospital</article-title><source>Medicine &#x0026; Philosophy</source><year>2025</year><volume>46</volume><issue>14</issue><fpage>22</fpage><lpage>27</lpage><pub-id pub-id-type="doi">10.12014/j.issn.1002-0772.2025.14.05</pub-id></nlm-citation></ref><ref id="ref74"><label>74</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Zhang</surname><given-names>M</given-names> </name><name name-style="western"><surname>Chow</surname><given-names>A</given-names> </name><name name-style="western"><surname>Smith</surname><given-names>H</given-names> </name></person-group><article-title>COVID-19 contact-tracing apps: analysis of the readability of privacy policies</article-title><source>J Med Internet Res</source><year>2020</year><month>12</month><day>3</day><volume>22</volume><issue>12</issue><fpage>e21572</fpage><pub-id pub-id-type="doi">10.2196/21572</pub-id><pub-id pub-id-type="medline">33170798</pub-id></nlm-citation></ref><ref id="ref75"><label>75</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Shen</surname><given-names>C</given-names> </name><name name-style="western"><surname>Jiang</surname><given-names>B</given-names> </name><name name-style="western"><surname>Yang</surname><given-names>Q</given-names> </name><etal/></person-group><article-title>Mobile apps for drug-drug interaction checks in Chinese app stores: systematic review and content analysis</article-title><source>JMIR Mhealth Uhealth</source><year>2021</year><month>06</month><day>15</day><volume>9</volume><issue>6</issue><fpage>e26262</fpage><pub-id pub-id-type="doi">10.2196/26262</pub-id><pub-id pub-id-type="medline">33962910</pub-id></nlm-citation></ref><ref id="ref76"><label>76</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Liu</surname><given-names>XH</given-names> </name><name name-style="western"><surname>Jin</surname><given-names>F</given-names> </name><name name-style="western"><surname>Hsu</surname><given-names>J</given-names> </name><name name-style="western"><surname>Li</surname><given-names>DN</given-names> </name><name name-style="western"><surname>Chen</surname><given-names>W</given-names> </name></person-group><article-title>Comparing smartphone apps for traditional Chinese medicine and modern medicine in China: systematic search and content analysis</article-title><source>JMIR Mhealth Uhealth</source><year>2021</year><month>03</month><day>24</day><volume>9</volume><issue>3</issue><fpage>e27406</fpage><pub-id pub-id-type="doi">10.2196/27406</pub-id><pub-id pub-id-type="medline">33759786</pub-id></nlm-citation></ref><ref id="ref77"><label>77</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Meishan</surname><given-names>Z</given-names> </name><name name-style="western"><surname>Fengjuan</surname><given-names>W</given-names> </name></person-group><article-title>The privacy protection dilemmas and strategies for chronic disease big data management</article-title><source>Medicine &#x0026; Philosophy</source><year>2024</year><volume>45</volume><issue>5</issue><fpage>21</fpage><lpage>26</lpage><pub-id pub-id-type="doi">10.12014/j.issn.1002-0772.2024.05.05</pub-id></nlm-citation></ref><ref id="ref78"><label>78</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Nissenbaum</surname><given-names>H</given-names> </name></person-group><article-title>Privacy as contextual integrity [Symposium]</article-title><source>Wash L Rev</source><year>2004</year><access-date>2026-01-18</access-date><volume>79</volume><issue>1</issue><fpage>119</fpage><comment><ext-link ext-link-type="uri" xlink:href="https://digitalcommons.law.uw.edu/wlr/vol79/iss1/10">https://digitalcommons.law.uw.edu/wlr/vol79/iss1/10</ext-link></comment></nlm-citation></ref><ref id="ref79"><label>79</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Lyu</surname><given-names>X</given-names> </name><name name-style="western"><surname>Liu</surname><given-names>X</given-names> </name><name name-style="western"><surname>Yang</surname><given-names>T</given-names> </name><name name-style="western"><surname>Fu</surname><given-names>C</given-names> </name></person-group><article-title>Intervention strategies for health rumors: an overview based on the information lifecycle theory</article-title><source>Advances in Psychological Science</source><year>2024</year><volume>32</volume><issue>4</issue><fpage>664</fpage><pub-id pub-id-type="doi">10.3724/SP.J.1042.2024.00664</pub-id></nlm-citation></ref><ref id="ref80"><label>80</label><nlm-citation citation-type="confproc"><person-group person-group-type="author"><name name-style="western"><surname>Katherine</surname><given-names>H</given-names> </name></person-group><article-title>Websites&#x2019; global privacy control compliance at scale and over time</article-title><access-date>2025-08-22</access-date><conf-name>Proceedings of the 34th USENIX Security Symposium</conf-name><conf-date>Aug 13-15, 2025</conf-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.usenix.org/system/files/usenixsecurity25-hausladen.pdf">https://www.usenix.org/system/files/usenixsecurity25-hausladen.pdf</ext-link></comment></nlm-citation></ref><ref id="ref81"><label>81</label><nlm-citation citation-type="web"><article-title>Notice from the Ministry of Industry and Information Technology on further enhancing mobile internet application service capabilities</article-title><source>Ministry of Industry and Information Technology</source><access-date>2025-08-01</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.gov.cn/zhengce/zhengceku/2023-03/02/content_5744106.htm">https://www.gov.cn/zhengce/zhengceku/2023-03/02/content_5744106.htm</ext-link></comment></nlm-citation></ref><ref id="ref82"><label>82</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Chen</surname><given-names>M</given-names> </name><name name-style="western"><surname>Ding</surname><given-names>F</given-names> </name></person-group><article-title>Research on the construction of a compliance evaluation index system for government website privacy policies</article-title><source>J Intell</source><year>2025</year><volume>44</volume><issue>3</issue><fpage>198</fpage><lpage>206</lpage><pub-id pub-id-type="doi">10.3969/j.issn.1002-1965.2025.03.024</pub-id></nlm-citation></ref><ref id="ref83"><label>83</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Jing</surname><given-names>Y</given-names> </name><name name-style="western"><surname>Jiejie</surname><given-names>Z</given-names> </name><name name-style="western"><surname>Kailiang</surname><given-names>Z</given-names> </name></person-group><article-title>Evaluation index system construction and empirical study of user privacy literacy on open government data platform</article-title><source>Library Work and Study</source><year>2024</year><volume>1</volume><issue>12</issue><fpage>17</fpage><lpage>26</lpage><pub-id pub-id-type="doi">10.16384/j.cnki.lwas.2024.12.012</pub-id></nlm-citation></ref><ref id="ref84"><label>84</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Hendricks-Sturrup</surname><given-names>R</given-names> </name><name name-style="western"><surname>Lu</surname><given-names>CY</given-names> </name></person-group><article-title>An assessment of perspectives and concerns among research participants of childbearing age regarding the health-relatedness of data, online data privacy, and donating data to researchers: survey study</article-title><source>J Med Internet Res</source><year>2023</year><month>03</month><day>10</day><volume>25</volume><fpage>e41937</fpage><pub-id pub-id-type="doi">10.2196/41937</pub-id><pub-id pub-id-type="medline">36897637</pub-id></nlm-citation></ref><ref id="ref85"><label>85</label><nlm-citation citation-type="web"><article-title>Civil Code of the People&#x2019;s Republic of China</article-title><source>Trans-lex</source><access-date>2025-03-01</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.trans-lex.org/601705/_/civil-code-of-the-peoples-republic-of-china-/">https://www.trans-lex.org/601705/_/civil-code-of-the-peoples-republic-of-china-/</ext-link></comment></nlm-citation></ref><ref id="ref86"><label>86</label><nlm-citation citation-type="web"><article-title>Cybersecurity law of the People&#x2019;s Republic of China</article-title><source>China Securities Regulatory Commission</source><access-date>2025-03-01</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.dataguidance.com/sites/default/files/en_cybersecurity_law_of_the_peoples_republic_of_china_1.pdf">https://www.dataguidance.com/sites/default/files/en_cybersecurity_law_of_the_peoples_republic_of_china_1.pdf</ext-link></comment></nlm-citation></ref><ref id="ref87"><label>87</label><nlm-citation citation-type="web"><article-title>Law of the people&#x2019;s republic of China on basic medical and health care and the promotion of health</article-title><source>The National People&#x2019;s Congress of the People&#x2019;s Republic of China</source><access-date>2025-03-01</access-date><comment><ext-link ext-link-type="uri" xlink:href="http://www.npc.gov.cn/englishnpc/c2759/c23934/202012/t20201225_384343.html">http://www.npc.gov.cn/englishnpc/c2759/c23934/202012/t20201225_384343.html</ext-link></comment></nlm-citation></ref><ref id="ref88"><label>88</label><nlm-citation citation-type="report"><article-title>Australian mHealth apps assessment framework</article-title><year>2024</year><access-date>2025-03-01</access-date><publisher-name>Australasian Institute of Digital Health</publisher-name><comment><ext-link ext-link-type="uri" xlink:href="https://digitalhealth.org.au/wp-content/uploads/2024/06/AIDH_mHealth-Framework-Options.pdf">https://digitalhealth.org.au/wp-content/uploads/2024/06/AIDH_mHealth-Framework-Options.pdf</ext-link></comment></nlm-citation></ref><ref id="ref89"><label>89</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Ge</surname><given-names>F</given-names> </name><name name-style="western"><surname>Qian</surname><given-names>H</given-names> </name><name name-style="western"><surname>Lei</surname><given-names>J</given-names> </name><etal/></person-group><article-title>Experiences and challenges of emerging online health services combating COVID-19 in China: retrospective, cross-sectional study of internet hospitals</article-title><source>JMIR Med Inform</source><year>2022</year><month>06</month><day>1</day><volume>10</volume><issue>6</issue><fpage>e37042</fpage><pub-id pub-id-type="doi">10.2196/37042</pub-id><pub-id pub-id-type="medline">35500013</pub-id></nlm-citation></ref><ref id="ref90"><label>90</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Jiang</surname><given-names>X</given-names> </name><name name-style="western"><surname>Xie</surname><given-names>H</given-names> </name><name name-style="western"><surname>Tang</surname><given-names>R</given-names> </name><etal/></person-group><article-title>Characteristics of online health care services from China&#x2019;s largest online medical platform: cross-sectional survey study</article-title><source>J Med Internet Res</source><year>2021</year><month>04</month><day>15</day><volume>23</volume><issue>4</issue><fpage>e25817</fpage><pub-id pub-id-type="doi">10.2196/25817</pub-id><pub-id pub-id-type="medline">33729985</pub-id></nlm-citation></ref><ref id="ref91"><label>91</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Theodos</surname><given-names>K</given-names> </name><name name-style="western"><surname>Sittig</surname><given-names>S</given-names> </name></person-group><article-title>Health information privacy laws in the digital age: HIPAA doesn&#x2019;t apply</article-title><source>Perspect Health Inf Manag</source><year>2021</year><volume>18</volume><issue>Winter</issue><fpage>1l</fpage><pub-id pub-id-type="medline">33633522</pub-id></nlm-citation></ref><ref id="ref92"><label>92</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Shahid</surname><given-names>J</given-names> </name><name name-style="western"><surname>Ahmad</surname><given-names>R</given-names> </name><name name-style="western"><surname>Kiani</surname><given-names>AK</given-names> </name><name name-style="western"><surname>Ahmad</surname><given-names>T</given-names> </name><name name-style="western"><surname>Saeed</surname><given-names>S</given-names> </name><name name-style="western"><surname>Almuhaideb</surname><given-names>AM</given-names> </name></person-group><article-title>Data protection and privacy of the internet of healthcare things (IoHTs)</article-title><source>Appl Sci (Basel)</source><year>2022</year><volume>12</volume><issue>4</issue><fpage>1927</fpage><pub-id pub-id-type="doi">10.3390/app12041927</pub-id></nlm-citation></ref><ref id="ref93"><label>93</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Zhou</surname><given-names>SL</given-names> </name><name name-style="western"><surname>Jia</surname><given-names>X</given-names> </name><name name-style="western"><surname>Skinner</surname><given-names>SP</given-names> </name><name name-style="western"><surname>Yang</surname><given-names>W</given-names> </name><name name-style="western"><surname>Claude</surname><given-names>I</given-names> </name></person-group><article-title>Lessons on mobile apps for COVID-19 from China</article-title><source>J Saf Sci Resil</source><year>2021</year><month>06</month><volume>2</volume><issue>2</issue><fpage>40</fpage><lpage>49</lpage><pub-id pub-id-type="doi">10.1016/j.jnlssr.2021.04.002</pub-id><pub-id pub-id-type="medline">40477492</pub-id></nlm-citation></ref><ref id="ref94"><label>94</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Liang</surname><given-names>F</given-names> </name></person-group><article-title>COVID-19 and health code: how digital platforms tackle the pandemic in China</article-title><source>Soc Media Soc</source><year>2020</year><month>07</month><volume>6</volume><issue>3</issue><fpage>2056305120947657</fpage><pub-id pub-id-type="doi">10.1177/2056305120947657</pub-id><pub-id pub-id-type="medline">34192023</pub-id></nlm-citation></ref><ref id="ref95"><label>95</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Cong</surname><given-names>W</given-names> </name></person-group><article-title>From pandemic control to data-driven governance: the case of China&#x2019;s health code</article-title><source>Front Polit Sci</source><year>2021</year><month>04</month><volume>3</volume><pub-id pub-id-type="doi">10.3389/fpos.2021.627959</pub-id></nlm-citation></ref><ref id="ref96"><label>96</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Alamri</surname><given-names>H</given-names> </name><name name-style="western"><surname>Maple</surname><given-names>C</given-names> </name><name name-style="western"><surname>Mohamad</surname><given-names>S</given-names> </name><name name-style="western"><surname>Epiphaniou</surname><given-names>G</given-names> </name></person-group><article-title>Do the right thing: a privacy policy adherence analysis of over two million apps in Apple iOS App Store</article-title><source>Sensors (Basel)</source><year>2022</year><month>11</month><day>19</day><volume>22</volume><issue>22</issue><fpage>8964</fpage><pub-id pub-id-type="doi">10.3390/s22228964</pub-id><pub-id pub-id-type="medline">36433560</pub-id></nlm-citation></ref></ref-list><app-group><supplementary-material id="app1"><label>Multimedia Appendix 1</label><p>Excluded samples.</p><media xlink:href="mhealth_v14i1e73651_app1.xlsx" xlink:title="XLSX File, 33 KB"/></supplementary-material><supplementary-material id="app2"><label>Multimedia Appendix 2</label><p>The characteristics of the valid sports and health apps.</p><media xlink:href="mhealth_v14i1e73651_app2.xlsx" xlink:title="XLSX File, 24 KB"/></supplementary-material><supplementary-material id="app3"><label>Multimedia Appendix 3</label><p>Names, compliance indicators, and scores of sports and health apps.</p><media xlink:href="mhealth_v14i1e73651_app3.xlsx" xlink:title="XLSX File, 75 KB"/></supplementary-material><supplementary-material id="app4"><label>Checklist 1</label><p>PRISMA-LSR checklist.</p><media xlink:href="mhealth_v14i1e73651_app4.pdf" xlink:title="PDF File, 105 KB"/></supplementary-material></app-group></back></article>