RIFTBORN

Who this covers

Riftborn is a small independent browser game, played at riftborn.us (it used to be at chancrisp.github.io/riftborn). This page explains what the game and its online service (the leaderboard and Riftborn accounts) keep about you. It covers the live game, its classic edition at riftborn.us/classic/ and the test build at dev.riftborn.us.

What is stored if you have a Riftborn account

A “Riftborn account” means you signed in with Google, Discord or GitHub and then chose a username. We store:

• Your Riftborn username. You choose it yourself. We never copy a name from Google, Discord or GitHub. It is public: it appears on the leaderboard, so do not use your real name if you would rather not. Next to it we keep a simplified form (lower case, look-alike letters merged, separators removed), used only to stop guests from posting under a name that looks like yours.
• For each platform you link, a scrambled, one-way form of that platform’s account number. During sign-in the platform tells us your account number. We run it through a one-way scramble keyed with a secret that only our server holds (a keyed hash) and keep only the result. It lets us recognise you when you come back. Without that secret key it cannot be turned back into your account number.
• Your saved game progress and settings: the cosmetics you unlocked and equipped, characters and palettes, Journal entries, records and recent runs, mastery and your tracked goal, stats, redeemed codes and the last name you used for a run. The settings that say how you like to play are saved with it, so they follow you to every device: volume levels, key bindings and other controls, accessibility options, gameplay options (such as aim assist and game speed) and look choices (such as the lighting style). Settings tied to a device stay on that device and are not synced: graphics quality and performance (pixelation, frame-rate limit and Show FPS), UI scale, auto-fire and the mute switch. The server keeps your progress and settings as a single block of data and does not read it.
• Leaderboard scores: your name and run stats (score, stage, wave, kills, time, ruleset, Death Mode or not, statue count and curse, how the run ended, Rift Score, game version and the date), plus a random id the game gives each run. Scores you post while signed in are attached to your account, so if you change your username your past rows show the new one.
• Sign-in session records for each device you are signed in on: a scrambled form of a random sign-in token, and the dates it was created, last used and expires (180 days after you last use it, and never more than a year after you signed in). No device details are recorded. Signing out ends the session. Settings > Account > Sign out other devices ends every session except the one you are using, and so does linking or unlinking a platform.
• Dates: when your account was created, when your username last changed (usernames can change once every 30 days), when your progress or username was last saved to the account, and when each platform was linked.

Signing in creates a few short-lived working records (for example, while you are choosing a username). They expire within 15 minutes at most, and are deleted when used or by the server’s routine cleanup, which runs about every 10 minutes while accounts are in use.

What is not stored

• No email address, real name, profile picture or avatar, from any platform.
• No password. We never see your Google, Discord or GitHub password; you type it only on that platform’s own page.
• No contacts, friends, servers, repositories or anything else from your platform account.
• No IP addresses. Like every website, our server sees your IP address while it answers a request. We use it only to slow down abuse: the server keeps a scrambled, one-way version of it (for newer IPv6 addresses, of the network part only) as a counter key for at most a few hours, never the address itself.
• Guests: nothing on the server except scores they post (a name they typed and the run stats) and any feedback they send. When you type a name for a run, the game asks the server whether that name belongs to a Riftborn account, so the name is sent; it is not stored.

The sign-in platforms and what we ask for

When you press Continue with a platform, your browser goes to that platform’s own sign-in page, and its privacy policy applies to that step. We ask for the smallest permission each one offers, and read only your account number:

• Google: basic sign-in identity only (the openid permission). No email, name or profile.
• Discord: the identify permission, the smallest Discord offers for sign-in. Discord lets an app with it see basic account details, but our server reads only your numeric user ID and discards the rest. No email, servers or friends.
• GitHub: no extra permissions, so public profile access only. We read only your numeric user ID. No email, repositories or private data.

The platform’s temporary access code is used once during sign-in and is not stored. You can remove Riftborn’s access at any time in your platform’s own settings (Google Account security, Discord Authorized Apps, GitHub Applications). That stops future sign-ins with that platform but does not delete your Riftborn data; use Delete account for that.

How the data is used

Only to sign you in, keep your progress and cosmetics with your Riftborn account, and show your username on the leaderboard. It is never sold, never shared except as described on this page, and never used for advertising or profiling. There are no analytics or tracking scripts in the game or on this page.

The game is hosted on Cloudflare Pages, and the leaderboard and accounts run on Cloudflare too (a Worker and its database, at api.riftborn.us). Feedback messages are also posted to Discord (see Feedback messages below). Those services handle your requests in the normal way and may keep their own standard logs under their own policies. Cloudflare’s short-lived operational logs for our Worker record each request, including its web address: a name being checked for availability, or the one-time codes of a sign-in (useless minutes later), can appear there. We read those logs only to fix problems.

Feedback messages

The game’s FEEDBACK form is optional and sends nothing until you press SEND. A message includes what you write, a category, an optional star rating and an optional contact line (Discord or email, only if you type one and want a reply). To help fix bugs it also adds basic technical context: game version, browser and operating system name, screen size, whether you used touch, mouse or a controller, average frame rate, a few game settings and a short summary of your last run. The form shows the exact data under “WHAT GETS SENT”. Your IP address is not stored, and feedback is not linked to your account.

Feedback also goes to Discord. So the developer sees new feedback quickly, each message is also posted to a private channel on the developer’s Discord server: its category, star rating, whether it came from the live game or the test build, and the start of your message (up to 300 characters). Your contact line and the technical details are not included in that post. Discord stores that copy under Discord’s privacy policy. Please do not put private details in the message text.

Storage on your own device

Riftborn keeps its data in your browser’s local storage. It holds: your settings, your saved progress on this device, scores and boards saved on this device, scores or feedback waiting to be sent, the last name you used, your sign-in token if you are signed in, a random one-time check value while a sign-in is in progress (it stops working after 10 minutes, and is deleted when the sign-in finishes or is cancelled, or replaced when the next one starts), and small flags such as which intro or notes you have seen. It stays on your device until you clear this site’s data in your browser settings.

Moving from the old address: when you open the old address (chancrisp.github.io/riftborn), it moves the game data saved there in your browser to riftborn.us in the same browser: your saved progress, settings, scores and boards saved on the device, and anything waiting to be sent. Sign-in details are never moved. The data travels in the part of the web address after the # sign, which browsers do not send to any server, and riftborn.us removes it from the address as soon as the page opens. The copy at the old address stays as it was.

Cookies: no tracking or advertising cookies, and the game itself sets none. The only cookie is a sign-in security cookie: when you press Continue with Google, Discord or GitHub, the Riftborn sign-in server sets one short-lived cookie (10 minutes) on its own address (api.riftborn.us). It holds a random value and nothing about you, and makes sure the sign-in finishes in the same browser that started it.

Deleting your data

• Riftborn account: Settings > Account > Delete account. You confirm by typing your username. This removes the account, its linked platform records, its sign-in sessions and its saved progress. Your past leaderboard rows stay but are cut loose from you and renamed to an anonymous guest name.
• Unlink a platform: Settings > Account, if you have more than one linked. Its scrambled account number is deleted, and your other devices are signed out.
• Anything else (a guest score, a feedback message, or if you cannot get into the game): ask through the in-game FEEDBACK form and say what to remove. When a feedback message is removed, its copy in the developer’s Discord channel is deleted too.
• On your device: clear this site’s data in your browser settings.

Children

Riftborn is not aimed at children under 13. Google, Discord and GitHub set their own minimum ages for their accounts. Guests provide no personal information. If you think a child has made a Riftborn account, tell us through FEEDBACK and we will delete it.

Changes to this policy

If this policy changes, the “Last updated” date above changes with it, and significant changes will also be mentioned in the game’s patch notes.

Contact

Open Riftborn and press the FEEDBACK button on the main menu. Guests and signed-in players can both use it.