Privacy for the site and the plan
wailkingtour.com is a static explanation of software in build. Its pages do not load an advertising tracker. The motion script only records, in the page itself, whether you asked the browser to reduce motion, so the route line can either draw or appear whole. It does not identify you and it does not store a trip.
What the form collects
The contact form sends the name, email, topic, and message you submit to the operator through Netlify's form handling. Leave the hidden honeypot empty. Do not put an itinerary, a passport number, or a traveller's document in the message. The site does not sell form messages. Following the link to clutchappdevelopment.com takes you to the studio's separate site.
Itineraries are not a marketing-site collection
Product data is designed to stay on the device when the app exists. This marketing site does not collect practice data of any kind, and it does not collect itineraries, city plans, daily distances, connectivity choices, home country, or passport country. Those are trip settings for the app, not fields on these pages. There is no account here that could reconstruct a walking day.
Hosting may create ordinary server logs. Those logs are not a tour archive. Questions about this notice go to Clutch Developer in Barcelona through the contact form.
Advertising in the mobile app
This website does not serve AdSense ads. Mobile app versions integrating Google AdMob may show contextual banners to signed-in, non-Premium users on the planning screen. Premium users do not see ads. Advertising is not placed over active walking navigation, narration, sign-in or purchases. Declining advertising consent does not prevent using the planner.
Before requesting ads, the app refreshes consent information through Google's User Messaging Platform (UMP) and presents a privacy message where required. Where available, Settings → Advertising privacy lets you reopen your choices. Advertising choices are separate from optional app diagnostics. Development and QA builds use test ads, not paid impressions.
The integration does not request personalized advertising, IDFA tracking permission or Android advertising-ID access. The app does not pass precise walk GPS, routes, interests, passport/residence information, account identity or narration to the advertising SDK. AdMob can still process IP address (which can imply approximate location), app/device information, ad interactions and SDK diagnostics for contextual advertising, measurement and fraud prevention. This processing is not anonymous.
Google applies its own retention practices. Read how Google uses information from partner sites and apps. For app privacy requests, contact info@clutchdeveloper.com. This section describes app versions containing the new integration; installing a different build can mean different features are present.