TrailScope is a local-first Android and Wear OS app for importing routes, recording outdoor workouts, following routes from a Wear OS watch, and exporting workout files.
Privacy policy details
Scope
This policy covers the TrailScope phone and Wear OS app surfaces distributed under package com.trailscope.mobile and the Wear OS implementation namespace com.trailscope.wear.
TrailScope currently does not provide a TrailScope account, social feed, TrailScope cloud backup, automatic analytics, or automatic crash reporting.
Workouts: timestamps, duration, distance, speed or pace, elevation, route progress, laps, GPS samples, GPS accuracy, off-route status, route-cue metadata, and heart rate when watch hardware and permissions allow it.
Files: imported GPX or ZIP files, generated GPX/FIT workout files, route export ZIPs, workout export bundles, backup ZIPs, manifests, and checksums.
Settings: units, alert distances, lap distance, quiet/DND behavior, audio/voice cue choices, haptic patterns, workout data fields, and turn alerts.
Location, workout, and heart-rate data can be sensitive. Route and workout files may reveal places you visit, exercise habits, and health or fitness information.
How Data Is Used
TrailScope uses data for app functionality:
Importing, previewing, organizing, and exporting routes.
Sending routes, route filters, and workout settings between your phone and paired Wear OS watch.
Recording and displaying outdoor workouts on the watch and showing workout history on the phone and watch.
Generating GPX and FIT files for your own export and backup workflows.
Showing local export queue state, sync state, retry state, and attention states.
TrailScope does not use your data for advertising, profiling, or a TrailScope social graph.
Sharing And Export
TrailScope data leaves the app only through user-controlled flows or paired-device sync:
Phone and Wear sync exchanges route, settings, filter preset, workout, and backfill data between your paired devices through the Wear OS Data Layer.
Share sheets and file providers share route files, workout files, export bundles, and backup ZIPs only after explicit user action.
Support files or filtered logs may be sent only if you choose to send them for troubleshooting. Review files first because routes, workouts, and logs can contain sensitive location or fitness data.
TrailScope does not operate a TrailScope backend that receives your routes or workouts in the current MVP. Current public release builds do not expose TrailScope Strava uploads.
Storage And Deletion
TrailScope stores app data locally on your phone and watch. Android Auto Backup is disabled for both packages so local route, workout, health, and location data is not automatically copied by platform backup outside explicit export flows. Phone and Wear app manifests also disable cleartext traffic.
You can delete local routes, workouts, exports, and backup files from the app where those controls are available, or by clearing app data from Android settings. Files exported, shared, or saved to another app are controlled by the destination app or service.
Because TrailScope currently has no TrailScope account or backend, there is no TrailScope server-side account deletion process for the current MVP.
Permissions
Location permissions on Wear OS for workout GPS recording and route following.
Heart-rate or body-sensor permissions on Wear OS where hardware and OS support heart-rate recording.
Activity recognition and foreground-service permissions for workout recording.
Notification permission for active workout status and alerts where required by Android.
Internet permission on the phone for platform networking and release-disabled optional Strava code paths. Current public release builds do not expose Strava uploads.
Bluetooth and Google Play services transport may be used by the platform for Wear OS phone/watch communication.
Children
TrailScope is intended for general outdoor fitness use and is not designed as a child-directed app.
Changes
This policy will be updated before release whenever TrailScope adds analytics, crash reporting, a backend, account sync, cloud backup, subscriptions, payments, third-party sharing, or a changed Strava authorization flow.