Privacy Policy

What we collect

• Trip details you enter — origin, destination, dates, party, preferences, any note you add — and the itineraries we generate for you.
• What you type into a place field, while you type it, so we can offer suggestions. It goes to our maps provider for that purpose and we don't keep it as a search history.
• Your email, if you sign in. We use passwordless magic links; we never store a password.
• Your rough location— to fill in a starting point, and as part of usage analytics (below). When you tap "use my location" in the app or the web planner, we ask your device for its position and use it to work out the nearest town and what's worth driving to; decline and everything else still works. On the home page, "Road trips from" your city uses the approximate city of your internet connection, which our host passes along with every request. We use it to name that city. The iPhone app's planner uses the same city to suggest where to start and trips that begin nearby.
• Usage analytics — which screens and actions you use — tied to a random id, not to your name. On the web they start only once you accept; in the iPhone app they are on by default and you can switch them off in Account at any time. If you installed the app from an Apple Search Ads campaign, Apple tells us which campaign it was, not who you are; we keep that with the same analytics and it follows the same switch. Each analytics event also notes the approximate country, region and city of your internet connection, as our host works it out; we never send your IP address or precise location to analytics.
• Payment status, if you subscribe — through Stripe on the web and through Apple in the app. Card details go to them, never to us.

Service providers

We share the minimum needed with processors that make the product work:

• Google Places & Mapbox — resolving places and driving routes.
• Anthropic & Google (Gemini) — drafting itineraries and illustrations.
• Open-Meteo — weather forecasts.
• Stripe & Link — subscription payments on the web. When a purchase is sold through Link, Link also receives your name, email and billing address to handle tax, receipts and billing support.
• Resend — sending your sign-in emails.
• PostHog — product analytics. There is no PostHog code in your browser or in the app: events go to our own server first and we forward them.
• Apple — subscriptions bought in the iPhone app.
• Vercel & Neon — hosting and database.
• Travelpayouts — affiliate booking links (see below).

Affiliate links

Some links to hotels, cars and other travel services are affiliate links, served through the Travelpayouts network. If you book through one, the booking site pays us a commission; you pay the same price either way. To credit the booking to us, Travelpayouts sets a cookie in your browser when you use those links. Your booking itself — name, dates, payment — happens on the booking site and never passes through us.

Cookies, and the app

• Essential — a device id (trip limits & abuse prevention) and, once you sign in, a session cookie. These are required for the app to work.
• Analytics — on the web, nothing is sent until you accept. Decline and you can still use everything.
• In the iPhone app there are no cookies and no advertising identifier. The same random id lives in the device keychain instead, and the analytics switch sits in Account.

Your rights

You can view your data, export your trips, and delete your account at any time from your account page— or from Account inside the iPhone app, which deletes it the same way. Deleting your account removes your trips and profile. For anything else, email us and we'll help.

Retention

We keep your trips and account while your account is active. Delete your account and we remove them. Anonymous analytics are retained in aggregate; place and route data we cache from providers expires automatically.

Contact

Questions or requests: info@roadanza.com.