Skip to content

Privacy

Short, because there is little to say: this site has no accounts, no cookies and no analytics.

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.

What is not done

  • No cookies are set and no local storage is used, on the pages or by the API.
  • No analytics or tracking scripts are loaded. If aggregate, cookieless page-view analytics are ever added, this page will say so first.
  • 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 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.

Questions

Email hello@skinrender.dev. See also the about page and the caching and limits documentation.