Privacy
Supper Court has no accounts. A court on one phone stays in this browser and is never sent to us. A shared court keeps first names and answers on our server for a day after it last changed, then deletes them. We count page views, which questions get asked and errors, never names and never what the court decided.
Supper Court runs a short question-and-answer court to pick dinner. A solo or pass-the-phone court runs in your browser: the names you enter, each answer, each veto and the questions asked are kept in this browser's localStorage so a refresh does not lose your place, starting over deletes them, and none of it is sent to our server. A shared court runs on our server so that everyone can answer on their own phone: it keeps the first names people type, their answers and vetoes, and a hash of each phone's random rejoin token, shows the names to everyone in that court, and deletes all of it 24 hours after the court last changed. It is never backed up and never linked to an account, an email or an IP address. Page views (as a route, not a full address), counts of which questions were asked and which kind of answer they got, how many people are in a court, and errors go to Lotl Observe, which we operate. Those counts never include a name, a court's code, who gave an answer, or the verdict.
What we collect
Here is everything that leaves your browser, and what stays in it:
- Your court, kept in this browser: For a solo or pass-the-phone court: the names you type, each answer and veto, and which questions were asked, stored in localStorage in this browser (supper-court.court) so a refresh does not lose your place, and never sent to our server. Starting over deletes it; so does clearing your browsing data. For a shared court, this browser keeps your seat (supper-court.seats): the court code, the first name you joined with, a random token that lets this phone rejoin as you, and the host token if you opened it. Seats older than two days are dropped. Your theme choice (supper-court.theme) is stored the same way, and a tab-only flag in sessionStorage (supper-court.reloaded) remembers that the page already reloaded once after an update.
- Shared courts, kept on our server for a day: When you start or join a shared court, our server keeps what the court needs to run on everyone's phone: the first name you type, each answer and veto, which questions were asked, and a hash of the random token your phone sends so it can rejoin as you. Everyone in the court sees the names and, at the verdict, the reasons built from the answers. A court is deleted 24 hours after its last answer or change; it is never backed up. No account, no email, and no IP address or device details are stored with it.
- Places near you (via Google): Only when you tap "Near you" on a verdict pick, and only after your browser asks you: this phone sends its latitude and longitude, with which pick it is, to our server. The server rounds the position to a square about 500 m across and asks Google (the Places API) for places of that kind near the middle of the square, so Google never receives your exact position; Google handles that request under its own privacy policy (policies.google.com/privacy). Your position is used for that one answer, to work out distances, and is not stored or logged. To avoid asking Google again, the server keeps the list of places it found (names, addresses, positions, price level and weekly opening hours, never ratings) for 24 hours, filed under the kind of place and the rounded square, not under who asked. In a shared court each phone looks near itself; nothing about a lookup is shared with the court. The Google Maps and Uber Eats links open those services only when you tap them.
- Usage telemetry: Page views, reported as the route (such as /court) rather than the full address, errors the app throws, and counts of what happens in a court: which question was asked, which kind of answer it got, how many people are playing. Sent to Lotl Observe. Never a name, never who gave which answer, and never what the court decided.
Third parties
These external services receive some of your data:
- DigitalOcean — hosting for Supper Court
- Google Maps Platform (Places API) — Finds places near you when you tap "Near you" on a verdict pick. Receives the centre of a square about 500 m across around your position, for that one search, from our server.
Where your data is stored
Telemetry and shared courts are stored on Lotlsoft's own server. A solo or pass-the-phone court never leaves your browser. When you tap "Near you", our server sends a rounded position (a square about 500 m across) to Google, which may process it outside Australia.
Your rights
A solo or pass-the-phone court lives in this browser: start over, or clear this site's data, and it is gone; we never receive it. A shared court is deleted automatically 24 hours after it last changed, and there is no account to tie it to you; if you want one deleted sooner, email hello@lotlsoft.com with the court's link. Telemetry counts are not linked to you.
Last updated: 2026-10-06.