Effective date: August 20, 2026
My Hiking Library is a personal hiking journal for iPhone. It uses information from Apple Health to organize and display your hiking history.
My Hiking Library does not require you to create an account with the developer. The developer does not operate a server that receives your hiking history, photographs, current location, or personal HealthKit information.
With your permission, My Hiking Library may access:
You can deny or revoke Health, Photo Library, or Location permissions at any time. Some features may be unavailable without the corresponding permission, but unrelated features will remain available.
HealthKit-derived information—including workouts, dates, routes, coordinates, distance, duration, elevation, energy, heart-rate information, and weather recorded with a workout—is stored in the app’s local data store on your device.
My Hiking Library:
Except for the limited Apple Weather request described below, HealthKit-derived information remains on your device.
When you open an eligible completed hike, My Hiking Library may send that hike’s trail coordinate and representative date and time directly to Apple Weather through Apple’s WeatherKit service. This is used only to retrieve historical conditions associated with that hike, such as temperature, humidity, precipitation, wind, and general weather conditions.
This request does not use or transmit your current live location. The developer does not receive the request or the returned weather information.
Weather returned by Apple Weather is temporarily cached in memory to avoid unnecessary repeat requests during the current app session. It is not permanently stored by the app and is not synchronized through iCloud.
Apple’s handling of information submitted to Apple services is governed by the Apple Privacy Policy.
Current-location access is used only to show your position when using supported map features.
My Hiking Library does not permanently store your current location and does not send it to the developer, advertisers, data brokers, or analytics providers. It is not used for advertising, tracking, or marketing.
Saved GPS workout routes imported from Apple Health are treated as HealthKit-derived data and remain in the app’s local data store.
The following user-created information and preferences may be stored in your private iCloud account so they can be restored and synchronized across your devices:
Opaque hike identifiers do not contain workout measurements, GPS coordinates, workout dates, routes, heart-rate information, or raw HealthKit workout identifiers.
When you delete a collection, a limited deletion marker may remain in your private iCloud data so that an outdated copy of the collection is not restored from another device. This marker contains only a randomly generated collection identifier and deletion time. It does not contain the collection’s name, description, membership, or hiking information.
Renamed trails and areas remain on your device and are not synchronized through iCloud.
Private iCloud information is stored using Apple CloudKit under your Apple Account. The developer does not operate a separate server for this information and does not have access to your private CloudKit records.
My Hiking Library does not copy or upload your photographs. Photos remain in your Apple Photos library.
The app stores local Photo Library references for photographs you associate with hikes. These references remain on your device and are used only to locate and display the corresponding photographs within the app.
Photo creation dates and available location metadata are used locally to suggest potential matches. They are not sent to the developer, stored in iCloud, or used for advertising, tracking, or marketing.
Removing the app does not delete photographs from Apple Photos. Removing a photograph from Apple Photos may make it unavailable within My Hiking Library.
The app may store settings and operational information on your device, including:
This information is used only to provide app functionality and preferences. It is not sent to the developer or used for tracking.
My Hiking Library does not:
The app uses Apple-provided services, including HealthKit, Photos, Location Services, WeatherKit, and private CloudKit storage, for the purposes described in this policy.
HealthKit-derived information, Photo Library references, renamed trails and areas, and other locally stored app information remain on your device until the app’s local data is deleted or the app is uninstalled.
Uninstalling My Hiking Library does not delete the original workouts from Apple Health or photographs from Apple Photos.
User-created information synchronized through iCloud may remain in your private iCloud account after uninstalling the app. This allows supported information to be restored if the app is reinstalled or used on another device signed in to the same Apple Account.
Within My Hiking Library, you can:
Deleting a collection removes its descriptive information and membership. A limited deletion marker may remain as described above to synchronize that deletion across devices.
You can manage or delete all of the app’s private iCloud data through your Apple Account’s iCloud storage settings. Deleting synchronized information may remove it from every device signed in to the same Apple Account.
Because the developer does not have access to your private CloudKit records, the developer cannot retrieve or delete that information on your behalf.
You can withdraw access at any time:
Revoking permission prevents future access to the corresponding protected information. Previously cached local app information may remain until the app’s local data is deleted or the app is uninstalled.
My Hiking Library relies on Apple’s platform security, application sandboxing, HealthKit protections, and private CloudKit storage. No method of electronic storage is completely secure, but the app minimizes data transmission and does not operate a separate developer-controlled server containing your personal hiking information.
My Hiking Library is not directed toward children and is not designed to knowingly collect personal information from children through developer-operated services. The developer does not operate an account system, analytics service, advertising service, or user-data server for the app.
This policy may be updated when the app’s features or data practices change. The effective date at the top of this page identifies the latest revision.
Material changes will be reflected in the published policy before or when the corresponding app update becomes available.
Questions about this privacy policy may be sent to: