This page explains, in as much detail as I can give, what each of my sites stores, where it goes, who else can see it, how long it stays, and how to get rid of it. It is long on purpose. Nothing on it is boilerplate copied from somewhere else: every line describes what the sites actually do.
Last updated 19 November 2026 · Version 34
Every detail, site by site → — for each site, exactly which outside services it contacts, which cookies it leaves and what it keeps on your device, recorded by loading every one of them.
The short version. These are hobby games and tools made by one person. There is no selling of data, and no data broker ever gets anything. (Open Road used to load the Poki games platform's advertising; since 12 October 2026 that code only runs when the game is played on Poki's own website.) You can play almost everything without an account or a name. If you make an account, it holds your email address, a display name, your level and progress, your profile picture and description if you add them, your friends, your messages, and any pages you build. Your password never reaches me. Delete my account, in the account panel on any site, removes all of it. A few games keep data of their own that it does not reach; they are listed under Deleting everything.
Every site listed on the hub at vercels-hub.vercel.app is made and run by one person, the owner, as a hobby. There is no company behind them, no staff, no investors and no business model. Nothing is sold, and nothing is paid for by showing you advertising on my own pages.
Because it is one person, "I" and "me" on this page mean the owner. "The sites" means everything the hub lists, plus the Voxel Client launcher, which shares an account system with some of them.
This page covers every project listed on the hub, the hub itself, pages people build on the hub, and the Voxel Client launcher. Most sites share one account system, run on the Google Firebase project called geo-da. A few older games use Firebase projects of their own; those are named in Site by site.
If a site loads something from another company — a map, a font, a game library, an AI — that company's own privacy policy applies to what it receives. Those companies are listed in Other companies involved, together with exactly what they get.
@, which becomes your permanent @name. It is set once and never changes.You never have to make an account. Every game can be played as a guest.
On your first visit you get a made-up name — something like Otter, Comet or Piston — and a profile that exists only in your browser's local storage. Your level, coins, skin choices and each game's saved progress are written there. None of it leaves your device.
As a guest, exactly one thing is sent to my database: each site adds the number 1 to a public counter once per browsing session, so the hub can show the most-played projects first. That counter is a single running total per site. It is not tied to you, to a name, to an account or to your address, and it cannot be changed except by adding one.
Some older multiplayer games (listed in Site by site) create an anonymous account for you automatically while you play. That is a random identifier with no name or email attached; it exists so the game's database can tell players apart. Your in-game position, and anything you type in that game's chat, go to that game's database while you play.
An account is only useful if you want the same level, progress and friends on every site and every device. Making one stores the following in the database:
| What | Why | Who can see it |
|---|---|---|
| Email address | So you can sign back in and reset a forgotten password. | Held by Google Firebase Authentication. Never shown to other players. |
Handle (@name) | A permanent name people can find you by. | Other players, on your profile and the leaderboard. |
| Display name | The name shown in chat and on the board. | Other players. |
| Level, experience and coins | Progress that carries between sites. | Other players, on the leaderboard. |
| Skin (the ring around your picture) | A cosmetic you choose. | Other players. |
| Profile picture, if you add one | Shown on your profile. Shrunk to 128 pixels before it is saved, and a 48-pixel copy is used on the public board. | Other players. |
| Description, if you write one | Shown on your own profile (up to 280 characters). | Only you, at the moment — it is not shown to other players or put on the public board. |
| Saved games | A copy of each site's own save, so it follows you to another computer. Anything a site keeps that looks like a password, sign-in token or key is left out and stays on your device. | Only you. |
| Play time per site | Part of how experience is earned. | Only you. |
| Friends, friend requests and groups | So chat works. | You and the people involved. |
| Messages | Chat. | Everyone in that conversation. See Chat, friends and groups. |
| Pages you build | The page builder. | Anyone with the address. See Pages you build. |
| A count of AI builds per day | Enforces the daily limit. | Only you. |
| Feedback you send, if you use a site's Feedback button or the hub's contact page | Your message, its subject, your display name, which site it came from and when. The time of your last message is also kept, so each account can send one a minute. | Only the hub's administrator. You can't read it back, and Delete my account removes it. |
| Players you block | So their messages stay hidden from you and they can't message you or send you friend requests. | Only you. They aren't told. |
| Reports you send, if you report a player or a message | Who you reported, the reason you picked, your note, a copy of the message (up to 500 characters) and where it was, and the time. The time of your last report is also kept, so each account can send one every 20 seconds. | Only the hub's administrator. Your reports are removed when you delete your account; a report about someone stays until the administrator deals with it. |
That is the complete list. No site ever asks for your real name, home address, school, phone number, birthday, photo ID or payment details, and none of them has anywhere to put them.
Your password is typed into a box on my page and sent straight from your browser to Google over an encrypted connection. It never passes through any server of mine, and I never see it, store it, or have any way to read it. Google keeps only a scrambled ("hashed") form, which cannot be turned back into the password.
A new account's password must be at least ten characters and must not be one of the most commonly guessed passwords. After five wrong attempts in a row, the page makes you wait before trying again, and the wait doubles each time, up to five minutes. Google applies its own limits on top of that.
If you forget it, Forgot your password? asks Google to email you a reset link. The page gives the same answer whether or not the address has an account, so it cannot be used to find out who has signed up.
Please use a password you do not use anywhere else.
Every signed-in player can read the public chat, called "Everyone". Anything you post there can be seen by every other signed-in player. Do not put anything private in it.
A direct message can be read only by the two people in the conversation. The database refuses to show it to anyone else.
A group's messages can be read only by its members. The person who creates a group decides who is in it.
While you are signed in and one of the sites is open in front of you, it records the time every 30 seconds (the database's own clock, nothing else — not which site, not which browser or device). Your friends — and only your friends — see a green dot on your picture while that time is recent, and "last seen" after that. You can switch this off from the menu (right-click the hub → "Appear offline"); the record is then removed. It is deleted with your account.
Writing @ and someone's handle in a message (for example @bobby) lets them know: the hub shows them a note when they have it open, and their computer shows a notification if they turned those on in the chat ("Notify me"). Nothing extra is stored — the mention is just part of the message's text.
Pictures are shrunk before sending and stored inside the message itself. Files up to about 140 kB can be attached. Program files and web pages (for example .exe, .bat, .js, .html, .svg, .php) are refused, so chat cannot be used to pass someone something that would run on their computer.
A message can be up to 300 characters. You can send one message every 1.5 seconds; the database itself enforces this, not just the page, so it applies to everyone equally.
Friendship works by request. Someone searches your handle and sends a request; nothing changes until you accept. Your friends list is visible only to you. Removing a friend takes them off your list.
Signed-in players can make their own page, which gets an address like vercels-hub.vercel.app/my-page. For each page, the database stores the name you chose, the title, the finished page, your account's identifier as the owner, your handle, and when it was created, last changed and approved. A page made in the code editor also stores its source: its files (up to twenty), its blocks if you used them, and the name of the template it started from. Files you upload — pictures, sounds, videos, 3D models, fonts and data files — are stored as part of the page (each up to about 2 MB).
Every page is checked before it goes live. When you publish, the page is stored in a waiting list that only you and the hub's administrator can read. The administrator looks at it and either puts it live or turns it down with a short reason, which is stored with it so you can see it and fix the page. Changes to a page that is already live wait the same way; the live version stays up meanwhile. You can take a waiting page back at any time. The administrator's own pages go live without waiting.
You can use the code editor without an account. Until you publish, your work — including anything you upload — is kept only on your own computer, in this browser (see "What is kept on your own device"). You need to be signed in to publish or to use the AI.
Anyone who knows the address can open your page, and anyone can open it in the editor to see how it was made — its files and blocks — and make a copy under their own address. That is what a website is. Only you can change or delete yours.
Visitors and developer badges. When someone who is signed in opens a live page that is not their own, the hub records their account's identifier under that page (once per account — opening it again changes nothing), and adds one to the page's visitor count. Visits by the page's owner, and by people who are not signed in, are not recorded. Only the administrator can see which accounts visited a page; everyone can see the count. A page opened by more than 100 different accounts earns its maker the Dev badge, and a maker with more than 25 approved pages gets the Pro dev badge. Badges, the name of the page that earned the Dev badge, and how many pages a maker has released are public, and show next to the maker's name. You can remove your own badge record when you delete your account. The record of which accounts visited a page stays after they delete their account, holding only an identifier that no longer belongs to anyone — ask if you want yours removed (see "Asking a question").
Making games for Tabcade. At tabcade.net/dev, a signed-in player can become a developer by choosing a developer name. The database stores that name and the date you set it up under your account's identifier, and anyone can read the name, because it is shown under your games. Use a made-up name, not your real one. A game you send in (made in the editor or imported from your own files) is stored exactly like a page, in the same waiting list, with a short description, how to play and the kind of game you picked. When the administrator approves it, it also goes on the public list of community games (its title, description, how to play, kind, your developer name and your account's identifier), and the number of your games that went live that month is stored (at most 10 a month), readable only by you and the administrator. Delete your account and your developer name goes with it.
While you work, the editor's test stage runs your page in the same sealed frame described below.
A built page runs in a sealed frame on an address of its own. It cannot:
That is why pictures on a built page have to be built into the page itself rather than linked. It means a page made by a stranger cannot collect anything you type into it and send it away. A bar at the top of every built page says it was made by a player, not by the hub.
The page builder and the code editor can write or change a page for you from a description. When you press Build it with AI or Ask AI:
OpenRouter and Groq receive only the description and the page's code (and, from the code editor, the chat and the test stage's console). They do not receive your email, your name, your handle, your account identifier or your address from me, although, like any server, they can see the address of my server. OpenRouter hands the request to the company that runs the AI model it uses (by default OpenAI's open "gpt-oss" model, run by one of OpenRouter's hosting partners). What they do with it is covered by OpenRouter's privacy policy and Groq's privacy policy. Do not put personal details in a description.
The AI key that pays for this is kept on the server. Your browser never sees it.
The AI inside pages built on the hub. A page someone built can have its own AI helper (for example a chatbot, or a game character that talks). The page itself cannot reach the AI or its key — it runs in the sealed frame with no network. When it wants an answer, the hub page around it first asks you, in the hub's own bar at the top, whether the page may use the AI; nothing is sent unless you press Allow, and you are asked again each time you open the page. If you allow it, the question the page asks (which may include what you typed into the page), the page's short description of what its helper is for, and its recent questions and answers are sent to the hub's server and on to Groq, as above, and the tokens count against your daily allowance. The page gets back only the answer's text — never your account, your sign-in, your token count or the key. You must be signed in, and a page can ask at most 30 questions each time it is opened. Don't type personal details into a page's AI.
Only the parts of your project that fit are sent — often not the whole project — and the AI answers with small edits. After each answer the hub adds the number of tokens Groq says it used to your count for the day. That count is stored against your account's identifier as just two numbers (which day, and how many tokens), so the allowance works on every device. It starts again at midnight Toronto time. So that nobody can reset their allowance, the count cannot be deleted from a page — not even by you, and not when you delete your account; it holds nothing about you except that identifier, and it is simply replaced the next day you use the AI. If you want it removed, ask (see "Asking a question").
The sites are hosted by Vercel, and one copy of the tank games hub is also hosted by Google Firebase Hosting. Like every web host, they record ordinary technical information when your browser asks for a page: your internet address (IP address), the page asked for, the time, and your browser's self-description (the "user agent"). I do not use these records to identify anyone, and I do not combine them with anything else. They are kept by those companies under their own policies.
Google Firebase keeps its own technical records of requests to the database. I can see totals (for example, how much data was downloaded in a day) but not a list of who did what.
None of the sites records what you click, how you move the mouse, what you look at, or how long you look at it, beyond the game progress described above.
The shared account keeps these items in your browser's local storage, on your device only:
| Name | What it holds |
|---|---|
jd.account.profile | Your display name, handle, and whether you are signed in. |
jd.account.auth | Your session — the proof that you are signed in. Signing out deletes it. |
jd.account.stats | Level, experience, coins, skin, play time, picture and description. |
jd.account.data.<site> | Anything a game saves through the shared account. |
jd.account.age | The birth year you gave when making an account, so you are not asked again. It is never sent anywhere. |
jd.account.tries | How many wrong passwords were typed in a row, for the waiting time. |
jd.account.saveAt | When the saved games were last copied to your account. |
jd.theme | Light, dark or automatic. |
hub.played | On Tabcade (tabcade.net) only: the names of the last few games you opened from it, for the "Play again" row. It stays on your device. |
hub.projects.v1 | On Tabcade (tabcade.net) only: a copy of the public list of games (names, links, descriptions), so the cards show at once on your next visit. Nothing about you is in it. |
tc.games.<game>.*, tc.games.mute | Tabcade's own games on tabcade.net (Drift Edge, Hook Swing and the ones that follow): your best score, the level you reached, coins you collected, what you unlocked or bought in that game, your progress on today's three missions, your daily streak (the date you last played and how many days in a row), and whether you turned the sound off. It stays on your device and is never sent anywhere. |
tc.menu | On Tabcade (tabcade.net) only: whether you shrank the menu on the left to icons ("mini" or "full"). It stays on your device. |
jd-editor (IndexedDB) | The page you are working on in the code editor — its files, uploads, blocks, your AI chat and up to ten earlier chats — so it is still there if you close the tab. IndexedDB is the browser's own storage for bigger things; like local storage, it stays on your computer. Nothing in it is sent anywhere until you publish (older drafts kept under jd.editor.draft in local storage are moved here and removed). |
jd.editor.chat | Whether you had the AI chat open or closed in the editor. |
jd.editor.ai | Your AI chat settings: which AI, how hard it thinks, how it talks, its mode (straight away, ask first, or plan only), and whether Vim keys are on. |
jd.editor.sent | The last 50 messages you typed to the AI, so the up arrow can bring them back. They stay on this computer. |
jd.editor.chatWidth | How wide you made the AI chat. |
Each game also keeps its own progress in local storage under names of its own. If you are signed in, a copy of that progress is kept with your account (see "Saved games" above).
For one browsing session only (until you close the tab), the sites also note which site you have already counted a visit to, so the counter is not added to twice.
Clearing your browser's data for a site removes all of this for that site. Doing that while signed in simply signs you out; your account is untouched.
My own code sets no cookies. Everything above lives in local storage, which, unlike a cookie, is never sent to a server with your requests.
Loading every site as a new visitor found cookies in exactly one place, set by another company's code:
poki_pubcid and poki_pubcid_cst on the game's own address (an advertising identifier). If you played it before then, those two may still be in your browser until they expire or you clear the site's data.NetworkProbeLimit and WMF-Uniq on its own address, for its own statistics.No other site sets any cookie. If you do not want the advertising cookies, do not open Open Road — nothing else on the hub has them.
Ads on Tabcade (coming). Tabcade (tabcade.net) has applied to show ads from Google AdSense. No ad code runs yet. When ads are switched on, Google and its partners will use cookies or similar storage on Tabcade's pages to show ads and to measure them, which can include ads based on your earlier visits to Tabcade and other websites. You can turn off personalised ads at adssettings.google.com, and see how Google uses this data at policies.google.com/technologies/partner-sites. Ads will only be on Tabcade, never in the other sites listed here. This page will be updated on the day ads start.
Every site on the hub loads the shared account and can use it as described above, unless its row says it does not. This table lists what each one does beyond that. Where a site says "plays in the browser", nothing about your play leaves your device except the shared account's progress, if you are signed in.
| Site | What else it does with data |
|---|---|
| The hub | The account, chat, friends, groups, leaderboard, page builder and AI builder described above. |
| Tower Parkour | Multiplayer: while you play, your position, name and chat messages go to the shared database so other players see them. Levels you build and publish are stored there too and can be played by others. |
| Last Jump (Last Jump) | Multiplayer ghosts: your position and chosen name are shared with other players while you play. Scores, completion times and levels you publish are stored publicly under the name you choose, which does not have to be your real name. |
| Tank games hub (and its homework helper) | Uses a separate Firebase project (tank-d367c), including its Firestore database. Creates an anonymous account while you play. Match state, lobby, invites, queues, chess games and who is online go to that database. It asks GitHub for the latest Voxel Client release. The same hub is also served at tank-d367c.web.app. The homework helper (StudyQuest) uses the shared account instead: your nickname, grade, coins, experience, badges, items and wins are saved with your account (only you can read them), and your name, coins and experience appear on its public leaderboard. Shared study rooms use an anonymous sign-in on the games hub's project and show your display name to others in the room. If you had an old StudyQuest account, you can bring its progress over once: the old username and password are sent to Google to check them, then only the progress is copied. They are not stored. |
| Underwater Survival | Uses the undercurrent-ci4w6 Firebase project for sign-in and multiplayer; you can also play with an offline profile kept in your browser. |
| Legend of Sword | Uses the undercurrent-ci4w6 Firebase project, with no sign-in. While you are in a world, your name, level, position and equipment are shared with others in it, along with shared boss fights, duels and trades. |
| Drift game | Uses its own Firebase project (forza-5a285) with an anonymous account for multiplayer position and chat. The Feedback button sends what you type, with your player name and that anonymous account's identifier, to the game's database, where only I can read it. The landing page's "players online" number comes from my server, which reads the player list the way any player can and sends your browser only the count. The game was prepared for the Poki games platform, but Poki's code only loads when it is played on Poki's own website. |
| Low-poly sandbox | Uses its own Firebase project for multiplayer. |
| Blockcraft | Plays in the browser. Worlds are kept in your browser. When you are signed in, each world is also saved to the shared Firebase project (geo-da, Cloud Firestore) under your account, where only you can read or change it: the world's name, seed and settings, your player's position, inventory and progress, maps you have drawn, and the blocks you changed. Deleting a world in the game can remove that copy too; Delete my account does not, so delete your worlds first, or ask. If you load a resource pack, the game file of a Minecraft version you own, or your Minecraft assets folder, its pictures are read in your browser and kept only on that device; the files are never uploaded. |
| Infinite Earth | Blockcraft's game on the real Earth. Worlds are kept in your browser and, when you are signed in, also in your account (geo-da, Cloud Firestore), where only you can read or change them: the same things as a Blockcraft world, plus where on Earth the world is, at what scale, and a place you marked on the map. Deleting a world in the game can remove that copy; Delete my account does not, so delete your worlds first, or ask. The land streams in as you play from outside map services: terrain and buildings made from OpenStreetMap data, from Cesium ion; the real city in the Real Life view from Google Photorealistic 3D Tiles, reached through Cesium ion; land cover from ESA WorldCover, through Microsoft's Planetary Computer; and Bing aerial pictures on the world map, through Cesium ion. They see your internet address and roughly which part of the world you are playing in or looking at, and place names you search for go to Cesium ion. Map tiles are kept only in memory and your browser's normal cache, never in your saves. A Cesium ion token you paste in yourself stays in your browser. Use Music From My Minecraft asks your browser to let the game read your own .minecraft folder and plays Minecraft's music from your disk; the music never leaves your device. Multiplayer (Open to Friends, then a 6-letter code) goes through Supabase Realtime: while you are in a shared world, the players in it receive a random session number, your display name (or "Guest" and a number), where you are and which way you look, the item in your hand, the blocks you place or break, what you put in chests, furnaces and brewing stands and write on signs, the animals and monsters near you, and your chat lines. Chat and sign text pass the hub's word filter. A friend who joins gets the host world's settings and changed blocks; nothing is stored on Supabase, and a joined world is not saved on the guest's side. The Earth Server (Multiplayer, then Join the Earth Server) is one public world anyone can join, up to 12 at a time: the players on it receive the same things, and the blocks you change there and what you put in its chests and on its signs are stored in Supabase's database (oayeirqalqxnolxbdlnq) so they stay for everyone, without your name or any id. To stop people flooding it, the database also notes your internet address and how many changes it sent in the last minute; that note is overwritten every minute and deleted after ten minutes. Your own spot and inventory on the server stay in your browser. Only signed-in players can chat there. |
| Eternal Realms | A single-player RPG with no multiplayer, chat or leaderboard. Up to three journeys are kept in your browser (IndexedDB). When you are signed in, three more are saved with your account in the shared database, where only you can read them: each journey's name, level, region and chapter, your party, gear, items and gold, quests, places found, position and play time. Delete my account removes them. |
| Chess Ultimate | Bots, analysis, puzzles and lessons work without an account. The Stockfish chess engine runs in your browser, on your own computer; the positions it looks at are not sent anywhere (only if you pick a "Full" Stockfish build is its large file downloaded once from unpkg). Online play uses the shared account, and the chess data is kept in geo-da (Cloud Firestore); only the game's server can write games, ratings and results. Public, to anyone: your chess username, profile (when you joined, when you were last online, and a bio and country if you add them), ratings, stats, achievements, tournament results, leaderboard places, and every online game with its moves, move times and result. While the site is open, signed-in players can see whether you are online, and anyone watching a game can see whether each player is still connected. Chat between the two players can be read by them and the moderators; spectator chat by anyone watching. Your friends, notifications, puzzle history, lesson progress and settings are private. Delete my account does not remove chess data: games stay public, and your chess profile stays under its username. Ask to have it removed. |
| Cookie Empire | You sign in with the shared account, or play as a guest on this device. Your bakery is kept in your browser and, when signed in, saved to the game's server on the shared Firebase project (geo-da, under /ce), which checks each save. Other signed-in players see your public profile (name, title, badge, frame, showcase, score, guild) and your leaderboard place; friends see whether you are online unless you hide it. Room and guild chat is ready-made phrases only. You can download or delete all of it in the game's account panel. There is nothing to buy. |
| IB Entrance Prep | Practice tests marked in your browser. Your attempts, drafts and settings stay in your browser only; nothing you write is sent anywhere. It shows the shared account's sign-in button, which counts a visit. |
| Blocksong Studio | Makes music in your browser. Your songs stay in your browser only. The grand piano sound streams from the Tone.js sample library (tonejs.github.io); a MIDI keyboard, if you allow it, is read by your browser only. It shows the shared account's sign-in button, which counts a visit. |
| Motion Hands | Uses your camera, if you allow it; your hands are tracked in your browser by Google's MediaPipe and the picture is never uploaded. Starting a game downloads the tracking code and model (jsDelivr, Google Cloud Storage); the globe game loads map pictures from Esri. It keeps nothing about you. |
| Kickcraft | Plays entirely in your browser. It does not load the shared account and contacts nothing outside its own address. Worlds, settings and your skin (including a picture you import) are kept in your browser only. |
| NEXUS Browser website | The website and download page for the NEXUS web browser. It does not load the shared account and contacts nothing outside its own address: no cookies, analytics, advertising or outside fonts. Your light or dark choice, and the sites you pin on its Start page, are kept in your browser. The downloads themselves come from GitHub (the public releases page), so GitHub sees that request. This policy covers the website only; what the NEXUS browser does once installed is described in its own privacy policy, on the NEXUS website. |
| Fishing map | If you allow your location, it is used to look up weather, nearby water and routes from the public services listed below. Catch reports you log, with an optional photo, are kept in your browser under your shared account's name, and copied to your account while you are signed in (like any saved game). They are not shown to other visitors. The map has no sign-in of its own any more. The fish-identification camera runs entirely on your device; that photo is never uploaded. Species pictures come from Wikipedia. |
| Webcam fighting games (two versions) | Use your camera, if you allow it. Your movement is worked out in your browser by Google's MediaPipe library; the games do not upload your camera picture to any server of mine. Multiplayer connects players' browsers to each other directly (using PeerJS), which means the other player's browser can see your internet address. Both use the shared account; there is no separate sign-in. If you had an account in the older version, you can bring its progress over once by typing the old username and password, which are checked inside your browser and never sent anywhere. Your account then remembers which old name was brought over (or that you skipped), so it does not ask again. |
| 3D sports games (Ankle Breakers, Sightline, Head Start, Love All, Top Bins, Dodge Rush, Spike City, You're It, Birdie Blitz) | Play against bots in the browser. Online play uses each game's own automatic guest sign-in on a separate Firebase project (ankle-breakers-hoops, or birdie-blitz-shuttle for Birdie Blitz); you only ever sign in with the shared account. Your game profile (name, @handle, what you have equipped, rating and stats) can be seen by other signed-in players; your coins, items and match history are private and only the game's server can change them. In every one of them except Head Start, signing in links the game's account to yours so your coins and items follow you to other devices: the game's server checks your shared sign-in and keeps only your account number, and coins a guest earned in another browser are added in (up to five browsers). During an online match, players' browsers connect directly through Google's public connection servers, so other players in the match can see your internet address. None of them use your camera or microphone. |
| Neon Glide (3D air hockey) | Play against bots, a friend on the same keyboard, training drills and tournaments without going online. Your player name, avatar, level, coins, items, stats, settings and last 40 results are kept in this browser, and replays of your last 15 matches stay in this browser's IndexedDB and are never uploaded. Before playing you make a Neon Glide account with a player name and a password, or log in to one. There is no email: the login runs on Firebase Authentication on the game's Firebase project (ankle-breakers-hoops) with a made-up address built from a random key, and Firebase keeps only a scrambled (hashed) copy of the password, so a forgotten password cannot be reset. Player names are unique; each name is stored with its owner's account id and login key so the game can check a name is free and log you in by name. A copy of your progress is saved to your account, readable only by you. Profile → Delete account removes your name, progress, leaderboard row and login. The game has its own short privacy page at neon-glide-one.vercel.app/privacy.html. The global leaderboard shows your player name, avatar, level, wins, losses, goals and rating to everyone. Online rooms, quick match and ranked run through that Firebase database: the browser of whoever made the room runs the match and everyone else syncs to it, and the people in a room see each other's names, avatars, levels, ratings, equipped items and quick-chat lines. There are no direct browser-to-browser connections, so other players do not see your internet address. While the page is open it notes that you are online (yes/no and a time) for the hub's online count. If you enter your own game server address the game connects there instead. No camera, microphone, ads or tracking cookies. |
| PvE Client (Minecraft mod download page) | A download page. Nothing beyond the shared account. |
| Browser Sandbox | Multiplayer connects players' browsers directly (PeerJS), which exposes your internet address to the people you play with. Scripts and models you make are saved in your browser only. |
| Atlas | As soon as the page opens — before any access code — it looks up your approximate location from your internet address (GeoJS) and the weather there (Open-Meteo), and checks whether its helper program is running on your own computer (a check that never leaves your device). The assistant itself only works with an access code. What you type or say is sent to AI companies (OpenRouter, Groq, or Google Gemini) to get an answer, and speech may be produced by Microsoft's Edge voices or ElevenLabs. For weather and location it uses your approximate location from your internet address (via geojs.io) or, if you allow it, your device's location, with Open-Meteo for weather. It can look things up with Brave Search or DuckDuckGo and show nearby aircraft from adsb.lol. Chat history is kept in your browser. |
| AI chat | Sends your messages to an AI gateway running on my own computer, reached through a Cloudflare tunnel; it only answers while my computer and the tunnel are running. That gateway passes your messages on to whichever AI service the chosen model belongs to. Your conversations are kept in your browser. |
| Math tutor, Minecraft schematic designer and chemistry lab (its AI helper) | The AI features work only with an Anthropic key that you paste in. It is saved in your browser and sent only to Anthropic, with your questions. Everything else runs in the browser. |
| Flight simulator (Stratos) | Downloads map and terrain pictures from public map providers as you fly, which means those providers see your internet address and roughly which part of the world you are looking at. |
| Minecraft web client | This is a copy of the open-source client from mcraft.fun. Joining a server connects you to that server, which sees your internet address and your chosen player name. That project's Umami analytics tag has been taken out. Once you are in a world it downloads its sounds and block pictures from GitHub, and Explore maps opens that project's map site (maps.mcraft.fun). An older second copy now only shows a "Moved" note pointing here. Signing in with Microsoft or Google goes to those companies directly. |
| Photo simulator | Everything runs in the browser. |
| Voxel Client (the launcher) and its website | The launcher signs in with Google or with email and password on the tank-d367c project. It stores your Minecraft name, friends, friend requests, capes, chat messages, whether you are online, and feedback you send. Launcher chat can be read by every signed-in launcher user. |
| Every other game and tool | Plays in the browser. Nothing beyond the shared account. |
These are all the outside companies and services that receive anything when you use the sites, and exactly what they get. Each has its own privacy policy.
Some games load open-source libraries (for example three.js for 3D, or a physics engine) from public code servers: jsDelivr, cdnjs (Cloudflare), unpkg, esm.sh, Skypack and Google's gstatic. They see the request for the library, like any web server. Where a library has a fixed version, the page checks it with a cryptographic fingerprint, so a tampered copy is refused rather than run.
Nobody else receives anything.
The database and account system are Google's, and the default location for these databases is the United States. Vercel runs its servers in many countries, and the server that runs the AI builder is in the United States. So if you are outside the United States, using the sites means your data is stored and handled there.
Anything kept in local storage stays on your own device.
Only to make the sites work:
If you are somewhere where the law asks for a reason ("legal basis") for handling your data: accounts, messages and progress are handled because you asked for the feature by signing up and using it; the abuse limits and security measures are handled because keeping the sites safe for everyone is a legitimate reason; and anything that depends on your permission — your camera, your location — is used only after you give it and stops when you take it back in your browser's settings.
| Anyone on the internet | Built pages (by their address), the leaderboard (display name, handle, level, coins, skin and small picture), the visit counters, and scores and levels published in the games that have public boards. In Chess Ultimate: chess profiles, ratings, leaderboards and every online game. |
|---|---|
| Any signed-in player | All of the above, plus the public chat, and whether you are online in Chess Ultimate. |
| Your friends | That you are friends, and the messages you send them. |
| A group's members | The group's messages and member list. |
| Only you | Your email, profile description, saved games, play time, friend list, requests, AI count, and everything on your device. |
I want to be straightforward about this. As the owner of the Firebase projects, I can open Google's console and see everything stored in them, including direct messages and group messages, in the same way that the owner of any online service can. The rules on this page decide what other players can see; they do not hide anything from the owner of the database.
I cannot see your password — nobody can, not even Google — and I cannot see anything kept only on your device.
I can delete messages, remove a profile from the leaderboard, and, in the launcher, put someone in a timed chat time-out, if someone is being abusive or breaking the rules. These actions are checked by the database against my own account; no other account can do them, whatever a page shows.
When I remove a profile from the leaderboard, a copy is kept in a trash area so that a mistake can be put straight back. I empty it by hand. This is separate from Delete my account, which you control and which keeps no copy.
| What | How long |
|---|---|
| Your account and everything in it | Until you delete it. There is no automatic expiry. |
| Chat messages | Until the sender or a moderator deletes them. The chat shows the latest 40. |
| Built pages | Until you delete them or your account. |
| Sign-in tickets between sites | One minute, and destroyed the moment they are used. |
| "Who is online" entries | While you are connected; anything left behind is removed after ten minutes. |
| Daily AI build counts | Kept with your account; deleted with it. |
| Visit counters | Indefinitely, as totals. They contain nothing about any person. |
| Profiles removed by a moderator | In the trash until I empty it. |
| Infinite Earth's Earth Server builds | Kept while the server runs; anyone playing there can build over them. They carry no name or id. The flood-control note (internet address and change count) is deleted after ten minutes. |
| Chess Ultimate profiles and games; Blockcraft and Infinite Earth worlds saved to your account | No automatic expiry. Worlds go when you delete them in the game. Delete my account does not remove these; ask (see Asking a question). |
| Hosting and database records | As long as Vercel and Google keep them, under their own policies. |
| Things on your device | Until you clear them, sign out, or delete your account. |
Open the account panel in the top corner of any site and choose Delete my account. You will be asked to type DELETE to be sure. It removes, in one go:
There is no undo, and no hidden copy is kept for later. Signing out instead leaves your account alone and only stops using it on that device.
Four things are outside that button: Cookie Empire's bakery data (delete it in the game's account panel, where you can also download it); the games that use their own Firebase projects with anonymous accounts (their data is tied to a random identifier, not to you); what Chess Ultimate, Blockcraft and Infinite Earth keep in the shared project's other database, Cloud Firestore (your chess profile and games, and worlds saved to your account — delete worlds in the game first); and the records the hosting companies keep. If you want anything from those removed, ask (see Asking a question).
Wherever you live, you can:
A parent or guardian can ask for any of these on behalf of a child.
An account gives you a name other people can see and a chat other people can read, so accounts are for players 13 and over. Before a first account is made, the page asks for your birth year. The year is kept only on your own device, so you are not asked again; it is never sent to me.
None of the sites carries advertising. (Open Road used to, until 12 October 2026; if someone played it before then, two old advertising cookies may remain until they expire or are cleared, see Cookies.)
If the year means you are under 13, no account is created — and nothing else changes: every game plays exactly the same as a guest, with progress saved on your device.
If you are a parent and think your child under 13 has made an account anyway, use Delete my account on their device, or ask me and I will remove it.
One account at a time. To keep bots out, only one account can be used at a time in your browser. Using the same account in several tabs is fine. But if another tab signs in to a different account, the older tab stops and asks to be closed. This is worked out entirely inside your browser, from the sign-in it already keeps; nothing about it is sent anywhere or stored. It cannot see other browsers or private windows, because doing that would mean fingerprinting people, which these sites never do.
No system is perfect, but these are the measures in place:
The part that depends on you: use a password that you do not use anywhere else, and do not share your account.
When you click a project on the hub while signed in, the link carries a random ticket number — never your sign-in itself. The ticket is kept in the database for one minute, works only on the one site it was made for, and is destroyed the moment that site uses it. If a link like that is copied, shared, or opened later, it does nothing.
Sites can also ask the hub to sign you in through a small window. The hub only hands your sign-in to sites that belong to me.
If I learn that someone has got at account data they should not have, I will fix the cause as quickly as I can, put a notice on the hub saying what happened, what was affected and what you should do, and, where the law requires it, tell the privacy regulator. Because the sites never send email, a notice on the hub is how you will hear about it.
If you find a security problem yourself, please report it — see /.well-known/security.txt on the hub.
None of the sites sends email of any kind — no newsletters, no notifications, no marketing. There is nothing to unsubscribe from. The only emails you can ever receive are ones you ask Google to send: a password reset link.
None of my own code tracks you across websites, so a "Do Not Track" or "Global Privacy Control" signal has nothing of mine to switch off. The outside services listed above follow their own policies on those signals.
The sites are run by one person in Ontario, Canada. Canada's privacy law applies, and so do the laws of the places whose visitors have their own rights, as far as a hobby project can meet them. If anything on this page is ever less protective than the law where you live, the law wins.
When the sites change what they do with data, this page is updated at the same time, and the date and version at the top change. A change that means more of your data is shared, or shared with someone new, will also be announced on the hub before it takes effect.
tabcade.net/dev): a public developer name, games sent in for approval, a public list of approved community games, and a monthly count (see "Pages you build on the hub"). Tabcade's own games also keep daily missions and a daily streak on your device.hub.played, hub.projects.v1, tc.menu, tc.games.*) are now kept on tabcade.net. Signing in there uses the same account as the hub.tc.games.*).tc.games.<game>.best) and nothing else.tc.menu, on your device only).hub.played, on your device only) to show a "Play again" row.hub.projects.v1) so the cards show at once next time. It holds only the public list, nothing about you, and is never sent anywhere.Everything held about you is on your own profile, and Delete my account removes it without asking anyone. For anything else — a copy of your data, removal of something the button does not cover, a question about this page, or a report about someone else's page — contact me through my GitHub profile at github.com/jordanengrashes-ux. Please do not put personal details in anything posted publicly there; say what you need, and I will reply with a private way to sort it out.
↑ Back to the top