Privacy policy

Overview

The public puzzle can be played without an account. We apply data minimization: game rules run in the browser, and the analytics event contract excludes board geometry, piece paths and IDs, blocker graphs, solution order, seed, email, precise IP, and exact play duration.

This page is a pre-release policy draft. The operator, target jurisdictions, analytics consent decision, retention periods, processor list, and verified privacy contact must be approved before production.

Data stored on your device

The game uses browser local storage for V2 progress, including compatible level/version identifiers, removed-piece state needed for refresh restoration, lives, completion summaries, move/attempt statistics, hint counts, and coarse timing. It uses session storage for a rotating anonymous analytics session ID. Clearing site data removes these local records.

No V1 board state is converted into V2 progress. Corrupt or incompatible local data is discarded safely.

Optional account data

Playing does not require an account. If you voluntarily use account features, the authentication system may process the name, email, session, provider-account details, and security records needed to provide that account. Production retention and deletion procedures must be confirmed before account features are promoted publicly.

Optional analytics and support tools

Analytics or customer-support scripts render only when an operator configures them. Allowed game events use a short-lived anonymous session ID and coarse fields such as level/version, difficulty, attempts, moves, lives, duration bucket, locale, and source page. Optional services must not receive the prohibited puzzle or identity fields listed above.

The final provider list, consent mechanism, cookie behavior, IP handling, region, and retention schedule must be documented here before those services are enabled in production. Fingerprinting is not an acceptable substitute for consent.

Server and security logs

Hosting and security infrastructure may process limited request metadata needed to deliver the site, prevent abuse, and investigate failures. Production log fields, retention, access owners, and deletion procedures remain part of the infrastructure approval gate.

Sharing and sale

We do not design this service to sell personal information. Data may be disclosed only to approved service providers acting for the operator, to comply with a valid legal obligation, or to protect users and the service. The final processor list must be reviewed before launch.

Your choices and requests

You can play without registering, clear browser data, disable optional storage in browser settings, and decline optional analytics where the final consent design requires it. Depending on applicable law, you may request access, correction, deletion, restriction, objection, or export of personal data held by the operator.

Privacy contact is not configured; production release is blocked.

Changes

Material changes will update the date and, where legally required, receive a new notice or consent. Prior versions and the production-effective date must be retained by the operator.