Support & Privacy

RunHeat Support & Privacy Policy

This is a snapshot of the previous public page saved on 2026-11-01. View current support and 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

RunHeat does not require account registration or login.

In the standard App Store version, the developer does not receive, transmit, or share your running or Health data. RunHeat does not store running records on a backend server. Feedback attachments in test builds may include information shown on screen, as described below.

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.

Health data is processed on-device and is not transmitted externally. 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. The current App Store version is 1.5; version 1.6 is being prepared for review.

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.

TestFlight Feedback

In TestFlight builds that include feedback, shaking the device captures the current app screen and attaches it to the feedback form. Send Feedback in the menu starts without an attachment. The capture may include running information shown on screen; review, edit, or remove it before sending. Captures are not saved to your photo library. Choosing to send submits your text, attached images, app version, platform, and screen name to the mini-voc feedback service. Raw HealthKit data and import files are not attached separately. Cancelling before submission discards the draft. Failed submissions are stored on-device and retried on the next app launch. Submitted feedback is retained for developer review. Contact the support email above for deletion requests. The latest feedback-enabled TestFlight build sends feedback over the internet and does not require Tailscale. Older test builds may require Tailscale. This feedback feature is excluded from the standard App Store Release build.

Changes to This Policy

Any updates to this Privacy Policy will be reflected on this page.

Last updated: 2026-10-11