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.

Bookings and travel documents

Roadstash keeps the trip's bookings — flights, car hire, accommodation and others — with the details you confirm: booking references, passenger names, baggage allowance, hire and cancellation conditions, and prices.

Adding a document — a ticket, a rental voucher or an insurance policy — is not enabled on this deployment yet: a file cannot be attached to a booking at the moment. The paragraphs below describe how documents are handled once it is switched on.

A document you upload is read by the server itself to suggest the booking's details; no model and no outside service is asked to read it. Nothing is saved until you have looked at the suggested details and confirmed them. Documents are opened only through the application, behind the same sign-in; there are no public links to them. Booking references and documents are never sent to the assistant's model provider, and they do not appear in the PDF of the plan.

Documents are kept among the trip's own files and are deleted there; Roadstash keeps no copy of the file itself, only a fingerprint — a hash — so that the same document is not stored twice. Removing a booking removes the details Roadstash added to it, such as baggage allowance or hire conditions.

Roadstash does not check with airlines, hire companies or hotels for changes: what it shows is what the booking says.

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:

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

Other services

The assistant

Roadstash has an assistant you can write to. It is used only when you send it a message. Looking at the trip, the map or the plan sends nothing to it, and the rest of the application works whether or not it answers.

To answer, the server sends your message and a short summary of the part of the trip the question is about — the day, the names of its places and their planned times — to the model provider named above. It does not send the whole trip, and it never sends booking references or any key. What comes back is read as an answer, not as an instruction: the assistant may only use the application's own limited set of actions, and anything that changes the trip is shown to you first.

ChatGPT

Roadstash can be reached from ChatGPT as a connector. That path is used only when you ask ChatGPT about the trip. Nothing is copied or synchronised in advance, and the application does not send anything there on its own.

When you do ask, ChatGPT calls the server's own limited set of actions, and what those answer reaches ChatGPT and therefore OpenAI: the day being discussed, the names of its places and their planned times, the options for getting between two of them, and — when you ask about bookings — the bookings themselves, with their references, passengers, baggage, hire and stay conditions, and the text of a travel document you ask it to read. Keys, settings and the server's own files are never part of an answer. What OpenAI does with what it receives is governed by OpenAI's own privacy policy.

Signing in is required. The connector reaches the server only through Cloudflare Access, which authenticates the person asking, and only the owner is allowed through. Changing the trip from ChatGPT takes two steps: the server computes a preview, and only that one preview can then be applied — so nothing is changed by the model on its own.

If you attach a ticket or a voucher in ChatGPT and ask to add it to the trip, the server downloads that file from OpenAI to prepare the preview, and stores it with the booking only after you confirm.

Voice

Roadstash can take a message by voice and read an answer aloud. Both use the speech features built into your browser and device; Roadstash adds no speech service of its own.

The microphone is used only after you tap the microphone button, for one short phrase. It stops when the phrase ends, when you tap the button again, or when you leave the page. Nothing is recorded, and no audio reaches the Roadstash server. The phrase is recognised by your browser's own speech service: on an iPhone that is Apple's speech recognition, which may process the audio on the device or may send the audio to Apple; in Chrome it is Google's online speech service. What comes back is plain text placed in the message box, and it is sent to Roadstash only when you tap Send, exactly as if you had typed it.

Answers are read aloud by your browser's speech synthesis, with a Russian voice it offers — on an iPhone, a voice installed on the device. Roadstash does not send the answer to any speech service itself.

The voice settings on that screen — which Russian voice, how fast it reads, and whether new answers are read aloud automatically — are kept in your browser's local storage on this device. They are not sent to the server, and nothing else is kept there.

Your location

Roadstash can show places near you, and it asks where you are only when you request that. Tapping the button that asks for places near you is what makes your browser or device ask for your permission; nothing is requested before that, and refusing leaves the rest of the application working.

The position is used to answer that one request: it is sent to the server, which asks the place provider on your behalf, and it is discarded with the answer. It is not written to the trip, to the application's storage or to its logs, and no history of where you have been is kept.

On this device

Three things are kept in your browser on this device, and nothing else. The voice settings described above. So that leaving for a navigation app and coming back does not lose your place, the screen and the day you were looking at, for a few hours. And, when you have more than one trip, which trip you had open, so that the application reopens on it. None of them is sent to the server, and none of them says anything about where you are.

The application also keeps a copy of the pages and trip data it has already shown you, so that the last plan you saw opens without a connection. It is the plan as it was when it last reached your phone, and the screen says so and offers to refresh when it is showing that copy. The copy includes the booking cards you have opened, with their references, so that a flight can be found at the airport without a connection; the travel documents themselves are never kept in it. Nothing about offline navigation is promised: routes, places and anything else that needs the network are not available without it.

What the application does not do

Provider content

Content obtained from Google about places and routes — such as ratings, opening hours or travel times — 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.