What we store, in plain terms

When you save a trip

Building a plan and looking at it stores nothing about you. The first time you tap “Save this trip”, we create an anonymous session for your browser — an identifier with no name, email or password attached — so the trip can be found again later on the same device. Answering a question on your profile does the same thing, the first time you save one.

Once you save a trip, we store your itinerary (the ordered days and stops), the lodging you told us you’re staying near, and the interview answers that shaped the plan — pace, walking limit, and whichever preferences you answered.

When you edit a saved trip

Removing a stop, reordering a day, moving a stop to another day, clearing a day’s stops, or restoring one you removed is recorded as an event — what you changed and roughly when — separately from the itinerary itself. We use these events to learn where a generated plan didn’t match what a traveller actually wanted, so future plans can be better. An event records that an edit happened, never anything about you beyond the trip you were already editing.

If you try to place a stop somewhere the plan reserves for Shabbat or a holiday, that attempt is recorded the same way — it’s the clearest signal we get that a plan didn’t fit a real traveller, and recording it changes nothing on your screen.

If your trip is ever deleted, its edit history is deleted with it — nothing about your edits outlives the trip they belong to.

What we don’t ask for

No account and no email address are required to plan or save a trip on the free plan. There is no password to lose and nothing to verify. A display name is optional and used only if you choose to set one on your profile.