Roadstash — Privacy Policy

Roadstash — a private travel planning application.

Roadstash is a private travel planning application used by its owner to plan a personal trip. It is not open to the public and has no user accounts of its own.

What the application holds

Roadstash stores the trip itself — days, places, notes, bookings and the times you entered — on the server that runs it. It also stores its own working data: road legs between the trip's points, the route variants you chose, and the record of which map place each of the trip's places was matched to.

Google Maps

Roadstash includes Google Maps features and content. Use of Google Maps features and content is subject to the then-current versions of the Google Maps/Google Earth Additional Terms of Service and the Google Privacy Policy.

This deployment uses the following Google Maps Platform services:

• Maps JavaScript API — draws the map in your browser. Your browser requests map tiles and related resources directly from Google.
• Places — details about places on the trip, such as an address or opening hours, and suggestions along a route when you ask for them. Requested by the server.

Google's use of the data it receives is governed by the Google Privacy Policy linked above.

Other services

• OSRM — driving distances and road geometry between the trip's points.
• Cloudflare — the application is reached through Cloudflare and access to it is gated by Cloudflare Access, which authenticates the person opening it. These legal pages are published separately, at legal.roadstash.com, and are not part of the application.

What the application does not do

• It does not ask for or use your device's location, and does not track location in the background.
• It does not use analytics, advertising or tracking services.
• It sets no cookies of its own and stores nothing in your browser.
• It does not sell or share the trip with anyone.

Provider content

Content obtained from Google about places — such as ratings or opening hours — is not kept on Roadstash's own storage. It is requested when a screen needs it and is not written down afterwards. The place identifier used to ask the question again is kept.