What Roadvoya stores, and for how long

What we collect

Everything a check sends us: what the answer cannot be worked out without, and what you choose to add on top.

• The coordinates of the two places you pick. Finding them means your search text does leave the browser: every few keystrokes it is sent to us and straight on to HeiGIT, which returns the places to choose from. We keep none of it — and the name of the place you finally pick is never sent with the route or stored beside it.
• Your departure and return dates, if you give any: those are stored with the checked route, as the estimate behind each border crossing. The dates you then confirm country by country are sent with each pricing request and used to work the answer out — they are never stored.
• The vehicle class you choose, and any follow-up answer a country needs before it can price you.
• Your email address, and only if you ask for change alerts. It is stored the moment you submit it, marked unconfirmed, because that is what the confirmation link is sent to. Click the link and it becomes a subscription; ignore it and the address is deleted after 7 days.
• A keyed hash of the address that submitted the email form — the address itself is never written down. The raw address is also used in memory, and only in memory, to count how many requests have just come from it. That is what caps how fast one address can hammer this site: it makes flooding expensive, not impossible.

What we do not collect

• No account, no password, no name.
• No analytics service, no advertising network, no social widget, no cross-site cookie.
• Nothing here is sold, rented or handed to anyone for marketing.
• Your route checks are tied neither to each other nor to you. A checked route is reachable only through the link you were given, and that link expires.

Who else sees any of it

Two third parties are involved in a route check, and only these two.

• openrouteservice, run by HeiGIT in Germany, does two jobs here: it turns your search text into places you can pick, and it draws the line between the two you picked. So it receives what you type and those coordinates — and nothing else: no travel dates, no vehicle class, no email address. How long HeiGIT keeps what it receives is set by its own privacy policy, which gives criteria rather than a fixed number of days — so we will not put a number in its mouth. Read HeiGIT's privacy policy
• OpenFreeMap serves the map tiles on the result page. Your browser fetches them directly, so OpenFreeMap sees your IP address and the stretch of route on your screen. Everything else on the page works without it.
• Our own server and its database, in the EU, hold what the table below lists and nothing beyond it.

How long each thing is kept

Every period for something we store is read from the same declaration the deletion job enforces, so those rows cannot drift from what actually happens. The last row is the exception: nothing there is written down, so there is no period to name — it says what makes it go instead.

A job runs every hour and deletes everything past its period. Nothing is archived on the way out.

Getting it deleted

There is nothing to ask us about a checked route: the link stops working after 24 hours and the next cleanup deletes what was behind it. An email address goes with the unsubscribe link in any message we send — or by never confirming it in the first place.