Hibee is operated by SWIFT PIXEL LLC. This page describes how Hibee handles information when you play, save an account or buy cosmetics. Contact amazingsdk@gmail.com with privacy questions.
We store an account identifier, your chosen username, race results, experience, earned pollen, cosmetic ownership and equipment. Guest progress is associated with a browser session; creating or signing into an account lets you keep verified progress across devices. Your chosen in-game name and race performance are visible to other players in your garden.
For username sign-in, Hibee stores a salted password hash and a hash of your recovery key. We do not store their plain text. For Google or Discord sign-in, we use the provider's account identifier to recognize you. The sign-in flow requests basic identity access; Hibee does not request access to your messages, contacts, files or Discord servers. Provider access tokens are used during sign-in and are not retained in the account database.
Each season, Hibee stores your rating, number of rated races, wins, and your placement and rating change in each rated race. Only saved accounts are rated; guest races are unrated. If you have a saved account and at least one rated race, your username, tier, rating, wins and race count appear on the public leaderboard.
Hibee measures whether the game is fun and whether players come back using its own first-party analytics. On hibee.io there are no third-party analytics, advertising identifiers, tracking pixels or fingerprinting. Each event records only the day and time, an event name, a pseudonymous player identifier and at most five of these small values: device class (phone, tablet or desktop), tutorial step, finishing place, crowns, garden, number of human players, a duration in seconds, where you left from (a race, the podium, practice or the menu), the shop item, the sign-up method, whether a race was ranked, and a post-race rating from one to five with an optional reason chosen from a fixed list.
Your browser reports: opening the game, tutorial start, steps, completion or skipping, your first live race, finishing a race, choosing “Race again”, leaving a garden, enabling sound, opening the shop or leaderboard, starting a checkout, starting to watch a live race, and rating a race when you choose to. The server records: joining, finishing or leaving a race, rematches, colony defeats, practice progress and account creation. The server also keeps per-race totals (human and bot colonies, duration) and a per-minute count of connected players, without player identifiers.
The pseudonymous identifier is a salted, one-way hash of your account identifier. It lets us count returning players without storing your account identifier, IP address, browser details or typed names with these events. Rate limits use your IP address briefly in server memory only. If your browser sends Global Privacy Control or Do Not Track, it does not send usage events; events the server records while operating races, rewards and the ladder still apply. Raw usage events are deleted after 400 days.
When you play Hibee embedded on a game portal such as CrazyGames or Poki, that portal's software development kit is loaded from the portal to report loading and play time and to show ads between lives. The portal and its advertising partners handle that information under the portal's own privacy policy and consent choices. Hibee does not load a portal or advertising SDK when you play on hibee.io directly.
An essential, HTTP-only session cookie keeps you signed in for up to 30 days. Signing out revokes it; “sign out everywhere” revokes your other sessions too. Browser storage holds preferences, tutorial completion, older local race records and a marker that a one-time milestone (such as your first live race) was already reported. Clearing site storage removes those local preferences and can make an unsaved guest account inaccessible.
Stripe hosts checkout and handles payment information under Stripe's privacy policy. Hibee stores order identifiers, selected cosmetics, price and payment/refund status. Card details are entered on Stripe and are not stored by Hibee. Purchase information is used to deliver cosmetics, handle refunds and prevent fraud.
Our hosting provider processes the information needed to serve the game. Operational logs may include IP addresses, request details and errors for security and troubleshooting. We keep account information to provide saved progress, and transaction records as needed for billing, fraud prevention and applicable obligations. Account backups rotate through 24 hourly and 14 daily snapshots. Hibee does not sell your personal information or use Google sign-in data for advertising.
You can play as a guest, change your username, sign out, and revoke Hibee's access in your Google or Discord account settings. For a copy of your account data or deletion, contact the address above with your Hibee username. We will verify account ownership before acting. Do not email passwords, recovery keys or card details. Some transaction records may need to be retained after account deletion.