Esme my Multiple Sclerosis app privacy label
Aptar Digital Health · Medical · Android
Data last synced September 14, 2026
Esme my Multiple Sclerosis app collects health info, fitness info, files and docs, and shares some of this with third parties.
✓ Shares with third parties✓ Encrypts data in transit✓ Supports deletion requests
Data collected
Health info
App functionality, Personalization
Fitness info
App functionality, Personalization
Files and docs
App functionality
Photos
App functionality
Device or other IDs
Advertising or marketing
Name
App functionality, Account management
Email address
App functionality, Account management
Other info
App functionality, Personalization, Account management
Data shared
Device or other IDs
Advertising or marketing
Email address
Developer communications
Third parties potentially receiving data (unverified)
Extracted automatically from the developer's own privacy policy text -- not independently verified by Nomatra.
Apple Unverified
“Sign in with Apple, Google, or Facebook”
Google Unverified
“Sign in with Apple, Google, or Facebook”
Facebook Unverified
“Sign in with Apple, Google, or Facebook”
Apple Unverified
“Apple, Google, and Facebook handle information in connection with your sign-in — including the fact that you have signed in to this app — under their own privacy policies”
Google Unverified
“Apple, Google, and Facebook handle information in connection with your sign-in — including the fact that you have signed in to this app — under their own privacy policies”
Facebook Unverified
“Apple, Google, and Facebook handle information in connection with your sign-in — including the fact that you have signed in to this app — under their own privacy policies”
Apple Health Unverified
“Apple Health or Google Health app interactions.”
Google Health Unverified
“Apple Health or Google Health app interactions.”
WhatsApp Unverified
“e-mail, text message or WhatsApp message”
More medical apps
About this data: sourced from Android's official privacy-label disclosures, last synced 2026-09-14. Third-party sharing claims are extracted from the developer's own privacy policy and are unverified.