What happens, in order, from the address bar onwards

Last revised 11 September 2026.

Written as a sequence rather than a list of categories, because the sequence is short and nothing survives the end of it. There are no accounts on this domain.

Step one: the request

Your browser asks this server for a file. The server appends a single row — which file, at what moment, the status and byte count sent back, the network address the request came from, a referrer if one was volunteered, and the user-agent string the browser announces itself with.

Step two: the page arrives

Nothing on it reaches out to a third party. No analytics, no advertising beacon, no session replay, no embedded frame, and the lettering is served from this domain rather than a font network, which would leak the visit by a side door.

Step three: two values are read

A short script looks in your own browser storage for the colour scheme you last chose. If there is nothing there it asks the operating system and stops. If the age prompt has not been answered on this device, it appears, and your answer is written to the same local storage and transmitted nowhere.

Step four: the row ages out

The file those rows land in rotates on a timer and is discarded. It keeps the machine upright and separates readers from the automated crawling that reaches every public address continuously. Nothing is built on top of it and nothing is compared against it.

Step five: the link, where this stops

Following it hands you to another company on other hardware under terms of their own, effective from the moment the page changes. Whether calls are recorded there, and for how long anything is kept, are questions for them and unanswerable from here.

Two things outside the sequence

Nobody under eighteen should be reading this, and the control that reaches a person able to act sits inside the chat. Revisions announce themselves by the date under the heading.