Small beans.
Clear data rules.

Private beta notice. Operator identity and support contact are being configured before public invitations.

Applications

We store your chosen username, X and Telegram handles, two-word bean résumé, agreement version/time and beta group. These details help the team select testers and distribute invitations. Social handles and the résumé are private to the operator console. Handles are self-reported; submitting one does not verify that you own it.

Playing and wallet connections

If you join, we associate your application with the wallet you prove you control. We keep game results, statistics, balance records, transactions and security records such as sign-in IP addresses. Player names, wallet identifiers and game statistics can appear in public games and leaderboards. Blockchain transactions and wallet addresses are public on the network.

Wallets hold your private keys. BeanBattle does not ask for seed phrases or wallet passwords. If you choose WalletConnect QR, its relay service processes wallet-session connection data; your wallet and configured RPC provider also process the requests you approve. We do not automatically connect a wallet when you open this page.

Reports and suggestions

We store the title, description, optional steps and nickname, selected game area, originating page path and report status. If signed in, your report is associated with your player wallet. Browser name, input type and viewport size are included only if you tick that option. We do not collect screenshots, unrelated browsing history or private wallet keys through the form. Team notes are private.

Bean Club and community

We store your founding member number, earned badges, chosen title, competition entries and prize records, poll choice and optional wallet-distribution consent. Competition standings show player names, scores and rewards. Your own clubhouse shows your match history and rivals. Poll results are public totals; individual wallet choices are kept privately by the operator. Clicking Share result uses your device’s share menu or clipboard only.

Distribution is optional and off by default. If you opt in, the operator can export your signed wallet and username privately to distribute beta tokens manually. Opting out removes you from future distribution exports; already exported copies and public blockchain transfers may remain. Entering a manual-token competition also lets the operator use your signed wallet to deliver its stated prize.

Storage and retention

Essential cookies keep sign-in and security sessions working. Browser storage remembers theme/audio and language preferences, announcement dismissals and wallet connection choices. Optional Meta advertising measurement is off unless the operator configures and enables it and you accept marketing cookies. When enabled, the public landing, signup and Bean Club pages offer equal accept/reject choices. After consent, Meta receives standard request data such as IP/browser information and page URLs, PageView events and a Lead event when a signup submission is acknowledged. We do not add wallet addresses, social handles, résumé, form text, balances or game results to these events. A Lead is not proof of a unique accepted application. Meta may use this information under its own privacy policy.

The operations worker removes identifying text from unjoined applications older than 90 days once any invitation has expired, and from feedback 90 days after it is resolved or closed. Joined-player and transaction/security records remain for operation and investigation while the beta runs; the operator must review retention before public launch. Encrypted backups are separate copies and require their own retention management. Retention jobs must be running for automatic cleanup to occur.

Marketing consent is remembered for up to 180 days in this browser. Use the Marketing cookies button on public pages to change it. Rejection leaves application and gameplay available. Withdrawal stops future events from this integration and attempts to remove its first-party Meta cookies; it does not recall data already sent to Meta. Essential sign-in cookies are separate. Meta privacy policy.

Your choices and requests

Only include public handles and game-related text. You can leave the feedback nickname blank and turn off device details. For access, correction or removal requests, contact the team through the contact below. Until that contact is configured, submit a suggestion titled “Privacy request” with your public username or report reference; do not attach identity documents or secrets. The team must verify ownership before changing another person’s information. Some transaction/security records may need to be retained.

Contact: Public contact pending. Send a privacy request to the team →

Beta rules →