Unique visitor counter
When a non-automated production visitor loads the site, the server derives an HMAC-SHA-256 marker from the public IP address and a private site secret. The raw IP is not written to the counter store. Repeat visits from the same public IP do not increase the lifetime count.
Server votes
Voting uses a separate secret and creates one pseudonymous marker per server, public IP and UTC day. This enforces the one-vote-per-network rule without publishing a raw IP. A shared office, carrier-grade NAT or household can therefore share one vote allowance.
- Server identifier
- UTC vote date
- Non-reversible keyed hash marker
- No name, email or account required
Submissions and contact
Add Server and Contact require an email so moderators can request evidence or confirm a correction. The email is encrypted with AES-256-GCM before storage. Public-intent fields such as server name, website and description are stored with a random submission identifier but are not automatically published.
A keyed daily network marker limits spam. Do not submit passwords, payment card data, private player records or unrelated sensitive information.
Storage and retention
Vote and lifetime visitor markers can be retained to preserve accurate totals and abuse controls. Moderation submissions are retained while a request is reviewed and for a reasonable accountability period. We may delete rejected spam earlier.
Third-party hosting and content delivery providers process requests as necessary to serve and secure the site. Outbound server websites have their own privacy practices.
Your requests
Use Contact and select Privacy request to ask about a submitted message, correction or deletion. Because counter and vote markers are intentionally pseudonymous and not linked to an account, we may be unable to identify a specific marker without additional evidence.
Security
Secrets remain server-side. APIs enforce same-origin requests, bot filtering, input limits and moderation. No internet service can promise absolute security; report a suspected issue through Contact without including exploit payloads that could harm other users.