What this site collects

The short version

• No cookies are set by this site.
• No analytics script, no advertising script, no third-party pixel.
• No accounts, no passwords, no advertising identifier.
• Your trip, your map and your checklist stay in your own browser.
• We do not sell data and we do not pass it to data brokers.
• This site does not publish an email address, because no mailbox is configured on it.

What the request form stores

Some destination pages carry a short request form ("leave your details and we put you in touch with the operator running this trip"). If you fill it in, these are the fields, and these are the only ones:

• Name

  Your name, so the operator knows who is asking.

• Email

  Your email, so somebody can answer you.

• Phone (optional)

  Only if you type it. It is stored as you write it.

• Message (optional)

  Only if you write it. It is stored as you write it.

The request is written to our own database, together with which destination you asked about and the date. It does not stay in your browser after you send it. From there it goes to the site's team, which passes it to the operator of that destination, and to the delivery channel the site is configured to use, if one is configured.

What is recorded automatically

When you click a link that leaves the site, the click is counted. These are the fields of that count:

• Page

  Which page the click left from.

• Route

  The address on the site.

• Language

  English or Spanish.

• Intent

  Whether the click went to a booking link or to a tool.

• Partner network

  Which marketplace the click went to, when it went to one.

• Date and time

  When the click happened.

No IP address is stored, no user agent, no advertising identifier. The count tells us which pages are useful, not who you are: there is nothing in it that identifies a person.

What stays in your browser

The trip planner, the map builder, the budget calculator, the packing list, the altitude guide, the moon calendar and the shortlist all save in your browser's local storage. Nothing is uploaded and there is no account: if you clear the browser data, the plan is gone.

There is one deliberate exception: the "save and share" option in My Trip. When you use it, a copy of your trip is stored on our server under a random eight-character code, and anyone who has the link can read it. That is the whole point of sharing, and it is your decision to press the button.

Cookies, trackers and fonts

This site sets no cookies of its own and loads no analytics or advertising script. It does load its typefaces from Google Fonts, which means Google sees your IP address at the moment the page loads. That is the only third-party request the site makes, and we would rather say it than not.

Who can see what you send

• The site's team, in the site's own internal panel, so somebody can answer you.
• The operator of the destination you asked about, because the form exists to put you in touch with that operator.
• The delivery channel the site is configured to use, if one is configured: a webhook that receives your name, email, phone and message so the request can be routed. The site ships with that channel turned off, and this page does not claim it is on.
• Nobody else. We do not sell the data and we do not hand it to advertisers or brokers.

Asking us to delete your data

Use the same request form and write "data deletion request" at the start of the message, with the email address you used. We delete the row from our database.

Two honest notes about that channel. This site does not publish an email address, because no mailbox is configured on it — a printed address would reach nobody. And the form belongs to a destination, so the message is read by that destination's operator as well as by us. If you would rather we did not pass it on, write "do not forward" in the message and we handle it here.

AI assistants and crawlers

Every response from this site carries a "Content-Signal" header withai-train=no, ai-search=yes. In practice that means: we do not authorise the use of this site's content to train models, and we do authorise search engines and AI search assistants to read it and cite it. The robots file says the same thing in a way any crawler can read: the search crawlers and the AI search crawlers are welcome, and Common Crawl, the corpus that feeds many training runs, is blocked.

We also publish the site on purpose for assistants: the open manifest, the full text export and the map protocol are all public. They carry the same rules — cite them, do not train on them.