Skip to content

Privacy

Short, because there is little to say: this site has no accounts and no cookies, and counts page views without identifying anyone.

What is processed

  • The identifier in the URL. A render request names a player by UUID, username or texture hash. That identifier is used to look up the skin and is kept in memory caches for up to 24 hours so repeated requests are fast.
  • Requests to Mojang on your behalf. To resolve a username or UUID to a skin, the server contacts Mojang’s public profile and texture services. Your IP address is not forwarded; Mojang sees the server’s address and the identifier.
  • Standard server logs. The web server records the request path, status code, timing, user agent and client IP address, as almost every web server does. Logs are used to keep the service running and to diagnose abuse, and are rotated and deleted on a routine basis.
  • Aggregate page views. The pages of this site load a small analytics script from api.panalytics.money, which reports the page that was viewed, the referrer and coarse browser and country information. It sets no cookies, stores nothing in your browser and builds no cross-site or per-visitor profile; the result is a count of visits per page. The image API under /render/ loads no scripts at all, so embedded renders are never counted.

What is not done

  • No cookies are set and no local storage is used, on the pages or by the API.
  • No advertising or cross-site tracking scripts are loaded, and visitors are not identified or followed between sites.
  • No record is kept of which visitor requested which player beyond the server logs above.
  • No data is sold or shared with third parties; the only outbound requests are the Mojang lookups and the page-view counts described above.

If you embed renders on your site

Your visitors’ browsers fetch the images directly from skinrender.dev, so their requests appear in these server logs like any other. If your own privacy policy lists third-party image hosts, add skinrender.dev to it; alternatively fetch renders server-side and serve them yourself, which the caching headers make easy.

More

See also the about page and the caching and limits documentation.