DOCUMENTATION
Accounts, preferences and local trips
Understand what sign-in stores and how local trips differ from assistant-accessible snapshots.
Content updated
Plan as a guest or sign in
Planning does not require an account. Optional Google sign-in identifies your Adventure Runner account and enables saved gear preferences and assistant authorization. Apple sign-in is not enabled. Google sign-in does not grant access to Gmail, Drive or Calendar.
Where are my trips?
Your trip library belongs to this browser and origin. A different device, browser profile, private window or hosting URL has a separate library. Sign-in does not upload, sync or separate local trips by account. Signing out leaves local trips on the device. Use Download trip and import its JSON file to move or restore a local plan.
Share a snapshot deliberately
In Account, select a local trip and choose Share selected trip. This uploads its route and notes to your account for authorized assistants. Later local edits are not uploaded automatically. Approved assistant edits change the cloud snapshot; Save as local copy creates a separate editable local plan. Sharing a snapshot is different from generating an editable link.
Control assistant access
Account lists authorized connections and pending proposals. Stop sharing blocks assistant access to that plan. Disconnect revokes the connection; previously issued access tokens may remain valid until expiry. Exported files and copied content cannot be recalled. Read the Privacy page for storage and provider details.
Next step
Still have a question? Email project support. Include the control and what you expected; keep private trip links and credentials out.