Privacy
Preview draft. Operator details and provider retention arrangements must be confirmed before this policy is published to production.
This page describes the data used by Offboard’s website. Last updated 26 September 2026.
Your location and searches
Location is requested only when you choose “Use my location” and your browser permits it. Offboard sends the returned position to its server to find an approximate address and plan your journey. You can type an address or station instead. Choosing “Show my live location” starts position updates while this page is visible. The moving marker and accuracy circle are processed in your browser; this feature does not save a location history or send each update to Offboard’s server. Following the map loads tiles for the area shown. Use “Stop sharing” to stop updates and remove the marker. Switching away pauses updates; closing the page stops them. “Use my location” also starts the moving marker after finding your starting position.
Journey endpoints, travel time, pass zones and accessibility choices are used to request routes. Station and address searches send the text you enter to search services. Avoid entering information that is not needed for your journey.
Services that receive requests
TfL provides transport planning, fares and arrival information. Photon / komoot provides address search and reverse geocoding. FOSSGIS / OSRM provides pedestrian routing. Selecting a named map place sends its name and mapped coordinates to Offboard for an OpenStreetMap / Overpass lookup of available public details. Links to photos, reviews and Street View open Google Maps only when selected. Map tiles are loaded from OpenFreeMap, whose requests expose your IP address and map area. Vercel hosts this website and processes connection and operational information.
Requests to routing and search providers may include journey endpoints or coordinates. Each provider handles its own operational records under its policies. The operator must confirm applicable provider retention periods and any international transfer arrangements before final publication.
Optional accounts
When sign-in is enabled, Clerk processes your account identifiers, verification and session information. Google and Facebook handle social sign-in when you choose them. Email and phone verification use the contact details you supply. Offboard uses the authenticated account identity to show account settings and provide your account export; it does not receive your Google or Facebook password.
Authentication uses session cookies. You can sign out, manage sessions and delete your account through the account page when sign-in is connected. Account deletion is separate from browser-local saved places. Identity-provider records and required operational retention are subject to their policies and must be included in the final operator privacy review.
Data stored on your device
Saved place names and addresses, travel preferences, weekly commute snapshots and appearance choice use browser local storage. They remain until you remove them or clear site data. They do not automatically sync across devices. Walking-calorie body weight is held in the current page.
Opening a saved place to plan a journey sends that location for routing, just like a new search. Weekly totals are calculated in your browser. The service worker supports installation and an offline notice; it does not provide offline journey predictions.
Account travel storage
When connected, the account database stores the display name and preferences you save, places explicitly saved to your account, and journeys you choose to save after enabling history. Each record is linked to your Clerk account ID. Route snapshots describe plans, not completed trips. No continuous GPS history is stored. Account journey history is limited to 100 entries and 90 days. Expired journeys are hidden immediately and removed on access or by the scheduled cleanup job. Account places and preferences remain until you delete them. Manage, export and delete travel data from your account page. Device-only data stays separate. Deleting a Clerk account triggers database deletion through the verified account-deletion webhook when configured. Database backups follow the hosting provider’s retention settings and must be confirmed before production launch.
Retention and control
The server uses short-lived request caches to reduce repeat calls. Provider and hosting logs are separate from your browser data. This release does not add advertising trackers or analytics.
Manage your data to inspect and rename saved places, export stored preferences and commute data, or delete them from this device. You can also revoke location permission in your browser.
Privacy requests
You may request access, correction or deletion of personal data held by the operator and ask about restriction, portability or objection where applicable. Contact details and the lawful basis for processing must be finalised by the operator before launch of this policy. You can raise concerns with the UK Information Commissioner’s Office.