Privacy policy
How this version of Cybet handles account and play information.
Information used
Wallet sign-in records your public wallet address, account identifier, creation and login times, and a short-lived signed challenge. Game records include stakes, outcomes, decisions, balances and transaction references. Fun play creates a separate demo identity. Chat stores submitted messages and moderation information. The game server processes connection IP/device information for rate limits and abuse review.
What we do not request
Cybet does not request or store wallet recovery phrases or private keys. Connecting a wallet does not authorize movement of funds. Wallet providers may process connection information under their own privacy policies when you choose to connect.
Cookies and device storage
An essential HttpOnly cookie keeps your website session. A separate cookie protects operator access. Short-lived game tickets are stored in session storage; preferences, recent searches and a player identifier are stored on your device. Sound and motion settings can be changed in Settings. This version does not load advertising pixels or external font services.
Purposes and access
Records support account access, game operation, recovery, user support and abuse prevention. Operator interfaces require authentication. Do not put sensitive personal information in public chat. Provider games, when enabled, may require sharing an opaque player reference and technical session details with the contracted provider.
Retention and your choices
Expired sign-in challenges are removed. Chat has a 24-hour retention window in the current store. Persistent game and ledger records are retained for recovery and audit. Production retention periods, the data controller’s identity, support contact, legal bases and applicable rights process must be finalized before public real-money operation. Signing out clears your active browser game ticket; clearing browser data removes device-local preferences and searches but does not delete server records.
Security and updates
Use a secure device and review wallet signature requests. Production transport must use HTTPS/WSS. No system can promise absolute security. This notice describes the current fun-play build and must be reviewed with the operator’s actual deployment and providers before launch.