Support & Privacy

RunHeat Support & Privacy Policy

About RunHeat

RunHeat visualizes running workouts from Apple Health and running records imported from supported Strava or Garmin Bulk Export zip files. You can review yearly heatmaps, daily sessions, and shareable yearly, monthly, or weekly cards.

Support

If you have any questions, feedback, or bug reports, please contact:

Email: dseopg@gmail.com

Privacy Policy

Current document version: 2026-11-02. Previous public versions: Saved 2026-11-02 · Saved 2026-11-01

RunHeat does not require account registration or login.

Original running records and import files are processed on your device and are not stored on a server. Optional feedback in the submitted version 1.6.2 sends only the text and images you choose to submit to the developer’s feedback server. Attachments may contain running or health information displayed on screen.

The app processes running workout data and user-selected import files locally on your device to provide its heatmaps, session details, and sharing features.

RunHeat does not use analytics SDKs, advertising SDKs, or third-party tracking tools.

Health Data Access

RunHeat requests read-only access to workout records from Apple Health and uses running workouts only. It does not request permission to write data to Apple Health.

Raw HealthKit data is processed on-device and is not automatically uploaded. A screen capture you choose to submit as feedback may include displayed running or health information; review, edit, or remove it before sending. When you return to RunHeat after another app syncs with Apple Health, RunHeat refreshes the available years and the currently displayed year's running records.

Strava and Garmin Imports

RunHeat processes only a Strava or Garmin Bulk Export zip file that you explicitly select. Supported running records are extracted and processed on-device.

Imported running records are retained in RunHeat's local app storage so they remain available the next time you open the app. They are not written to Apple Health or sent to an external server. Overlapping records are merged to avoid duplicate totals.

Data Retention

Apple Health data remains managed by Apple Health. Imported running records remain in RunHeat's local app storage until the app data or app is deleted. The developer cannot access or restore this local data.

Heatmap Settings and Sharing

This section describes the 1.6 update.

Use Heatmap Settings in the menu to apply and save colors and distance thresholds or restore defaults. Refresh is available in the menu, with Retry shown after a failed load.

How to Share in the menu explains the existing yearly, monthly, and weekly sharing locations. Tap the yearly distance above the heatmap, the month name and total on the left, or a weekly total on the right, then use the share button in Share Preview. Only periods with running records can be shared, and shared cards do not show the app name. The menu adds instructions only; the existing preview flow is unchanged.

Send Feedback (submitted version 1.6.2)

This feature is not in the current public version 1.6.1 and will be available after version 1.6.2 is reviewed and released. Send Feedback in the menu starts without an attachment. Shaking the device captures the current app screen into the draft without saving it to Photos. You can review, edit, or remove up to three images.

Choosing Send submits your feedback text, selected images, app version/build, iOS platform and screen name over HTTPS to the developer’s mini-voc server. Raw HealthKit records, import files, email addresses, user IDs and device IDs are not attached automatically. Opening the form or taking a capture does not upload it. Cancelling before submission discards the draft.

A failed submission stays on your device and is retried with the same submission ID on the next app launch. Received feedback and images are stored on the server for developer support and troubleshooting, not advertising or tracking. Contact the support email above to request deletion.

Changes to This Policy

Updates to this Privacy Policy are published on this page, and previous public versions are retained.

Last updated: 2026-11-02