Health data stays trapped.
Useful records become hard to reuse when export controls are broad or unclear.
Independent product · iOS
Move the Apple Health data you choose, on your terms.
Open on the App Store ↗
Information flow, interface, and release story
Apple Health export utility
Version 1.0
With explicit data choices
Project value
Let users choose data before the app requests access.
Support a local file and a personal server destination.
Keep sensitive transfer choices visible and reversible.
Useful records become hard to reuse when export controls are broad or unclear.
A health utility can request more data or storage than the task requires.
Place selection, permission, destination, and file review in a clear order.
Design decisions
Users choose the Health data types they need before the related read permission appears.
Connect each permission request to a visible purpose.
The product creates a ZIP file or sends JSON batches to the user’s own HTTPS webhook.
Support a simple file flow and a repeatable personal sync flow.
A documented JSON schema, manifest, and sample batches make the output easier to understand.
Reduce uncertainty before the data enters another system.
The app has no account, analytics, ads, tracking, or bundled backend. Users can review and delete stored ZIP files.
Keep control with the person who owns the data.
Product proof

The range, selected data, access, and file action share one screen.

A personal webhook stays separate from local file export.

Search and selection happen before Health access.
Result
Health Exporter launched for iPhone and iPad on August 4, 2026.
The public product states no accounts, analytics, ads, tracking, or bundled backend.
Track completed exports, retry recovery, deleted files, and webhook errors. Public results are not yet available.
Released productOpen Health Exporter on the App Store ↗