"Your Doctor is Spying on You": An Analysis of Data Practices in Mobile Healthcare Applications
Luke Stevenson, Sanchari Das
Audit your healthcare app's permission stack against this three-tool methodology. If you're requesting location, camera, or contacts, your privacy policy must explicitly justify each permission with a clinical use case. Assume regulators will adopt this forensic standard.
mHealth apps collect sensitive patient data but operate in a regulatory gray zone. 26.1% request fine-grained location without disclosure, creating systemic privacy exposure.
Method: Multi-tool forensic audit of 272 Android mHealth apps using MobSF, RiskInDroid, and OWASP Mobile Audit revealed that 26.1% request fine-grained location permissions without disclosure in privacy policies. The study combined permission forensics, static vulnerability analysis, and user review mining to expose systemic weaknesses in apps that promise patient-provider interaction but deliver surveillance infrastructure.
Caveats: Android-only analysis; iOS permission model differs. Static analysis can't catch runtime data exfiltration or third-party SDK behavior.
Reflections: How do iOS mHealth apps compare in permission overreach and disclosure gaps? · What percentage of location data is actually used for clinical purposes versus marketing? · Can automated policy-permission alignment checks be integrated into app store review processes?