Privacy
Short, because there is little to say: this site has no accounts and no cookies, it asks nobody else about you, and it counts page views without identifying anyone.
What is processed
- The id in the URL. A render request names a block or an item. That id is the whole input, it is about Minecraft rather than about you, and the finished PNG is kept in a memory cache so the next request for it is free.
- 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/and/texture/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 third-party service is contacted while answering a request. The Minecraft assets are unpacked into the server image when it is built, so a render involves nothing but this machine.
- No data is sold or shared with third parties; the only outbound requests are the page-view counts described above.
If you embed renders on your site
Your visitors' browsers fetch the images directly from blockrender.dev, so their requests appear in these
server logs like any other. If your own privacy policy lists third-party image hosts, add blockrender.dev to
it; alternatively fetch renders server-side and serve them yourself, which the caching headers make
easy — they are immutable, so one fetch is genuinely enough.
Questions
Email hello@blockrender.dev. See also the about page and the caching and limits documentation.