Privacy Policy
Effective October 14, 2026
The short version: accounts are optional, there are no ads and no tracking, and we don’t sell anything about you. Without an account we keep the name you type and your table’s play-money scores only while the table exists, and tables delete themselves. After that we keep a short record of each game (the room code, when it ran, and how many played and were signed in), with no names in it. If you sign in with Google, we also keep your name, email address and the Past Games you save, until you delete them or your account. If you buy the table unlock, Stripe takes the payment and we keep only a note that your account bought it. We also count visits to the site, without cookies, under a code that changes every day.
This policy explains what Starsade (“we”, “us”) stores when you use starsade.com and its games, and why. It goes with our Terms of Service.
1. What we collect, and why
Table data. When you take a seat we store the name you type, and what happens at your table: play-money chips and buy-ins, bets, hands and results, and the table’s settings. The game also creates a random seat ID and a secret seat code for you, so you can get back to your seat if your connection drops or you refresh. We use this to run the game and show it on the TV and phones. The name you type is shown to everyone at the table and on its TV, so use a nickname if you like.
Technical data. Like any website, our host receives your IP address, browser and device type, the address you asked for (which includes a room code) and the time of each request. We use it to deliver the site, keep it secure and prevent abuse. To stop people sweeping through room codes, our server limits how often one IP address can look up or join rooms; it keeps only a counter for each address for a few seconds, and it is not saved with the table.
Account data (only if you sign in). Signing in is optional, and Google is the only way to do it for now. When you do, we store your name and email address as Google gives them to us, and the account ID Google uses for you. We don’t receive a password or your contacts. Google also sends a link to your profile picture; we don’t keep it or show it. We use this to recognize you when you come back, to show your name, and to keep your saved games (section 3).
Usage counts. For each game played at a table, from the moment the host starts it, we keep a short record in our database: the room code, which game it was, when it started and ended, how many rounds were played, how many players sat down, and how many of them were signed in (a signed-in phone tells the table so). It holds no names, seat IDs, IP addresses or account IDs. If someone at the table saves the game to their account (section 3), that saved game has the same room code and times, so the two can be matched. We use it to see how the site is used, such as how many games are played each day.
Visit counts. To see how people find the site and what they do there, we count visits in our database: which pages were viewed (as the kind of page, such as a table’s TV screen, never with its room code); which of a few buttons were pressed (a game on the front page, Join Room, Sign in with Google, opening the table unlock, and its buy button) and whether a new account was made; the site that linked to us, or the campaign tag in the link (such as utm_source=tiktok); whether the browser was signed in; and whether it looks like a bot or a script. Each visit is filed under a code for that day, made from your IP address and browser type with a random secret. The secret is deleted when the day is over and, like other deleted data, can still be restored from our database’s recovery history for up to 30 days after that (section 3). Once it is gone, visits can’t be linked from one day to the next or back to a person. We don’t store your IP address or browser details for this. We keep the counts for 400 days.
Otherwise, apart from the name you type, we don’t ask for your email, phone number, precise location or contacts, and we never see or store your card details (section 3).
2. Cookies and your browser’s storage
Starsade sets one cookie that is always there, starsade_howto. It lasts a year and only remembers that you have seen the “How to play” tour so it doesn’t open again.
If you sign in, it also sets sid, which keeps you signed in on that browser. It holds a random code that only we can match to your session (we store only a one-way hash of it, not the code itself). It lasts 90 days, or until you sign out or delete your account. It is sent only to starsade.com, and your browser’s scripts can’t read it.
While you are at Google signing in, it sets oauth, which holds the one-time check that the sign-in coming back is the one you started. It lasts 10 minutes at most, is cleared as soon as sign-in finishes, and is only sent to our sign-in pages. We use no advertising, analytics or tracking cookies, and the visit counts (section 1) store nothing on your device.
The site also keeps a few things in your browser, on your device only:
- Per tab (session storage, gone when you close the tab): your name, seat ID and seat code for the room you are in, so a refresh puts you back in your seat.
- Per browser (local storage, kept until you clear it): a seat key for each room and name you have sat as, so you can take that seat back after closing a tab (removed when you leave the room); a list of the last 20 finished games this device has seen (room code, date, and the players’ names and play-money results) shown as “Past Games” on the front page, and, if you have signed in, a note of which of them your account already has; whether you have seen the tour; and your sound and music volume.
We never receive your settings; the seat key goes back to the table only to prove that a seat is yours. We receive your Past Games only if you sign in (section 3). When a game ends, the TV and every phone at the table save it to their own Past Games, with everyone’s names and results. Those copies live on those devices; we can’t see or delete them, except for copies saved to an account. Clearing site data in a browser erases what that browser holds; the cost is that the tour shows again and its Past Games are gone.
3. Accounts and saved games
Saved games. While you are signed in on a browser, each game that ends there is saved to your account, and the first time you sign in the games already on that device are saved too. A saved game holds the room code, when it started and ended, how many rounds were played, which game it was, and, for everyone who sat at that table, their name, buy-in, final chips, result and whether they left or were removed. That is the same information the Past Games list already shows, so it includes the names other players typed. If you play on a phone, the game also notes which row was you. A TV that is signed in saves the table’s games to the account it is signed in to, so only sign a TV in to your own account.
Where and how long. Your account and saved games are kept in a Cloudflare D1 database. We keep them until you delete them or your account, and we keep up to 500 saved games per account (past that, the oldest are removed). A sign-in session lasts up to 90 days, or until you sign out.
Deleting. “Delete account”, under Past Games on the front page while you are signed in, removes your account, your sign-in sessions and your saved games from our database immediately. Our database (Cloudflare D1) keeps a point-in-time recovery history that is always on, so deleted data can still be restored from it for up to 30 days, after which it is gone for good. Games saved on your own devices stay there until you clear them.
Purchases. The table unlock is paid for through Stripe Checkout, on Stripe’s own page, where you enter your payment details. To start the payment we send Stripe your account’s email address and an account ID, so the payment reaches your account. Stripe processes the payment under its own privacy policy (section 5). We never receive your card details. We store only that your account bought the unlock: the Stripe checkout session ID and the date. That note is deleted with your account, and, like the rest of the account, can be restored from the database’s recovery history for up to 30 days after.
Google. When you choose “Sign in with Google”, your browser goes to Google, which asks you to approve and then tells us your name, email address and account ID. Google handles that step under its own privacy policy (section 5). We don’t send Google anything about your games or the tables you play at.
4. How long we keep it
- Table data sits in the table’s own room, which deletes itself: within a day of the last time anyone played at it or had it open if the table never started or has finished, and within a week of that if a game is still in progress (so you can pick one up after a weekend). A player who leaves may stay on the table’s scoreboard until the table is deleted.
- Request logs are kept by our host for a limited time under its own policies.
- Rate-limit counters last seconds.
- Usage counts are kept for as long as they are useful; they hold no names or account IDs (section 1).
- Visit counts are kept for 400 days. The secret that makes each day’s visitor codes is deleted when the day is over, and stays in the database’s recovery history for up to 30 days after that (section 1).
- Account data and saved games stay until you delete them or your account (section 3). Sign-in sessions last up to 90 days. After you delete an account, its data stays in the database’s recovery history for up to 30 days (section 3).
- On your device, until you clear it, as described above.
5. Who else handles data
- Cloudflare hosts Starsade, runs its game servers, keeps the request logs and stores account data in its D1 database. Its global network may process data in other countries. See Cloudflare’s privacy policy.
- Google, if you sign in with Google, handles the sign-in itself and tells us your name, email address and account ID. Your browser sends Google its usual request details, including your IP address. See Google’s privacy policy.
- Stripe, if you buy the table unlock, takes the payment and keeps its own records of it, including your payment and billing details. To start the payment we send Stripe your account’s email address and an account ID, so the payment reaches your account. See Stripe’s privacy policy.
- Google Fonts supplies our typefaces. Pages load them from Google, so your browser sends Google a request that includes your IP address and browser details. See Google’s privacy policy.
- MLB Stats API. The TV screen can show a baseball score line. The TV’s browser, not our servers, asks
statsapi.mlb.comfor it, so MLB can see that browser’s IP address and standard request details. No names or table information are sent, and phones don’t make this request.
These providers handle data under their own policies. We don’t sell your information, we don’t share it for advertising, we use no ad networks and we don’t track you across other sites. We may disclose information if the law requires it or to protect people or the Service.
6. Your choices, and deleting data
Tables delete themselves, as above, and you can clear your browser data yourself. If you have an account, you can sign out any time and delete the account yourself with “Delete account” on the front page (section 3). Past Games copies on other people’s devices (see section 2) are theirs to clear; we can’t reach them. To ask what we hold or to have something deleted, email support@starsade.com with the room code and the name you used; we can only find table data by room code. For an account, send it from, or give us, the email address you signed in with. Depending on where you live you may have rights to access, correct or delete your information, and you can use the same address for that.
7. Children
Starsade is for adults aged 18 and over and is not directed at children under 13. We don’t knowingly collect information from them. If you think a child’s name has ended up at a table, email us and we will delete that table’s data.
8. Security
Traffic to Starsade is encrypted (HTTPS). No system is perfectly secure, so please don’t type anything into Starsade that you would not want the other people at your table to see.
9. Changes
Starsade’s only payment is the one-time table unlock (section 3). If we add anything else that changes what we collect, we will update this policy before it launches. When we change it, the effective date at the top changes too.
10. Contact
Questions about privacy: support@starsade.com.