Privacy

The short version

We store what you put into a trip so we can show it back to you and to whoever you send the link to. We send the things you paste to Anthropic so they can be read into an itinerary. We don't sell anything to anyone, and we don't run advertising.

What we store

• —The trip itself: name, destination, dates, occasion, theme, and every item on the itinerary — including confirmation numbers, if you paste them.
• —Anything you paste or upload: booking text, screenshots, PDFs, cover images and board images.
• —Traveller names and their RSVP answers.
• —Comments, reactions and outfit votes, along with the name whoever left them typed in.
• —An anonymous creator key, stored in a cookie in your browser, which is how we know a trip is yours before you have an account.
• —Your email address, only if you sign in with a magic link or enter it at checkout.

Confirmation numbers and addresses you paste are stored as written and shown to anyone with the trip link. Don't paste passport numbers, card details or anything you wouldn't want a link-holder to read.

Who else sees it

These are the services TripTini relies on, and what each one receives:

Supabase

Hosts the database and the image storage. All trip content lives here.

Stripe

Processes payments and holds your billing details. We never receive your card number.

Anthropic

Receives the text, screenshots and PDFs you paste in, so it can turn them into itinerary items — and the trip's destination, dates and occasion when generating suggestions or meal research.

Vercel

Runs and serves the application. Handles standard request logs.

Open-Meteo

Receives a destination's coordinates to return a forecast. No personal data.

Google Places / Unsplash / Openverse

Receive a venue name and city to return a photograph. No personal data.

Mapbox

Renders the map view in your browser, if it's enabled on this deployment.

Pinterest

Receives a board URL you paste, to import its images.

Some of these are outside your country. Which ones are configured depends on this particular deployment.

Who can read your trip

Anyone with the link. Trip URLs contain a random, unguessable component and carry a no-index instruction for search engines, but they are unlisted rather than private — there is no password. A co-editor link additionally lets its holder change the itinerary.

If a name is typed into an RSVP, a comment or a vote, that name is visible to everyone else with the link. Your browser remembers the last name you used, locally, so it doesn't have to ask again.

Cookies

We use one functional cookie: an anonymous creator key that identifies your trips before you sign in. Your colour-mode preference and the name you last used are stored in your browser's local storage, not sent to us. There is no analytics or advertising tracking.

How long we keep it

Trips are kept until you ask us to delete them, because the point of a paid unlock is that the itinerary stays available. Venue photographs are cached for 30 days and then refetched.

Getting your data out, or deleted

Every unlocked trip has a PDF export and a calendar export built in. For a full copy of what we hold, or to have a trip and its images deleted permanently, email hello@example.com from the address you used, or include the trip link. We'll action it within 30 days.

Depending on where you live you may have additional rights — to access, correct, export or object to our use of your data. The same address handles those.

Children

TripTini isn't intended for under-13s and we don't knowingly collect their data.

Contact

hello@example.com