Privacy

Wally uses your selected start, destination, walking preferences, and visited-place IDs to suggest walks. In Live Mode, if you search for walks without choosing a start, Wally asks your browser for your current location. Location access is optional: you can deny it and choose a place through search or the map instead. You can also request your location with the location button.

Preferences, visited-place IDs, and your path history (the routes you open, with your star ratings and favourites) are stored in your browser’s localStorage. When you search, Wally sends the stop IDs of up to 50 recent routes, your ratings and favourites, and, with the Favourites tag, the names and coordinates of favourite stops, so the server can avoid repeats and prefer what you liked. They are not kept after the request. Clear your browser’s site data or use “Clear history” to remove them. Wally has no accounts or analytics integration.

When you rate or favourite a live route, Wally’s server stores an anonymous review: the stars, the favourite flag, the route name, its stop names, Google place IDs and categories, and the route settings (shape, walk or run, tags, and times). It contains no start or destination coordinates and nothing that identifies you. Averaged ratings per place help rank future routes for everyone. Demo routes are never sent.

Live map interactions load Google Maps in your browser. When you type three or more characters in a place field, Wally sends your search text and a nearby location bias to Google Places through Wally’s server. Walking and nearby-place requests also send coordinates to Google Maps Platform. When you select a live route, Wally’s server asks Google Places for up to three photos of its stops; your browser then loads those images directly from Google. Generated routes and requests are retained temporarily in server memory for event detours and walk previews and expire after 20 minutes. The “Get me to Google Maps” button opens Google Maps with the route start, stops, and finish in the link. Hosting providers may keep ordinary request logs.

Google handles information under its Privacy Policy. Demo route generation uses local sample data; loading an interactive Google map still contacts Google. Without a map key, sample routes use a local schematic preview.