Privacy
No accounts, no email, no ads, no tracking, and no analytics code in the pages. Nothing about you is sold, because there is nothing to sell. Here is everything that is kept, and where.
What your browser keeps
- A game key made on your device at your first visit, and the name you typed. They are kept in this browser's storage.
- If you signed in with Nostr while that was offered: your public key and, for a remote signer, what your browser needs to reach it again, until you go back to this browser's own.
- For each table: a key for that table, your seat, the results list, the table's results as your browser counted them, your total against the bots as the table last told it, the data your browser uses to check hands, with the last 50 checked hands, and who at the table wears the ♛ that week.
- For the Daily Deal: a key for that day's run, the run's table, its hands' results, the data your browser uses to check them, each day's lock as your browser was first shown it, with its own check of the day's block, and each hand's lock as your browser was sent it before the hand, for the day's own check of the cards once the day is over, with that check's result. A day's are forgotten a week later.
- If you play a match with a friend: a key of its own for asking the server about your match, and your friend's name, so that your page can say once if the match ends. A match link opened in a tab is kept in that tab alone until you answer it, and is taken off the page's address at once.
- On your first visit, until you first sit down: how you reached the site, as two fixed words (the page you came in on, such as an invite link or the home page, and the kind of site the link was on, such as a chat app or a search engine, or none). They are kept in this tab only, sent with that sit-down, and dropped from the tab at the next page you open here. Nothing else about the visit or the other site is kept or sent.
- If you save your spot: that it is saved, so the line under your name box says so; and, until it is saved, the passkey's own id made for it (it holds the spot's secret), so that trying again makes the same passkey. The passkey itself is kept by your passkey app, not by this site (see below).
- If you link your own Nostr id to your spot: that Nostr id's public part (its npub), so the line under your name box shows it.
- Tables you haven't opened for a week are forgotten the next time you open a table. Clearing this site's data in your browser removes all of it, and makes you a new player, unless you saved your spot: then tapping your name box brings it back (your passkey is offered above the keyboard; where your browser can't offer it there, "New phone? Get them back" under the box does the same). If you linked your own Nostr id, tapping "your nostr id" under the box, with the same Nostr app, brings it back too.
- A Daily Deal page left open with nothing to play asks the server now and then whether the page's code has changed, and loads the new one if it has. A Daily Deal page also asks the server for the day's block, and, once the day is over, its secret, to check them itself. Neither request says anything about you.
- The game sets no cookies. Cloudflare may check that your browser is a real one before letting it through, as it does for everyone while the site is under attack: its check page runs Cloudflare's code and sets a Cloudflare cookie.
- Your browser notes that this site is reached only over an encrypted connection (a note browsers keep for each site that asks, here for six months), so it never asks for a page of it over a plain one.
What the server keeps
- Tables live in the server's memory: names, public keys, chips, the hands in play, the table's results (each player's name, chips won or lost, and hands played, the biggest pot, and the best hand shown at a showdown), which go with the table when it closes, and, for each player while seated, its chips won or lost against the bots since sitting down and in how many hands, which go when it leaves. A table closes 30 minutes after a player last made a move at it (in a hand, or a seat taken, left, or changed), or 5 minutes after it is left with nobody seated (5 minutes after it is made, if nobody sits down; a seat the server frees for a player who is away does not count as leaving it). It never closes during a hand, and waits up to 16 more minutes for a player who went away during a hand to be sent its end. It closes at once if the server keeps hitting a problem in its hands.
- When the server restarts for an update, it first writes each table with a player seated to a file on the server, so the table carries on: its names, public keys, and chips, the table's results, each seated player's chips won or lost against the bots since sitting down and in how many hands, and the messages of play kept for players who were away. Never an address, and no card that was not shown at the table. It reads the file back as it starts again, a few seconds later, and deletes it. After a crash nothing is saved, and the tables are gone.
- A small database of the game's own totals, which only the site's owner sees, on a private page: how many players each day, week, and month (a device counts once it has played a hand), hours played, hands, how often an invite link, a Daily Deal result, or a player's results at a table were shared, how new players first reached the site (the two words above), and the countries players connect from. For the Daily Deal the page also shows, from the records described below and as counts only, how many of the runs started were played through all 20 hands, and how many of one day's players played again the next day. No names, public keys, addresses, or cookies. To count each device once in a week or a month without keeping who it is, the server keeps, for each day the device plays, a scrambled tag of its game key made with a secret key for that week alone, and, kept apart, one for the month made with a secret key for that month alone. No record holds both. Each secret is deleted as soon as its week or month is over, so no tag can then be matched to anyone. A month's tags are deleted when the month is over, a day's after 40 days, and what is deleted is wiped from the database, not just marked as free. The country is the one Cloudflare names for your connection, kept with those tags, never your address. The state or region and the city Cloudflare names for it are counted too, but only as how many players each has, never kept with a tag or anything else about you, and a state, region, or city is written to the database only once at least five players were counted there in that day, week, or month. Until then its count is held in the server's memory alone, and it is recorded only as "other", so a quiet day's records never say where its players were. One limit, as with any count of players by day: on a very quiet day, with only a player or two, someone holding the server's files who knew who might have played could tell who did, and then, from that player's tag for the week, on which other days that week they played.
- For each player who plays the Daily Deal, the database keeps the name played under and the public key, and each run: its deal, its result and score against par, and every hand of it, with the cards of every seat (your own folded cards included, which nobody else is shown) and every move, when the run and each hand began and ended, and how many seconds each move took; and, while a run is not over, its table as it stands, so it can carry on after a restart (cleared once you have seen its end, or a week after its day). Never an address or an email. They are kept for as long as the game runs, so that a player's history can move into an account later. Nobody watches a Daily Deal run: its table is yours alone. When your run is finished, you are shown where your score stands among the runs finished that day so far (a percentage once ten have finished; before that, only how many have, so that a place among two or three never says how someone else did), and nothing about any other player. You are also shown your score for the day as one number (each hand's chips over or under its par, counted in whole big blinds, added up), your edge (the average over your last 20 days of how your decisions compared with what one of the bots, the Shark, expects from each spot, once the server has worked a day out, and until then of your chips over or under par each day, in big blinds), how many days in a row you have beaten par, each hand's result against its own par as soon as your run is over, and, if you ask for it, the three hands where you fell furthest under par, with your own cards and moves in them and how the Shark starts them (its own line in them, and each hand's par, only once that day's deal is over for everyone, at 5:15 am Central the next morning). All of that is worked out from the records above each time your page asks (your edge's number for each day from the file the job below keeps for it), and is sent only to a browser that proves it holds your game key: the one that played the run, or another device signed in with the same Nostr identity while that was offered (it is shown your last result). Nothing more is stored for it but those numbers. It goes with your game key, so a new device starts over, unless you saved your spot or linked your Nostr id to it (below): bringing your spot back brings all of it back. If you share your result, what leaves your device is the text you see: which Daily Deal it was, that one number, whether you beat par, that percentage, a mark for each hand, and a link to the Daily Deal; on a phone that can share a picture, the same goes as a picture, drawn on your phone, which the server never sees. It holds no cards and no name, and not your edge. The server is told only that a result was shared, to count it. Each run also keeps whether your page said your spot is saved (yes or no, never which passkey or Nostr id), which the ♛ asks of the player who wears it (below).
- The ♛: at the reset that opens each Monday the server works out, from the records above, who wears it for the week (the saved player with the best edge over the last 30 days), and keeps the public key of whoever wears it (each of them, if several tie), or that nobody does, for as long as the game runs. A page is told who wears it only at a table where that player sits, and your own results say only whether you wear it.
- A match with a friend: if you ask a friend to a match, the database keeps your public key with the link's code and when it was made, until a friend answers it (yes, or no thanks) or you stop. After a week the link no longer works, and it is deleted the next time anyone asks a friend to a match. Whoever opens your link is shown the name you play the Daily Deal under, and nothing else of yours, until it is answered or a week old; after that it shows nobody anything. The code is after the "#" in the link, so opening it never sends it to the server or puts it in any log: the page asks about it only over its own connection. Once your friend says yes, the database keeps your two public keys and the day the match began, nothing else, until either of you stops it, and then deletes it. From 5:15 am Central the morning after each day you both played, from the day of the yes on, each of you is shown the other's name and that day's 20 hands of theirs: each hand's number against its par in big blinds, its cards and board, and their moves. Never anything else of theirs: not their edge, streak, ♛, place, other days, or public key, and nothing about anyone outside your match. It is worked out from the records above each time your page asks, and sent only to one of you two, to a browser that proves it holds your game key; a stopped match shows nothing more to either of you, not even days already played. Nothing ranks. It goes with your game key, so saving your spot or linking your Nostr id carries it to a new phone.
- Your total against the bots: for each player who plays a hand at a table where nobody else is seated, only bots, the database keeps its public key with one running total, the chips it won or lost in such hands and how many there were, from its first such hand on, never reset. A hand played while anyone else holds a seat at the table never counts, and the Daily Deal's hands never do. Nothing else is kept for it: no name, table, date, or address. It is sent only to your own browser, at the table, and is never ranked or shown to anyone else. It goes with your game key, so a new device starts over, unless you saved your spot or linked your Nostr id to it: bringing your spot back brings it back.
- If you save your spot with a passkey: one locked box, and the address it is kept at, in the database. Nothing else: no name, public key, account, email, date, or address of yours. The box holds your game key and your name, locked with a key worked out from a secret your browser makes when you save. The secret lives inside the passkey, as its own id, and your passkey app hands it back to your browser only after Face ID or its own unlock. The address is worked out from the secret too, so nobody can find your box without the passkey. The secret is never sent to the server: it can't open a box, and can't tell whose one is. A box is kept until a save with the same passkey puts a new box in its place. (A spot saved in the first days of saving, before this way, used a secret the passkey works out itself, and still opens wherever your browser can ask the passkey for it.) Saving and asking for boxes is limited to a few times an hour from one address. The one catch: the secret is in your passkey, so anyone who can open your password manager can open your saved spot, the same as your passwords; and lose that account and the saved spot is lost with it. There is no "forgot password", because the game holds nothing that could open the box.
- If you link your own Nostr id to your spot: that Nostr id's public part (its npub), tied to your spot, in the database, and nothing more. Your spot is kept there locked so that only your own Nostr app can open it (it holds your game key and your name), with the public half of that lock. No name, email, date, or address of yours, and nothing that ties the link to your runs. To link, your Nostr app signs one fresh question from the server, once; the game never asks for, sees, or keeps the secret your Nostr app holds. Undoing the link deletes it.
- Every night the server sends a copy of the database to Cloudflare's storage, so the records survive if the server is lost. Each copy is kept until the same day of a later month, when that night's copy takes its place. A copy holds what the database holds (saved spots' and linked spots' locked boxes, the matches and their open asks, and the totals against the bots, included), and never the secret keys for the tags. So a stopped match stays in the copies made before it stopped until each is replaced.
- Your network address is held in memory while you are connected, while a table you made is open and for 10 minutes after you make one, and for an hour after you start a Daily Deal run, save or ask for a saved spot, link your Nostr id, or look at, ask for, answer, or stop a match (until the next update). It is used only to limit how many connections, tables, Daily Deal runs, saved spots, links, and match asks one address can have, and is never written to a log or a file.
- The game's log holds a line when it starts (with whether its database is on, and how many tables saved for an update it brought back), one line of counts a minute (tables, connections, hands, memory), a line when its defence against attacks is turned up or down, and error reports with names, table links, keys, cards, and addresses taken out (a crash is the exception: the system reports it in its own words).
- A watchdog on the server looks at the game once a minute and keeps its own notes, in a file and in the system's journal: counts only (connections, tables, memory, whether the site answers), never a name, a table link, or an address. During an attack it can turn up the game's defence and Cloudflare's check by itself, and it tells the site's owner in a message through Telegram, with the same counts and nothing about any player. It also keeps fingerprints of the game's own files and of the server's settings and commands, to tell the owner if any of them changes without an update, and notes which of the server's programs still run an old copy of themselves after an update: none of it about any player.
- The tunnel that links the server to Cloudflare keeps a log too: when it connects and, when the game doesn't answer, the time and the page that was asked for (an invite link names its table). Never who asked.
- The job that prepares each day's Daily Deal ahead of time notes in the system's journal what it did (dates, block numbers, counts, how long it took), never anything about a player. Once a day is over, it also reads the database above, without ever changing it, to work out each run's number for the edge, and keeps those numbers, by run, in a file for that day in the game's own folder on the server, for as long as the game runs (while it works on a day, what it has worked out so far too, in another file it removes when done). The nightly copy above copies the database alone, not those files: nothing new leaves the server.
- The game's, the watchdog's, that job's, and the tunnel's logs are kept twice: in a file deleted after about five weeks, and in the system's journal, capped at 200 MB with the oldest lines dropped first.
- The server's own system log notes machines that try to reach it directly instead of through the site (login attempts, blocked probes), with their addresses, for up to two months. Playing never does that.
What other players see
Your name, your public key (the screen shows a short form), and how you play at that table. Anyone who has the table's link can watch. Every hand's proof is shared with everyone at the table. It never holds cards you didn't show.
A table's results show your name and your chips won or lost to everyone there, also to a player who sits down later. A card of them you share holds your own numbers only: no other player's name, and not the table's link. Your total against the bots is shown to you alone, at a table where nobody else sits and after you leave one, and never on a card.
Who else is involved
- Cloudflare carries all traffic between you and the server, so everything passes through its machines: your address, the pages you ask for, and the game's messages. It keeps its own records under its own privacy policy. It passes your address on to the server, for the limits above, and the country it places that address in, for the totals. Once its visitor location setting is on, it also passes the region and city, for the counts above, with a postal code, a time zone, and rough map coordinates, which the game reads nothing of and never keeps. It also stores the nightly copy of the database.
- Cloudflare shows us totals (visits, countries) and, for visits it blocked as attacks, their addresses. If the site fails to load, your browser may report that to Cloudflare.
- The server is a machine at DigitalOcean, in New York. DigitalOcean measures the machine (memory, processor, disk), not the players.
- The server gets the security fixes of its system from Canonical, the maker of Ubuntu, those of its kernel while it runs (Livepatch, with a free Ubuntu Pro subscription). To get them it tells Canonical which machine it is and which kernel and system it runs, and nothing about any player.
- Each day the server looks up one block of a public blockchain on three public sites (mempool.space, blockstream.info, and blockchain.info), to mix it into a later day's Daily Deal cards, and the blocks between it and the newest one when that day was locked, so your browser can check it. It sends them nothing about any player. Your browser asks only this site for them.
- If you save your spot, your passkey is kept by the passkey app your device uses: Apple Passwords, Google Password Manager, Windows Hello, or another password manager such as 1Password, Dashlane, or Bitwarden, under its own privacy policy. It is named there with your name, your kind of device, and the day you saved it (such as "Brandon iPhone · Oct 24"), so you can tell it apart, and it holds the saved spot's secret. The game's server never sees the passkey or its secret: your passkey app hands the secret to your browser for this site only, after Face ID or its own unlock. Bringing your spot back on another kind of device uses your system's own scan-a-code step with your phone.
- The pages load nothing from any other site: no outside scripts, fonts, or pictures.
- A browser signed in with Nostr while that was offered shares its public key, and a note signed with it that names the table, with the server and everyone at the table, until you go back to this browser's own. If it uses a remote signer, your browser talks to the relay your signer names.
- Linking your own Nostr id is optional, and nobody at a table sees it: your seat shows your game key's public key, as before. If you link with a Nostr app on your phone (its link opened there, or copied into it), your browser talks to it through public Nostr relays (relay.primal.net, relay.damus.io, nos.lol, and relay.powr.build), which pass the messages between them, locked so that only the two can read them; with a bunker:// link, through the relays it names.
Contact: hello@ryvl.poker