What Troovi
knows about you.

So you can sign in. We send a one-time code to your inbox. No password ever.

A display name, an avatar if you upload one, an optional bio. Everything except the name is optional.

The trip itself plus its activities, days, votes, comments, bookings, and photos.

Photos and documents you attach to a trip or activity, kept in storage scoped to that trip.

Only you and our auth system. Other members of your trips never see it.

People you share a trip with. Database row-level security blocks anyone else.

Only members you invited. There is no public discovery, no search index, no feed. Read-only share links work without sign-in but only reveal what’s on that link.

Served through short-lived signed URLs to trip members. The bucket is private.

Our primary stop. Hosts authentication, the database, and file storage. Everything we collect lives here.

When you search for a place or view a map. Mapbox sees the location query, not who you are.

When you use an AI feature — generating a trip, suggesting activities, or Ask AI — what you typed and the trip it relates to are sent so a draft can come back. Also when a travel advisor imports a supplier quote: the document itself is sent so its prices and dates can be read, and quote documents often print traveler names and dates of birth. Nothing else is sent, and never for advertising.

No analytics. No advertising trackers. No third-party scripts pulling rings around the page. Just an auth cookie.

From the trip menu. The trip, its activities, votes, comments, photos, and bookings all go with it.

From the People panel. Your votes and comments remain attached to the trip you left, but tied to your display name only.

A formal in-app flow is on the roadmap. While we’re in alpha, ask the person who invited you to Troovi — they’ll take care of it.

Same as above for now. A proper exporter is coming with general release.