SUPPORT & LEGAL
Privacy Policy
Updated 9 November 2026 · Tigran Gevorgyan, Armenia
Versions covered
The published App Store version 1.0 (build 12) operates without Firebase, advertising or purchases. Sections covering analytics, diagnostics, advertising consent, ads and Plus apply to the upcoming update containing those features. New features become available when that update is installed. Local recording, maps, exports and support also apply to the current release.
Your activity stays on your device
TrailMetric records outdoor activities and calculates statistics locally. You do not need a TrailMetric account. We do not operate a server that receives your activity history. Map requests, exports you choose and messages you send to support are described below.
Data used by the app
Location is used to show your position and record distance, speed and a route. Motion, steps, activity recognition and barometer measurements support movement and elevation estimates. Standard Bluetooth sensors can provide heart rate, cadence, speed, distance and power, depending on the sensor and activity. Settings, workouts, lap markers and recorded measurements are stored locally. A separately started diagnostic test may record accelerometer and gyroscope data locally. Diagnostic files leave the device only if you export them.
Permissions and background recording
The app requests location, motion, Bluetooth or health access when the corresponding feature requires it. An activity you start can continue recording location when the screen is locked. TrailMetric does not request permanent “Always” location permission. With an existing location permission, opening an empty map can obtain a one-off position for centering without starting an activity. You can change permissions in system settings; doing so can limit recording.
Maps and external services
Maps load tiles from OpenStreetMap Foundation servers. Those servers receive your IP address, request time, app User-Agent and tile identifiers. Tile identifiers describe the viewed area, potentially precisely at high zoom. A map centered on your position or a saved route can therefore reveal your location or visited places. The app does not upload its complete recorded route or activity event log to the tile server. OSMF processes service requests and keeps logs under its privacy policy. In the upcoming update with offline maps, areas you choose are downloaded from OpenFreeMap. The provider receives your IP address, User-Agent and tile identifiers describing the chosen area. Its privacy policy and terms also apply to these requests. Saved offline maps are displayed locally. In “Offline maps only” mode, missing areas are not requested from the network; an explicit download of another area requires internet. Map files are disposable system cache and are not part of workout backups. The mode is stored separately: clearing the cache does not enable network fallback. Area data is not sent to Firebase.
Health data
Where health export is available, you choose whether to copy a finished workout to Apple Health or, in Android test builds, Health Connect. Type and time are exported; distance, heart rate and route follow the switches you choose. Route export is off by default. Enabling it exports the recorded route, including its start and end; PNG privacy settings do not apply to health export. On iOS, a separate import action requests read access to workouts and the heart rate and routes you select in Apple Health. You preview and select workouts before local copies are saved; copies are included in Files backups. An optional same-source heart rate search by time is marked in the record. Reimport does not replace a different local version. Deleting a local copy does not delete the Health original, and revoking read access does not erase existing local copies. Export retries still reconcile the app’s own copies to avoid duplicates. Health data is not sent to us or used for advertising. System permissions, sharing, backups and sync are controlled by you and Apple or Google.
Sharing and saving files
GPX, PNG and diagnostic exports are generated at your request. GPX can contain exact coordinates, timestamps and heart rate. A PNG map or contour can reveal a route, even without coordinates in text or metadata. Review export privacy settings before sharing. Copies are handled by the destination app or service you choose.
Retention, backups and deletion
Activities remain on your device until you delete them or remove the app. You can delete an activity, an unreadable or set-aside entry, or an unfinished recording in the app. This does not delete exported copies, backups or workouts already copied to a health store; manage those in their respective apps. Shared temporary PNG files are eligible for cleanup after seven days; the operating system can clear its cache sooner. A temporary source for “Save PNG” is removed after the system dialog finishes. Device backups and restores follow your device and cloud settings.
Support messages
If you email tgstartup@icloud.com, we receive your email address, message and any files you attach. We use them to answer your request and investigate reported problems. A route or diagnostic file is optional. We keep correspondence only as needed for support and applicable obligations; you can ask us to delete it. The email provider processes delivery and storage.
This website
These pages contain no analytics scripts, forms or embedded trackers. GitHub Pages hosts the website and can process visitor requests, including IP addresses, under the GitHub Privacy Statement. The published app 1.0 (build 12) has no advertising, tracking or purchases. Map and system services have their own policies.
Optional usage analytics in the upcoming update
In the upcoming update after build 18, usage analytics and crash reports are on for a new installation. You can turn them off independently in Settings → Analytics and diagnostics. Existing users’ saved choices are preserved; collection stays off if no choice is stored. In test build 18, crash reports have a separate switch and are initially off. Turning either option off does not limit recording or other features. While analytics is on, Google Analytics for Firebase receives app launch, views of the three introduction pages, completion or skipping of the introduction, recording start, pause, resume, save, discard and draft recovery events and their outcomes, app version, build and distribution channel. Its SDK can also process automatic app lifecycle and session events, device and operating system details, usage timing, a pseudonymous app-instance identifier and approximate location derived from the network IP address. Analytics does not use the phone’s precise Location Services for this purpose. This data helps us understand which features work and where users encounter problems.
Optional crash reporting in the upcoming update
If you enable diagnostics, Google Firebase Crashlytics receives technical crash and non-fatal error reports, stack traces, app state, device and operating system information, app version, and installation identifiers. When both analytics and diagnostics are enabled, reports may include recent analytics events as breadcrumbs. The app removes free-text Dart error messages and does not add routes, exact coordinates, heart rate, Health records, workout names or sensor names to telemetry events or diagnostic logs. Native crash reports are generated by the SDK and contain technical crash context. These are pseudonymous reports, not a promise of anonymity.
Providers and international processing
Google processes Firebase and AdMob data under the Firebase privacy information and Google Privacy Policy. Processing may occur outside your country. For Firebase analytics, the app disables IDFA and IDFV collection and sets no account user ID. The advertising SDK handles identifiers according to UMP, ATT and Google settings. Health data and recorded routes are used for app functionality.
Telemetry retention and withdrawing consent
You can turn either option off in the app’s settings. This stops further sending by that service and requests clearing its pending data on the device; it does not erase data already sent. Google states that Crashlytics keeps crash stack traces and associated installation identifiers for 90 days before starting removal from live and backup systems. The Google Analytics property used for TrailMetric is configured to retain event data for 2 months and user data for 14 months, as confirmed on 8 November 2026. Activity can reset identifier retention depending on the property settings; automatic deletion runs monthly. Standard aggregated Analytics reports are not subject to that detailed-data period. See Google’s retention rules or contact us for the applicable property setting.
Privacy requests for telemetry
For access or deletion requests, email tgstartup@icloud.com. Please state that the request concerns TrailMetric, your app version and the approximate period concerned. Do not send a route or health data. TrailMetric has no user account and we do not attach your email address to telemetry, so an email address alone may not identify a pseudonymous installation. We will explain any additional information needed and the options supported by the provider. Turning sharing off or removing the app does not itself delete earlier server reports. We cannot erase records kept only on your device or in a destination service you selected.
Your choices and rights
You can review and delete local records, export your data and revoke permissions. For support correspondence or privacy requests, contact tgstartup@icloud.com. Depending on your jurisdiction, you may have rights to access, correct, delete or restrict processing of personal data and to complain to a competent authority. We cannot access or erase records that exist only on your device.
Children and updates
TrailMetric is not directed to children under 13 and does not knowingly collect their personal information. Contact us about any concern. Changes to this policy will be published here with an updated effective date; material changes to app data handling will also be described in the app’s release information. Before saving imported Apple Health data, the app excludes its internal database directory from new automatic device backups and applies file protection to the database, WAL and SHM files, available after the first device unlock. Explicit backups through Files remain available; a cloud provider you choose may receive that file. The exclusion does not delete previously created external or device backups; manage those in their respective services.
Advertising and your choices
In the upcoming update, TrailMetric uses Google User Messaging Platform to collect and store advertising privacy choices. Google processes technical request information and choices according to its messages and privacy policy. After the second onboarding page, iOS may request permission for tracking used to personalize advertising. Ad preferences provide access to privacy options when required by UMP, and ATT permission can be changed in iOS Settings. Firebase IDFA collection remains disabled. Workouts, location, heart rate and Apple Health data are not passed to the consent adapter. The upcoming update integrates interstitial, native and App Open ads subject to consent and Plus checks. Ads are blocked throughout recording, pauses and unfinished workouts. Plus disables ad requests and displays. ATT denial selects non-personalized requests. Automatic collection of approximate location through Location Services is disabled before SDK initialization. Google Mobile Ads may process IP addresses, device identifiers as permitted, ad views and interactions, and technical SDK information. Workouts, routes, heart rate and Apple Health data are excluded from advertising requests and targeting. Local frequency counters contain visits, full-screen counts, the day and the last display time. See Google SDK disclosures. Analytics and diagnostics switches control Firebase services. Advertising choices are managed separately through UMP and iOS ATT settings. Google may process technical advertising SDK information when ads are permitted, independently of the Crashlytics switch.
Plus subscriptions and purchase restoration
The update with purchases offers monthly and annual TrailMetric Plus subscriptions. Both remove advertising while the entitlement remains active. Apple processes payment, renewal, cancellation and refunds through the App Store and StoreKit. The app checks Apple-verified product and transaction information and the entitlement period on your device. Restore Purchases synchronizes with the App Store at your request. You can manage your subscription in the App Store. We do not receive your card number, bank details or Apple Account password. The current implementation sends no receipts, transaction identifiers or subscription history to our server, Firebase or AdMob. The advertising SDK may have processed ad information before you subscribed. Plus stops new ad requests and displays, but does not erase earlier processing. Removing the app does not cancel a subscription. See App Store privacy information for Apple's processing. Apple may provide the developer with sales and subscription reports, including the product, country and a pseudonymous subscriber identifier. These reports support accounting and subscription operations and are retained as needed for applicable financial and legal obligations.