Privacy & security telemetry

mc.henrygetz.com is run by one person as a free Minecraft network. To keep it online and stop abuse, the site, the browser game socket and the game server record limited connection, session and device telemetry. This page describes exactly what is recorded, why, for how long, and how to turn the browser beacon off.

In one paragraph

We log the connection metadata a web server normally sees (your IP address, request path, status, timing, TLS version, user agent), plus one optional first-party fingerprint beacon that summarises your browser and device. It is used only for abuse and bot prevention, rate limiting and diagnostics. It is never sold, never used for advertising, and never shared with third parties. Logs are deleted after 30 days.

What is recorded

Telemetry categories and examples
Category	Examples
Connection	Client IP address, source port, timestamp, requested host and SNI, HTTP version, TLS version and cipher, method, path (no query string), status, bytes, response and upstream timings, connection id.
Request headers	User-Agent, Referer, Accept-Language, Accept-Encoding, Sec-CH-UA (browser brand, mobile flag, platform), Sec-GPC, DNT, Upgrade, Origin, Sec-WebSocket-Protocol and -Version, X-Forwarded-For.
Browser beacon	Optional, same-origin, sent once per page load after the page is idle: user agent and platform/vendor, languages, timezone, screen and viewport size, device pixel ratio, colour depth, reduced-motion / colour-scheme / forced-colors preference, touch points, pointer type, CPU cores, device memory, cookie-enabled and webdriver flags, plug-in and MIME-type counts and names, PDF viewer flag, network effective type / downlink / RTT, storage quota, client hint brands, WebGL vendor/renderer/version and an extension hash, one canvas hash, and a SHA-256 hash of the stable parts.
Game connection (edge)	WebSocket handshake metadata (IP, path, status, protocol header, timing) and per-connection session time and byte counts for the browser Minecraft server. For Java, Bedrock and browser traffic, the client address and source port as seen by the edge gateway, one record per connection.
Game session (game server)	The identity, client and device details the game server receives when you join, plus event timestamps. Enumerated in full below.

Game session telemetry

When you join the Minecraft world (Java, Bedrock or browser), the game server records the session metadata it needs to route, run and secure the world. These records live in the game server's own logs on the backend host, not in the website logs.

Game session telemetry fields
Group	Fields
Identity	Minecraft username, UUID, XUID (Bedrock accounts).
Session	Virtual host / server name, protocol version, client brand.
Client settings	Locale, view distance, main hand, chat colours, skin parts.
Device	Device OS, UI profile, input mode, Bedrock version, language, linked status.
Timing	Event timestamps (join, settings changes, disconnect).
Network	The proxy-hop address the game server sees. Your true client IP is recorded at the edge, not on the backend.

Game-session logs are kept for 30 days and are readable by root only.

Game-session telemetry is separate from the browser beacon. The beacon is optional and can be switched off; game-session records are written whenever you connect to the server, because they are part of operating it. Beacon payloads are never merged into game logs, and game logs are not used for advertising or profiling.

What is never collected

Cookies, authentication headers, bearer tokens, API keys or passwords.
Request bodies or form contents.
Game chat, passwords, account credentials, or commands you type — on the site or in the game.
Raw Minecraft handshake bytes, or the forwarding secrets used between proxy layers.
Ordinary request query strings — only the path ($uri) is logged, so deep-link parameters stay private. The one disclosed exception is the /__fp?d= beacon payload described above: it is capped, sanitised and written only to the beacon log (fp.json.log), never as a raw URL.
WebRTC local IP addresses or other network-interface details.
Audio samples or audio fingerprints.
Font enumeration or installed-font lists.
Cross-site behaviour, advertising identifiers, or any third-party tracker.

Why

Abuse and bot prevention — spotting scripted floods, credential stuffing and scraping before they take the server down.
Rate limiting — per-IP limits on page loads, the game socket and the beacon endpoint require a real client address.
Diagnostics — knowing which TLS versions, browsers and routes fail lets us fix it.

How long it is kept

Website and edge access logs are rotated daily, compressed, capped at 500 MB per day and deleted after 30 days. Game-session logs on the backend are also deleted after 30 days. Aggregate counts may be kept longer; those contain no IP addresses or identities. Nothing in the beacon payload is stored anywhere except the edge logs.

Who can see it

Only the operator, on the servers themselves. Website and edge log directories are readable by root and the web-server group; game-session logs on the backend are readable by root only. There are no analytics vendors, no CDNs that receive the beacon, and no data-sharing agreements of any kind.

Your controls

Global Privacy Control or Do Not Track: when your browser sends Sec-GPC: 1 or DNT: 1, the fingerprint beacon is not loaded or sent.
Link opt-out: open any page with ?no-fp=1 appended (for example mc.henrygetz.com/?no-fp=1). The choice is remembered in your browser's local storage under mc_no_fp=1. Clear site data to undo it.
Blocking: any content blocker that blocks /__fp disables the beacon without affecting the site.

Opting out stops the beacon. Ordinary web-server logs (IP address, path, status, timing) are still written for every request, because they are required for security and rate limiting. If you need those suppressed too, use a VPN or Tor.

Legal note

This telemetry is first-party, security-focused and proportionate, and is disclosed here with an opt-out. It is not used for profiling or marketing. Whether your jurisdiction requires prior consent for security logging (rather than a legitimate-interest basis) is a question for you and your local law; this page is a disclosure, not legal advice.

Contact

Questions or a data request: reach the operator through henrygetz.com. Include the approximate time of your visit so the matching log lines can be found and removed.

Last updated: 29 October 2026.