What does this site record about you?
The request log our host keeps in order to serve the page, and nothing else. There is no cookie, no analytics script, no identifier, no profile and no third party. Loading any page here issues requests to tlwinset.com and to no other origin, so no other company learns that you read this.
§1Edge logs, which is the whole of it
This site is served as static files from Cloudflare Pages. In the course of delivering a page and protecting the origin, Cloudflare records the ordinary server-side facts about a request: the IP address it came from, the time, the URL requested, the HTTP status returned, the number of bytes sent, the user-agent string, the referrer if the browser sent one, and the edge location that answered. Every web server on the internet records approximately this set, and a static site cannot be served without it.
What we will look at is the aggregate: requests per day, which pages, which status codes, which countries. Nothing has been served from this address by us yet, so that log does not exist and we have read none of it. It is worth being exact about what the log is not the source of: the reason several pages here sit at the strange addresses they do is not a reading of our own traffic. A third-party backlink index records fourteen-year-old download-catalogue pages still pointing at those exact paths, and we have not confirmed any of those placements ourselves. Once this site is serving, the aggregate is the thing that would confirm or refute them, and whichever way it goes it is reported on the page that made the claim. We will not query those logs for individuals, we will not export them, and we will not join them to anything.
Stated as an uncertainty rather than glossed: the retention schedule and internal handling of those logs are Cloudflare’s, not ours, and are governed by Cloudflare’s own privacy policy at cloudflare.com/privacypolicy. We can tell you what this site asks for and what it does not; we cannot make a promise on behalf of the infrastructure underneath it, and a privacy page that pretends otherwise is making a claim it cannot support.
§2Everything this site does not do
No cookies. This site sets none — not a session cookie, not a preference cookie, not an analytics cookie. You will not be asked to agree to anything when you arrive, because we are not doing anything you would need to agree to.
No analytics JavaScript. There is no JavaScript on this site at all. Not a line, on any page, in any deploy. No page-view beacon, no event tracking, no heat mapping, no session recording, no scroll-depth measurement, no A/B testing framework.
No third-party requests. No font CDN, no hosted stylesheet, no image host, no embedded video, no social widget, no share button, no advertising slot, no tag manager, no pixel of any kind. The two faces the stylesheet names are requested from your own machine, and if they are not installed the page falls back to your system’s own faces rather than fetching anything.
No tracking. No cross-site identifier, no fingerprinting, no advertising profile, no data broker, no audience segment, no retargeting list. Nothing about your visit is sold, shared or transferred, because nothing about your visit is collected beyond the log described above.
No newsletter and no comments. There is no subscription form, so there is no mailing list and no email address of yours in our possession. There is no comment system, so there is no account, no profile and no moderation database. There is no search box, no login and no form of any kind on this site — which means there is no page here into which you can type anything that reaches us.
The feed at /feed.xml is a plain Atom file. It contains no tracking pixel, no per-subscriber URL and no click wrapper. A feed reader fetching it appears in the edge log exactly the way a browser does, and in no other way.
§3If you write to us
The one channel that exists is email to the contact form, and using it is entirely your decision. A message you send sits in a mailbox with whatever your own mail provider and ours attach to it — the addresses, the timestamps and the message itself. We keep correspondence that led to a published correction so that the record of the correction is complete, and we do not otherwise retain it.
Writing to us subscribes you to nothing; there is nothing here to be subscribed to. A sender’s address is never published. Where a message produces a correction, the person who sent it is credited by name in the body of the corrected page — that is the standing policy at /corrections/ — and anyone who would rather not be named should say so, in which case they are not.
§4If this page ever changes
A change to this page is a change to a published claim, and it is handled the same way as any other: a dated block at the point of the change, the previous wording struck through rather than deleted, and an entry in the corrections list. This page was written for launch and last checked against the build on 2026-08-06. It has not yet been verified against a deployed site, because as of that date this site has not been deployed: every statement above is a statement about what is in the build and what the hosting configuration asks for, and the first reading of a served page against it happens on the day of the first deploy. If anything above turns out to be inaccurate about what your browser actually did when it loaded this page, that is a correction and the address for it is the contact form.