Privacy policy.
Short, because there is not much to tell.

collected

What the server records

Like essentially every web server on the internet, this one writes a line to a log file for each request it handles. That line contains:

• Your IP address. Necessary to send the response back to you. It is also what makes abuse and attack traffic traceable.
• The date and time of the request.
• What you asked for. The request method, path, and protocol version, for example a GET for a page on this site.
• The response status and size, so I can tell working pages from broken ones.
• Your user agent string, which your browser sends on its own and which identifies the browser and operating system in general terms.
• The referring page, if your browser sent one. This site sets a referrer policy that suppresses sending referrers outward, but I cannot control what other sites send when they link here.

Nothing else is recorded, and no attempt is made to combine these records with anything, to build a profile of you, or to identify who you are.

purpose

Why the logs exist

Three reasons, all operational:

• Keeping the site working. Logs are how I find broken links, misconfigurations, and pages that quietly stopped serving.
• Security. This host is on the public internet and is probed continuously. Logs are how automated attacks get spotted and blocked.
• Capacity. Knowing roughly how much traffic arrives tells me whether anything needs more resources.

Logs are rotated and deleted after 13 months. That is longer than a small site strictly needs, and the extra month past a year is deliberate: it means any period can be compared against the same period a year earlier, which is what makes a slow-moving abuse pattern visible at all.

They live on servers I control, and no third party has access to them. They are never sold, rented, traded, or handed to advertisers, because there are no advertisers.

not-collected

What this site does not do

• No cookies. This site sets none. There is nothing to consent to, which is why there is no consent banner.
• No analytics. No Google Analytics, no Plausible, no Matomo, no pixel, no beacon.
• No advertising and no advertising networks.
• No third-party resources. No CDN-hosted fonts, scripts, or stylesheets. Every byte your browser loads comes from this server, so no outside company learns that you visited.
• No social media widgets, embedded players, or share buttons.
• No fingerprinting, no local storage, no session storage, and no account system.
• No mailing list and no newsletter.

games

The games

The browser games under /games/ run entirely inside your browser. Each one is a single self-contained HTML file with no network code in it at all. Once the page has loaded, nothing you do in a game is transmitted anywhere, and nothing is written to your device. Scores exist only in memory and are gone when you close the tab.

The server log records that you requested the game file, the same as any other page. It cannot record anything about how you played it.

email

If you email me

Mail sent to markvd@markvd.net arrives at a mail server I run myself. I keep correspondence for as long as it is useful to keep, which for most threads means indefinitely, in the same way anyone keeps their inbox.

Your message and your address are used to reply to you and nothing else. They do not go on a list, and they are not shared with anyone. If you would like a thread deleted, ask and I will delete it.

hosted

Other sites hosted here

This server also hosts community and hobby projects, including tw2002.net, frrl.org, and evil-genius.net. Those sites are covered by the same server logging described above, but they are separate projects and may have their own content, their own contributors, and their own practices. This policy speaks for markvd.net.

One specific case worth naming: the TradeWars game server at tw2002.net accepts telnet connections. Those connections are logged with the same information as a web request, and anything you type into a game there is handled by the game server software rather than by this site.

external

Links off this site

This site links to plenty of other places: club sites, vendor pages, QRZ, GitHub, and so on. Once you follow a link you are on someone else's server under someone else's rules, and I have no control over and no insight into what they do. Their privacy policy applies there, not this one.

your-rights

Your choices

Because no account exists and nothing identifies you, there is very little for me to look up on request. Still:

• Ask what I have. Mail me with an approximate date and IP address and I will tell you what the logs show, if they still exist.
• Ask me to delete it. I will remove matching log entries and any correspondence you name. Note that logs older than 13 months are already gone.
• Browse without being logged at all. Not possible on any web server, mine included, but a VPN or Tor puts a different address in the log rather than yours.

If you are in a jurisdiction with formal data protection rights, such as the GDPR in the EU and UK or the CCPA in California, you are welcome to exercise them by writing to the address below. I would rather just honor the request than argue about which statute applies.

security

Security

Everything here is served over HTTPS with modern TLS, and HTTP requests are redirected to it. The site sends a strict Content Security Policy and the usual hardening headers. I do my day job in security, so the standard is at least the one I would set for a client.

Found a vulnerability? Please tell me. Reporting details are published at /.well-known/security.txt, and good-faith reports are always welcome.

changes

Changes to this policy

If how this site handles data ever changes, this page changes with it and the effective date at the top moves. There is no mailing list to notify, so the date is the honest signal. This policy is effective as of 28 July 2026.

abuse-c

Contact

Questions about any of this, or a request to see or delete something: