Your data, in your care
Privacy policy
Effective October 18, 2026
HealthMule reads the Apple Health metrics you enable and exports daily JSON directly to your own Google Drive. We do not operate a backend that receives your health records. The app has no ads, analytics, or telemetry.
Who provides HealthMule
HealthMule is provided by undefined is not a function LLC. For privacy questions or support, email dev@uinaf.dev.
Apple Health access
With your permission, HealthMule reads only the supported types you enable: body mass, steps, active energy, resting energy, resting heart rate, heart-rate variability SDNN, VO₂ max, sleep, and workouts. It aggregates them into daily records. Exported records can also include workout details, source device names, and sample counts.
HealthKit access is read-only. HealthMule does not write to or change your Apple Health records. It does not export raw routes, raw heart-rate samples, or unrelated medical records. You can change Health permissions in Apple’s Health app or Settings.
Google sign-in and Drive
Google Sign-In authorizes access to the Google account you choose. HealthMule requests the drive.file permission to create and manage files it creates or files you explicitly share with it. It does not request unrestricted access to your Drive.
Daily health records and a manifest are sent from your iPhone to the Apple Health Sync folder in your Google Drive. Google stores those files under your account. This is remote storage: your exports leave the device and are stored by Google, even though HealthMule’s developer does not receive a copy. Your Google account settings, sharing choices, and Google’s privacy policy apply to that service.
Google Sign-In manages authentication credentials in the iPhone’s Keychain. HealthMule keeps account-specific folder and file identifiers locally so it can find and update the same exports. It does not send those credentials or identifiers to a developer server.
Local storage and the Watch
The iPhone stores prepared daily records, sync state, and HealthKit query state locally. Health-related staging and query files use device file protection and are excluded from device backups. Preferences and account-specific Drive metadata are kept locally.
The Apple Watch companion receives sanitized sync status, timestamps, and queue counts from your iPhone. It does not receive health values, Google credentials, or account details.
Diagnostics
HealthMule keeps bounded diagnostics and sync-activity receipts. These do not include health values, exported record bodies, raw HealthKit metadata, OAuth tokens, or account details. Diagnostics leave the app only if you choose to share them. If you email support, we receive the message and any information you include; please do not send health records or credentials.
Your choices and deletion
- Disable individual metrics in HealthMule to stop including them in future exports, or revoke Health access through Apple’s controls.
- Disconnect Google in HealthMule, or revoke access in your Google account, to stop future authorized Drive sync.
- Disconnecting and resetting local sync state do not delete existing Drive exports. Delete unwanted files in Google Drive yourself, including any copies you have shared or downloaded.
- Removing the app removes its local files, but Google sign-in credentials may remain in iOS Keychain and be restored after reinstalling. Disconnect Google before removing the app, or revoke access through your Google account. Uninstalling does not delete your Google Drive files.
Previously exported files can remain in Drive when you change selected metrics or the export date range. Review and remove older files if you no longer want them stored there.
This website
This website has no analytics, advertising, tracking scripts, cookies, or forms added by HealthMule. Like other websites, its hosting provider processes connection information such as IP addresses and request details to serve pages and maintain security. Links to Google, GitHub, or other websites follow those services’ own policies.
Policy updates
We will publish changes on this page and update the effective date. Material changes to the app’s data handling will be reflected here.