This page is short because there is not much to describe. WebTumble is a set of static files. It runs no analytics, serves no advertising, sets no cookies and loads no third-party script, so the great majority of what a privacy policy normally has to account for does not happen here at all.
What the site does not do
There is no measurement product here, and equally no container tag, no tracking image, no heatmap recorder and no session replay. Advertising is absent, so an advertising identifier has nowhere to come from. Nor is any social embed present, which matters: an embed reaches its own provider the moment a page loads, whether or not a reader touches it. The typefaces come off this domain rather than a type service, so no font request tells a stranger what you are reading.
Nothing is written to your machine, for any reason, and that is why no consent dialogue ever appears. Saying it outright is necessary because a missing dialogue usually reads as something forgotten. A dialogue is a request for permission, and nothing here asks for any.
The decoders
Three tools on the site accept text: the record field decoder, the DNS record decoder and the lifecycle calculator. All three parse entirely in the browser. They contain no code that sends anything anywhere, they write nothing to browser storage, and they work with the network disconnected, which is the easiest way to confirm the claim rather than take it on trust.
That design is not primarily a privacy decision. It is what is left after the services these tools would once have queried closed, which the report on closed measurement tools sets out. The privacy property is a consequence of it, and a welcome one.
What the server records
Handing over a page writes one ordinary access record: the path asked for, the status returned, the moment, the originating network address and the browser identification string. That is the least a server can note down and still be operable and debuggable. It feeds no aggregation, assembles no picture of any individual reader, and goes nowhere else. Records are cycled out and destroyed on a short rhythm.
Requests are served over a content delivery and certificate layer, as essentially all sites are, and that layer keeps its own operational logs for the same reasons. Nothing in that path is configured to collect more than delivery requires.
Links away from the site
The catalog is made of pointers, so most pages link outward. Following one of those links puts you on somebody else's site, under their terms and their own practices, for which nothing here can answer. Every source carries the host it sits on for exactly that reason: the destination is legible before the click, not after it.
Your rights, and how to exercise them
Because no personal data is collected through the site, there is generally nothing held to access, correct or delete. Where you have written to the editorial desk, that correspondence exists as correspondence and is kept only as long as the matter it concerns is open. A request about it can be sent to [email protected], which is the same address as on the contact page.
If this statement changes, the change will be reflected here. Publication details are on the imprint.