Privacy

What there isn't

• No cookies. Not for tracking, not for ads, not for logging in.
• No ads and no third-party advertising or tracking services on the site.
• No selling or sharing of the game's data with anyone.

What stays in your browser

The game keeps a few things in your browser's own storage (localStorage) to remember you from one visit to the next. They stay on your device; they only go to the server in the cases described here.

peleja.apelido

the last nickname you used, so you don't have to type it again.

peleja.idioma

the language you picked (PT or EN).

peleja.som

whether sound is on, and the volume.

peleja.avisoTeste, peleja.convite

whether you've already seen the playtest notice and the tutorial invitation.

peleja.navegador

a random code so the "Play now" queue doesn't put two of your tabs at the same table. It goes to the server when you join the queue.

peleja.id, peleja.retorno

the return code and the dates of your first and latest match (see below).

In a room, the tab also keeps your seat in it (peleja.lugar, in sessionStorage, which is cleared when the tab closes). That's what lets you get back to the same table if your connection drops or the page reloads.

What goes to the server

• To play: your nickname, your moves and your seat in the room. Everyone at the table sees your nickname. This stays in the server's memory while the room exists; during a game update, open rooms are written to disk for a few seconds so the match can go on, and the file is deleted right after.
• The server's technical log records room codes and the nickname of whoever creates, joins, leaves or drops from a room, to track down bugs. It stays on the game's server and doesn't record IPs.
• Your IP address reaches the server, as with any website, and is only used in memory for the anti-abuse limits (how many connections and rooms per address). It doesn't go to logs, metrics or any other service.

The return code

To know whether people come back to play, your browser keeps a random code, drawn on your first match, plus the dates of your first and latest match. When a match starts, it sends that code, how many days have passed and how the match started (room, "Play now" or "Play again", the mode and the number of players). The code doesn't say who you are: it has no name, nickname, email or IP, and it isn't sent with anything else from the game. It only shows that the same browser came back.

Counts and errors

• To improve the game, the server counts matches, queues, times and errors. The numbers go to the project's metrics dashboard (OpenObserve) with no nickname, no IP and no room code.
• Each finished match becomes one anonymous line: the mode, the number of players, how long it lasted and how it ended. Its number is drawn on the spot and isn't linked to anything.
• The tutorial only sends how far you got, with nothing that identifies you.
• When something breaks, on the server or in your browser, the error goes to GlitchTip with no personal data: no nickname, no room code and no stored IP. From the browser, only the browser type (the User-Agent) goes along.

"Send feedback"

"Send feedback" sends what you write plus only the game version, the browser and system, the screen size and which screen you were on (in a match, the mode and the number of players). No nickname and no room code.

For how long

What reaches the metrics dashboard is deleted automatically after a while:

Rooms disappear from the server's memory when the match ends and everyone leaves.

Deleting what's stored here

The button removes the return code and the dates from this browser. To delete the rest (nickname, language, sound), clear the site's data in your browser settings.

Contact

Questions about your data? Write to contato@peleja.app.