Report a route issue
Send trail name errors, disconnected route suggestions, questionable connectors, impossible distance requests, or map geometry problems.
support@trailfu.com
Support
Build 1 includes a support structure before the backend arrives. Replace placeholder emails and forms with your real support tooling when ready.

Send trail name errors, disconnected route suggestions, questionable connectors, impossible distance requests, or map geometry problems.
support@trailfu.com
Send GPS gaps, sleep-state recording failures, speed spikes, jump misses, elevation problems, or ride story map framing bugs.
support@trailfu.com
Ask about privacy zones, public sharing, raw GPS, diagnostics, future cloud sync, export, or account deletion.
support@trailfu.com
Tell us what feels useful, what feels fake, and what would make TrailFu earn a permanent spot before every ride.
support@trailfu.com
No. Route planning is one part of the product. TrailFu is also a ride recorder, trail memory, coach, garage, ride story tool, and future planning companion.
No. The apps stay primary for recording, on-trail use, ride history, offline surfaces, and wearable companion features. The website extends TrailFu where a bigger screen helps.
The product direction is the opposite: routes should be grounded in connected trail data. If the requested ride cannot be honestly built, TrailFu should say so and suggest realistic alternatives.
No. Any condition or readiness feature should be labeled as data-dependent and should not replace official trail sources, land manager notices, weather checks, or rider judgment.
The planned ecosystem is local-first. Cloud sync can add backup, web garage, ride summaries, and future route sync, but the mobile apps should remain useful without forcing an account.
The next build should be the app.trailfu.com portal shell, then account foundation, garage sync, web garage, ride summary sync, progress dashboard, ride library, and route planning.