Legal

Privacy

This site does not collect information about you as you browse it. It sets no cookies, runs no analytics, loads no tracking pixel, and contacts no third-party host while a page is open.

That is a statement about the code, and it is checkable: the project has six runtime dependencies and none of them is an analytics, telemetry or authentication package. Loading every page of this site in a browser and scrolling each to the bottom produces no third-party request and no cookie.

Two small values are saved in your own browser's local storage. Neither is ever sent anywhere — they exist so the site remembers small preferences between visits, and clearing your site data removes them.

theme

“dark” or “light”, written only when you use the theme toggle in the search panel.

search-recents

Up to five pages you have opened from the on-site search, so the panel can offer them again. The panel has a control that clears them.

The contact form does not submit anything to this site. It assembles a message and hands it to your own mail application, which sends it from your own mail account to mine.

That means the words never pass through this site, there is no form storing them, and a copy stays in your sent folder. What reaches me is an ordinary email, carrying whatever your mail provider normally carries.

The guestbook is the one place on this site that keeps what you write. Submitting stores the message and the name you chose so they can be read and, if put up, shown on the public wall. Nothing is published automatically.

That is the whole record: a message, a name, and the times it arrived and went up. No email address is asked for and none is kept. No account is created. No cookie is set by signing.

Your IP address is not stored. To stop one person flooding the wall, it is hashed with a secret salt and that hash is held for ten minutes to count submissions, then deleted. The hash is never written next to an entry and the address itself is never recorded.

A salted hash of the message itself is kept the same way for an hour, so that a double-tap or a refreshed page does not put the same card up twice. It reveals nothing the message does not, and it expires on its own.

Ask and anything you left will be removed.

No third-party code runs in your browser on any page of this site.

Links that lead off this site — GitHub, the people credited on the attribution page, the repositories behind the packages this site is built on — are governed by those sites' own policies once you follow them.

One request is made to a third party by the server rather than by you: at most once an hour, the server asks Cal.com whether a booking page exists, so the contact page knows whether to offer one. That request is made from the server and carries no information about any visitor.

It is often more useful to say what is not happening. None of the following exists here: an account you could create or sign in to, a newsletter or mailing list, advertising, profiling, A/B testing, session recording, fingerprinting, or the sale or sharing of anything about you with anyone.

The guestbook is the single exception to nothing being kept, and it is deliberately narrow: section 04 sets out everything it stores and for how long. Every other page reaches you without recording anything at all.

If any of that changes, this document changes with it, and the date at the top moves.

Every web host keeps some record of the requests it serves — typically IP address, user agent and timestamp — as a technical necessity of delivering a page. That happens below the level of this site's code.

Which host serves this site, what it records, and how long it keeps it are not established anywhere in this project, so this document does not state them. Rather than guess, the question is left open: the site owner is the only person who can answer it, and it will be answered here once he does.

If you want to know anything else about this — including what is in section 07 — write to me and ask. There is no form to fill in and no ticket to open.

When this document changes, the date at the top changes with it. There is no archive of previous versions; the current text is the whole policy.