Privacy
Short, because there is not much to tell.
What we collect
No personal data. The site sets no cookies, runs no third-party analytics or ad tracking, and has no accounts. It is statically generated and served via Vercel, whose infrastructure may log anonymous access data (IP, timestamp) for operational purposes — see Vercel's privacy policy.
Page views are counted — like this, and no more
To know which pages are used we count page views ourselves, with no cookies and no browser storage. Per view we store: path (query parameters stripped), country (two-letter code from a geo header — never the IP), device class (mobile/desktop from viewport width — the user agent is never read), language as a two-letter code, and the referring domain when you arrive from elsewhere (never the full URL). No IP address, no identifiers, no fingerprinting — which is also why unique visitors are not counted: we count pages, not people. The database column constraints do not permit more than the fields above. If your browser sends Global Privacy Control or Do Not Track, nothing is sent at all. Data is stored with Supabase (AWS eu-west-2, London — covered by the EU adequacy decision for the UK).
Contact
All contact goes through the community Discord. Whatever you post there is handled under Discord's terms.
Error reports
If you report an error via Discord, we process your username and the content of the report until the case is closed — after that it is purged. Reporters are never published. If you wish to exercise your rights under GDPR (rectification, erasure, objection — for example if a name in ownership information concerns you), you can do so in Discord or via an issue on our open data repo on GitHub; you do not need to be a member of the community to be helped.