Objective Digital technology has the potential to support or infringe upon human rights. The ubiquity of mobile technology in low- and middle-income countries (LMICs) presents an opportunity to leverage mobile health (mHealth) interventions to reach remote populations and enable them to exercise human rights. Yet, simultaneously, the proliferation of mHealth results in expanding sensitive datasets and data processing, which risks endangering rights. The promotion of digital health often centers on its role in enhancing rights and health equity, particularly in LMICs. However, the interplay between mHealth in LMICs and digital rights is underexplored. The objective of this scoping review is to bridge this gap and identify digital rights topics in the 2022 literature on mHealth in Southeast Asian LMICs. Furthermore, it aims to highlight the importance of patient empowerment and data protection in mHealth and related policies in LMICs. Methods This review follows Arksey and O’Malley's framework for scoping reviews. Search results are reported using the PRISMA-ScR (Preferred Reporting Items for Systematic Reviews and Meta-Analyses Extension for Scoping Reviews) checklist. Frequency and content analyses were applied to summarize and interpret the data. Results Three key findings emerge from this review. First, the digital rights topics covered in the literature are sparse, sporadic, and unsystematic. Second, despite significant concerns surrounding data privacy in Southeast Asian LMICs, no article in this review explores challenges to data privacy. Third, all included articles state or allude to the role of mHealth in advancing the right to health. Conclusions Engagement in digital rights topics in the literature on mHealth in Southeast Asian mHealth is limited and irregular. Researchers and practitioners lack guidance, collective understanding, and shared language to proactively examine and communicate digital rights topics in mHealth in LMIC research. A systematic method for engaging with digital rights in this context is required going forward.