Tower Hub
Privacy
Short version: the tools on this site run in your browser and keep your data there. The exceptions are sharing your tower in the Flipstars Tower Discord, a live review of your tower on the stream, and in the Creator Code Report loading earnings with an impact.com API key or asking the chat, both of which pass through our server without being stored, and signing in with Google to see your own channel on /account — all of them you start yourself.
Tools that stay in your browser
The Advisor, the Run Tracker and the game-export import keep everything in your browser's local storage. Your game export is read on your device and is never uploaded by these tools. Clearing your browser data removes it.
Creator Code Report
A CSV report you drop on the Creator Code Report page is read in your browser and never uploaded. If you load your purchases with an impact.com API key instead, the Account SID and Auth Token are sent to this site's server with each load. The server uses them only to ask impact.com for your purchases and hands the result back to your browser; it does not store or log the key or the purchases. "Remember on this device" keeps the key in your browser's local storage, and "Forget my key" removes it. If you enter your YouTube channel, the server asks YouTube for that channel's public video numbers and may keep the answer in a cache for up to an hour.
If you ask something in that page's chat, your question, your earlier questions in the chat and the purchases and uploads shown on the page go through this site's server to OpenRouter and the company running the AI model, to write the answer. The request asks for providers that don't keep it for training. We don't store any of it, and your impact.com key is never part of it. Nothing is sent until you ask.
Sharing your tower (Discord /tower)
When you run /tower upload and post from the page it links to, your tower card appears in your own thread in the Flipstars Tower Discord, visible to the members of that server. To compare uploads we store, in a private storage area of this site:
- your Discord user id, your server display name and your league role at the time of each upload;
- the id of your thread;
- per upload: the date, your lab levels and the labs you are researching, ultimate weapon levels, current tier and wave, your best wave per tier, your stones on hand, your equipped modules with their substats, the cards you own (stars, which are equipped, which masteries are unlocked), your last 10 runs as the battle report shows them (tier, wave, time, coins and coins by source, cells, cash, gems, reroll shards, enemies, damage, what killed you), your last 10 tournament results and your league, and lifetime totals (coins, cells, damage, waves, enemies, research, stones earned);
- what the game's ultimate weapon screen adds on top of the levels, so your thread shows the same values: your best Dissonance wave per tier, which of the relics that raise ultimate weapon damage you have unlocked, your ultimate weapon vault upgrades and the Black Hole size slider. No other relics or vault upgrades are sent.
Your thread shows a summary of your labs; anyone in the server can open the full list of a category from the menu below it, and only they see that reply. Card and module icons are the game's own art, used as the bot's Discord emojis.
"Stones earned" is the number from the game's stats screen, and the game counts bought stones in it. So a big jump between two uploads can show that you bought some. How many of your stones were bought is never sent.
Never stored or sent — it does not leave your device:
- the export file itself;
- your in-game name, player/account id and session data;
- purchases, how many of your stones were bought, gems, cash and coins on hand.
Before anything is posted, the upload page shows you the card and the exact data it will send.
Live review on the stream (/review)
When you pick your game export on /review and ask for a code, your browser sends the numbers the review calculates with: your battle history (if your export contains it), lab, ultimate weapon, module, card, workshop, enhancement, vault and relic levels, lifetime totals, your coins on hand and your spare modules. It is stored in a private storage area under the code, for 24 hours at most.
When you type !review CODE in the live chat, the stream server fetches it, the co-host reviews your tower live on a public stream — your chat name and your tower's numbers are shown and spoken on air — and the upload is deleted right after. An upload that is never used is deleted after 24 hours.
Never sent: the export file itself, your in-game name, player/account id, session data, purchases, gems, cash and how many stones you bought.
Answer pages from the stream (/a/…)
When the co-host answers a game question you asked in the live chat and the answer has videos or guides to go with it, the stream server stores your chat name, your question, the answer and those links in a private storage area and shows a short link on stream. Anyone with the link can open that page. It is not indexed by search engines and is deleted after 24 hours. Nothing else about you is stored for it.
Sign in with Google (creator dashboard, /account)
Creators can sign in with Google to see their own YouTube channel on /account. The sign-in asks for your Google account id, e-mail address and name, plus two read-only YouTube permissions: see your YouTube account (channel name, picture, your uploads) and see its YouTube Analytics reports. Tower Hub cannot upload, edit or delete anything.
Nothing of this is stored on our server. The access Google grants sits encrypted (AES-256-GCM) in a cookie in your own browser for up to 30 days. Each time you open the dashboard the server uses it to read your numbers live from YouTube, keeps the result in memory for up to 15 minutes so a reload is fast, and shows it only to the browser that holds the cookie. The data is used for nothing but showing you your dashboard: not for ads, not sold, not shared, not used to train AI models, and no person at Tower Hub reads it.
"Ask your channel" on /account is optional. When you ask a question, the question, the conversation so far and your dashboard numbers are sent through OpenRouter to an AI model (Anthropic's Claude by default) to write the answer. Requests are only routed to model providers that do not store or train on them. Tower Hub keeps neither the question nor the answer; the conversation stays in your browser tab. The server only logs how many tokens a question used and what it cost.
The comments view on /account shows the public comments under your videos. They are read with Tower Hub's own YouTube key, not with your sign-in, kept in memory for up to 15 minutes and shown only to you. Tower Hub builds no profile of the people who comment and stores none of it.
Tower Hub's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. The YouTube data comes through the YouTube API Services; the Google Privacy Policy applies to it on Google's side.
"Sign out" deletes the cookie. "Remove access" on /account also tells Google to withdraw the permission; you can do the same at myaccount.google.com/permissions.
Tower Cutter (/creators/cutter)
Your stream recording stays on your computer: the page reads and cuts it in your browser. To find the moments, only the audio (compressed) goes to a speech-to-text service, and the transcript's words, and for the clips you make the words in them, go to an AI model provider. Both work for us as processors, only to do this job. Tower Hub stores neither the audio nor the words; the transcript stays in your browser, and so do the moments (for the private beta, see the next paragraph). The server only logs how much a search or a title round cost, and with the private-beta code, which tester came in. You can delete what your browser keeps by clearing this site's data.
Numbers, graphs and the memes you make from your own pictures are drawn in your browser. For a meme from one of the templates, the two lines you write go through Tower Hub's server to a service that draws the picture. Nothing else is sent with them; the lines appear in the server's request log, which is kept for a short time.
In the private beta, what you do with the moments the search finds is sent to Tower Hub a few seconds after each change: which ones you tick, where you move their start and end, which ones you make clips of or export for your editor, and the ratings and notes you give. With it go the moments as the search listed them (their times, topic, the search's one-line reason and the chat question a moment answers), the moments you mark as missed, and the recording's file name and length, filed under your tester name. No video, no audio, no transcript. We use it only to make the moment search better and keep it until the beta ends; tell us and we delete yours sooner.
Deleting it
Run /tower delete in the Discord: it deletes your thread and everything stored about it, immediately. A moderator who removes a thread stops further posts to it; ask a mod if you want to post again.
Who processes it
The site runs on Vercel (hosting and storage). Discord hosts the threads under its own terms. A live review runs on the stream's own server, which keeps nothing of your upload after the review. Nothing is sold or shared with anyone else.