Privacy Policy BETA
Plain language summary: Block Bee has no player accounts and never asks players for a name or email; only testers we invite can sign in, with Google or an emailed link. Your progress stays in your browser; a tester who signs in can choose to save it to their account, so it follows them to other devices. If you tap Allow, each level you finish sends us one anonymous line about how it went, so we can tune the levels; until then nothing is sent, and you can turn it off any time. We delete those lines after 12 months. Google Analytics counts which screens you open and when levels start and end, but only if you tap Allow; until then nothing loads from Google Analytics. We don't sell anything about you, and there are no ad networks.
1. Who we are
Block Bee is a puzzle game for players 16 and over, played at blockbeegame.com and, later, in the app stores. It is made and operated by MASONBYTE LLC, of Accokeek, Maryland. This policy is adopted by MASONBYTE LLC and governed by Maryland law, like the policies of MASONBYTE's other apps, which are listed at masonbyte.com. The game is in beta, so this page will change as the game does (section 9).
2. Information we collect
- No account information for players. There are no player accounts yet. The game never asks a player for a name, email, phone number or address.
- Testers who sign in (invited only). Testers we invite can sign in from the map's settings, with Google or with a link we email them. Our sign-in service (Supabase Auth) then keeps the tester's email address, when the account was made and when it last signed in, and a mark that it is a tester's. With Google, it also keeps what Google shares for sign-in: the name, the email and the profile picture's address (the
openid,emailandprofilepermissions, nothing more). The game keeps the sign-in session in the browser, which names the email address, so the tester stays signed in until they sign out. Sign-in emails are sent through Resend. - A tester's saved progress (only if they choose it). The first time a tester signs in on a device, the map asks Save to your account? and names the account. Only after they tap Save to my account does the game keep a copy of its save with that account: the place on each path's map, stars, Super levels cleared, hearts and the win streak, the game's record of wins, rewards and spends, the settings, the list of levels played and how they went, and which one-time cards were seen. It sends the copy after each win and when the map opens, and takes it back when the tester signs in on another device. It holds no payment details and nothing about the device. Not now keeps the game in that browser only.
- A signed-in tester's game record. When we switch it on for the beta, a signed-in tester's game also sends its record of what happened, one entry at a time: each level won (the level, stars and time taken), each special or booster used, each Nectar spend, each daily or gift claimed, and when, by the device's clock and time zone. We check each entry and keep it with the account, and the server works out the tester's Nectar and specials from them; once we switch that on, the game shows the server's count and keeps it in the browser. It holds no payment details and nothing about the device.
- A tester's player name (only if they pick one). After saving to their account, a tester can pick a player name. It is kept with the account, with a short number the game adds (like #4821) so two testers can share a name. Names are checked so they hold no slurs, sexual or hateful words, or contact details. A name is not shown to other players yet; when leaderboards with real players arrive, this page will say so first.
- On your device only. Your progress, settings, game items (Nectar, specials, looks) and your own play log are saved in this browser's storage. They are not sent to us.
- Anonymous play data (only if you allow it). The first time you open the game, a card asks. Only after you tap Allow does the game make a random id in this browser and, each time you finish a level, send one line: that id, the level and path, whether you won and how the level ended, the seconds it took, the time, the game's build, and where you played (blockbeegame.com, a test copy of the site, or the store app). It never includes a name, an email, your saved progress or anything you type. To stop it, turn off Share play data in the map's settings; the random id and lines not yet sent are thrown away too.
- Google Analytics (only if you allow it). The first time you open the game, a card asks. Only after you tap Allow does the game load Google Analytics, which then counts the screens you open and when a level starts and ends (the level and path, whether you won, the seconds it took). Like any website visit, Google also receives your IP address and your browser and device type, and sets its own cookies (section 7). The game never gives Google a name, an email, an id of ours or your saved progress. A browser that sends Global Privacy Control never loads Google Analytics, even after Allow.
- Error reports. If the game hits an error, it may send a report of it to Sentry: what went wrong, the browser type, which game screen was open and the game's version. Never your progress or personal details, and Sentry is set not to store IP addresses. At most 25 reports from one visit.
- Notices from us. When the game starts it reads a short notice and display settings from our server. That request sends nothing about you or your play.
- Share my progress. Only when you press it, the game writes a short summary (levels, stars, time played, where you got stuck, screen size and browser) and hands it to your phone's share sheet or clipboard. It goes only where you send it.
- Share Block Bee. After some levels the win card offers Share. Only when you press it, the game hands one line of text and the game's address to your phone's share sheet, or opens the social or email app you pick with that text filled in. The game sends nothing itself and is not told whether you shared.
- Purchases in the store app. When the Google Play or App Store app sells hive packs, the store takes the payment; we never see your card. RevenueCat checks the store's receipt and tells our server which pack was bought, its price, the store's transaction id, a random id RevenueCat makes for this install, and your country. We use it to record the sale and to handle refunds.
- Our own house ads. The only ads are for MASONBYTE's own apps. They track nothing. A Visit link tells that app only that the visit came from Block Bee.
3. How we use your information
- To see which levels are too hard or too easy, and tune them.
- To find and fix bugs.
- To decide what to build next.
- If you allow Google Analytics: to count how many people play, on which devices, and which screens they use.
We do not sell or rent any information, we do not share it with advertisers, and we do not use it to build advertising profiles.
4. How we store your information
- Supabase stores the anonymous play lines, invited testers' sign-in accounts and the progress testers choose to save to them, in the United States (us-east-1), encrypted at rest and in transit. Only MASONBYTE can read the play lines, and the game can add lines but never read them back. A tester's saved progress can be read only by that tester's signed-in game, and by MASONBYTE. supabase.com/privacy
- Netlify hosts the site and keeps standard web server logs (address requested, time, IP address) for a short period to run the service. netlify.com/privacy
- Google Analytics (Google LLC) counts screens and levels, only after you tap Allow. We have turned Google signals and ad personalization off and restricted data processing on, so the data is not used for ads or linked to your Google account. Google Analytics does not store IP addresses. policies.google.com/privacy · How Google uses data from sites that use its services
- Google signs a tester in when they pick Continue with Google, and tells our sign-in service the name, email and picture address above. policies.google.com/privacy
- Resend sends the sign-in emails for invited testers: it receives the tester's email address and the email it sends. resend.com/legal/privacy-policy
- RevenueCat checks store-app purchases with Google Play and the App Store, as section 2 says. revenuecat.com/privacy
- Sentry receives the error reports in section 2. sentry.io/privacy
A feature that would share information with a new company will be described here before it ships.
4a. Nectar and game items
Nectar, specials, boosters and looks are game items. They have no cash value, can't be sold, traded or exchanged, and can't be used outside the game. Purchases are not open during the beta; invited testers may try test hive packs, which cost nothing and carry no value. When purchases open, anything you buy will be the item you picked: there are no paid surprise boxes.
5. Data retention
- Anonymous play lines are deleted 12 months after we receive them, by a job that runs every day.
- What is saved on your device stays until you erase it (section 6).
- A tester's sign-in account stays until the tester asks us to delete it, or until the beta ends, when we delete the testers' accounts. Signing out ends the session in that browser at once.
- A tester's saved progress is replaced by each newer copy, so only the latest is kept, and it is deleted with the account. So are the player name and the game record.
- Google Analytics keeps the events it counted for 2 months, its shortest setting. Totals in its reports (how many players, which screens) are kept longer and name no one.
- Web server logs are kept by Netlify for a short period.
- Error reports are kept by Sentry for up to 90 days, then deleted.
6. Your choices and rights
- Play data: it stays off unless you tap Allow. To change your mind, use Share play data in the map's settings. Turning it off stops it at once and throws away the random id and lines not yet sent.
- Google Analytics: it stays off unless you tap Allow. To change your mind, use Google Analytics in the map's settings. Turning it off stops it at once and deletes Google's cookies on this site.
- Erase your progress: Reset progress, specials and hearts in the map's settings erases your progress, items and your own play log on this device. Clearing this site's data in your browser erases everything the game saved here.
- Lines already sent: they carry a random id, not your name, so we can't pick out yours from a request alone. They are deleted after 12 months.
- Tester accounts: Sign out on the Sign in card ends the session in that browser. To have the account deleted, with the progress saved to it, email us from its address.
- Questions or requests: email support@masonbyte.com. We will reply within 30 days.
7. Cookies and local storage
Block Bee sets no cookies of its own. If you allow Google Analytics, Google's script sets its cookies on this site (_ga and _ga_ followed by the property's id) to tell one visit from the next; turning Google Analytics off deletes them. The game saves its own data in your browser's local storage, under keys that start with edens-lab- (the game's first name), plus bb-tester-v1 for invited testers and know-it-all-proto-v1 for the classic game at /classic/. These hold:
- your progress, stars, lives and game items, and a record of your wins and spends, of the hidden gems you have found (and which of them the game has shown you), and of a seasonal treat once you have taken it (such as the Halloween hornet's);
- your settings, including Share play data and your Google Analytics choice, and which What's New card the game last showed you;
- your own play log, and play lines waiting to be sent;
- the random id used on play lines, made only after you allow them;
- for a tester who signs in, the sign-in session (a token our sign-in service checks), until they sign out.
So that Block Bee can be installed and played without internet, your browser also keeps a copy of the game's own files (its code, pictures and sounds) in its storage for this site. That copy holds nothing about you, and it goes when you clear this site's data or remove the installed game.
None of this is sold or shared. There are no ad networks or tracking pixels, and no outside analytics unless you allow Google Analytics.
8. Children's privacy
Block Bee is for players 16 and over. It has no accounts and asks no one for personal information. If you believe a child has sent us personal information, email support@masonbyte.com and we will delete it.
9. Changes to this privacy policy
When what the game keeps or sends changes, this page changes first, with a new date at the top. Before accounts, purchases, error reports or anything new is switched on, this page will say what changes, before it changes.
10. Contact us
Block Bee · Operated by MASONBYTE LLC
Email: support@masonbyte.com (privacy questions and requests)
Security reports: security.txt
Accokeek, MD
Block Bee © 2026 MASONBYTE LLC. All rights reserved.