This page describes what the Lake Biwa Ride Companion stores and shares. It is a small private tool for three riders — there are no accounts, no analytics and no advertising.
The shared trip (itinerary, places, manual checklist ticks and notes) is stored in a dedicated Redis database so all three phones see the same state. It is public shared state for this trip — no accounts and no invite token — served to browsers with private, no-store headers and kept with no expiry.
If you tap “use my location”, your browser takes a position that stays on your device for the rest of the session and centres every Nearby shortcut search you open — the coordinates travel to Google Maps inside those links only. The fix is never sent to our server, never stored beyond the session and never shared with the other riders.
Map previews, road-route geometry, terrain data and place details come from Google Maps Platform. When you view a map or request a route, the stop coordinates are sent to Google to compute the preview. Route, elevation and place details are shown transiently and are not stored with the trip — the only provider data kept server-side is the small set Google's caching rules allow: a resolved Google place ID (no expiry) and place coordinates (30 days at most). Photos, opening hours, ratings and photo links are never stored. Google's own privacy policy applies to that traffic.
There are no accounts and no access tokens. Provider keys live
server-side — except the Maps JavaScript key, which is deliberately
public but locked by HTTP-referrer restrictions to this site. None are
written to logs or sent anywhere but Google's own endpoints. This site's referrer
policy is strict-origin-when-cross-origin: third-party sites
you open from links (including Google Maps, whose script needs an origin
referrer for its restricted key) may see that you came from this site.