Privacy
Effective date:
This page explains what happens to your information when you use Sealbound: the website, the character chats and the games on it. It is written in plain language and describes what the site does today.
Who runs Sealbound
Sealbound is run by Henry. If you have a question about this page or about your information, write to info@ustechlab.com.
What we collect
- Google sign-in. When you sign in with Google we receive your name, your email address and the link to your profile picture. Sign-in runs through Supabase. We show your name and picture on your account page.
- Sign in with Apple. When you sign in with Apple we receive the email address Apple gives us (your own, or a private relay address if you chose to hide it) and, the first time, your name if you share it. Sign-in runs through Supabase. We also keep the token Apple issues, so that when you delete your account we can ask Apple to revoke Sealbound's access.
- Chat messages and game progress. We keep what you type in a character chat, the replies, and where your story stands: the room, relationships and numbers, scenes you have opened, results of in-chat games, and short summary and memory notes the story writes for itself. The approximate city of your request can be written into the story, and that text is then kept in your chat log. If you sign in, cloud saves of the Aether Monsters game are kept too.
- Credits, purchases and tickets. We keep your credit balance with a list of every change to it, your scene tickets, and a record of each purchase: the pack, the price, its status and the PayPal order, capture and refund numbers. You pay on PayPal's page, so we never receive your card number or PayPal password. Purchases in the apps are paid to Google Play or Apple, and we keep the store's purchase or transaction id with the credits it gave; we never receive your card details from the stores.
- A guest cookie. If you play without signing in, we set a cookie called sb_guest that holds a random number. It has no expiry date, which makes it a session cookie, and it is removed when you sign in and your guest chat moves to your account. Your guest chat is stored under an identifier worked out from that number with a secret key, not under the number itself.
- A hashed IP address. To limit free turns and stop abuse, we turn your IP address into a keyed hash and store only the hash with a count. For IPv6 the hash covers the whole /64 range your address belongs to. We use the real address to make the hash and do not write it to our database. The same hash is stored with the usage events your browser sends.
- Usage events. We record simple events such as a card seen, Play pressed, the intro watched, a sign-in started or finished, a turn sent, a scene opened or credits bought, with small numbers or ids such as the turn number or the scene. They never contain chat text or your email. Events sent from your browser carry the tab value below and a hashed IP address, and no account id. Events recorded by the server carry the tab value too, plus your account id if you are signed in.
- A tab-only value. Your browser keeps a random value in sessionStorage (key sb_track) so that events from one visit can be grouped. It disappears when you close the tab and is never a cookie. If you reach the sign-in wall with a message typed, or leave for PayPal with a message or a scene waiting, that line or scene is also kept in sessionStorage in your tab so it can pick up when you come back.
- Studio works. Studio is on our website only. If you make a work in Studio, we keep its text (title, world, characters, openings, status numbers and, for an imported character card, the card fields Studio has no place for), its rating and how it is shared, in our database. The pictures you upload or make for it are kept in a private storage bucket that only our server can read. Each time you publish a work that is not private we also note the time, to apply the daily publishing limit. Until you share it by link or publicly, only you can open it.
- The 18+ declaration. When you turn on the 18+ switch in Studio, we keep a record that your account declared it is 18 or over, with the time. Turning the switch off deletes that record.
- Birth year and month. If you enter your birth year and month on your account page, we keep them (not the day) to show stories that fit your age. When they make you 18 or older we also keep the 18+ record above; a later date that makes you younger deletes it.
- Reports. When you report a work, we keep your account id, the work, the reason you chose, the note you wrote and the time. Our staff read reports to decide what to do. Authors do not see reports.
- Reports on AI replies. When you report a reply in a chat, we keep the reply's text, the reason you chose, the note you wrote, the work and chat it came from, the time, and your account id (or, as a guest, your guest id). Our staff read these reports to fix what the AI writes. Nothing about a report is shown to other players.
- Notifications. If you allow notifications in the app, we keep your device's Firebase Cloud Messaging token with your account id (or, before you sign in, your guest id) and the platform, and a record of which reminders we sent so each goes out once. We use it only for reminders about your daily credits and a story you left off. Google's Firebase delivers them. Turning notifications off in your phone's settings stops them; deleting your account deletes the token.
- Moderation records. If our staff take a work down, we keep that it was taken down and why. If they block an account from Studio, we keep the account id and the time on a block list, and that account cannot make or change works.
- Likes, saves and comments. Your likes and saves are tied to your account. A comment is stored with its text and the name and picture from your Google profile at that time, and other visitors can read it.
- Reports on comments. When you report a comment, we keep the comment it names, the reason you chose, the note you wrote, the time, and your account id (or, as a guest, your guest id). Our staff read these reports. A comment that three different accounts report is hidden until our staff review it. The person who wrote the comment does not see who reported it.
- Blocks. When you block an account from a comment, we keep your account id, the blocked account's id, the name and picture its comment showed, and the time, so we can hide that account's comments from you. The blocked account is not told. You can see and undo your blocks under Me → Blocked accounts.
- Things kept on your own device. In the apps, a note (sb_ai_ok) that you agreed to AI replies before your first message, so we don't ask again; a language cookie (sb_lang, one year); short sign-in cookies (the page to return to, ten minutes, and a one-minute notice flag); the cookies that keep you signed in; and in your browser's storage a list of recently played games, a hint that you have seen, and copies of Aether Monsters save data.
The website (not our apps) loads Google Tag Manager, and through it the Meta Pixel, so we can measure our ads on Meta (Facebook and Instagram). They set their own cookies (such as _fbp) and see the pages you open and events such as opening a work. If you arrive from a Meta ad, we keep its click id in a cookie (_fbc, 90 days). The chat page and the Aether Monsters game load their fonts from Google Fonts, and your Google profile picture is loaded from Google, so Google's servers see those requests. The Daily Pack page (/pack) loads its card images straight from assets.tcgdex.net and tcgplayer-cdn.tcgplayer.com, so those hosts see your IP address when you open it.
Why we use it
- To run the chats and games and to keep your progress.
- To let you sign in, and to keep your credits, tickets and purchases right.
- To limit free guest turns, stop abuse and keep the cost of AI replies under control.
- To see which parts of the site are used, so we can improve them.
- To learn, in summary form, what players enjoy: which characters, stories and games people choose, how long they stay and what kinds of things they talk about. The section below says how.
- To show likes and comments, to act on comment reports and hide the comments of accounts you blocked, and to answer you when you write to us.
How we study chats and play
We study how Sealbound is used so we can decide which works and games to make, support and improve. For this we look at usage events (what was opened, played and finished) and at chat text.
Chat text is read for this purpose by automated tools, which can include the AI providers named on this page. They label a conversation with general topics and counts, for example the kind of scene, the mood, or which character was chosen. We then work with those labels and totals across many players, not with one person's conversation. Our staff do not read your chats for this purpose; they open a chat only for the reasons given elsewhere on this page, such as a report.
We share the results only as statistics about groups of players, for example with the authors of works and with game studios we work with. Those statistics do not include your name, your email address, your account id or the text of your messages. We do not sell your chat text.
If you do not want your chat text used for this, email info@ustechlab.com from your account's email address and we will leave your chats out from then on. Leaving them out does not change how the chats work for you.
Who receives it
- Supabase stores our database and runs sign-in. Everything described above that we store is kept there.
- Vercel hosts the site and runs its server code, so it handles your requests, including your IP address. Vercel also tells our server the approximate city of a request.
- Cloudflare R2 stores the pictures we show. They are served from our image address, so your browser asks for them and the request is visible to that service. Pictures for Studio works are kept there too: your browser uploads them straight to Cloudflare, in a private bucket. When you publish a work by link or publicly, and it is not rated adult, its pictures are copied to our public image address so players can see them.
- PayPal handles payment. We send it the pack and price of your order and it sends back the order, capture and refund numbers.
- Apple handles payment in the iOS app. When you buy credits there, the app passes us the App Store transaction id and the product, we ask Apple's App Store Server API about that transaction, and we credit it once. The app gives Apple your account id with the purchase so it is credited to the right account.
- Apple runs Sign in with Apple, described above, and receives a request to revoke its token when you delete your account.
- Google Play handles payment in the Android app. When you buy credits there, the app passes us Google's purchase token and the product, we ask Google whether the purchase went through, and we keep a record that it was credited (a hash of the token). Google receives your account id with the purchase so a purchase is credited to the right account.
- AI model providers, OpenRouter and BytePlus, write the replies in the chats. OpenRouter does not run the models itself: it passes the text on to the companies that host the models it routes to.
- BytePlus (its ModelArk service, the Seedream models) makes pictures in Studio, as a processor working for us. It receives what is needed to make the picture you asked for, described below.
- Google runs Google Tag Manager on the website, which loads our measurement tags. Google's servers see the request for it.
- Meta receives ad measurement from the website: the Meta Pixel in your browser, and from our server when you create an account, reach your 11th turn in a work in a day, or buy credits. From our server we send the event, the work, the price of a purchase, your email address and account id as one-way hashes, Meta's cookies (_fbc, _fbp), your browser's user agent and, when the event happens in a request from your browser, your IP address. Meta uses it to measure and deliver our ads. Never your chats. Our apps send Meta nothing.
Chat text goes to the AI providers. To generate a reply, the text of the message you send is sent to OpenRouter or BytePlus, together with recent messages from your chat, the story summary and memory notes, and the approximate city of your request. This happens for visitors who have not signed in as well as for people with an account. The same kind of request is sent when the story summary is rewritten. In works with unlock steps, a separate check sends the line you typed and the reply to the same AI providers, for signed-in players, to decide whether a step was reached. OpenRouter passes it on to the companies that host the models. The providers and those hosts handle that text under their own terms, which we do not control.
Studio works go to the AI providers too. When anyone chats with a Studio work, including you testing your own, the work's text (its world, characters and openings) is sent with the chat to OpenRouter or BytePlus to write the reply. When you make a picture in Studio, the prompt you typed and any of the work's own pictures you chose as references are sent to BytePlus ModelArk: the references as links to the private files that work for five minutes. BytePlus sends back the picture, which we keep in the private bucket.
Our staff see a private work only after a report. Staff can read the report list, with each reported work's title and pictures. Our server shows staff a private work's pictures only once someone has reported that work; otherwise only the author can open them.
Please do not share sensitive personal information in chat, such as health details, government ID numbers, financial details, passwords, or private information about other people. Replies are written by AI.
How long we keep it
- Accounts. Nothing in the code deletes an account's chats, progress, purchases, events, comments, saves or Studio works after a set time. They stay until the account is deleted. Deleting an account removes its chat rooms and messages, turn counts, scene unlocks, game records, events tied to the account id, wallet and ledger, tickets, purchases, likes, saves, comments (with the reports about them), the comment reports it sent, the blocks it made and the blocks others made on it, and cloud saves. It also removes its Studio works (with the reports and publishing records about them), its 18+ declaration and any block on it, and we remove the works' pictures, both the private files and the public copies. One exception: a Studio work other players have already played or bought stays up for them, with its pictures, but its link to the deleted account is removed and nobody can edit it again. Reports the account sent, about other people's works or about AI replies in chat, are kept for the record, without the account id.
- Studio works you delete. When you delete a work, nobody can open it any more and its public picture copies are removed. The work's record and its private pictures are kept for the record until your account is deleted. The same is true of a work our staff take down or delete. A copy already held by someone's browser cannot be recalled.
- Studio uploads. An upload that is started but never finished is deleted from the bucket after one day.
- Guest chats. A guest chat and its counters are meant to be cleared after seven days without activity. That cleanup runs when someone signs in and moves a guest chat to an account, not on a clock, so guest data can stay longer if nobody signs in for a while.
- Usage events. Events are not deleted on a schedule. Events tied to an account id go when the account goes. Events sent from your browser have no account id, so they stay, with their tab value and hashed IP address.
- Comments. When a comment is moderated it is hidden, not erased. Reports on a comment are kept with it until the comment or the reporting account is deleted; a guest's report has no account behind it, so it stays until the comment goes. Blocks stay until you undo them or either account is deleted.
- Older copies. Wishfall chats from before the chat moved to a new set of tables are still kept in the old tables.
- Providers. Logs and backups held by Supabase, Vercel, Cloudflare, PayPal, Google, Apple and the AI providers follow their own schedules, which this site's code does not control.
Access and deletion
You can delete your account yourself: in the app under Account → Delete account, or on the web at sealboundgame.com/account/delete. Deleting it removes what the "Accounts." item above lists, at once and for good. To see what we hold about your account, or to have it deleted without signing in, write to info@ustechlab.com from the email address of your Google account so we can find it. Guest chats are not tied to an email address, so we may not be able to find one; they are cleared as described above.
Children
Sealbound is for people 15 and over. It is not directed to children under 15, and we do not mean to collect information from them. If you think a child under 15 has given us information, write to info@ustechlab.com and we will delete it.
Changes to this page
If the way the site handles information changes, we will update this page and change the effective date above.