Your travel inspiration should never cost you your privacy

Your Wanderlust account

Your account holds your email address, a username, your name if you give it, and your password, which we store only as a bcrypt hash. If you sign in with Apple or Google instead, we receive the name and email address they share with us. Everything else on your profile, such as a photo, a bio or the countries you've visited, is optional.

• Your trips are private until you invite someone to one or make it public.
• If you book a place on a group trip, the trip's host sees your name and email address.

Trip details you add

The itineraries, flights, hotels, expenses, notes and bucket-list places you add are stored with your account so you can plan, share and revisit your trips.

• Booking confirmations you forward to your personal Wanderlust address, or paste into a trip, are read by our booking parser, which runs on Anthropic's Claude. What it finds waits for your review before it's added to the trip.
• Flight numbers and dates on your trips are used to look up flight status.

AI features

When you use an AI feature, what you type and the trip details it needs are sent to the AI provider behind it to generate the answer. The AI trip planner, the city concierge, the travel-stats summary and the browser extension's destination chat use OpenAI. The assistant, stop suggestions, booking import and publishers' AI guide drafts use Anthropic.

Payment information

Subscriptions, the video add-on and group-trip bookings are paid through Stripe, Inc., a PCI-compliant payment processor. That includes upgrades started in the iPhone app or the browser extension, which open Stripe's checkout on the web.

• Card details are entered on Stripe's checkout and go straight to Stripe. They never touch our servers.
• We can see limited billing details in Stripe, such as your billing name and address and the last four digits of your card, and use them only to help with cancellations, refunds or account changes you ask for.

The browser extension

The extension asks for no browser permissions beyond reaching Wanderlust's own servers, so it can't read your tabs, your bookmarks or your browsing history.

• To suggest places near you, each new tab estimates your approximate location from your IP address, refreshed at most every 12 hours. That location, or a city you choose, is sent to Google to find places nearby.
• Your settings, your home city and the list of destinations you've been shown are stored in your browser, not on our servers.
• App loads, sign-ups and similar events are counted as daily totals, without your user ID.

The iPhone app

The app asks for camera or photo-library access only when you set a profile photo, and for permission to send notifications after you sign in. It doesn't use your location, and it contains no analytics or tracking SDKs.

• If you allow notifications, we store a push token and send trip reminders through Expo and Apple's push service. Reminders can show your destination and hotel on the lock screen.
• Your sign-in is kept in the iPhone Keychain, and a copy of your upcoming trip is shared with the app's home-screen widget.

Website usage data

On the website we record which features get used, such as a trip being saved or a checkout starting, to learn what's working. Events sent from your browser carry a random ID kept in a cookie (wl_anon) for up to a year. Events our servers record, such as signing up or using an AI feature, are linked to your account.

• Google Analytics, loaded through Google Tag Manager, receives page views and these events. We don't send it your name, email address or account ID. Google Analytics sets its own cookies.
• Google Analytics doesn't log or store IP addresses. Like most web servers, ours record them in their request logs.