Privacy Policy

Our Privacy Commitment

Health.md was built from the ground up with one core principle: your health data is yours alone. This privacy policy explains what data we collect (none), how Health.md handles Apple Health exports locally, and what happens when you choose destinations such as iCloud Drive, third-party file providers, or the Mac companion.

Data Collection

We do not collect any personal data, health data, or usage data. Health.md is a local-first application for Apple devices. Specifically:

• No account creation or registration required
• No email addresses, names, or contact information collected
• No health data uploaded to a Health.md server or Health.md cloud service
• No usage analytics or telemetry tracked by Health.md
• No in-app crash reporting SDK or analytics SDK
• No advertising identifiers or tracking pixels

How the App Works

Health.md reads your Apple Health data locally using HealthKit APIs provided by Apple. The iPhone remains the source for HealthKit exports; the Mac app can act as a local destination when you enable Mac sync. This data:

• Remains in Apple's HealthKit database unless you explicitly export it
• Is processed on your Apple device for the export you request
• Is exported only to destinations you choose, such as Files, iCloud Drive, third-party file providers, Obsidian vaults, or a local-network Mac destination
• May leave a device only through destinations you configure, such as iCloud Drive, Dropbox, another file provider, or optional local-network Mac sync

Data Storage

Data processed by Health.md is stored on your Apple devices and in storage locations you control:

• Source Data: Apple Health data remains in Apple's HealthKit database on your device
• Exported Data: Markdown, Obsidian, CSV, and JSON files are written to the folder or destination you select
• File Provider Sync: If your chosen folder is backed by iCloud Drive, Dropbox, Google Drive, Working Copy, or another file provider, that provider handles sync under its own terms
• App Preferences: Your app settings (sync schedule, folder selection, templates, and unlock state) are stored locally using Apple platform storage and StoreKit

We do not have access to any of this data. There are no Health.md health-data servers, databases, or cloud storage systems.

Third-Party Services

Health.md does not include advertising SDKs, analytics SDKs, or third-party tracking. The app interacts with Apple system services and destinations you choose:

• Apple HealthKit: To read your health data locally on your device (with your explicit permission)
• Apple Files and File Providers: To write exported files to your chosen folder location
• StoreKit and the App Store: To purchase or restore the one-time Full Access unlock
• Local Network / Nearby Connectivity: To discover and write to the optional Mac destination when you enable Mac sync

Network Activity

Health.md does not send your health data to Health.md servers. Network activity is limited to features you initiate or Apple system services, such as:

• StoreKit and App Store purchase or restore flows for Full Access
• Local-network discovery and transfer when you enable the Mac destination
• iCloud Drive or third-party file-provider sync if you choose those folders for exported files
• App updates delivered by the App Store

Permissions

Health.md may request the following Apple platform permissions:

• Health Data (HealthKit): To read your Apple Health data and export it to selected formats. You can grant or revoke specific health data categories in iOS Settings → Health → Data Access & Devices → Health.md.
• File System Access: To write exported files to your chosen file system location. You select this location using Apple's file picker.
• Local Network: To discover and send export jobs to the Mac companion when you enable Mac sync.
• Notifications: To alert you when a scheduled export needs manual action or completes.

These permissions are only used for their stated purposes and can be revoked at any time in iOS Settings.

Children's Privacy

Health.md does not collect any data from users of any age. The app complies with COPPA (Children's Online Privacy Protection Act) and similar regulations by design, as we do not collect personal information.

Data Security

Because Health.md does not store your health data on our servers, your data security depends on your Apple devices and the destinations you choose:

• Apple HealthKit data is protected by Apple's device security and HealthKit permissions
• Exported files are protected by the file system, vault, cloud drive, or Mac folder where you store them
• We recommend using device passcodes, keeping iOS/iPadOS/macOS updated, and reviewing permissions for any sync provider you use

Your Rights

Because we don't collect any data, there is no data for us to access, modify, or delete. You control the source permissions and exported files:

• Access: Apple Health data is managed through Apple Health settings; exported files are in the destination folders you chose
• Deletion: Delete the app to remove app settings, or delete exported files from your chosen folders and sync providers
• Portability: Your exported Markdown, Obsidian, CSV, and JSON files are portable and can be used outside Health.md

Changes to This Policy

If we ever change our privacy practices in a meaningful way, we will update this policy and notify users through an app update or website update. The "Last updated" date at the top of this policy reflects when changes were made.

Open Source

Portions of Health.md's data processing logic may be available for review as open source or in documentation, allowing users to audit how exports are shaped. Check the documentation or project repository for current source availability.

Contact

If you have questions about this privacy policy or how health.md works, you can contact us at:

Email: [email protected]
Website: https://isolated.tech

Jurisdiction

This privacy policy is governed by the laws of the jurisdiction where health.md is operated. However, since we collect no data, most privacy regulations (GDPR, CCPA, etc.) do not apply as there is no personal data to regulate.