Privacy should protect the ride before it becomes a story.

Draft for Build 1. Replace with counsel-reviewed copy before public launch.

Overview

TrailFu is designed around the idea that ride data can reveal sensitive personal patterns, including home location, work location, repeated routes, travel habits, and riding schedule. This draft policy explains the privacy posture for the public website and future app ecosystem.

Public website data

The Build 1 public website can be run without a backend. If you enable analytics, beta forms, email capture, or hosting logs, disclose what is collected, why it is collected, and how users can request deletion.

Future app and account data

Future TrailFu account sync may include profile details, bikes, components, maintenance logs, ride summaries, planned routes, privacy zones, and user settings. Raw GPS tracks should not be uploaded by default without clear user control.

Location and privacy zones

TrailFu should treat home, work, hotel, and frequent start or end locations as sensitive. Shared ride stories should trim or obscure protected zones before publishing.

User controls

Users should be able to export account data, delete account data, disable cloud backup, manage privacy zones, and decide whether diagnostics or raw tracks are included in any upload or share action.

Build note: this is product-safe starter copy, not legal advice. Replace with counsel-reviewed language before public launch.