No accounts
Scorekeepers do not sign in. There are no user records, email addresses, passwords, or profiles, for scorekeepers or for directors.
Privacy
QBSheet has no user accounts, no analytics, and no application server. This page describes what the software stores on a device and what a connected room transmits.
Data not collected
No analytics
No tracking, telemetry, tag manager, or third-party scripts. A loaded page makes no request to a third-party service, and the webfont is served with the site rather than from a CDN.
No application server
QBSheet is a static site. Standalone scoring makes no network requests, and this project runs no back end for game data to be sent to.
No cookies
QBSheet sets no cookies and shows no consent banner. What it stores is kept on the device for the room’s own use.
On the device
Data stored on the device
The following is stored in the browser of the device that scored the game and is readable only by that browser.
- Games in progress
- Each accepted question, written as it is scored, so that a reload or a closed tab does not lose the round.
- Completed games
- Retained for seven days. Games entered manually are retained for thirty days.
- Settings
- The keyboard preference, progress through the guided practice game, and the tournament server a room last paired with.
- Removal
- Clearing the browser's data for the site removes the local copy from that browser. Connected tournament servers may retain data they have received under their operators’ policies.
Connected rooms
Data sent by a connected room
A room connected to tournament control communicates with the server the tournament operates. That server is not run by this project, and QBSheet retains no copy of what it receives.
The room sends the game: the scoresheet as it is filled in, and the completed result. It also sends two further items. The scorekeeper's name, which tournament control displays in its view of the rooms, and an opaque per-device identifier, used to determine which device currently holds write access when two are open on one game.
Neither is a user account. Credentials, device identifiers, operator names, and server addresses are not written into QBJ documents, log lines, or error messages, so an exported scoresheet carries no access to the tournament. The protocol's security model states these rules in full.
A room that is not connected transmits none of this.
Hosting
Requests to the web server
Loading a website causes a request to the server hosting it, and web servers commonly log requests. This applies to any deployment of QBSheet. The requests occur when the site loads; scoring itself transmits nothing.
A self-hosted copy places those logs under your own control, because the site is static files on a host you choose. Self-hosting guide.
Source
Verifying this page
QBSheet is open source. Each statement above describes code that can be read: what is stored, what is transmitted, and the single module that makes network requests at all. Read the source.
Report anything on this page that the code does not support.
Other questions
Devices, formats, files, and licensing are covered in the FAQ.