Analytics Privacy Notice

Updated September 24, 2026

Mini Block Builder uses self-hosted Umami to understand site visits and whether core game actions work. It does not use advertising trackers.

What is counted

• Page views, visits, and approximate visitors.
• App opens and built-in world starts, grouped by game mode and template.
• Save results and multiplayer join outcomes, grouped into bounded categories.
• A coarse frame-time bucket on a 10% sample of page loads.

How it works

The self-hosted Umami script loads after the game is ready, only on the public Main site. It counts visits and the five game event types listed above. The game excludes URL search parameters and fragments. Umami receives ordinary network request metadata; page views and app opens are different measurements.

What game events leave out

Game event properties do not include names, email addresses, room codes, multiplayer client IDs, world IDs or contents, chat, voice, or coordinates. The game does not send a separate analytics-only browser token. Umami may process page URLs, referrers, and ordinary network metadata for site reporting; it does not receive world content, chat, voice, or room codes.

Retention and privacy signals

The former first-party counter files remain a read-only historical archive for reporting continuity and receive no new Main events. New Main events go only to Umami. Do Not Track and Global Privacy Control suppress the tracker. Analytics failure never blocks loading, playing, saving, or multiplayer.