Homekie**er's homelab journal

Privacy notice

Plain answers about what happens to information about you when you read this site. Last reviewed 9 November 2026.

Who runs this site

I do: kie**er, a student who writes this journal as a personal, non-commercial project. The site is static pages. It has no accounts, no comments, no forms and no admin page. You can reach me through the LinkedIn profile linked in the footer.

What happens in your browser only

Some parts of the site run entirely on your device and send nothing: the local clock in the footer, the lab console, the practice terminals, and the browser half of the "What your browser tells this page" card on the homepage (language, time zone and a guess at your browser family). The pause-motion switch in the footer is remembered in your browser's local storage on that device only; nothing else is stored there, and this site sets no cookies.

There are no analytics or advertising scripts, no third-party fonts and no embedded widgets. The site's Content Security Policy only allows files from this site.

The IP card on the homepage

When the homepage opens, its card asks portfolio.sirkits.tech/api/visitor, a small Cloudflare function on this site's own address, for the public IP address your connection arrives from and Cloudflare's rough location for that address: city, region, country, coordinates rounded to about 10 km, and the network's name. The function hands that back to your browser only, and the card shows it to you. Nothing is stored by the function, the card or the page, and the function's own logging is turned off. Your browser was already sending that IP address with every request; the card just shows you what it is. Press Hide if someone is looking at your screen. If the function is not deployed, the card says the lookup is unavailable and shows only your browser details.

What the web server logs

I do not run a server-side access log for this site. Requests are answered at Cloudflare's edge, so the only server-side record of a visit is the one Cloudflare keeps, described in the next section. I do not share or sell anything about visitors.

What Cloudflare processes

Every request passes through Cloudflare first: its DNS, its firewall rules and its hosting. Cloudflare sees your IP address, the page you ask for and your request headers, and keeps security and traffic records under its own policy. When one of my firewall rules blocks a request, its dashboard shows me that event, including the IP address, country and user-agent. Cloudflare's handling is described in itsprivacy policy.

Examples on this site

Lab logs, cases and screenshots on this site are sanitised. Addresses come from documentation ranges (RFC 5737), account and host names are substituted, and anything simulated or illustrative is labelled where it appears. No real visitor data appears in any example.

The rules I follow

I am in the Philippines, so the reference I use is the Data Privacy Act of 2012 (Republic Act 10173) and its Implementing Rules and Regulations from the National Privacy Commission. The rules exclude processing done purely for "personal, family, or household affairs", but a public website that keeps access logs is not obviously only that, so I follow the right to be informed anyway: what is processed, why, by whom, for how long and how to reach me, which is what this page is for. I have not had this notice reviewed by a lawyer or the Commission, and I make no claim of certified compliance with the Data Privacy Act, the GDPR or any other law.

Your choices

The IP card runs only on the homepage; every other page works without it. If you want me to remove log lines that relate to you, message me on LinkedIn with the date and time of your visit and the IP address you used, and I will tell you what I can see. I cannot delete Cloudflare's records; those requests go to Cloudflare.