Route Planner uses the StopDash server
When you press Optimize, route data is sent to the StopDash API/worker for processing.
PRE-LAUNCH PRIVACY
What stays on your device, and what reaches StopDash.
StopDash uses different data paths for server-routed route planning and browser-local driving tools.
Current behavior — not final legal policy
The launch privacy policy and retention terms are still being finalized.
Timeline, Mileage, Work Mode, Gig and Business are local-first today
These current tools store/process their local records in your browser/device.
Google Timeline files are not uploaded by the Timeline tool
Supported Timeline JSON is parsed in your browser tab.
Route drafts are local
A recent route draft can be recovered on this device and is excluded from Device Backup by default.
Shareable Insights are generated in the browser
Only the metrics shown in the share dialog are used for the generated card.
Device backups can contain sensitive data
Downloaded backups should be stored privately and are restored locally.
Accounts, cloud sync and billing are not active yet
Current free/local tools do not require sign-in.
Advertising is not connected yet
The preview shows ad placeholders only.
Server retention rules still need a launch policy
Route jobs are currently retained as part of the development routing system.