Your weekend. Your information.
The preview asks for travel preferences, not your identity.
Generating a plan
City searches run against our imported GeoNames snapshot; no external geocoding service is called during your search. Search text is not saved in the plan database. We process departure city, travel date, adult traveller count, spending budget and currency, travel approach, distance limit, region, countries, style, pace and excluded cities. Do not enter names, health information or booking references. Plan generation does not write these preferences to our database.
Saving and sharing
Only an explicit Save private link action stores the generated itinerary and preferences. A random secret in the link controls access; the server stores its hash. Links work for 30 days. A recipient with the complete link can view, change saved stop choices or permanently delete the plan. Explicitly saving route changes stores skipped-stop keys with the original itinerary; it does not extend the 30-day expiry. The latest save wins when multiple recipients edit. Use Delete saved plan on the saved itinerary to remove its stored preferences and disable the link for everyone. Downloaded copies cannot be recalled.
Storage lifecycle
Private link access expires after 30 days. Expired stored plans are physically removed when the next plan-storage request runs. There is no idle background deletion timer, so a period without requests can delay removal. Do not save confidential information. No third-party advertising analytics or marketing email collection is configured.
City-data attribution
Additional departure locations use GeoNames data under CC BY 4.0, filtered to the catalogue area and with rounded coordinates. GeoNames includes Ordnance Survey data © Crown copyright and database right 2010, licensed under Open Government Licence v1.0. The snapshot is imported on 31 October 2026, provided as-is, and covers larger towns and capitals rather than every village. It is not live transport information.
Before a paid launch
Seller and data-controller contact details, retention/deletion operations and payment/email processors must be completed before collecting customer contact data or payments. The current owner-private preview does not collect either.