Privacy
Bezel has no accounts, no cookies, no analytics and no ads. It never asks who you are, and nothing you do in it is sent to its makers.
To bring the phones of a table together over the internet, though, your phone talks to a few others. This page names each of them and what it sees. It was checked against the app on 13 November 2026.
Who your phone talks to
GitHub, which hosts these pages
The site and the app are files on GitHub Pages, run by GitHub, Inc. When your phone opens them, GitHub sees its IP address, the addresses it opens (for a phone that joins by the QR code, that includes the table’s code) and which browser it uses, as the host of any website does. GitHub says it logs visitors’ IP addresses for security (GitHub Pages: data collection, GitHub’s privacy statement).
Five public signaling relays, where phones find each other
Phones find their table through five public relays of the Nostr network, run by people and companies that have nothing to do with Bezel: relay.nostr.blockhenge.com, relay.flashapp.me, relay.nostrmap.net, relay.bullishbounty.com and relay.novospes.com. They are the ones the connection library Bezel is built on (Trystero) picks for it; Bezel does not pick its own. While the app is open, your phone stays connected to them. A relay sees:
- your phone’s IP address;
- the table’s name, scrambled: the code itself is not sent, but a code of four letters can be worked back out by anyone who tries;
- each phone’s offer to connect, locked with a key made from the table’s code. An offer holds the network addresses a direct connection could use.
Anyone else connected to the same relay can see the same messages. Nothing of the game itself passes through the relays. Your phone signs its messages with a key it makes anew each time the app opens, so that key does not tell your visits apart.
Google and Cloudflare, which tell a phone its address
Before two phones connect, each one asks an address server (STUN) where its traffic reaches the internet from: stun.l.google.com, stun1.l.google.com, stun2.l.google.com (Google) and stun.cloudflare.com (Cloudflare). They come with the same library. They see your phone’s IP address each time it sets up a connection, and nothing else.
Metered, which runs the Relay
When the build carries a Relay, as the app published here does, two phones that cannot reach each other directly (as on some phone hotspots and mobile networks) connect through it: standard.relay.metered.ca, run by Metered (Next Path Software Consulting Inc., Canada) on the makers’ account. Each phone then asks the Relay for a way through whenever it sets up a connection, so Metered sees your phone’s IP address each time; the game passes through it only when the direct way does not work. Then Metered also sees when the phones play and how much data passes. Everything that passes between the phones is encrypted, as every connection between browsers is, so the Relay cannot read the game. Metered says it keeps this connection data for 30 days (Metered’s privacy policy).
The other phones at your table
The phones of a table connect to each other directly whenever they can, and like any direct connection, each one sees the others’ IP addresses. Your phone also sends them what the table needs: what kind of phone it is (for example “iPhone” or “Android”), the size of its screen, its Device id and Player id (below), the Players’ names, and your touches during a game. The first phone passes every phone’s messages on to the others, so it sees all of them.
What the app keeps on your phone
It keeps these in your browser’s storage for manubown.github.io, not in cookies:
- A Device id. A random code made on your phone the first time it opens the app (one more for each tab that has the app open at the same time), so that a phone that drops out of a table is known again when it comes back. It stays until you delete it.
- A Player id. Another random code, one for each Device id, so that you keep your place in a game when the page reloads. It stays until you delete it.
- Maker mode, on or off. Only if the app was ever opened with ?maker in its address, as the makers do when they test. It stays until you delete it.
- Sound, on or off. Only once you switched the sound on the first phone’s sheet or on another phone’s top strip, so that the phone stays as you left it. It stays until you delete it.
- The offer to add the app to your home screen. How many games this phone has finished, and whether you closed a result card that carried the offer or used it there, so that the offer comes after your first finished game and does not keep coming back on the cards. It stays until you delete it.
- The last game you picked. On the first phone, once you picked a game on its sheet: which one, so that the next table you open starts with it. It stays until you delete it.
- The table you opened. On the first phone only: the table’s code and what was picked on its sheet (the Game, how the phones lie, the Players and their names), so that reloading the page keeps the table. It goes when you close the tab.
- A log of what happened on this phone. So that a problem at a table can be looked into: when phones joined and left, what kind of connection each one used (never its address), timings, errors, your screen’s size, your browser’s name and version, the page’s address with the table code, and the games played with the Players’ names. It keeps the newest 20,000 lines, about 3 MB, and drops older ones.
Of these, the other phones of your table get what the table needs: your Device id and Player id, and from the first phone the table’s picks. Nothing goes to the makers or anyone else. The log leaves your phone only if someone exports it (in Maker mode, with Export log) and sends the file on.
How to delete it
Delete the site data for manubown.github.io in your browser’s settings: in Safari under Website Data, in Chrome under Site settings, All sites. That deletes everything above. If you added the app to your home screen, remove it from there too. Closing the tab deletes the table you opened. In Maker mode, Clear on the first phone’s sheet empties the log.
What there is not
- No accounts and no sign-in.
- No cookies: neither the site nor the app sets any, and GitHub Pages sends none.
- No analytics, no counting of visits, no ads.
- Nothing loaded from another site: the pages and their scripts, pictures and fonts all come from manubown.github.io.
Who is responsible
The makers of Bezel: Manuel Gut, manubown@gmail.com. Their full details are on the imprint. Ask them anything about this page. The source code is public, so every sentence here can be checked against it.