Your in-progress cell entries and notes are kept in your browser and are not broadcast to other players.
PUZRU uses WebAuthn Passkeys instead of passwords. The server stores the public credential material needed to verify sign-in, not your device biometric.
The top-level game reserves a 300×250 transition bay. A PUZRU house creative is always available as the fallback; configured third-party ad providers can replace it only when the advertising and consent deployment gates are enabled. Distributed PUZRU embeds remain ad-free.
Information PUZRU uses
When you create or use a live account, PUZRU processes your public player handle, an internal player identifier, Passkey public-key credential data, session information and verified solve history. Completed live rounds can include the public handle of the Discoverer and verified solver statistics in the permanent puzzle history.
The game also stores limited preferences and progress locally in your browser, such as theme choice and your current puzzle progress. You can remove browser-local data using your browser or device controls.
Crew visibility and retention
When you join a Crew, your public player handle, membership and current Crew-season points are shown on that Crew profile. Crew invite-redemption records are pruned after 30 days, Crew audit records after 180 days, and resolved reports after 365 days. A minimal account-to-Crew creation ledger is retained to enforce the lifetime anti-spam limit. Active bans remain until a manager removes them or the Crew is dissolved.
Fair-play telemetry
To protect the first-solve race, PUZRU records server-side timing information associated with a player and round, such as when that round was first served to the player, accepted solve timing and fair-play risk signals. Correct claims receive a canonical server-side submit timestamp before any required Cloudflare Turnstile check. If additional human verification is requested, that verification latency is recorded separately and is not added to the player's solve time.
Cookies and session access
Authenticated sessions use a secure, HTTP-only PUZRU session cookie so the browser can remain signed in. PUZRU also uses Cloudflare infrastructure for hosting, security and Turnstile verification. Those services may process network and device information as necessary to provide their services under their own privacy terms.
Retention and deletion
PUZRU uses short-lived access sessions and longer refresh sessions so a signed-in browser can reconnect without putting account credentials on the live puzzle hot path. The current technical profile uses an access session of up to 24 hours and a refresh session of up to 90 days unless you sign out or revoke sessions earlier. Browser-local preferences remain until you clear them or the browser removes them.
Security and fair-play records are retained only for operating, integrity and abuse-review needs under the configured fairness retention policy; completed verified Chain rounds are designed as long-term public puzzle history. Signing out removes active browser sessions but does not rewrite already-published public Chain results. If you need an account or privacy request reviewed, use the PUZRU contact page.
Advertising status
PUZRU contains a fixed 300×250 bay only on the top-level live transition screen. The current provider-neutral waterfall can try Adcash first and, when separately configured, Google AdSense second; if neither produces a usable placement, the PUZRU house creative remains visible. Network advertising is fail-closed: no provider script or ad request is made unless the master advertising gate, the relevant provider configuration and the consent deployment gate are enabled. PUZRU embeds distributed to third-party sites are intentionally ad-free.
Where consent or disclosure rules apply, PUZRU requires the applicable consent/CMP deployment and current provider disclosures before third-party advertising is enabled. AdSense also retains its dedicated CMP-readiness gate. Advertising never controls the round clock, solve acceptance, transition timing or Chain progression.
Retention and public history
Live-world records are retained as needed to operate account access, fair play, leaderboards and the permanent Chain archive. Completed puzzle history is intentionally durable because it is part of the public integrity record of the live world. Guest Training progress and in-progress board entries remain under your browser's storage controls. For signed-in players, completed Training puzzle numbers and best solve times may be synced to account-scoped PUZRU storage so Training can resume across devices; private in-progress cell entries are not uploaded by this sync.
Your questions and requests
For privacy questions or requests relating to your PUZRU account, contact the PUZRU contact page. Never send Passkey secrets, session cookies or other credentials. Advertising-provider requests may also need to be directed to the relevant provider under its own policy.