Privacy Policy
Last updated September 27, 2026
Onceworlds runs onceworlds.com, where people play and publish browser games. This policy explains what we collect and why.
What we collect
- Account. If you sign up with just a username, your username and password; we keep only a salted hash of the password, never the password itself, and without an email a forgotten password can't be reset. If you sign up with email, your email address and password (held by our sign-in provider, never by us in readable form). If you sign in with GitHub, your GitHub user id, username, avatar, email address, and the ids of the GitHub organizations you belong to, which decide which games you can manage.
- Profile. Your display name, @username, the About text you write, your avatar, your friends and friend requests, the games you favorite and your likes and dislikes. Your profile, friends list, favorites and badges are public. Which game you're in (and its server) is shown only to your friends; game pages show how many people are in each server, not who.
- Playing. A random player id (for guests) or your account id, your display name, the progress games save for you, the badges you earn, and the chat messages you send. Chat is delivered to players in the same room (direct and group messages only to their recipients, never to the game's own code); the last 50 public messages stay in the room while it's open.
- Analytics. When you play we record when the play started, how long the game was on screen, your country (from our host), your device type and the referring website's domain. We don't store IP addresses. We delete these records after 90 days. Errors from games (message and stack trace) are kept for 30 days.
- Creators. Repository names, deploy details (branch and commit), the files you publish, images and videos you upload, badges, variables and secrets. Secrets are encrypted and only ever sent to the API you bind them to.
- Cookies.
ow_sidkeeps you signed in, or remembers your guest player. During sign-up and GitHub sign-in our sign-in provider sets a short-lived cookie, and a password reset link sets one for 15 minutes. We don't use advertising or third-party tracking cookies.
Games are made by other people
Each game runs in an isolated frame on onceworldsusercontent.com. A game can see your player name and id and what you do in it, and it can store data in your browser for its own use. It can't read your Onceworlds cookie. Games can load code from public libraries (such as jsDelivr, unpkg and esm.sh) and Google Fonts, which see your IP address when they do. When a game calls an AI or media service through Onceworlds, what the game sends, which can include what you type, goes to that service (for example Anthropic or OpenAI) under the creator's account.
Who processes data for us
- Cloudflare hosts Onceworlds and processes IP addresses and request details to deliver and protect it.
- Supabase handles sign-in, passwords and account emails.
- GitHub provides sign-in and, if you import a repo, the GitHub App integration.
How we use it
To run Onceworlds, keep it secure, prevent abuse, show creators aggregate stats about their games, and fix problems. We don't sell personal information or use it for advertising.
Your choices
Delete your account and its data any time in Settings. Email support@onceworlds.com to get a copy of your data or to correct it. Signing out removes the cookie from your browser.
Children
Onceworlds isn't directed to young children. If you think a child has given us personal information, email us and we'll delete it.
Retention
Account data is kept until you delete your account. Guest players nobody has used for 60 days are deleted with their saves and badges. Analytics are deleted after 90 days and game errors after 30 days. To limit sign-ups, new guests and visits counted from one network we keep a keyed hash of the IP address (not the address) for two days.
Changes
We'll post changes here and update the date above.