Privacy policy

Last updated 28 October 2026

curling.cam is live-scoring and live-streaming software for curling clubs, operated by Gareth Jones. This page explains what information the service handles, what it does with it, and how to have it removed.

What the service is

A club enters end-by-end scores on a tablet at each sheet. Those scores are shown on the club's public page at curling.cam, on lounge TV pages, and in a scoreboard overlay on the club's YouTube live streams. Scores are public by design; that is the point of the service. Club admins run all of it from admin.curling.cam. At the club there are small computers behind the TVs and, for a club that streams, one encoder box; both run software we provide and take their settings from the service.

Information we collect

What the club enters. Scores and game state (team names, ends, hammer, which sheet). The club's name, logo, sponsor logos, a short description, address and opening hours, web links and notices it chooses to show, and the addresses of any web pages it shows on its TVs. Scores are kept only for the game in play and the last finished game on each sheet; there is no archive of past games.

Club admins. Each admin has an account: a name, an email address and a password, stored as a hash. Signing in sets a session cookie on that device only. The admin site keeps a change log of what each admin changed and when, visible to the club's other admins and to the operator.

The club's devices. Each screen and box makes its own random identity and reports its state so the admin site can show it: online or not, model, software version, whether it is wired or on Wi-Fi and the signal, temperature, how long it has been up, what it is showing, and for the box the state of each stream. Nothing about the people in the building. Camera network addresses, camera logins and YouTube stream keys the club enters are stored encrypted, shown afterwards only as set or not set, and sent only to that club's own screens and box.

Server logs. Standard request logs (network address, time, page requested) kept briefly for operating the service.

Curlers and viewers. Nobody signs in to score or to watch. Curlers and viewers are not asked for any personal information. There is no advertising and no third-party tracking, and the site sets no tracking cookies. The pages keep a little in your own browser's storage, such as a notice you have hidden, a tablet's unsent ends or the chosen look; none of it is sent anywhere.

Google and YouTube data

A club that streams connects its own YouTube channel. To do that, the club creates a small application in its own Google account (a Google Cloud project with an OAuth client) and enters that application's client ID and secret on the admin site; the secret is stored encrypted and never shown again. An admin then signs in with Google and grants that application the YouTube permission (https://www.googleapis.com/auth/youtube) for the channel the club chooses.

From that consent we store, encrypted on our hosting, the authorisation token Google returns, together with the channel's ID and its title at the time of connecting. The token is used for one purpose: to obtain short-lived access tokens, which are handed to the club's own encoder box. The box uses them, on the club's channel only, to read the channel's live stream keys, to create and manage a live broadcast for each sheet (its title, its privacy setting, and the start and stop behaviour), and to read each broadcast's public watch address so the club's scores page can show a Watch live button. No other YouTube or Google account data is read, nothing is used for advertising or profiling, and nothing is shared with anyone else.

curling.cam's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

A club can withdraw this access at any time: Disconnect beside the channel on the admin site deletes the stored token and asks Google to revoke it, and the club can also remove the application's access in its Google account (myaccount.google.com/permissions). Because the application belongs to the club, the club can delete it from its Google account entirely, after which nothing we hold can be used.

Where data is stored

Scores, settings, accounts, logos and the encrypted secrets are stored with our hosting provider, Cloudflare, and served from its network. The software releases for the club's screens and box are stored there too. Each screen and box at the club keeps a copy of its own settings, and the camera logins or stream keys it needs, in files readable only by its own software, so it keeps working when the internet is away.

Data is kept while a club uses the service. When a club asks us to remove it, or the club's use of the service ends, we remove the club's data, including any stored Google token, and its devices forget their identity and settings.

Sharing

We do not sell or share any information with third parties, other than the hosting provider needed to run the service, Google and YouTube as described above when a club connects a channel, and the public display of scores and club information described above.

Changes and contact

If this policy changes, the date at the top of this page changes with it. Questions, or a request to remove a club's data: gareth@gareth.com.