Privacy Policy

Effective: August 27, 2026

The short version:

What data LoopRun accesses

Location (with your permission)

LoopRun requests access to your precise location to:

Location data is stored in the app on your device as part of your run history. LoopRun has no developer-operated backend. Coordinates are sent directly from the app to third-party services when needed to plan or reroute a route, find scenery, match a route you draw, load maps, or retrieve weather and elevation data.

When you open History, LoopRun automatically sends eligible recorded GPS tracks to GraphHopper to calculate elevation profiles. If processing fails, LoopRun may retry the next time you open History. It also sends the run's precise starting coordinate and date to Apple WeatherKit to retrieve historical weather when that information is missing.

Health and fitness data (with your permission)

If you enable HealthKit integration, LoopRun:

Health data is used solely to provide fitness features within LoopRun. It is never used for marketing, advertising, or data mining. Information saved in Apple Health is stored and managed by Apple and may sync through Apple services according to your Health and iCloud settings. You can revoke HealthKit access at any time in your device Settings.

Photos (with your permission)

You can optionally choose a profile photo. Apple's system photo picker gives LoopRun only the image you select, without granting broad access to your photo library. LoopRun stores the selected image in its app data and does not send it to routing or subscription providers. It may be included in your device backups.

Locally stored data

LoopRun stores the following in the app on your device:

Run history, preferences, profile data, and active-run recovery data live in the app sandbox. The trial usage and cached entitlement records are stored in the device Keychain. LoopRun uses them only to enforce the daily three-route trial allowance, preserve recently verified access during temporary connectivity problems, and prevent the trial allowance from being reset by reinstalling the app. They are not used for advertising, analytics, tracking, or profiling.

LoopRun has no account system, developer-operated backend, or LoopRun cloud sync. App sandbox data may be included in iCloud Backup or a computer backup according to your Apple and device backup settings. The Keychain records are restricted to the same device and may remain after you delete or reinstall LoopRun.

Third-party services

LoopRun does not have its own backend. However, it communicates with the following services to provide core functionality. As with any network request, these services may also receive your IP address and standard request metadata.

Service What it receives Why
GraphHopper Starting and waypoint coordinates, drawn-route coordinates, rerouting coordinates, and recorded historical GPS tracks Route calculation, rerouting, map matching, and elevation profiles
Overpass API Precise starting coordinates and search radius Finds scenic points of interest
CARTO / Esri Viewport and tile coordinates, IP address, and standard request metadata Renders map tiles
Apple (StoreKit) Purchase and subscription information Processes subscriptions
Apple (HealthKit) Body mass read with permission; completed workout, distance, energy, route, and altitude written with permission Stores and manages fitness data; may sync through Apple services according to your settings
Apple (WeatherKit) Precise run-start coordinate and run date or time Provides current or historical weather for a run
RevenueCat Anonymous subscription identifier, receipt, purchase history, entitlement status Verifies subscription and trial entitlement; LoopRun enforces the daily route allowance locally

LoopRun uses these providers only to deliver the features described above and selects services whose published privacy protections are intended to provide the same or equivalent protection for the data they process. Each provider processes and retains request or transaction data under its own linked privacy terms. Public, community-operated Overpass API instances may also keep ordinary server logs under the operator's own policy.

What LoopRun does not do

LoopRun sends limited data to the service providers listed above only when needed to provide app functionality.

Data retention

Delete a run from LoopRun and it is removed from the app's database. If that workout and route were saved to Apple Health, the Apple Health copy remains and must be deleted separately in the Health app. Deleting LoopRun removes its sandbox data from the device, including run history, routes, preferences, profile data, and an active-run checkpoint.

Sandbox data may remain in an existing iCloud or computer backup until that backup expires or you delete it through the relevant Apple or device backup controls. Apple Health data may remain or sync according to your Health and iCloud settings.

The trial usage and cached subscription entitlement records are stored in the device Keychain and may remain on the same device after you delete or reinstall LoopRun. There are no copies of these records on a LoopRun server.

Third-party providers may retain request, server-log, health, weather, or transaction data under their own policies. LoopRun does not hold a backend copy and generally cannot directly delete records controlled by those providers. Contact us if you need help identifying the relevant provider or deletion process.

Your rights

You can manage LoopRun's access and local data through the app and your device settings:

Website

The LoopRun website does not use analytics, advertising, or tracking cookies. Its home page loads fonts from Google Fonts, so Google receives your IP address and standard request metadata when your browser requests those font files. Google's processing is governed by its Privacy Policy.

Changes to this policy

If this policy changes, the updated version will be posted here with a new effective date.

Contact

Questions about this policy? Reach out at support@loopruns.app.