Privacy Policy

Starclaim has accounts and sells in-game purchases, so it collects more than the rest of the site.

What it collects, and why

• Email address — To identify your account, let you sign in and recover access, and contact you about your account or a purchase.
• Username — To identify you to other players in-game.
• Gameplay data — your progress, holdings, and in-game activity — To run the game. This is the save file; without it there is no game to return to.
• Purchase records — what was bought and when — To grant what you paid for, and to answer support questions about a purchase.

Who it is shared with

• A third-party payment processor — Takes payment and handles card details directly. Starclaim never receives or stores your card number — it only records that a purchase succeeded.

How long it is kept

Account and gameplay data is kept for as long as the account exists. Purchase records are kept longer, because tax and accounting rules require it.

Deleting your data

Email support@bytesizefactory.dev from the address on the account, or tell us the username, and we will delete it. The full explanation of what deletion removes is on the account deletion page.

Starclaim support

Bodkin is a multiplayer game, so it handles the data needed to put you in a match with other people.

What it collects, and why

• Username or display name — To identify you to other players in a match.
• Match and gameplay data — To run matches and keep results consistent between players.

Who it is shared with

No third parties beyond the hosting needed to run it. Your data is not sold or shared with advertisers.

How long it is kept

Match data is kept only as long as it is useful for running and debugging the game.

Deleting your data

Email support@bytesizefactory.dev from the address on the account, or tell us the username, and we will delete it. The full explanation of what deletion removes is on the account deletion page.

Bodkin support

Quantum Clash can be played all the way through without an account. Signing in is optional, and it is what turns on the public leaderboards and progress that follows you between devices.

What it collects, and why

• Email address, only if you choose to sign in — To send you a one-time sign-in link and code, to identify your account and recover access to it, and to contact you about the account. There is no password, so there is no password to store or leak.
• Callsign — the name you pick — To identify you to other pilots in a match and on the public leaderboards. You choose it, and it is never your email address.
• Pilot progression — your level, ship mastery, and unlocked paint jobs — To run the game. This is the save file; without it there is nothing to come back to.
• Match results — your score, kills, and placement in a finished match — To award progression for the match and to rank the daily, weekly, and monthly leaderboards.
• A random guest identifier, kept in your own browser — So you can play and keep progress without giving us anything at all. It identifies a browser, not a person, and it never reaches a leaderboard. Clear your browser storage and it is gone.

Who it is shared with

• Supabase — Runs the email sign-in and stores accounts, callsigns, progression, and match results.
• Resend — Delivers the sign-in emails. It handles the message and the address it goes to, and nothing about your game.
• Fly.io — Hosts the multiplayer server that runs matches. It sees the live traffic of a match in progress.
• Vercel — Serves the game itself to your browser.
• CrazyGames — Only when you play Quantum Clash on their site. They host the page and provide your identity there, so we never receive an email address for a CrazyGames player, and a CrazyGames account is separate from an email one.

How long it is kept

Your account, callsign, progression, and match results are kept for as long as the account exists — deleting the account deletes all of it. The daily, weekly, and monthly leaderboards are views over those results rather than separate copies, so a board rolling over changes what is shown and not what is kept. Guest progress is only ever in your own browser, so it lasts until you clear it.

Deleting your data

There is no delete button in the game yet, so the route is email and we run it by hand. The full explanation of what deletion removes is on the account deletion page.

Quantum Clash support

NeedToKnow has accounts and a backend that reads news feeds on your behalf, so it holds a little about you — your email, the filters you write, and the settings that decide when it runs — but it ships with no analytics, no advertising identifier, and no access to your location, contacts, or photos.

What it collects, and why

• Email address — To identify your account, sign you in, let you recover access, and reach you about the account. Sign-in is handled by Supabase Auth; if you use a password, only a salted hash of it is stored, never the password itself.
• An account identifier — a random id created when you sign up — Everything else the service stores is keyed to that id rather than to your email, so your filters and your results can be told apart from someone else's.
• The filters you write — the name and the criteria text of each one — To decide what to surface. This is the whole product; without it there is nothing to match against. It is also the one thing that leaves our servers for the scoring model, so read the Anthropic entry below before you write anything private into a filter.
• A notification token for your device, if you allow notifications — To send you a push when a story clears your bar. It is optional — decline the permission and the app works fine, you just check the Signal tab yourself. Turning notifications off in the app, or signing out, deletes that device's token.
• Your chosen scan frequency — To know when your next scan is due. You pick it in the app; your plan only sets the fastest cadence you are allowed to choose.
• The stories surfaced to you, and your scan counts — To fill the Signal tab and to show you the service actually ran — for each story, the headline, link, publisher, date, and the one-line reason the scorer gave. A short-lived record of which feed items you have already been screened against goes with it, so the same story is never scored against you twice.

Who it is shared with

• Supabase — Runs the database and the sign-in system. It holds your email, your account id, your filters, your settings, your device token, and the stories surfaced to you.
• Fly.io — Hosts the background worker that reads the feeds and runs your scans, in their US East region in Virginia. Everything above passes through it in memory; its logs record your account id and scan counts, never your email and never your filter text.
• Anthropic — Scores stories against your filters. Each scan sends the name and criteria of your enabled filters exactly as you typed them, together with a batch of public news items — headline, publisher, and up to roughly 400 characters of the published summary. It does not send your email, your account id, or your device token, and the request comes from our server rather than your phone, so it does not carry your IP address either. The practical version: a filter is a description of a topic, not a diary, so do not write anything into one you would not want a third-party model to read.
• Google Firebase Cloud Messaging — Delivers the push notifications. It receives your device token and the notification itself — when a single story clears your bar, that is the publisher name, the headline, and the link to the publisher's page; when several clear at once, it is only a count of how many.

How long it is kept

Your email, account id, filters, settings, and device tokens are kept for as long as the account exists. Surfaced stories are kept with the account as well — the app shows a rolling seven-day window, and older rows stay in the database until the account goes. The records of what has already been screened for you are deleted automatically seven days after they are written, and a device token is deleted as soon as you turn notifications off, sign out, or Firebase reports it dead. Deleting the account removes all of it. Two things trail behind it: copies inside encrypted database backups until those roll over, and the worker's log lines, which carry your account id and a couple of counts but never your email and never your filter text. Neither is kept more than 30 days.

Deleting your data

In the app: Account tab, then Delete my account, then type DELETE to unlock the button. It happens immediately and cannot be undone, and it takes everything with it — your login, your filters, every story surfaced to you, your scan stats, your settings, the record of what has already been screened against you, and any device tokens. What outlives it is described above and nothing else: the backup copies, which roll over on their own and are never used to bring one account back; the worker log lines, which carry a random id and nothing that reaches you; and the filter text already sent to the scoring model on earlier scans, which left our servers before you deleted and cannot be pulled back. If you would rather we did it, email us from the address on the account and we will. The full explanation of what deletion removes is on the account deletion page.

NeedToKnow support

GameHydra is a Windows app that runs on your own machine, with no account and no sign-in. It reads where your launchers record their games — Steam's library files, Epic's manifests, GOG Galaxy's registry entries and its local database, and the EA app's and Ubisoft Connect's registry entries and install folders — along with your drives, and it writes its settings, its record of what it has stored, and its log to a folder on your PC. None of that is sent anywhere. The app goes online for two things only: activating or releasing a licence key, and, when it was installed with the GameHydra installer, checking for updates. Buying it is what introduces an email address and a licence key. All of it is described below.

What it collects, and why

• Nothing about your games or your drives, from the app itself — GameHydra never sends your games, your libraries, your drives or its log anywhere. Its settings, its manifest of stored games and its log stay in %LOCALAPPDATA%\GameHydraData on your own disk. Those files name your games, your drive letters and your folder paths, which is precisely why they never leave the machine. The one request it makes without a licence is the update check, in copies installed with the GameHydra installer: a minute after it starts and every six hours after that, it asks the licence server whether a newer version exists and downloads it if so. That request carries no licence key and nothing about your games or drives.
• Email address — To send you your licence key, tie it to your purchase so you can recover it if you lose it, and reach you about that purchase.
• Purchase records — what was bought and when — To know what your licence covers, and to answer a question about a charge.
• A licence key, and one activation record per machine — To check that a licence is used on no more machines than it covers. A machine is identified by a one-way hash of a few facts that stay the same across reboots — the Windows machine id, the processor name, the system drive's label and size, and the computer name — worked out on your PC and sent with the licence key and the app version when you activate. Releasing a PC from GameHydra's Settings sends the same key and hash so the slot is freed. The activation record keeps the key, that hash, and when the machine was activated and last issued a token; it does not store your IP address. The underlying facts never leave your PC, none of them is a MAC address, and none of them says anything about what you play. After activation the app checks the licence on your PC and does not contact the server again on its own.

Who it is shared with

• Paddle — Acts as merchant of record — takes the payment, handles card details directly, and is responsible for sales tax and VAT on the purchase. Your card number never reaches us — only the fact that a purchase succeeded.
• Vercel — Hosts the getgamehydra.com website, including the sign-in and account pages, and its DNS.
• Supabase — Hosts the database behind sign-in — a plain Postgres instance holding session and email-verification-token rows for the licence portal, not your filters or anything about your machines.
• Fly.io — Runs the licence server — the one part of GameHydra with its own database — which issues licence keys, records and checks per-machine activations, and serves the app's update feed.
• Resend — Delivers the email carrying your licence key, and the sign-in links for the licence portal.

How long it is kept

What is on your own disk lasts as long as you leave it there. Uninstalling GameHydra deliberately leaves %LOCALAPPDATA%\GameHydraData behind so that a reinstall picks up where it left off; delete that folder yourself and nothing of it remains. On the store side: a licence and its activation records are kept for as long as the licence exists, and purchase records are kept longer than that, because tax and accounting rules require it.

Deleting your data

There is nothing on our side to delete for the app's own data, because it never sends any: what it sends when you activate is the licence key and machine hash covered by the activation records. To clear what it keeps locally, uninstall it and delete %LOCALAPPDATA%\GameHydraData. Email us from the address on the purchase and we will delete that account and its activation records — say whether the licence should go with it, because the account is also how a lost key is recovered. The full explanation of what deletion removes is on the account deletion page.

GameHydra support

The Guide Forge is retired. This section stays published because it had user accounts, and people with accounts keep their rights over that data after a product shuts down.

What it collects, and why

• Email address and username, from accounts created while it was running — It was used to sign in and to attribute published guides. Nothing new is being collected — the service is off.

Who it is shared with

No third parties beyond the hosting needed to run it. Your data is not sold or shared with advertisers.

How long it is kept

No new data is collected. Any remaining account data from when the service ran is kept only until it is deleted on request or removed in the course of shutting the service down.

Deleting your data

Email us and say you had a Guide Forge account. Include the email address or username you used, so we can find it. The full explanation of what deletion removes is on the account deletion page.

The Guide Forge support