What a party game should remember about you: nothing
No accounts, no cookies, no match history. Here is exactly what is left after a game.
Most game sites want an account so they can keep your progress, your friends and your score. Peerful keeps none of those, which raises an obvious question: what does it store instead?
The short answer is preferences, saved by your own browser, on your own device. Here is the longer one.
What stays on your device
Everything in this list is written to the browser's local storage, and it never travels to a server:
- the language you picked,
- the colour theme,
- the sound volume and whether effects are on,
- the last guest name you typed,
- the last room code, so a reconnect can find the match again.
Clearing site data removes all of it. Nothing else is written: there are no cookies, no fingerprinting scripts and no analytics that phone home about a visit.
What the game itself sends
During a match, players send moves to the device that is running the game — usually the shared screen. Those moves travel over a WebRTC connection that is encrypted in transit, directly between the two devices. The shared screen holds the scores in memory for the length of the match.
When the match ends, the scores are gone. There is no database to write them to, because there is no game server at all: the site is static files.
What the relays can see
Devices still need help finding each other. Peerful uses public signaling relays for that first introduction, the way two people need a mutual acquaintance before they can exchange numbers.
A relay sees that some device asked about a room, and it passes connection offers back and forth. It does not see the words people type, the scores, or who won, because all of that travels on the direct connection that the relay helped set up. It also does not need to know who you are: there is no login, so there is no identity to attach to the request.
That is still metadata, and it is worth being honest about: a relay operator can tell that two connections happened around the same time. What it cannot do is reconstruct a round of the game.
Why this is a feature
Accounts are usually added for persistence, social features and measurement. Each of those is a reason to keep data, and each is a liability when the players are a family in a living room or a class of children:
- nothing to breach, because nothing is stored,
- nothing to delete on request, because there was never a profile,
- nothing that follows a player from one game night to the next.
The trade is real: no accounts means no friends list, no cross-device history and no cloud saves. For a game that lasts eight minutes in one room, that seems like the right trade.
Hosting your own copy
The site is a folder of static files. If you would rather not use someone else's relays or domain, serve the same files yourself and point the networking at your own relay. The FAQ covers the practical parts, and how it works explains the pieces that need to be reachable.