Everything you write inside a session is encrypted before it is stored: your answers, the results, the title of the session, and the settings it was created with. Each session has its own key, and that key is itself locked with a master key that lives in a file on the server, outside the part of it the web can reach.

The practical meaning is this. If somebody steals a copy of the database — a leaked backup, a dumped table, a curious person with database access and no business reading it — what they get is unreadable. They cannot even move one answer into another session to make it decrypt, because every piece of ciphertext is tied to the exact row it was written for.

Some things are deliberately not encrypted, because the site cannot work without them: the fact that a session exists, which game it is, who is in it, when it was created, and when it ends. Somebody holding the database learns that you played, and with whom. They do not learn what any of you said.

An administrator of this site can read the contents of a session. Not by breaking anything — the panel has a button for it. It is there so that a report of something abusive can actually be looked into, and being straight about it is more useful to you than pretending otherwise.

What tempers it is that looking is recorded. Opening a session's contents writes a permanent line in the audit log naming the administrator, the session and the time. The log cannot be edited from the panel, and it can be exported whole.

What an administrator cannot do: read your password, because there isn't one — the site never has anything to steal from you but a nickname. They cannot see an email address, because you were never asked for one. They cannot see your IP address or which browser you used; those are stored only as a one-way fingerprint used for rate limiting, and cannot be turned back into an address.

Take this as the honest summary: this is not end-to-end encryption. The encryption protects you against somebody who steals the data. It does not protect you against the people who run the server. If you would not want an administrator to read it, do not type it here.

Every session has a deadline, set by whoever created it, between one hour and one week. When the deadline passes — or when everyone has finished and the results have been up for a day — the session is taken off the site. The seats, the answers and the results are deleted from the live database, the link stops working, and it gives the same page whether the session ended a minute ago or never existed at all.

There is no undo for you. You cannot reopen a finished session, get its results back, or ask anyone to. Nothing about it appears on your account afterwards.

One qualification, so that "gone" is not doing more work than it can carry: if something that happened in a session is reported, an administrator can still look into it afterwards. That is recorded, like every other time an administrator opens a session. Nothing about it comes back to the site, and nothing about it comes back to you.

An account here is a nickname and an authenticator app. There is no password to be reused or leaked, and no email address to be sold, lost or used to find you elsewhere. If you lose your phone, your ten recovery codes are the only way back — nobody can let you in without one, and an administrator cannot either.

Sessions you are signed in on are listed on your account page, and you can sign out everywhere else in one click.

• Other players can see what you write. That is the game. Encryption protects your answers from strangers, not from the people in the room with you, and nothing stops somebody taking a screenshot.
• An administrator can read a session while it is running, and can still look into one after it has ended if it is reported. Recorded both times, but real. See above.
• Somebody who takes both the database and the server's configuration file can decrypt everything. The two together are the whole secret. They are kept apart, and that is the protection — not magic.
• A session that is running on a compromised server is not protected. No server-side encryption scheme protects you from the server itself while it is being used.
• Sessions without a password are listed publicly on the front page, and anyone with an account can take a seat in one. Set a password if that is not what you want.
• Age ratings are self-declared. Where a game is marked for adults, the site asks you to say so and believes you. It does not ask for a date of birth and does not check one.
• Nothing here is a promise about the future. This describes how the site works today. If it changes, this page changes with it.

• Keep your recovery codes somewhere that is not your phone.
• Put a password on a session if it is not for everybody, and send the password separately from the link.
• Write what you would be content to have read back to you by the people in the room, because you will be.