Last Updated: October 22, 2026

1. Information We Collect

Location Data

TrailBeat records GPS location (latitude, longitude, and altitude) while you are recording an activity, including while the app is in the background with your permission. The route is stored on your device and, when iCloud is on, in your iCloud account.

That location is used to: - Display your route on a map - Identify the trail, road, or street name you are on - Determine the city or park where your activity took place - Fetch current weather conditions at the start and end of the activity

Naming a street or trail sends a map area, described in Section 3. That can happen during the activity and again later for a saved activity. If you attach a photo that contains a GPS location, TrailBeat stores that location with the photo.

Health and Fitness Data

With your permission, TrailBeat reads and writes the following data via Apple HealthKit: - Heart rate - Active energy burned (calories) - Distance (cycling, walking/running, swimming) - Workout sessions and workout routes

This data is collected from your Apple Watch during workouts and used to display real-time metrics, calculate statistics, and save completed workout summaries.

Weather Data

TrailBeat fetches current weather conditions (temperature, humidity, wind speed, and wind direction) at the start and end of each workout using Apple WeatherKit. Your GPS coordinates are sent to Apple to retrieve this data. Weather requests are processed by Apple and subject to Apple's Privacy Policy.

Motion Data

With your permission, TrailBeat uses your device's motion sensors (activity detection, pedometer, and barometric altimeter) during workouts to tell whether you're still moving when GPS drops out, and to measure cadence and elevation. Motion data is processed on your device, is not sent to TrailBeat or any third party, and is used only for the activity you're recording.

User-Provided Data

• Activity type selection (e.g., mountain biking, hiking, running)
• Notes you optionally write about your activities
• Photos you choose to attach to an activity, up to 20 per activity. TrailBeat stores a reduced copy of each photo with the activity, plus the capture date and GPS location when the photo includes them. Photos sync through your personal iCloud account, so a photo added on iPhone appears in TrailBeat for Mac. We cannot see them. Photos are not sent to the trail-name server and are not included in a Strava upload.
• App preferences such as unit system (imperial/metric) and display configuration

Diagnostic Logs

TrailBeat saves diagnostic logs on your device so you can troubleshoot. On iPhone, open Settings and tap View Logs. That screen is titled Diagnostics. On Mac, open the Diagnostics window. These logs stay on your devices and in your iCloud account. They are not sent to TrailBeat.

Logs contain app events (activity start and stop, connectivity, and errors) with timestamps. On iPhone and Mac, TrailBeat also saves reports from Apple's MetricKit: crashes, hangs, and performance figures such as CPU time, peak memory, and time in the foreground. Apple delivers these reports to the app on the device, and TrailBeat stores them with the other logs. Logs and MetricKit reports do not include your route, photos, or Health data. They are deleted after 7 days. We do not receive them unless you choose to share a log.

2. How We Use Your Information

Your data is used exclusively to: - Record and display your fitness activities - Show real-time metrics during workouts (speed, distance, heart rate, elevation) - Display trail and street names on the live map - Calculate workout statistics and summaries - Sync your activities, notes, and photos across your Apple devices via iCloud - Fetch weather conditions for your activity location - Export your activities in standard formats (GPX, JSON). The export includes the route, statistics, and notes. It does not include photos.

We do not use your data for advertising, profiling, or any purpose other than providing the TrailBeat service to you.

3. Third-Party Services

Apple iCloud (CloudKit)

Your activities, notes, and photos are synced across your devices using Apple's iCloud service. This data is stored in your personal iCloud account and is subject to Apple's Privacy Policy. We do not have access to your iCloud data.

Apple HealthKit

TrailBeat integrates with Apple HealthKit to read and write fitness data. All HealthKit data remains on your device and in your personal HealthKit store, governed by Apple's privacy protections. TrailBeat does not transfer HealthKit data to any server, except when you explicitly choose to export or share it.

Apple WeatherKit

TrailBeat uses Apple WeatherKit to fetch current weather conditions at your location. Your GPS coordinates are sent to Apple to retrieve weather data. These requests are processed by Apple and subject to Apple's Privacy Policy. We do not have access to weather request data or logs.

Apple Maps / Geocoding

TrailBeat uses Apple's built-in geocoding services to identify trail names, street names, and city names from your GPS coordinates. These requests are processed by Apple and subject to Apple's Privacy Policy.

Street and Trail Names

TrailBeat looks up street and trail names through TrailBeat's server. The app sends a map area, not a precise GPS point, an account, or another identifier.

During an activity, each lookup covers a square about 10 kilometers on a side, centered on where you are (about 5 kilometers in each direction). When you near the edge of an area the app has already fetched, it requests the next square.

For a saved activity, the lookup covers the map tiles that contain the whole route. Each tile is about 5 kilometers on a side, so the area can extend a few kilometers past the route. A long ride covers more ground than one live square.

These requests are not stored and are not linked to you. The server returns OpenStreetMap names for that area. If the server is unavailable, TrailBeat keeps any names it already has and falls back to Apple's built-in geocoding (see Apple Maps / Geocoding above). OpenStreetMap data is community-maintained; see the OSMF Privacy Policy.

Strava (Optional)

If you choose to connect your Strava account, TrailBeat can upload your workout data to Strava. This includes your GPS route, heart rate data, activity type, and duration. This data transfer only occurs when you explicitly initiate an upload or enable auto-upload. You can disconnect Strava at any time from TrailBeat's settings.

Importing a Strava data-export archive is local file parsing and does not contact Strava.

Strava integration uses OAuth 2.0 authentication. Your Strava credentials (access token and refresh token) are stored securely in your device's Keychain and are never transmitted to us. See Strava's Privacy Policy.

4. Data Storage and Security

On-Device Storage

Your workout data (routes, heart rate samples, statistics, weather conditions, notes, and photos) is stored locally on your device using Apple's SwiftData framework with encryption at rest.

iCloud Sync

When iCloud is enabled, your activities, notes, and photos are synced across your Apple devices (iPhone, Apple Watch, Mac) via Apple's CloudKit service. This data is encrypted in transit and at rest by Apple. We do not have access to your synced data. The only server we operate is the street and trail name lookup described in Section 3; it does not store requests or link them to you.

Keychain

If you connect to Strava, your authentication credentials are stored in the iOS/macOS Keychain, which provides hardware-backed encryption.

5. Data Sharing

TrailBeat does not share your personal data with third parties except:

• Apple iCloud: For syncing your activities, notes, and photos across your devices (under your iCloud account)
• Apple HealthKit: For reading and writing fitness data (on your device only)
• Apple WeatherKit: GPS coordinates only, for weather data (processed by Apple)
• Cloudflare: Hosts TrailBeat's street and trail name lookup server
• NextGIS / OpenStreetMap: Map data used to name streets and trails (the map areas described in Section 3; requests are not stored or linked to you)
• Strava: Only when you connect your Strava account and upload an activity

We do not sell, rent, or trade your personal information to any third party.

6. Data Retention

• Workout data, notes, and photos: Retained on your devices and in your iCloud account until you delete them. You can delete one photo without deleting the activity.
• Diagnostic logs: Automatically deleted after 7 days
• Strava credentials: Stored until you disconnect your Strava account
• App preferences: Stored until you delete the app

7. Your Rights and Choices

Location Access

You can control location access in iOS Settings → Privacy & Security → Location Services → TrailBeat. TrailBeat requires location access to track routes during workouts.

HealthKit Access

You can control which health data TrailBeat can access in iOS Settings → Privacy & Security → Health → TrailBeat. You can revoke access at any time.

iCloud Sync

You can disable iCloud sync for TrailBeat in iOS Settings → Apple ID → iCloud → Apps Using iCloud → TrailBeat.

Strava Integration

You can disconnect your Strava account from within TrailBeat's Settings tab at any time.

Data Deletion

You can delete a single photo from an activity, delete individual activities, or delete all activities using the "Delete All Activities" option. Deleting an activity deletes its photos. Deleting the app removes all local data. To remove iCloud data, go to iOS Settings → Apple ID → iCloud → Manage Account Storage → TrailBeat → Delete Data.

Data Export

You can export an activity at any time as GPX (the route) or JSON (the route, statistics, and notes). Photos are not included in either export. They remain with the activity on your devices and in iCloud.

8. Children's Privacy

TrailBeat does not knowingly collect personal information from children under 13. If you believe a child under 13 has provided us with personal information, please contact us so we can delete it.

9. Analytics and Tracking

TrailBeat does not use any third-party analytics, advertising, or tracking services. Crash and performance reports from Apple's MetricKit stay on your devices and in your iCloud account, as described under Diagnostic Logs. We do not receive them unless you choose to share a log. We have no visibility into how you use the app.

10. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. We will notify you of any changes by updating the "Last Updated" date at the top of this policy. We encourage you to review this Privacy Policy periodically.

11. Contact Us

If you have questions about this Privacy Policy or your data, please contact us at:

TrailBeat
Email: [email protected]

This privacy policy applies to TrailBeat version 2026.x and later for iOS, watchOS, and macOS.