Public Stats.
The only numbers we intend to keep. All aggregate. Nothing per-user. Rendered server-side from the same MySQL counters that will run the Save API.
The things we won't publish
This page shows the only numbers we publish. Separately, the server keeps request logs — IP address, User-Agent, path, timestamp — for abuse mitigation, blocklist enforcement, and rate limiting, exactly as described in Privacy Policy §2. Those logs are never joined to the counters on this page. Here is what this page will never show, because it will never be published:
- No individual IP addresses — not on this page, and never joined to a play, download, or source fetch. IP addresses exist in the server request logs (Privacy Policy §2) and are used only for abuse mitigation; they are never correlated with the counters above.
- No browser fingerprints beyond the User-Agent strings disclosed in our Privacy Policy.
- No referrer chains or cross-site tracking.
- No session IDs, no cookies, no localStorage identifiers.
- No per-user play history, ever.
- No geographic location beyond aggregate country (CDN routing only, never stored).
If it isn't on this page, it isn't published. What the server logs is what Privacy Policy §2 says it logs — no more.
How the counters will work
A server-side increment will run on every page load and file download. No JavaScript beacons, no third-party analytics, no pixels. Counters will live in a single MySQL table and be rolled up hourly. This page will read that table directly and return HTML — no client-side fetching, no JSON endpoint, no way to correlate a read with a visitor.