Rakun DojoPrivacy Notice
Data used by the preview
- Your public wallet address and signature-based session records.
- Game state, inventory, actions, achievements, rankings, settings, and support diagnostics.
- Technical request data such as IP address, timestamps, browser information, security events, and error logs.
Why it is used
Data is used to authenticate players, operate and save the game, prevent abuse, investigate failures, provide support, and protect the service. Saved gameplay activity is used to calculate aggregate game usage and return rates. No third-party analytics service is enabled.
Optional performance diagnostics
In Settings you may choose to share performance diagnostics for the current visit. This is off by default and resets when you reload. Consented samples contain coarse loading, frame, interaction, error and claim-stage categories, the game surface and a viewport-size range. They are associated with your signed-in or guest game session. They do not contain message text, browsing history, raw error stacks or wallet secrets. Diagnostic samples are pruned after 30 days by the daily cleanup; aggregate admin views use the latest seven days. You can stop further collection immediately in Settings.
Public information
Leaderboards, public profiles, clan information, and wallet-shortened identifiers may be visible to other players. A blockchain wallet address is pseudonymous, not necessarily anonymous, and may be linkable to public on-chain activity.
Feedback you choose to submit
The in-game feedback form sends your chosen topic, rating and message to the operator, associated with your game-session identity and release. Feedback is shown only in the protected admin view and is pruned after 30 days by daily cleanup. Do not include wallet credentials or recovery phrases. This form does not publish your message on the public status page.
Storage and security
Wallet sessions use a protected HttpOnly cookie in the current browser and roll forward for 30 days with authenticated use. Guest recovery credentials are stored in browser storage. The server stores cryptographic hashes of session tokens. The public service uses HTTPS. Protected routes require an authenticated game session, and token transactions and multiplayer actions require a wallet session.
Third-party infrastructure
Wallet connection and network features can involve wallet providers, WalletConnect/Reown, Shido RPC infrastructure, hosting providers, and other services chosen by the user. Their own privacy terms may apply.
Your choices
Do not connect a wallet if you do not want the preview to process its public address. You can disconnect and clear browser storage. A verified request channel for access, correction, deletion, restriction, or objection will be published with the final notice.
Children
The preview is not intentionally directed to children. A final minimum-age rule and parental-consent position must be set by the legal operator before release.