TrailSplits Privacy Policy
Effective Date: October 6, 2026
TrailSplits ("we," "our," or "us") is committed to protecting your privacy. This Privacy Policy explains how we collect, use, and safeguard your information when you use the TrailSplits apps and services (including the website and route planner).
1. Data types collected
TrailSplits collects data needed to provide activity tracking, route planning, and sharing. The exact data depends on what you use (mobile tracking vs. web route planning).
| Data category | Examples in TrailSplits | Purpose | Shared? |
|---|---|---|---|
| Location | GPS coordinates, route paths, elevation | Core activity tracking, navigation, route analysis, and route preview | Not shared without user action |
| Personal info | Email address (if account created), display name | Account creation, login, and community features | Not sold; only shared if you post publicly |
| Health & fitness | Distance, pace, calories, heart rate (if connected device) | Fitness tracking and performance insights | Not shared without consent |
| Training plans (optional) | Race plans and a race season you keep in your account: the races, their dates, and the training numbers you entered | Show them on your devices and build your personal calendar feed | Not shared; a calendar link shows the plan to whoever holds that link, and removing the plan stops it |
| App activity | Session logs, crash reports | Reliability, debugging, and analytics | Aggregated/anonymized only (where used) |
| Device & other IDs | Device type, OS version, browser info | Compatibility and performance optimization | Not shared |
| Photos & media (optional) | Profile picture, shared activity images | Community features | Only shared if you post publicly |
2. How we use data
- Core features: Provide activity tracking, navigation, route planning, and performance metrics.
- Quality: Improve reliability, fix bugs, and optimize performance.
- Community: Enable optional features like sharing, leaderboards, and challenges.
- Compliance: Meet legal obligations and app store requirements.
3. Data sharing
- No sale of data: We do not sell your data.
- User-directed sharing: Data is shared only when you explicitly choose to share routes, activities, or posts publicly.
- Your sections: To show the stretches you run again and again, we match each run in your training history to the path network and keep, with that run, the list of path junctions it passed and the times at which it passed them. This list is deleted with the run or with your account and is never shared.
- Connected training services: If you connect Intervals.icu to your TrailSplits account, it gives us read-only access to your activities (not your wellness data or settings). When Intervals.icu tells us about a new activity, we fetch its original file and store it in your training history, as if you had imported the file yourself. We also keep that original file, compressed, so your runs can be analysed again later at full detail; it is deleted with the run or with your account. To do this we keep the access key Intervals.icu gives us, encrypted, and never show it to anyone. Where activities come from a Garmin device, we name the device. Activities that reach Intervals.icu from Strava are not available to us. You can disconnect at any time on the Intervals.icu sync page of your runs: we then give up our access at Intervals.icu and delete the key, and activities already synced stay in your history until you delete them. If you also allow calendar access, we add the workouts of the training plan saved in your account to your Intervals.icu calendar for today and the next seven days, and keep them current once a day. We only add, change or remove workouts we placed ourselves, never your own entries, and we keep a list of the workouts we placed so we can update or remove them. You can stop at any time on the same page; we then remove the workouts we placed from that day on, and past days stay in your Intervals.icu calendar. On some race pages the same connection can read your recent activities once, to suggest a starting volume for the plan; those activities pass through our server to your browser without being stored. With calendar access, those pages can also add the race plan to your Intervals.icu calendar. We do not share this data with anyone else.
- Legal requirements: We may disclose information if required by law or to protect rights and safety.
- Optional usage statistics: We count broad website actions, such as generating a route file or keeping a plan. Counts are grouped by week and feature, with the site area and, for selected outcomes, signed-in, signed-out or unknown status. They are action counts, not counts of people.
These statistics use no analytics cookies, persistent browser identifiers, account identifiers or individual browsing histories. We do not include route names, locations, training details, full page addresses, referrers or device fingerprints. Analytics requests omit account credentials. We retain the weekly counts for up to 13 months and use Supabase as our database processor; we do not send them to an advertising analytics service.
Global Privacy Control and Do Not Track turn optional statistics off. You can also turn them off below, without an account. Only your preference is stored on this browser. Login sessions, plans you keep locally, and offline downloads use separate storage to provide those features.
Turning this off does not affect planning, downloads, saved work or your account. The choice stays on this browser.
Our hosting and security providers process connection information needed to deliver and protect the service. That is separate from these usage counters; we do not use security logs to reconstruct browsing histories for analytics. Older analytics identifiers are no longer collected, and legacy event records have been replaced with broad weekly totals. Provider backups expire separately under their retention schedules.
4. Data storage and security
- Storage location depends on features: Some data may be stored locally on your device/browser, and some data may be stored on our servers (for example, when you create an account and choose to sync or publish routes).
- Protection: We use industry-standard safeguards designed to protect your information.
- Control: You can delete activities or your account (where available) or request help deleting data by contacting support.
Developer API accounts and calls
If you use the TrailSplits API, this is what it keeps:
- Account: your TrailSplits sign-in (email address), as for any account.
- Projects: each project's name, plan, and when it was created or closed.
- Keys: a one-way fingerprint (SHA-256) of each key, its first characters and last four, your label, the web origins of a browser key, and when it was issued, revoked and last used (a day, never a time). The key itself is shown to you once and is never stored.
- Usage: per project, the number of calls and credits for each operation and UTC hour, and how often a limit was reached each day. Usage never holds coordinates, request bodies, query strings or network addresses.
- Requests for more: the plan, the message and the project you send from the console, read by support.
- Calls without a key: to apply the daily allowance and rate limits, the API keeps a hash of the caller's network address that changes every day, only in memory.
- What you send: coordinates, routes and GPX files in API calls are used to compute the answer; the API does not keep them. The one exception is a watch: its route is kept while the watch exists and deleted with it, or the day after its last date. A watch's delivery log keeps event ids, types, times and status codes for 30 days, never the contents.
- Downloads: which packages a project requested, when, their size and credits, to count the month's volume; the signed links themselves are not kept.
Closing a project revokes its keys. Deleting your account deletes its projects, keys, usage and requests.
5. Your choices
- Permissions: On mobile, you can manage location and notification permissions in your device settings. On the web, you can control location permission in your browser settings.
- Data management: Delete activities or your account within the app (where available) or via support.
- Privacy mode: Use TrailSplits without community features to keep your data private.
6. Children's privacy
TrailSplits is not directed to children under 13, and we do not knowingly collect personal information from children.
7. Changes to this policy
We may update this Privacy Policy from time to time. Updates will be posted within the app and on our website. If changes materially affect your rights, we will provide additional notice.
8. Contact us
If you have questions or concerns, contact us at:
- Email: support@trailsplits.com
- Privacy: privacy@trailsplits.com
- Website: https://trailsplits.com/