What MineSpecs collects and keeps

When a page opens, your browser sends a small beacon to the site’s own server (a Cloudflare worker). The beacon holds the page’s path, the address you came from, and whether this is the first page of a visit that arrived from another site. Each record keeps:

• the page path;
• the referring site's host name only (for example google.com), never the full address;
• your country, as Cloudflare works it out from your IP address;
• device type (desktop, mobile or tablet), browser family and operating-system family, read from your browser's user-agent — the full user-agent string is not stored;
• the time;
• a visitor ID (explained below);
• whether it was an entrance (the first page of a visit from outside the site).

The visitor ID. The server makes it by running your IP address and user-agent, together with a value that changes every UTC day, through a one-way hash. All your page views on one day share it, and the next day you get an unrelated one, so visits on different days can’t be linked to each other. The IP address and user-agent themselves are not written down.

Events. Some actions are counted as short labels that ride along with the next page view instead of being sent on their own: a file download (the file’s name), a click on a link to another site (that site’s host name only), a copy button (what kind of thing was copied, never the text), and a site search that found nothing (the search words, cut to 48 characters). If any are still waiting when you close the tab, one last beacon carries them.

“Live now.” A separate record of the page you’re on, your country and device type, under the same daily ID, powers the operator’s live-visitor count. It expires after 5 minutes.

Visits from crawlers that identify themselves as bots are not recorded. The admin dashboard itself is not tracked.

• Page-view and event records: 90 days, then deleted automatically.
• “Live now” record: 5 minutes.
• Daily totals (counts per page, referring site, country, device, browser, system, hour, event and landing page): 400 days. They are counts only and contain no visitor IDs.
• Leaderboard entries: kept while they stay in their game’s top 100 — an entry pushed out by higher scores is dropped. Oredle’s daily boards are deleted after 120 days.
• Skin submissions waiting for review: deleted on approval or rejection, and after 30 days at most.
• Per-day skin submission counters: 26 hours.
• Approved skins: kept until removed.
• Abuse counters (below): no more than 2 days, in Cloudflare’s cache rather than the database.

To stop scripts flooding the site, the server counts requests per network address: page-view beacons and skin submissions per day, score submissions per minute and wrong admin-key attempts per ten minutes. Each counter holds only a one-way hash of the address (for IPv6, of its first half, the network part) and a number. A counter exists only once a request of that kind has been made.

Leaderboards. Submitting a score stores the name you type (up to 16 characters), the score and the time — nothing else, no address or ID. The name and score appear on the game’s leaderboard and can appear in the activity ticker shown across the site. Names pass an automatic filter every time they are shown, and a blocked name shows as “Anon”. Please don’t use your real name.

Skins. A skin you submit is stored with its name, the credit name you give (optional, up to 16 characters), the arm model and the time. Only the image data is kept from the file — text and other embedded data are stripped. While it waits for review the entry also holds a one-way hash of your network address, used only to limit each address to three skins in the queue; that hash is not kept when the skin is approved. A moderator reviews every submission by hand. Once approved, the skin is public, anyone can download it, and your credit name is shown with it.

These live in your browser’s storage, and the server never reads them. Two leave the browser only in the ways already described: queued events go out with a page view, and your leaderboard name is sent when you submit a score. Clearing this site’s data removes them all.

• Cloudflare hosts the site and runs its server code, so it handles every request, including your IP address. Its own handling is described in Cloudflare’s privacy policy.
• Modrinth. Some catalogue pages show cover images loaded straight from Modrinth’s image server (cdn.modrinth.com). Your browser then connects to Modrinth, which receives your IP address and, under this site’s referrer policy, only the site’s address rather than the page you were on. See Modrinth’s privacy policy.
• Fonts are served from this site, not from a font provider.
• Links to Discord, Modrinth and other sites take you to those sites, whose own policies apply once you're there.

Because there are no accounts and no stored addresses, analytics records can’t be looked up by person. Public things can: to have a leaderboard name or a skin you submitted removed, or to ask anything about this page, contact us on Discord and say which game or skin, and where it appears. See also the contact page.

This stops your browser sending page views and events. It doesn’t affect anything else on the site. Browsers that send a Global Privacy Control signal are treated as opted out without doing anything here.