tomek.org is static html, css, assets, and a little client-side code. no analytics, ads, tracking pixels, session replay, accounts, comments, or forms.

requests still cross the usual web stack: browser, dns resolver, isp, and host. that stack can see request metadata. i do not build a reader-profile layer on top of it.

cookies
none
analytics
none
accounts
none
updated
2026.06.10

site

the site does not set cookies or create local storage identifiers for visitors. there is no account table, newsletter list, behavioral feed, or page-view database.

network

serving a page can expose ip address, user agent, path, timestamp, status code, and sometimes referrer to the infrastructure carrying the request. that is protocol exhaust, not a feature i added.

logs

i do not run a separate analytics or log-processing pipeline. provider-side logs may exist for uptime, abuse prevention, security, and debugging; i am not using them to study readers.