Privacy at Blokik

Game data

Solo worlds, camera settings, companion rewards and personal bests are stored in your browser. Clearing site storage removes those local records. Private shared rooms are stored on our game server for 30 days. A room includes its blocks, game state, access credentials and player positions needed for reconnecting.

Build & Climb attempts are temporary. Finished or expired attempts are removed; unused attempts expire after ten minutes of inactivity. Public challenge results contain a course, rules version, time, fall penalties and expiry date. They contain no player name or private-room access key and expire after 30 days.

Analytics

Gameplay analytics are currently disabled.

Before enabling analytics, we will add the operator contact details below and review the settings for our younger players. The prepared event system uses a random identifier held only in memory for a page visit, with no advertising SDK, cross-site identifier, full invitation URL or free-text field. Its retention limits are 14 days for raw events and 90 days for daily counts.

Hosting and backups

Vercel serves the website and Railway runs the game server. These services process connection information to deliver and protect the service. Private backups are used to recover game data; they are not public downloads. Backup copies are rotated rather than kept indefinitely.

Operator contact

Company and contact details will be added here before gameplay analytics are enabled.

Private invitations

Send a room invitation only to people you want to join. The owner can lock guest entries, turn guest building off or replace an invitation from the room menu. Challenge links expose only the finished race result.