Local Bluetooth use and optional health-cloud storage are separate. Cloud health uploads require authenticated access and explicit consent. Revoking consent stops future uploads; previously stored cloud records remain until you delete your account.
Name, date of birth and health readings are encrypted at rest by the application. Session and one-time tester codes are stored as hashes. Other users cannot read your records through the API.
Use the account screen to sign out, revoke consent or delete your cloud account and active records. Local cached records can be erased separately from the Android app. Administrator backups may retain encrypted records until their documented retention period; account deletion is not a promise of immediate erasure from historical backups.
SMS login is unavailable until a legitimate provider is configured and tested. No health data is sent to a generative AI service. Watch readings are informational and are not a medical assessment.
This internal application still requires physical smartwatch compatibility testing.
Back