Skip to content
Salt & Streetlight
Menu

Privacy

This page says what this site does with anything you choose to give it, and what it does not do. It is written from what the site's own code does, not from a template.

What you can choose to give me

The waitlist is the only thing on this site you can choose to give me. It asks for your email address, and under it there is one optional question about how you travel.

The travel question has six choices of its own and a seventh that lets you type a few words. Anything you type there is cut at 200 characters before it is stored.

You can skip this one. Leaving it blank is fine and nothing changes.

The contact page collects nothing at all. It opens your own email app, so your message goes from your own account to my inbox and never passes through this site.

Two hidden things sit in the form that you never fill: a field hidden from people, which is there to catch bots, and a note of the moment you sent the form, which is checked to drop a signup sent faster than a person could send one and then thrown away. If the hidden field is filled in, nothing at all is stored.

What is stored, and where

Five things, at most: your email address, the page you signed up from, the travel answer you chose, the few words you typed if you chose the seventh answer, and the tag on the link that brought you here, if that link carried one.

It goes into one table in this site's own database, a managed Postgres service. The row also carries an internal number of its own and the time it arrived, read from the server clock and not from yours.

Your address is also what stops the same person being added twice. A second signup with an address already on the list stores nothing and changes nothing.

If you skip the travel question, nothing is stored for it. Not an empty answer, no answer at all.

The address is kept for one thing only: the note I write when there is something. It is not used for anything else.

The site itself has no way to send mail. Anything you get from me is written by hand.

One honest caveat. If a signup cannot be saved, this site writes one line to its own log. As the code stands today that line does not contain your address, because a setting which would add it is switched off. Switch that setting on, or change how the error is read, and the line could contain it.

It stays on the list until you ask me to take it off.

What this site never receives

Your card number, its security code, its expiry date, the name on the card and your billing address. There is nowhere on this site to type them, because nothing here can take a payment.

Your IP address and the name your browser sends about itself. The code that answers a form reads only what it needs to reply, and it stores none of it.

Any password, because there is no account here to have one.

Your message. It never touches this site, and the contact page keeps nothing about you.

What your browser is set, and what else runs there

No cookie is set by this site's own code.

The library that moves you between pages keeps two small notes in the browser's own tab storage. One remembers where you had scrolled to on a page. The other appears only if part of a page fails to load and the page reloads itself once. Both are gone when you close the tab.

The fonts are served from this site itself, not from a font service.

Every image comes from this site's own address.

The only scripts that run on a page are this site's own.

The small icon in the browser tab is drawn into the page itself, so it is not a request to anywhere.

Three footer links, to Instagram, to Pinterest and to TikTok, leave this site when you click them and not before. From then on their own notices apply.

The address link on the contact page opens your own mail app. It looks like something the site is doing, and it is not.

A link you point at is fetched from this site a moment early, so the next page is quick when you click it. That is a request to this site and to nowhere else.

What is shared, and with whom

Nobody.

Nothing on this site sends anything about you to anyone else. Your address is not sold, not rented and not passed on, and there is no mailing list service behind this site at all.

Your signup sits in this site's own database, and that is the only place it goes.

There is no button here to take your address off the list, and nothing removes it on its own. Write to me through the contact page and I will take it off myself, by hand.

This site is served by a hosting service, and any record that service keeps is not something this site's own code controls.

What this site does not do

It adds no analytics script, no advertising pixel, no tag manager and no cross-site tracker. Nothing about your visit is measured, and nothing here follows you on to another site.

It has no mailing list service behind it, and no newsletter sent on a schedule.

It asks you for no account, no password and no profile. There is nothing to sign into.

Nothing on this site reads the list back out, and nothing here mails it.

It carries no price, no basket and no inventory, and nothing on it is for sale.

It does not promise how fast I will answer, and nothing here guarantees a reply at all.

It has no code that deletes an address on its own. There is no delete button and no automatic tidy up.

Logs, and one thing I can say only with a condition on it

The code that serves this site has eight places that can write a line to a log. One of them sits on the signup path, and it runs only if the database refuses to store a signup.

That line holds the error the database raised. The database client attaches the values of the query to an error and keeps them hidden unless its debug setting is on, and this site never turns that setting on.

So, as the code stands today, the address you leave does not print in that line. That is a condition rather than a promise, and the condition is a setting: turning the debug setting on, or a runtime that lists hidden values, would put a submitted address into a log line.

The one failed signup on record wrote a line with no address in it. A change that logs a fixed line instead of the error object is queued, and when it lands this paragraph gets shorter.

The payment rehearsal, and why nothing there is live

A test payment page was built for this site and then switched off. Today it cannot be reached at all: the page that would start a payment, the pages that would follow it, and the addresses behind them, all answer as a missing page.

Those addresses are also held out of the file that tells crawlers where they may look.

The rehearsal carries two draft pages of its own, one about privacy and one about terms, held behind the same switch. What you are reading is this site's own page, not either of those.

If it were ever opened, here is what it would hold: one row for each paid order, with the payment reference Stripe gives that order, the email you typed into Stripe's own page, the product name, the amount and the currency, whether the order was a test or a live one, the time it was recorded, and how many times a download link was used.

Even then it would run test payments only and would refuse a live one outright, and a buyer would never be added to the waitlist.

Card details would never reach this site's server: no card number, no security code, no expiry date, no name on the card and no billing address. No customer reference, no IP address and no browser name would be held there either. Those are typed into Stripe's own page, and Stripe's own notice covers them.

The support address on those draft pages is a placeholder that cannot receive mail. It is printed that way on purpose, so nothing there looks real that is not.

Nothing in that lane can take money from anyone today, because the whole of it sits behind one switch that is off.

If you want to ask me something, or to come off the list, the contact page is the way in.

Contact

A real person reads this, and it is me.

Terms