RPS Royale is a small hobby project. It collects about as little as a multiplayer game can — here's exactly what, and why.
The short version
| Data | When | Why |
|---|---|---|
| Discord display name (username or global name) | Only when launched as a Discord Activity, via Discord's own sign-in prompt | Shown next to your avatar in the arena, instead of asking you to type a name |
| A name you type yourself | Only when playing in a regular web browser, not inside Discord | Same — identifies you to other players in your game |
| Your moves, wins, and which abilities you hold | While a game is in progress | That's the game itself |
| A rejoin token, saved in your browser's local storage | When you join a game | Lets you get back into the same game if your connection drops |
We don't collect your email, IP address for any purpose beyond normal server operation, payment details, or anything from Discord beyond your display name.
Inside Discord, the game asks for the identify permission — nothing more. Discord hands our server a short-lived code, which we exchange, server-side, for a token that lets us read your username. That token is used once, immediately, and isn't written to a database. Your Discord password is never seen by us; that entire exchange happens through Discord's own systems.
There's no database behind RPS Royale. Every game room lives in server memory for as long as the game is being played, and is discarded — completely — when the game ends or the server restarts. The only thing that persists anywhere is the rejoin token and display name saved in your own browser's local storage, which you can clear at any time through your browser's own settings.
RPS Royale isn't directed at children and follows Discord's own minimum age policy (13+). We don't knowingly collect information from anyone younger than that.
We take reasonable, standard precautions (encrypted connections, secrets kept server-side and out of source control) — but as with any online service, we can't guarantee absolute security. Given how little is ever stored, there's very little exposure to begin with.
If this policy changes in any meaningful way, the date at the top of this page will change with it.
Questions about this policy can be raised as an issue on the GitHub repository.