Ads and Cookies

Voltour does not request Google-served ads from the app while premium planning is open to everybody. If ads are enabled later, they will be limited to screens with substantial planner content, approval, configuration, and consent where required.

Voltour publishes an ads.txt seller record at /ads.txt. The app does not load AdSense from navigation, login, registration, account, admin, partner, shared-route, alert, loading, or empty-result screens. Ad requests are configuration-gated so an unfinished deployment does not accidentally show ads on low-content screens.

If ads are enabled, Google and other advertising technology providers may place or read cookies, use web beacons, process IP addresses and device identifiers, and use information about the page or app context to serve, measure, and protect ads. Google explains its partner-site data use at policies.google.com/technologies/partner-sites.

Where ads are not shown

Ads are not part of route computation, map controls, station verification buttons, forms, modals, error messages, progress states, or account management. This keeps advertising separated from navigation and actions where accidental clicks are more likely.

Consent and control

Ad consent is stored locally with a timestamp and consent version when ads are enabled. Declining ads does not block the planner, and the planner footer includes controls to reset ad preference and clear local route data.