Privacy

Beebo AI is designed to minimize personal data collection. Wallet-based features generally use public blockchain addresses, shortened wallet display labels, transaction hashes, and public user-submitted content.

Data we avoid collecting

We do not ask for passwords, seed phrases, private keys, government-issued ID numbers, precise location, phone numbers, or email addresses for the current Fun Lab features.

Fortune Oracle

The Fortune Oracle asks for birth date and birth time in the browser to calculate an entertainment-style result. Exact birth date and exact birth time are not sent to the server or retained in the service records. The public ranking retains only wallet, shortened wallet, fortune scope, score, public sign/animal/hour labels, and payment transaction hash.

Security and abuse prevention

Protected actions use a short-lived wallet-signed browser session. The service may temporarily process a one-way network identifier, a random challenge nonce, wallet address, session expiry time, and security event timing to prevent automated abuse and unauthorized account actions. Raw network addresses are not intentionally stored in the wallet-authentication tables. Expired challenge and session records are removed through routine cleanup.

A wallet signature confirms control of the connected address only. It is not a token transfer or spending approval. We do not request or store wallet passwords, seed phrases, or private keys.

Traffic analytics

To understand service usage, Beebo may record a page route, selected interface language, a country code derived at the Cloudflare edge, a random browser-session identifier after one-way hashing, and a daily rotating one-way network identifier for approximate unique-network counts. The application analytics table does not store the raw IP address. Detailed traffic-event rows are designed to be deleted after 45 days.

Cloudflare and other infrastructure providers may separately process network addresses and request metadata to deliver, secure, and operate the service under their own infrastructure terms. Country estimates can be wrong when a visitor uses a VPN, relay, corporate gateway, mobile carrier route, or travels.

Language and Board discovery

A Board post may carry a language selected by its author from any of the 17 launch interface languages. All 17 launch languages use release translation packs across the audited pages and dynamic interface layer. A future newly-added system message may use an emergency English fallback until its translation is released; this never changes the user's geographic policy status. Public posts do not display the author's IP address or country. Interface language and geographic region are treated as separate signals.

Advertising and sponsored placements

Beebo may display clearly labeled first-party sponsored placements and Google AdSense advertising on designated content pages. The AdSense service may process cookies or local storage, browser and device information, IP-derived location, advertising identifiers, and ad interaction data under Google's policies. For EEA, UK, and Switzerland traffic, the project is intended to use Google's Privacy & messaging consent flow with the choices Consent, Do not consent, and Manage options where required. This privacy-policy page itself does not load the AdSense ad tag. First-party sponsor analytics remain privacy-minimized and do not add wallet addresses to traffic events. Users should be able to revisit advertising privacy choices through the Google consent revocation flow when it is available for the approved site.

Public content

Board posts, Beebo profiles, flying Beebo messages, and Fortune ranking entries may be publicly visible. Do not submit private information, personal identifiers, confidential information, or content that you do not have the right to publish.

Age and consent

Use the service only if you meet the minimum age required in your jurisdiction. Where parental or guardian consent is legally required, do not use the service without that consent. Do not enter another person's birth information without permission.

Security contact

Report suspected account misuse, fraudulent content, payment-record mismatch, or security incidents through the project support channel. Never send a seed phrase, private key, wallet backup, or full authentication cookie.