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 me the username, and I 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 me the username, and I will delete it. The full explanation of what deletion removes is on the account deletion page.

Bodkin 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 my 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 my 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 my servers before you deleted and cannot be pulled back. If you would rather I did it, email me from the address on the account and I will. The full explanation of what deletion removes is on the account deletion page.

NeedToKnow 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 me and say you had a Guide Forge account. Include the email address or username you used, so I can find it. The full explanation of what deletion removes is on the account deletion page.

The Guide Forge support