Privacy

Privacy Policy

Effective 2026-10-21

Trail by Mile is provided by AnchorTag Labs LLC. This policy describes the data handled by the iOS app.

Policy acceptance and sharing choices

Policy version: 2026-10-21.1. The app displays the Terms of Service and Privacy Policy when you have not accepted the versions bundled with the current app release. Both documents are available offline.

The final acceptance screen shows private trail statistics initially enabled and public profiles and leaderboards initially disabled. Existing saved sharing choices are preserved for policy updates. Acceptance requires checking an initially unchecked agreement box and tapping Agree & Continue. The box states that you agree to the Terms of Service, including its Safety and Liability provisions, and acknowledge this Privacy Policy. Neither optional sharing choice is applied before acceptance. Optional sharing is not required to use the app.

The device stores accepted document versions, content fingerprints, acceptance time, explicit agreement, app version/build and choices locally. New hikes and uploads (including iCloud Sync, iCloud Backups and reports) pause until the current documents are accepted and choices saved; an interrupted save resumes on the device. Decline keeps the app open with access to view and export existing local hike data, or review the terms again. Declining is remembered locally for the presented documents, preserves previous acceptance evidence and does not delete data or change saved sharing preferences. Recording recovery precedes review, which waits until recording ends. Older acceptance without explicit checkbox agreement requires review again. Review documents in Settings → Policies and change sharing in Menu → Community. An offline public opt-in is queued for all trails; linking an existing identity may still require your action. A queued join can be cancelled in Community.

Server acceptance receipts

Acceptance also creates a receipt queued on your device for delivery to AnchorTag Labs LLC at api.trailbymile.com over HTTPS through Cloudflare, even when both optional sharing choices are off. Acceptance works offline and never waits for the server. Delivery retries while the app is active, connected, outside Low Data Mode and not recording or restoring. A failed upload stays queued without an outage expiry. Declining revised documents pauses pending receipt uploads until you accept current documents; it does not erase earlier acceptance. Receipts created before this disclosure are not uploaded retroactively.

A receipt contains a random receipt reference and installation identifier, accepted document versions and SHA-256 content fingerprints, the version of the agreement wording and explicit agreement action, device-reported acceptance time, and app version/build. Our server adds its own receipt time and the App Attest key used to authenticate delivery. If that key has an unambiguous existing leaderboard identity association, we also retain that identity association; we do not create an account or public profile. These identifiers describe an app installation or existing pseudonymous identity, not a verified person's name. No optional sharing selections, private-statistics contributor code, hike data, locations, device name, email address or hardware identifier are included. Terms agreement and Privacy Policy acknowledgment do not authorize optional sharing, which remains controlled separately in Community.

We use receipts only to document agreement and policy acknowledgment, protect service integrity and handle disputes. We preserve the corresponding policy documents and agreement wording. Receipts are private, accessible only through authenticated administration on our private network, and retained indefinitely unless deleted through support. They are included in nightly server backups, which age out within 14 days of deletion. To request access or deletion, email support@anchortaglabs.com with the Receipt Reference from Settings → Policies. Deletion removes the receipt content and installation, App Attest and hiker associations; only the random receipt reference and original server receipt time remain to prevent queued retries from recreating deleted evidence. Turning optional sharing off or deleting leaderboard data does not delete these separate records. Removing the app removes its local queue but does not delete receipts already received. Cloudflare receives your IP address and ordinary request metadata for delivery and security. Our receipt records do not store IP addresses; App Attest registration uses the daily-changing keyed IP hash described under Feedback and error reports.

Data the app handles

When you intentionally start a recording, Trail by Mile records precise location coordinates and evidence such as timestamps, accuracy, altitude, speed, pauses, and recording events. It also stores information you create, including hike titles, manual endpoints, completion corrections, analysis settings, and recommendation preferences.

This data is used to record hikes, calculate and explain trail completion, restore interrupted recordings, produce hike statistics, and make on-device recommendations. It is not used for advertising or tracking.

Offline Maps purchases

Apple handles optional Offline Maps payments and purchase restoration. The app uses Apple's verified transaction information to recognize purchased trails on your device. It does not collect payment card details or send purchase receipts or hike history to AnchorTag Labs LLC for billing. No third-party billing SDK or advertising identifier is added. Offline Maps for a trail also enables writing Journal entries for that trail, including entries you choose to share publicly. Purchases are not used to identify you; leaderboards and other community sharing remain separately controlled, and purchases are separate from hike backups and sync.

Where data is stored

Hike history is stored in the app's private container on your device by default. It is not sent to AnchorTag Labs LLC or the package host during local-only use, except in a feedback or error report you choose to send or, if you turn them on, private community statistics or leaderboards (below).

If you turn on iCloud Sync (the Sync Devices switch), the app sends hike data—including precise recorded locations—to Apple's CloudKit service and stores it in your private iCloud database. Sync exists only to keep and restore your history on devices signed in to your iCloud account. Turning sync off stops future sync; it does not by itself erase copies already stored in iCloud.

Automatically Back Up Hike Data (iCloud Backups) is on by default when no preference is saved. While it is on, or when you choose Back Up Now, the app uploads snapshots of hike data for all trails—including precise recorded locations—to your private iCloud database. Automatic backups run at most once every 24 hours on this device while the app is open and not recording. The seven latest snapshots are retained separately from synchronized history. Downloaded maps are excluded. You can turn automatic backups off in Sync & Backup; that stops future uploads without deleting existing snapshots.

If you explicitly use a system share action, the destination you choose receives the exported file.

Network requests and host logs

Trail by Mile may contact its package host to check for and download signed offline-map packages. Those requests do not contain hike history or precise recorded locations.

Offline-map packages are served by Cloudflare from packages.trailbymile.com. Cloudflare receives your IP address and ordinary request metadata, such as device details and request time, for delivery, security, and abuse prevention. These pages include no analytics scripts, and website and package requests do not include saved hike history or precise recorded locations from the app.

Online Map Previews, on by default over Wi-Fi, stream map areas and terrain from the same package host where you have not downloaded detailed maps. The host receives the map areas you view, your IP address, and ordinary request metadata, not hike history or recorded locations. To use only downloaded and built-in maps, turn off Online Map Previews in Downloads → Advanced Options.

When the visible map extends beyond downloaded coverage, the app may display an Apple Maps fallback, which may use a network connection to load map detail for the area you view. Do not rely on the fallback map for offline navigation.

Feedback and error reports

Send Feedback and error-report prompts send a report only when you tap Send. A report contains your message (if any), an optional reply email, the app version and build, iOS version, device model, language and region setting, and selected trail. An error report adds the error type and code, a fixed description, up to 20 recent app event names with times, and for crashes or hangs a list of code locations (app and system libraries). Reports never contain recorded locations, hike names, or notes. Include Diagnostic Summary, off by default, adds counts of your stored records and their internal identifiers. Reports are not sent while a recording is in progress (one already sending when a recording starts may finish).

Reports travel over HTTPS through Cloudflare to a server operated by AnchorTag Labs LLC. The connection is encrypted between the app and Cloudflare and then carried over Cloudflare's tunnel to our server. Cloudflare receives your IP address and request metadata for delivery, security, and rate limiting. Our server keeps your IP address only as a keyed hash that changes daily, used for registration rate limits. Reports are kept until we delete them. The app proves it is a genuine copy using Apple's App Attest; that key limits abuse but is not stored with your reports. A report that cannot be sent waits on the device for up to 7 days and is then discarded. To have a report deleted, email support@anchortaglabs.com with the reference shown after sending or the reply address you entered. Deleted reports can remain in nightly server backups for up to 14 days before they age out.

Community statistics (optional)

Share Private Trail Statistics is initially enabled in policy review, but starts only after you tap Agree & Continue with it enabled. You can disable it before accepting or later in Menu → Community. This version changes the previously unlinked monthly statistics to private linked daily records. Existing users must review and accept the revised policy before collection resumes. The old upload queue is discarded. Only hikes ending after the new acceptance or a later opt-in contribute, and only from the device that recorded or entered them. No earlier hike history is backfilled. Synced or restored hikes from other devices are not sent.

Each upload includes a persistent random contributor code, separate from public profiles and leaderboard identity. The code stays in this device's Keychain and is reused across trails and hikes. It does not synchronize through iCloud Keychain. Losing it or using separate devices can count one person more than once. Counts measure contributors whose data was received, not verified people or everyone hiking a trail. We receive no name or contact information with the code, but these records are pseudonymous, not unlinkable: days and mile patterns could identify someone when combined with outside knowledge.

We use private daily records for first-party trail-usage analytics and aggregate statistics: counting contributors and studying which trail miles they report hiking. They are not used for advertising or cross-company tracking.

For each on-trail mile-day visit, the app sends the trail, trail data version, whole mile number, year/month/day in the trail's time zone, direction, recorded or manual kind, a day-evidence label, and an opaque hike reference. The hike reference links records from the same hike and is derived using the contributor code, independently of public leaderboard references. Recorded daily coverage uses matched track evidence and the existing half-mile coverage rule. Return visits on different days of one recording can contribute separately. Manual single-day entries are labeled reported; allocations across multiple days, approximate dates, assumed coverage and unavailable timing are labeled estimated. An estimated day is not proof that the mile was walked that day. A clean recorded mile may also include a time-per-mile range. Detours include leave/rejoin mile numbers, departure day, direction, and distance/time ranges, not their GPS path. No precise coordinates, exact clock times, hike titles, notes, achievements, trail names, or public profile identifiers are sent.

Completed-hike records upload as soon as the app can send them: online, not recording, and outside Low Data Mode. The app drains its local queue in batches of up to 60 records, without a seven-day upload delay or daily request cap. Received records count immediately in private statistics. A temporary network or server failure keeps records queued and pauses retries for five minutes, including across app restarts; the service also rate-limits requests. Unsent records still expire at the earlier of 120 days and three days before their month is finalized, so an extended absence or outage may leave incomplete statistics. Each request uses a fresh App Attest key; the server verifies and forgets that key, but the separate contributor code links the records. HTTPS requests travel through Cloudflare to AnchorTag Labs LLC. Cloudflare receives IP addresses and request metadata for delivery and security. Our server uses a daily-changing keyed IP hash for hourly rate limiting; it does not store IP addresses, App Attest keys or request timestamps with daily records.

Private daily records, hike references and contributor codes are retained until we delete them and are included in nightly server backups, which age out within 14 days. They can be inspected only through authenticated administration on the private network. Public files continue to contain finalized monthly aggregates, never contributor codes, individual hike references or daily histories. A month is finalized on the first of the third following month. Legacy unlinked records still lose their raw rows at finalization and cannot supply distinct-hiker counts. Public figures can reflect a single contributing hike on a quiet stretch, so outside knowledge could reveal its approximate month, direction and pace.

Editing or deleting a hike changes unsent records; it does not retract records already received. Turning sharing off stops uploads and discards unsent records. To request deletion of private daily records, first turn sharing off, then copy your contributor code from Community → Statistics Details and email support@anchortaglabs.com. Without the code we may be unable to locate your records. Existing monthly aggregate inputs and published figures have no contributor link and remain after deletion. Future opt-in contributions can create new records under the same code.

Trail names and leaderboards (optional)

A trail name you set in Settings → Trail Name stays on your device. If you turn on iCloud Sync, names also go to your private iCloud database as separate app-wide records (TrailByMileGlobal), not with any one trail's hikes. A trail name is not sent to AnchorTag Labs LLC unless you join a leaderboard, and a share card with your name leaves the device only when you share it.

Public Profile & Leaderboards is one app-wide choice, off by default. Turning it on asks you to Agree and Join, unless you already chose public sharing during policy acceptance. Joining makes your approved trail names, unique trail-mile rankings, hiking totals, completed-hike count and approximate named-section progress public across all trails. Individual trails cannot be enabled or disabled; names may still differ by trail. Turning it off queues removal across all trails, including while offline. Your searchable public profile links your approved names across trails using an opaque public identifier separate from your private signing identity. Find Hikers includes participants outside the top 100.

All Time, Year and Quarter rank unique current-trail coverage; repeat hikes and out-and-back returns count once within each period. Calendar periods use each hike’s finish quarter in trail time. Ranking totals and repeat-inclusive hiking totals count uploaded completed hikes immediately, with no seven-day eligibility delay. Boards update when shared contributions or approved names change and ranking distances are rounded down to ten miles. Public section progress uses only hikes ended at least seven full days earlier. Section percentages round down to ten percent and section miles to a tenth. Profiles include available time, elevation, moving pace, recorded repeat travel and estimated manual hiking time, with contributing-hike counts and estimate labels; analysis uses the same release window. Missing coverage or measurements remain unavailable. Profiles contain no routes, exact dates, hike titles or personal details. Older clients retain unique-mile season boards and their original upload schedule. No individual recent-hike feed is currently shown; any individual public hike must have ended at least seven full days earlier.

For public profiles, private uploads may happen immediately after a hike is completed. Each opaque contribution can include current-alignment trail mile bins and a release day rounded up from the hike’s end plus seven full days. The server stores these inputs privately and excludes them from public profiles until that day, without needing another app sync. Day rounding can add up to 24 hours; publication and delivery can add more. No exact hike time is sent. Only eligible approximate named-section percentages, whole-trail percentage and rounded distance are public. These are estimates, not GPS route maps.

For the Overall board, the app also sends private per-hike distance contributions for each joined trail, including completed history from before joining. Each has an opaque reference derived from the stored hike ID, known GPS distance and total hiking distance (including mapped endpoint entries), plus its finish year and calendar quarter. Linked-device copies use the same reference so one hike is not counted twice; different hikes on the same route still add distance. Updates and removals replace earlier contributions. These inputs contain no hike name, notes, exact dates, times, endpoints or route coordinates, and only aggregate hiking totals and eligible coarse coverage summaries are published. Leaving the trail's board removes its contributions from every install slot. Offline copies of a published board can remain until refreshed.

New and changed trail names are reviewed before public display. Pending or rejected names appear as "Hiker" while eligible statistics remain public. The app shows your review status and a rejection reason. Changing the name requires approval again. We store the submitted name, review decision, time and reason until you leave that trail’s board or delete your leaderboard data; deleted data can remain in backups for up to 14 days.

For each joined trail and season, the app sends your trail name for that trail and two sets of whole mile numbers on it: miles covered by recorded hikes and miles entered manually, counting only miles from hikes ended at least seven full days earlier (and with mile evidence at least seven days old). When the sets change, the app sends them again in full at a random time within the next 7 days, so editing or deleting a hike shrinks them too. They never contain coordinates, routes, dates, times, hike names, or notes. The server works out your totals from the sets. Leaderboard uploads that add more than 600 trail miles in 7 days are rejected, so the app spreads a large history over several weeks.

There is no account, email, or password. When you first join, the app creates a signing key and keeps it as a synchronizable item in iCloud Keychain, so your devices signed in to the same Apple ID can use the same identity; without iCloud Keychain it stays on that device. You can also link another device by scanning a code and save an optional recovery code. Each leaderboard request is signed with this key and proves the app is genuine with the device's App Attest key.

Our server stores, for leaderboards:

Requests travel through Cloudflare to our server as described above, and Cloudflare receives your IP address and request metadata. Leaderboard mile sets are never used to build community statistics, and statistics are never matched to leaderboards.

You can see the keys your identity uses in Menu → Community → Devices and remove one there. Removing a key added before this device's, or removing the recovery code, takes effect after 7 days, and any of your devices can cancel it. Adding or replacing a recovery code takes effect after 7 days unless you save it within 24 hours of joining on your only device. Any of your devices can cancel it. Merging two leaderboard identities takes effect after 7 days, and either identity can cancel it. Two identities that both have a recovery code can't be merged; remove one recovery code first.

Menu → Community → Delete Leaderboard Data deletes your keys, names, mile sets, reports about your names and reports filed from your devices from our server, then removes the key and join state from the device. It takes effect after 7 days, and you can cancel it from any of your other devices in that time, which protects you if someone else gets your key. With your recovery code (Use Recovery Code in Community, or in Community → Devices), Delete Leaderboard Data Now deletes it at once, and Remove Other Devices removes every key except the recovery code at once and keeps your trail name on the device you're using. The app never stores your recovery code. Leaving a trail's board deletes that trail's name and mile sets. If you no longer have any key, email support@anchortaglabs.com. An identity with no signed request for 18 months is deleted automatically. When you delete your leaderboard data, or a name is hidden or removed, affected cached boards are rebuilt without it after the change. Boards already downloaded to other people's devices keep showing your name until they download the updated file, and deleted data can remain in nightly server backups for up to 14 days.

Analytics, advertising, and tracking

The app contains no advertising SDK, third-party analytics SDK, or cross-company tracking. It does not request App Tracking Transparency permission or build advertising profiles from hike data. Feedback and error reports are sent only when you tap Send and are not used for analytics, advertising, or tracking. Community statistics are sent only after you accept with them enabled or turn them on later, are private linked daily records used to build trail-wide statistics, and are not used for advertising or tracking. Leaderboard data is used only to show leaderboards.

Retention, export, deletion, and choices

Trail Reports

Submitting a Trail Report is an optional publication request, separate from statistics and leaderboards. Reports are free to write and read. We receive your 1–5 stars, condition tags, optional one-line tip and description, trail/alignment and exact mapped intervals, recorded/manual source, hike day when known, random review ID/revision and private author credential through Cloudflare. Hike titles and raw GPS are not sent. The server stores a hash of the author credential and the App Attest key for ownership and abuse controls.

The hike day is the last calendar day in the trail's achievement time zone (Pacific for the PCT, Eastern for the AT and Mountain for the CDT); approximate-date hikes publish no day. Only the hike day is published; submission and moderation times stay private. Queued reports retain their submitted day; editing uses the hike's current day and mapped miles.

Each new or edited report needs moderator approval before stars, tags, tip, description, source, hike day and exact trail intervals become public. The day plus exact intervals can reveal where you were on that day, and approval can happen within hours. The leaderboard's seven-day location-release delay does not apply to Trail Reports. Keep personal details out. Editing withdraws publication and votes until approved. Ratings average each approved overlapping hike once, excluding gaps and other alignments. Recent conditions summarize unverified tags on reports with a known day in the last 30 days. Moderation does not verify hikes, conditions or safety.

Helpfulness votes are one current vote per App Attest key and review; authors cannot vote on their own reports. Cards can sort by helpfulness or hike day and filter to recorded hikes, including Start & End Only. Header numbers include every approved overlapping rating, including star-only reports. Viewing public reports and voting require a network; public responses are not cached for offline reading. Own submissions and status stay on your device. Submissions/removals queue offline without expiry and retry while active, connected, outside Low Data Mode and not recording/restoring after current policy acceptance.

Content and its moderation decision are retained until removal in Hike Details → Your Trail Report → Remove, or support removal using the Report Reference. Removal clears stars, tags, tip, description, day, coverage and votes; a minimal ID/revision/ownership tombstone prevents delayed resurrection. Backups age out within 14 days. Uninstalling removes local author access and unsent work but does not remove server reports. Statistics and leaderboard opt-outs do not remove Trail Reports.

Journal entries and photos

Journal defaults to Private. Rich text, photo copies, exact date/time and one editable GPS location are saved on your device for offline use. Imported photos are resized and re-rendered without embedded EXIF GPS metadata. Your chosen entry location remains attached and must be within 1 km (0.6 mi) of its trail; the app offers the nearest trail point rather than moving it for you. The shared Automatic iCloud Backups preference controls separate private journal snapshots, keeping up to seven and scheduling automatic snapshots at most once daily while open and not recording/restoring. Journal Backups provides confirmed status, manual backup and missing-entry restore. These are separate from iPhone system backups and live hike Sync. The app warns when backup is off or fails; turning it off does not delete earlier snapshots.

Selecting Public and confirming Save Public Entry sends the exact location/date/time, text, selected photos, trail, random entry ID/revision and private random author credential through Cloudflare to our server. The server stores the credential hash and never returns it publicly. Public journal publication is separate from statistics/leaderboards and has no seven-day delay. Anyone using Public Trail can view it; do not publish private locations or other people's personal information without permission. Distance sorting in Public Trail sends the reader's location only to order that request; it is not stored in the journal database.

Your own entries work offline. Browsing others' public entries requires a connection and those results are not saved as an offline collection. Uploads/removals queue without outage expiry and retry while active, connected, outside Low Data Mode and not recording/restoring after current policy acceptance. Changing to Private or deleting queues server removal; the older public copy can remain visible until delivery succeeds. Removal clears text, photos, date and location and keeps only an ID/ownership/revision/update-time tombstone. Nightly backups age out within 14 days. Others' saved copies may remain. Uninstalling or leaving leaderboards does not remove publications. Keep the original device or contact support with the Entry Reference for removal. Restoring an old public entry creates a private copy without republishing or withdrawing the original.

Sharing, children, and security

AnchorTag Labs LLC does not sell hike data. Acceptance receipts go to AnchorTag Labs LLC through Cloudflare even when optional sharing is off, as described above. Hike data goes to your private iCloud database only when you use iCloud Sync or iCloud Backups. Package requests send ordinary request metadata to the package host. Online Map Previews request map areas from the package host, and Apple Maps fallback views may contact Apple. An export goes only to the destination you select. Feedback and error reports go to AnchorTag Labs LLC through Cloudflare, a service provider that carries the connection and receives your IP address and request metadata, when you send feedback or an error report. If you turn on community statistics, private linked daily records go the same way, and the aggregate totals are published for everyone. If you join a leaderboard, your trail name, rounded hiking totals for each calendar period, hike count and eligible named-section progress are published for everyone.

Trail by Mile is not directed to children and does not knowingly collect children's personal information for advertising or profiling. The app uses Apple's sandbox and private CloudKit database, but no storage or transmission method can be guaranteed perfectly secure.

Contact

Email support@anchortaglabs.com with privacy questions. Do not include precise locations or other sensitive data in ordinary email.

Use of the app is also governed by the Trail by Mile terms of use. Material changes to this policy will be dated here and reflected in the app's store privacy disclosures.