Privacy Policy

Last updated: 16 October 2026

English only, for the same reason as the Terms of Service - see that page.

This describes what decide (the "Service"), operated by Robert Petrov, collects, why, and how it's used. We don't sell your data, and we don't use third-party advertising or tracking cookies - the only cookies decide sets are a session cookie that keeps you signed in and, if you vote on a shared trip, a random id that stops a vote being counted twice.

What we collect

Email address

If you sign in (magic link) or subscribe to Pro - identifies your account, sends sign-in links, and links your Stripe subscription to your account.

Trip details you type in

Destinations, dates, budget, party size/description, interests, and any constraints - sent to Anthropic (maker of the Claude model that powers generation) to produce your itinerary.

Ask a Local questions

Sent to Anthropic to generate an answer. On a Pro account, a question may also trigger a live web search (via Anthropic's search tool) when it needs current information.

Photos you attach to a question (Pro)

Sent to Anthropic to answer the question about them, and never stored by decide - not on our servers, not in our database. They exist for the length of that one request and then they're gone. They stay visible in your browser for the rest of that conversation only, and disappear when you reload or leave the page. Photos in this context are often of hotel rooms, menus, receipts or documents, so avoid including anything you wouldn't want read by a third-party AI provider - passports, boarding passes, card numbers.

Booking confirmations you paste in (flight-history import)

Sent to Anthropic once, to read the flights out of them, and never stored by decide - not on our servers, not in our database. Only the flights you then confirm are saved, and only as airports, dates and airline. Passenger names, booking references, ticket numbers and payment details are explicitly excluded from what we extract, and the email text itself is discarded as soon as the flights are read. Import your own bookings only.

Visited-countries data

If you use that feature: stored against your email if you're signed in, or only in your own browser's local storage if you're not.

IP address

Used briefly, and only, to apply anonymous rate limits that prevent abuse. Not linked to your account or stored long-term.

Payment information

Handled entirely by Stripe. decide never receives or stores your card number - only your email, a Stripe customer ID, and your subscription status.

Aggregate usage counts

E.g. how many trips were generated per day, per language. Not tied to any individual visitor - used only for our own internal stats.

Trips you publish

If you publish a trip you planned while signed in, a copy of the plan becomes a public page: the plan, the cities, the number of days and who it was for in your words. Never your name, email, budget or anything else you told us. Kept until you take it down.

Evening trip emails

If you switch them on for a trip you planned while signed in - a flag on that trip, so we email tomorrow's plan to your account's address the evening before each trip day. Every email has a one-click stop link. Deleted with the trip.

How was your trip?

The day after a trip you planned while signed in ends, we email your account's address once to ask how it went. If you tap an answer, we keep it with the trip's cities and any note you add - not your email or name - for about 13 months, to see where plans go wrong.

Invites

If you share your invite link: a random code for your account, and which account each friend who joined came from, so each of you gets your free trip once. The link itself never contains your email.

Votes on a shared trip

If you tap Keep or Skip on a trip's line - the vote, tied to a random id in a cookie (decide_voter) so a second tap changes it. Only the counts are shown, never who voted. Deleted with the trip.

Where it's stored

Upstash Redis, a hosted database, for everything the product does while you use it. Finished trips are also copied to a Postgres database hosted by Neon in the EU (Frankfurt), where they are kept for exactly as long as below and then deleted. A trip made while signed in is stored with your email address, so it appears under "Your trips" on any device you sign in on. Only you see that list.

Who we share it with

Travelpayouts - a script that credits bookings made through our links to decide. It sees the page's links, not your trip details or account.
Anthropic - trip details and questions, to generate itineraries and answers.
Stripe - your email and billing details, to process subscription payments.
Resend - your email address, to deliver sign-in links.

Depending on what's configured on a given deployment, Google Places, Amadeus, and Open-Meteo may also be queried for destination, venue, flight, or weather information - these receive search terms about places, not information that identifies you personally.

City suggestions in the trip form come from GeoNames, licensed under CC BY 4.0. What you type there is looked up on our own server and is not sent to GeoNames.

How long we keep it

Generated trip records: 30 days, or about 13 months for a trip made while signed in, so a trip planned months ahead is still there when you travel. The same in both databases above. Usage/quota counters: roughly 40 days. Account and subscription records, and visited-countries data (if you're signed in): kept for as long as your account exists.

Your rights

You can request a copy of your data, ask us to correct it, or ask us to delete your account and associated data at any time by emailing petrovrobart@gmail.com. If you're in the EU/UK, this includes your rights under GDPR - access, rectification, erasure, portability, and objection.

We don't currently offer a self-service "delete my account" button in the app - deletion requests are handled manually once we receive your email.

Children

decide isn't directed at children, and we don't knowingly collect data from anyone under 16.

Changes

We may update this policy from time to time; the "Last updated" date above will change when we do.

Contact

Questions about this policy, or to exercise your rights above: petrovrobart@gmail.com.