What touches a browser
What Touches a Browser Here
Four rows, and the fourth is not this site's. There is no consent wall on this domain, because nothing is stored until a reader answers a card that sits in the flow of the page rather than over the reading.
The four
| Thing | Kind | What it is for | How long |
|---|---|---|---|
The word recording that the storage card was answered, stored under the key tl_card_read | Local storage, this domain only | So a reader who has answered is not asked again | Until site data is cleared |
| The stylesheet, the faces, the images and the two scripts | Ordinary browser cache | So a second page loads without fetching them again | Whatever the browser decides |
| The place list the fare lookup offers | Ordinary browser cache | So the field can suggest cities without asking the server each time | Whatever the browser decides |
| Whatever the booking service sets, once a search is submitted | That service's own storage on its own subdomain | Its business, described in its own notice | Its own term |
The first row is the only thing this site deliberately writes, and it is written only after a reader presses one of the two buttons on the card.
There is no cookie on this domain
Not as a technicality. This site sets no cookie at all: the one thing it stores is a single word in local storage, on this domain, on the reader's own machine, and it never travels with a request.
That word carries no identifier, no number, no timestamp that would order visits, and nothing that could be joined to anything else. It says either that the card was accepted or that it was refused, and both answers make the card go away.
Why there is no consent wall
Because there is nothing to consent to before a page is read. Nothing is stored on arrival, nothing is measured, and nothing third party runs, so a wall across the reading would be theater.
The card sits above the footer, in the flow of the page, and can be ignored indefinitely without any effect on anything. Refusing it stores the word saying it was refused, which is the smallest honest way to remember an answer. A reader who wants nothing stored at all can simply not press either button, or clear site data afterwards.
How to be rid of all of it
Clearing site data for this domain in the browser removes the word and the cached files together. No account exists here, so there is nothing to close and nobody to notify.
The fourth row is not this site's to clear. Storage set by the booking service on its own subdomain is governed by that service, and clearing it is done the same way in the browser.
Absent by design
No advertising or measurement identifier of any kind. No pixel, no beacon, no fingerprinting. Nothing that recognizes a device across visits and nothing that recognizes it across sites. No script from anybody outside this domain, on any page.
Reviewed August 9, 2026.