Privacy Policy

TripSapien turns submitted travel recommendations into a validated trip plan. This policy explains exactly what data the TripSapien website and the TripSapien “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 saves places in your own Google Maps session. Its limited lifecycle analytics and local storage are described below.

The TripSapien 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 magic links 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, and Ticketmaster (events). Public-holiday checks use generated date-holidays data. Provider responses are cached briefly to reduce repeat lookups.
• Parsing. The text you submit 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 TripSapien tab you triggered it from, passed directly to the extension through Chrome’s messaging API.
• Limited lifecycle analytics. The store build sends install, update and browser-start events to Google Analytics to measure installation and browser-start activity. These events include a random persistent per-install identifier (a pseudonymous ID), a session ID, an engagement marker and, for updates, the previous extension version. They do not include your itinerary/place list or Google account details. The save flow passes your selected places to Google Maps in your signed-in session.
• What it stores. Run/resume state (including the selected places, progress and the list’s ID) and the lifecycle session ID are held in chrome.storage.session, which Chrome clears when the browser closes. The random install identifier remains in local storage across browser restarts in chrome.storage.local. It is not a TripSapien account identifier.
• 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 run/resume state and analytics identifiers described above. alarms: a keep-alive so the save run is not interrupted if Chrome idles the extension mid-run. externally_connectable is limited to TripSapien’s own domains and localhost, so only a TripSapien 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’s limited lifecycle analytics are described above. 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. A deleted trip leaves your dashboard immediately and is permanently purged within 30 days. 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 TripSapien team via www.tripsapien.com. We will update the “last updated” date above when this policy changes.

See also our Terms of Service.