Privacy

Updated 2026-10-23. Operator: liangchen. Privacy contact: 1830819660@qq.com.

Endless Dive has no account signup, advertising, purchases or independent app analytics. The game does not ask for your name, email, location, camera or microphone. Sound is synthesized on your device.

What the game saves

The standalone game uses browser storage for a random secret token, settings, answer drafts, active-dive and retry identifiers, and a copy of your completed history. The server stores a digest of the token linked to a random player identifier, question snapshots, submitted answers, scores, round times, completion status and practice rotation. This lets you resume, review results and keep daily and practice records separate. The identity is pseudonymous; it is not an account or a promise that the data cannot identify you.

If optional feedback is sent to the feedback endpoint, its text and timestamp are also stored with the player identifier. There is currently no feedback form in the game. Do not enter personal or sensitive information in answers or feedback. Game answers are not sent to question providers or AI services.

Hosting and embedded play

The hosted version uses Cloudflare Workers and D1 to serve the game and store records. Requests necessarily expose network metadata such as IP address and browser headers to the host. Cloudflare may retain operational logs under the hosting account’s configuration.

The application uses an IP-derived hash with the player identifier and a one-minute window for rate limiting, rather than storing a raw IP in its game tables. Old rate-limit rows are removed during later requests once their window is more than five minutes old; this is not a guaranteed five-minute deletion timer or a policy for hosting logs.

The game API does not require cookies. In the CrazyGames version, the CrazyGames SDK Data Module stores the random recovery token, settings, current draft, active-dive and retry identifiers, and the latest 100 cached completed dives. It uses local storage for guests and can sync these data with an existing CrazyGames account. Standalone and platform saves are separate. The SDK also reports loading and gameplay start/stop events; the game does not request ads or an account login. CrazyGames handles platform identity, data synchronization and related usage data under its privacy policy. Signing in or out on the platform can reload the game to select the appropriate save. If persistent storage is blocked, the game warns you and uses a temporary in-memory identity; progress may be inaccessible after closing the page.

Retention, access and deletion

This build has no automatic expiry or deletion job for player records, answers, feedback or server history. The local/platform cache holds up to 100 completed dives and one current answer draft. Server records remain until the operator deletes them. Returning only the latest 100 completed dives from the server, or showing 30 in the logbook, does not delete older data. Browser data remains until you or your browser clear it. Worker observability logging is disabled in this preview deployment. Cloudflare may still process infrastructure/security metadata under its own policies; this application does not set that retention period.

You can export your history from the logbook. To ask about access, correction or deletion, contact the operator at the address above and identify a dive using the run ID in your exported history. Never send your secret token. The operator may need enough non-secret information to locate and verify the request. There is no automated deletion tool or account-recovery service in this build.

Clearing site storage removes the secret needed to access your records; it does not erase the server copy. Without that secret, recovery or reliable association with your earlier records may not be possible. Settings allow you to mute sound and reduce motion. The source and license notices are available from Credits & licenses.