WanderWise

Privacy

WanderWise uses your account name and email to authenticate you and associate saved trips with your account. Password sign-ins store a password hash. Google sign-ins use Google OAuth.

Your messages and trip preferences are sent to Google Gemini to generate plans. Attraction queries and candidate selections use Google Places, and route coordinates are sent to Google Routes. The browser loads Google Maps directly. Avoid including sensitive personal information in trip requests.

Saved itinerary text and Google Place IDs are stored in MongoDB until you delete the trip. Place IDs let WanderWise refresh the exact saved locations. Coordinates, canonical Google addresses, attributions, discovery results, routes, and other map results remain temporary and are not saved with your itinerary. Operational logs record request identifiers, endpoint names, status codes, and timings.

Trips are private by default. If you enable sharing, anyone holding the link can view your saved itinerary. Revoke the link to stop future access; recipients may already have made their own copies.

Google services process data according to the Google Privacy Policy. Authentication uses session cookies. You can delete saved trips in My Trips.