What on device means
· Software in build. Not a safety guarantee.
On device is a place, not a mood. The route is built where the trip settings already are: on the phone or computer you are carrying.
No per-user AI request
Personalizing a walk could have meant sending your city, dates, interests, and distance to a remote model and waiting for a fresh answer. That is not how Wailkingtour is designed. Routes are personalized without a per-user AI request. The settings you entered are read on the device, and the day is assembled there. This page will not dress that up as a claim about a particular chip, a private model name, or a benchmark. Those details are not the public contract. The public contract is narrower: your plan is not a one-off prompt sent for you.
The marketing site is a different machine from the app. wailkingtour.com does not collect itineraries. It does not have a field for passport country, home country, or the stops in a day. If you write to Clutch Developer through the contact form, send a question about the product, not the contents of a trip. The privacy note is the short version: when the app exists, product data is designed to stay on the device, and these pages do not gather it.
Offline is specific, not magical
Barcelona, Lisbon, Rome, and Paris have curated offline routes. Offline here means the curated route can be read without asking this product's servers for the day's text. It does not mean the phone has become a complete offline atlas of the city, and it does not mean every alley has been surveyed by the studio this week. Opening the route in Google Maps is a handoff. Maps may need a connection even when the curated description did not. If your connectivity setting says the day should stand alone, prefer the curated route and treat the Maps button as optional.
Narration follows the same local idea. Stop descriptions are spoken by the device's text-to-speech. Wailkingtour does not ship a house voice and does not stream a studio recording as the default teller. Whether a given voice works without a network depends on the voice installed on that device. The product does not pretend to manage every phone maker's voice download. What it refuses is a design in which the words of the stop live only as audio on a server.
Credits are access to narration, not an upload
The first usable walking day includes narration. Later audio days use consumable credits. Pro unlocks narration for generated days. Spending a credit is about whether a later day speaks, not about uploading the itinerary in exchange for a file. Generated days are still built on the device. Pro is a name for that unlock. It is not a price, and this site will not invent one. Stores, if a store listing ever exists, would own the number. Nothing here is a checkout.
On device also means the plan can be lost if the device is lost. That is the ordinary trade of keeping a trip off a marketing website. There is no account on these pages that reconstitutes your days, and there is no team sync hiding under another name. The note on shaping a day lists the settings. The product page repeats the boundary around passport data: context for a plan, not a document check.
If a sentence on this site and a future build disagree, believe the build you are actually holding, and write to the studio if the public explanation has gone stale. Today the software is in build, so "on device" is the design being implemented. It is not a claim that you can install a finished app from this domain this afternoon.