Privacy

Last changed October 12, 2026

What we collect, why, where it sits, and how to make us delete it. If something here is unclear, write to us and ask.

Who is responsible

What this site does today

It describes what we are building. You can join the waitlist, and if we already hold your address you can sign in with a link we email you. You can answer a short set of questions about a trip so that we can make you a plan, which is free. Where something is for sale, you can put it in a basket and buy it, and you do not need an account to do that.

There is nothing for sale here yet, so today there is no basket and no checkout to reach.

The plan questions are not open yet either, so today there is nothing here to answer.

Cookies

This site sets no cookies unless you do one of three things. If you sign in, one cookie keeps you signed in. If you put something in a basket, one cookie remembers which basket is yours and nothing else about you. If you start answering the plan questions, one cookie remembers which set of answers is yours, so you can come back to them. We do not ask your permission for any of the three, because none of those things can work without one, and you can end them by clearing them in your browser. There is no analytics, no advertising, and there are no tracking pixels. One other cookie exists on a page only we can open, for our own work on orders and plan requests, and no visitor is ever given it.

The sign-in cookie lasts 7 days unless you clear it sooner, and using the site does not extend it.

The basket cookie lasts 30 days unless you clear it sooner, and buying what is in the basket ends it too.

The plan-questions cookie lasts 30 days unless you clear it sooner, and sending us the answers ends it too.

There is nothing for sale here yet, so nothing on this site can give you that second cookie today.

What we collect

Most of what we hold is there only because you gave it to us. If you type your email address into the form and tick the box beside it, sign in, answer the plan questions, or buy something, we store:

• Your email address.
• The exact wording you agreed to, the version of it, and when you agreed. We record which wording you were shown rather than a tick, because a tick does not say what you agreed to.
• How you arrived: the campaign parameters in the link you followed, the site that referred you, and the page you landed on. The referring site is stored as a domain name and never as a full address, and the landing page without anything after the question mark.
• If you sign in: the address we sent the link to, and when you signed in. We only ever email a sign-in link to an address we already hold, and every link expires. Any address typed into the sign-in form is stored until the link made for it expires, whether or not we hold it and whether or not a link was sent, and a daily job deletes it after that.
• If you answer the plan questions: which of the two you are planning around, the dates you are travelling, who is coming, how full you want the days, roughly what you want to spend, what you want out of it, and the region you are flying from. Nothing is attached to you until you ask us for a plan and give us an address. We then send a message there with a link to confirm the address is yours, and nobody starts on the plan until you follow it. From then on we also keep the plan an AI model prepares from your answers when you confirm, the changes one of us makes to it, which of us checked it, and the plan exactly as we sent it to you. Every answer is one of the choices we offer or a date or a number, so there is nowhere in these questions to type anything else.
• If you buy something: the email address you gave us at the checkout, what you bought, what it cost at the moment you bought it, and when. We keep the price as it stood then rather than as it stands now, because that is what you agreed to pay. The basket itself holds only what is in it and is not attached to you until you buy.

Two things happen whether or not you fill anything in. First, to stop automated abuse, we count how many requests the forms receive from each visitor, over a few minutes and over a day. What the count is filed under is a scrambled form of your network address rather than the address itself. A count stops counting within a day, and a daily job deletes it after that.

Second, Railway, which hosts the site for us, keeps a record of every request the site receives: your network address, which browser you use as it describes itself, the page you asked for, and when. Railway's documentation says these records are kept for 30 days on our plan. We read them only to keep the site working and to look into abuse, and nothing else is made from them.

We do not ask what you want treated and there is nowhere on this site to tell us. No health information reaches these records.

Why we are allowed to

For the email list, your consent. You can withdraw it at any time, every email we send carries a link that does it in one click, and withdrawing does not undo emails already sent. For signing in, we do not rely on consent: you asked us for the link, and an account cannot work without the address you sign in with and the cookie that keeps you signed in. For the plan questions, we do not rely on consent either: you asked us for a plan, and we cannot write one without the answers or keep your place in them without the cookie. For buying, the same: a basket cannot work without the cookie that tells us which one is yours, and we cannot send you what you paid for without the email address you gave us. For the abuse counting, we rely on our own legitimate interest in keeping these forms working, which is why it happens whether or not you sign up, and why it keeps as little as it can for as short a time as it can. For the record of requests, we rely on our own legitimate interest in keeping the site running and in looking into abuse. For how you arrived, we rely on our own legitimate interest in knowing which links and pages bring people here. It is counted across everybody and never used to decide anything about you.

How long we keep it

We delete your email address and everything attached to it 24 months after the last thing you do here. Signing up, confirming your address, signing in, sending us your plan answers and placing an order are all things you do here, and each one starts that clock again.

If you unsubscribe, we delete the record of your signup 12 months later, and your address with it if nothing else of yours is here. We keep it that long so we can prove you asked to be removed, and no longer.

Resend, which delivers our email, keeps each message it sends for us, with your address in it, for 30 days, according to its documentation. Railway's record of requests is kept for the period given above.

Who else can see it

Railway, who run the servers and the database for us. Resend, who deliver the email this site sends you. Google, whose Workspace holds our own mailboxes, so it has any email you send us and any we send you ourselves. Each processes it on our instructions and for nothing else. If we ever add another, this page says so before they receive anything.

Anthropic Ireland, Limited, whose AI model drafts your plan, claude-sonnet-5-5, on our instructions and for nothing else. It receives your answers, the region you are flying from among them, and a list of services in Seoul we might suggest, without your address or anything else that says who you are, and your dates only as the month the trip starts in and how many days it lasts. Under its terms with us, Anthropic may not train its models on what we send it. It deletes what it receives within 30 days, unless the law requires it to keep it longer or its systems flag a request as breaking its usage policy. A flagged request it may keep for up to two years, and the scores its safety systems gave it for up to seven.

Where it is kept, and where it is read

Our database is on servers in the Netherlands, in the European Union. We work on it from Germany and from South Korea, and your plan may be checked from either, so what you send us for it may be read in either country. The European Commission has recognised South Korea as protecting personal data adequately, in what EU law calls an adequacy decision, and that is what we rely on for it to be read there. If we ever move our database, or work on it from another country, this page says so before that happens.

Railway, Resend and Google are American, and some of what they hold for us is, or may be, in the United States. Resend sends our email from Ireland, and keeps each message it sends, with your address in it, in the United States. Railway says its own work happens mainly in the United States, so the record of requests may be kept there. Google may keep our mailboxes in any country where it or the companies it uses have data centres. Each of them has data processing terms with us that protect your data when it leaves the European Union, with the European Commission's standard contractual clauses or another safeguard EU law recognises, and that is what we rely on for it to go there.

Anthropic Ireland, Limited processes your plan answers in the United States, where Anthropic keeps what it receives, and in whichever countries Anthropic runs its AI models at the time, and sending them there rests on the European Commission's standard contractual clauses, which Anthropic's data processing terms with us include.

What you can make us do

Write to the address above and we will do any of these. You do not have to give a reason and it costs nothing.

• Tell you exactly what we hold about you.
• Correct anything that is wrong.
• Delete what we hold. Your records in our database go in one operation, not a flag saying to ignore them, and we delete the emails between us from our own mailboxes.
• Stop using it while a disagreement is being sorted out.
• Send you a copy in a form you can take elsewhere.
• Stop processing it.

Seeing what we hold and deleting it reach the copies the companies above keep for us too, with two limits. The messages Resend sent you we can find by your address, and we ask Resend to delete them rather than wait for its own period to end. Railway's record of requests is filed by network address, so we can find yours only if you tell us what it was, and nothing we have found removes it sooner than Railway's own period.

You can also complain to a data protection authority in the country where you live, without going through us first.

Automated decisions

There are none. An AI model drafts your plan from your answers, and one of us reads and checks it before it is sent, so nothing about you is decided by a machine, and no profile is built from what you give us.

Changes to this page

We will update it when what we do changes, and before rather than after. The date at the top is when it last changed.