Privacy

Last updated 25 August 2026

The Places You Will Go builds a travelogue page from the trip you enter. This page explains what we store, why, and how to get rid of it. It is written to be read, not to be survived.

What we store

What you type in: your travelogue's name and title, and the stops you log — place names, dates and times, coordinates, notes, and photos you upload.
Your passphrase, hashed. We store a PBKDF2 hash and a random salt, never the passphrase itself. The same is true of the optional passcode you can set for visitors.
If you make an account: your email address, your name if you give one, and your password as a PBKDF2 hash. Accounts live in this project's own database — there is no "sign in with Google" here and no third-party identity provider is involved.

What we do with it

We use it to build and show your travelogue page, and to know that you are the person allowed to edit it. That is the whole list. We do not sell it, we do not share it with advertisers, and we do not use it to train anything.

Who can see your travelogue

By default a travelogue is public to anyone who has the link — that is the point of it. It is not listed in a directory, but it is not secret either. If you set a visitor passcode in your admin page, the page, its photos and its data all require that code, and we ask search engines not to index it.

Worth knowing before you post: a travelogue can show where you are right now. If you are travelling alone, consider setting a visitor passcode, or logging each stop after you have left it rather than while you are there. A stop also does not have to be your exact address — pin the bigger place instead. “Bangkok” tells your people everything they need to know; nobody needs the name of your hotel. You can always come back after the trip and sharpen the pins.

Photos help with this rather than working against it. Phone cameras embed hidden metadata in every shot — GPS position, capture time, camera details. When you attach a photo, the log book reads that location in your browser and — while the tick-box under the photo field is on — fills in the pin, date and place name from it. Then the metadata is stripped from the photo itself before it uploads, so a photo someone downloads from your page cannot say more about where you were than the pin you chose.

Where it lives

The site runs on Cloudflare. Your text lives in Cloudflare D1, your photos in Cloudflare R2, both tied to this project. Map tiles are loaded from OpenStreetMap and CARTO, and fonts from Google Fonts, which means those providers see the IP address of whoever is viewing the page — the same as on most of the web. We do not run analytics or advertising trackers.

Counting visits

We count page views so we know whether any of this is working: which pages were opened, on which day, and roughly how many separate people that was. To tell people apart within a day without knowing who they are, we store a one-way hash of your IP address and browser combined with the date — it cannot be reversed, it is not shared, and it stops meaning anything when the date changes. We do not store IP addresses, we do not use a tracking cookie for this, and there is no third-party analytics service involved.

Cookies

Only sign-in cookies. One says you are logged in to edit a travelogue, one says you are signed in to an account, and one says you have entered a visitor passcode. There are no advertising or tracking cookies, so there is no consent banner to click.

Getting rid of it

You can delete any moment from your admin page, which deletes its photo too. To delete a whole travelogue and everything in it, or to get a copy of your data, email seansp@saasaas.llc from the address on the account and we will do it.

Children

This is not aimed at children under 13 and we do not knowingly collect their information.

Changes

If this page changes in a way that matters, the date at the top changes with it.

Contact

The Places You Will Go is operated by SaaSaaS, LLC (sean-makes-stuff.com). Write to seansp@saasaas.llc.