Legal

Privacy Policy

Last updated: May 18, 2026

ValidaTrip turns pasted travel recommendations into a validated trip plan. This policy explains exactly what data the ValidaTrip website and the ValidaTrip “Send to Google Maps” Chrome extension touch, why, and what we do not do. It is written to be read, not to be survived.

Short version: we do not sell your data, we do not run advertising trackers, and the Chrome extension sends nothing to us — it runs entirely inside your own browser session.

The ValidaTrip website

When you create a trip, the text you paste and the resulting places (names, addresses, coordinates, hours, booking links) are stored so the trip can be shown back to you. Trips you create while signed out are associated with a random ID kept in your browser’s localStorage; trips you create while signed in are associated with your account.

• Account & auth. Email/password or Google sign-in, handled by Supabase Auth. We store your email and an account ID. We never receive your Google password.
• Trip content. The recommendations you paste and the enriched place data are stored in our database (Supabase) so your trip persists. You can delete a trip at any time.
• Place enrichment. To check hours, closures, and booking links we query third-party providers with the place names/locations in your trip: Google Places, OpenStreetMap/Nominatim, Ticketmaster (events), and Nager.Date (public holidays). Provider responses are cached briefly to reduce repeat lookups.
• Parsing. Pasted text may be sent to an LLM provider (OpenAI or Google Gemini) solely to normalize it into structured trip items. It is not used to train models by us.
• Analytics. We measure aggregate usage with Amplitude and Google Analytics 4 (page views and a small number of product events such as sign-in). You can exclude your own devices via the internal-traffic cookie. We do not use advertising or cross-site tracking pixels.

The “Send to Google Maps” Chrome extension

The extension exists for one purpose: when you click “Send to Google Maps” on a trip, it recreates that trip’s validated places as a private saved list in your own signed-in Google Maps. This is the entire single purpose of the extension.

• It runs only in your browser. The extension automates the Google Maps “Save” UI on your machine, in your signed-in session. The list of places comes from the ValidaTrip tab you triggered it from, passed directly to the extension through Chrome’s messaging API.
• It sends nothing to ValidaTrip or anyone else. There is no ValidaTrip server call from the extension, no analytics in the extension, no remote code, and no third-party SDKs. The places never leave your browser except to go into your own Google Maps list.
• What it stores. Only transient run state (which place it is on, the new list’s ID) in chrome.storage.session, which Chrome clears when the browser closes. Nothing is stored persistently.
• Permissions, and why each is needed. tabs and host access to https://www.google.com/*: to open a Google Maps tab and drive the Save-to-list flow. storage: the transient resume state above. alarms: a keep-alive so the save run is not interrupted if Chrome idles the extension mid-run. externally_connectable is limited to ValidaTrip’s own domains and localhost, so only a ValidaTrip page can hand it a trip.
• It does not read your browsing history. Chrome labels the tabs permission as “read your browsing history,” but the extension only opens and inspects the Google Maps tab it created for the export. It does not read, collect, or transmit your history or other tabs.

What we do not do

We do not sell or rent your data. We do not share it with data brokers. We do not use it for advertising. The extension does not transmit your data to us at all. Trip data is shared with the place/LLM providers listed above only as needed to validate and enrich the trip you asked us to build.

Retention & deletion

Trips persist until you delete them or, for signed-out trips, until you clear your browser storage. To delete account data, delete your trips and contact us to remove your account. Provider lookup caches expire automatically.

Contact

Questions about this policy or a data request: reach the ValidaTrip team via www.validatrip.com. We will update the “last updated” date above when this policy changes.

See also our Terms of Service.