Privacy

Trippie stores account details, sessions and shared trip content for invited members. No email is required; Trippie stores a display name, protected PIN credentials and hashed invitation tokens. Trip members can read shared notes, saved places and source recommendations. Owners manage membership and deletion.

In live import mode, submitted public Reel URLs are sent to Apify. Bounded caption or transcript text and trip destination context are sent to Groq, with OpenAI as a fallback. Place names and destination context are sent to Geoapify. Their account-specific data policies apply. Trippie does not store videos or complete raw provider responses. It keeps a resized copy of each Reel’s cover picture for trip members.

When a member looks for photos, a place’s name, city and map location are sent to Wikimedia Commons, and cover searches are sent to Unsplash. Uploaded cover photos are resized and stripped of camera details such as location. Unsplash covers and photo search previews load from those services in your browser.

To work without a connection, your browser keeps copies of the trip pages you open, their photos and the map areas you view, on that device only. They are removed when you sign out or another account signs in there.

Configured map services receive normal browser tile requests and the viewed map area. Source links open Instagram independently. Contact your installation operator about account removal, provider policies, backup retention or your data. Deleting a trip removes its active records; retained operator backups may expire separately.