Privacy Policy

How Health Exporter & Shortcuts handles your data

This privacy policy applies to the Health Exporter & Shortcuts app for iOS (the “App”), developed by an independent developer (the “Developer”).

Effective date: 2026-08-21

The Short Version

Your health data stays on your device. It is never sent to any server, to the Developer, or to any third party. There are no servers holding your data, no accounts, and no advertising.

That includes the GPS routes of your workouts, which you can add to an export and which are switched off until you do. The App never asks for location permission and cannot see where you are; it reads routes your device already recorded, only while producing a file you asked for.

The App does send a small amount of anonymous usage statistics, so the Developer can see how often exports run and when they fail, along with a technical report when an export fails or the App stops unexpectedly. Those statistics and reports never contain health data, and nothing that identifies you.

Apple Health Data

The App reads data from Apple HealthKit solely to generate export files at your explicit request. This includes health metrics (such as steps, heart rate, sleep, body measurements, and more), workout data (such as activity type, duration, distance, and statistics), and, when you switch it on, the GPS route recorded with a workout along with the heart rate series measured over it.

• Health data is read only when you initiate an export, whether manually or through an Apple Shortcuts automation that you configure
• Health data is processed entirely on your device
• The resulting JSON export file is saved locally; you control where it goes (share sheet, Files, iCloud Drive, or any other destination you choose)
• No health data is ever sent to any server or third party by the App

Apple’s HealthKit guidelines require that health data is not used for advertising or sold to data brokers. This App fully complies: it does not use health data for any purpose other than generating the export file you request.

Workout Routes and Location

Exporting GPS routes is off by default. You switch it on yourself, in the Workouts tab, and it stays a choice you make per export.

With it on, the App reads the route your device recorded during a workout, which is a series of coordinates, altitudes and timestamps, and writes it into the file you asked for. Location deserves to be described precisely rather than reassuringly, so:

• The App never asks for location permission and never uses GPS. It cannot see where you are and cannot follow you. It reads only routes your device had already recorded, only through HealthKit, and only with the authorization you granted
• Routes are read only while an export you started is running, never in the background and never on a schedule
• Coordinates are processed entirely on your device and written only into your export file. They are never sent to any server, to the Developer, or to any third party
• The anonymous usage statistics described below never contain a coordinate, a route, a place name, or anything derived from one. All they record about this is which of the three options you picked: routes off, routes in the JSON, or routes as GPX files
• You can revoke access to workout routes on its own, in Settings > Privacy & Security > Health > Health Exporter, and workout export keeps working without them

One thing that is your responsibility rather than the App’s: an export containing routes describes where you have been, often including where you live. Once you save or share that file, its contents are wherever you put them. Treat it with the care you would give any location history, particularly before uploading it to another service.

Anonymous Usage Statistics

The App sends a small number of anonymous events: when an export completes, when one fails, and when the App asks you to rate it. They exist so the Developer can fix bugs and get a rough sense of how the App is used. These events carry no health data and nothing that identifies you.

They are handled by TelemetryDeck, an analytics provider based in Germany and built around GDPR compliance, funded by developer subscriptions rather than advertising. The installation identifier attached to each event is hashed on your device and hashed again on arrival, so neither the Developer nor TelemetryDeck can trace it back to you, to your device, or to any other app you use.

The events the App sends

This is the complete list:

• healthExportCompleted: a health data export finished. It records which period you picked, whether you exported every data type or a selection, and how many types were in it
• workoutExportCompleted: a workout export finished. It records the same, plus how many activity types were in it and which of the three route options you chose
• exportFailed: an export stopped with an error. What the event carries is described below
• reviewRequested: the App asked you to rate it, and which moment prompted the ask

None of these carry a health value, a date from your health data, a workout, a coordinate, or a file you exported.

When an export fails, and when the App crashes

A failed export is reported as an error rather than as a plain event, and it carries more detail than the events above: which step failed, how iOS described the failure, and the list of internal function names on the stack at the moment it happened. If the App stops unexpectedly, that is reported the same way. There is no third-party crash reporting SDK; the same TelemetryDeck connection carries it.

What these reports never carry is anything read from your data. They describe the App’s own code and the system frameworks it calls, so they contain no health value, no workout, no coordinate, and no export file. They are attached to nothing beyond the doubly hashed installation identifier described above.

What the App Does Not Do

• No advertising SDKs, advertising identifiers, or ad targeting
• No cross-app or cross-site tracking, and no data sold or shared with data brokers
• No account creation or login
• No cookies
• No location permission, no use of GPS, and no knowledge of where you are. Workout routes are a different thing, read from HealthKit and only during an export you asked for: see above
• No health data transmitted anywhere, to anyone, at any time

Data Retention

The App does not retain any data beyond the current session. Export files are created in a temporary directory and handed to the system share sheet or Shortcuts. The App does not maintain a history of your exports.

The anonymous usage statistics described above are retained by TelemetryDeck on the Developer’s behalf, in aggregate form, to show usage trends over time.

Children

The App does not collect personal information from anyone, including children under the age of 13. The anonymous usage statistics described above contain no personal information and no health data, so no special provisions for children’s data are necessary.

Security

Your health data is protected by iOS and HealthKit’s built-in encryption and access controls, and it never leaves your device. The App accesses HealthKit data only with your explicit authorization, and you can revoke access at any time in Settings > Health > Health Exporter. The anonymous usage statistics are transmitted over an encrypted connection.

Your Rights

The App does not collect or store personal data, so there is no personal data to access, correct, or delete. The usage statistics are anonymous and cannot be traced back to you, which also means they cannot be singled out and deleted on request. You can revoke HealthKit permissions at any time, and you can delete the App without any data remaining on any server.

Changes

This Privacy Policy may be updated to reflect changes in the App. Updates will be posted on this page. Continued use of the App after changes constitutes acceptance of the updated policy.

Contact

If you have questions about this Privacy Policy, contact the Developer at [email protected].