Privacy

Local trips and preferences

Guest trips are stored in your browser by default, including itineraries, travel details, notes, checklists, progress and rescue state. Travel preferences and display settings also use local browser storage. Data is specific to the browser and website address used; clearing browser storage may remove it. Local planning does not mean all activity stays on your device: provider requests and the limited production analytics described below can still occur.

Optional accounts and cloud trips

You can use guest planning without an account. Where account services are configured, Supabase handles email/password sign-in, password recovery and authentication sessions. Signing in uses authentication session storage; this is separate from analytics. Supabase receives account credentials and maintains an account identifier.

For signed-in users, supported trip saves and edits can sync saved-trip data to Supabase under that account. Saved-trip data can include destinations, dates, preferences, itinerary places, logistics and reservation details, traveler-entered notes, checklists, progress and rescue state. These cloud records are private to their owner under database access rules, not public share records. Failed sync operations may remain queued locally for a later attempt. Guest trips are not automatically uploaded merely by visiting the site. Do not enter information you do not want stored with a trip.

Public sharing

Anyone with a shared-trip link can view and forward its read-only public snapshot. It includes itinerary text, destinations, dates, travel timing, places and public logistics details, which may include flight numbers and hotel names. Dedicated private notes, booking references, confirmation details, custom checklist labels, action history, assistant messages and travel profile data are omitted. Information typed into public activity titles or descriptions can still be shared; review the snapshot before sending it.

New share links carry the snapshot in the URL fragment, not a private cloud-trip lookup, and support up to 200,000 encoded data characters. Larger snapshots are not copied. Legacy query-based links can also be read. A copied snapshot is not revoked by deleting the original trip, and recipients may retain their own copy.

Product analytics

In production, Command Center and Trip Rescue interactions send limited first-party usage events to TripQuarry for storage in Supabase when ingestion is configured. Events contain the interaction type, receipt time, day index, and applicable stop period, fixed check-in choice or rescue action. They do not include trip details, destinations, notes, reservation data, names, email addresses or coordinates. No analytics cookies, account identifiers or fingerprints are added. Event rows are not readable by browser users. The public demo does not send these events. These events help us understand use of those features, not advertise to or track users across other companies' services.

Places, routes and weather

When enabled for a deployment, Google Places receives place searches and destination or geographic context through TripQuarry's server, and Google Routes receives route endpoints and travel-mode information. Visual Crossing receives requested itinerary-place coordinates and forecast dates when its weather service is configured. These are trip locations, not a claim that we continuously track your device location. Unconfigured or unavailable services may show fallback information instead.

Provider requests and website hosting involve normal network information. Providers and hosting services may keep operational logs, including IP addresses and request details, under their own terms. See Google's privacy policy and Visual Crossing's privacy policy. Opening an external travel-provider link is subject to that provider's practices. Sample flights, hotels, cars and activities are not live bookings or live availability. TripQuarry does not process payments or make provider bookings in this beta, and an external AI model is not connected.

Support and data choices

Email support receives your email address and anything you choose to send. In-app feedback does not automatically attach your trip; avoid including sensitive information in either channel. Support information is used to respond to your request.

Use data controls to export or clear local trips and preferences. Exports may contain private trip information, so protect your downloaded file. Clearing local data does not delete cloud records, authentication sessions or your Supabase account. Signed-in users can initiate permanent account deletion from the separate Delete TripQuarry account section: open confirmation, type DELETE, and choose Delete my account permanently. After a successful deletion, the Supabase account and owned cloud-synced trips, including account identity and trip notes or reservation details stored there, are removed. There is no separate cloud profile table in the current product. The browser signs out and pending cloud-sync operations are cleared; local trips and preferences remain unless you separately clear them.

Account deletion does not erase previously shared public snapshots or recipient copies, support emails, operational logs, external provider records or analytics events that have no account identifier and cannot be tied to an account. Optional feedback records are subject to separate retention; where the reference feedback table is deployed, deleting an account clears its account link rather than deleting the feedback. A failed deletion may have completed cloud trip cleanup before account removal failed. Retry or contact zack@tripquarry.com for help; do not assume completion until success is confirmed. Other privacy requests may require ownership verification. This notice does not promise a fixed retention period or immediate erasure of backups and third-party records.

TripQuarry support | Account