Privacy policy

Last updated: October 27, 2026

CueResults (cueresults.com) publishes results, standings and fixtures of pool leagues and tournaments. This page explains what we store about you, why, who else is involved, and how to have it changed or removed.

Who runs CueResults

CueResults is run by Nebojša Perić, Bosnia and Herzegovina, who decides what is done with the data described here (the "controller"). Contact for anything on this page: [email protected].

What we store, and why

Players. A league or tournament can only be published with the names of the people playing in it. For each player we keep a first and last name, an optional nickname, a city and country, and their matches, scores and results. We also keep gender, used to write sentences in the right grammatical form and possibly for women's competitions; it isn't shown on its own. A club or league manager can add a player who has no account, the same way a name is written on a paper scoresheet.

This is public: player pages, standings and results can be seen by anyone and found through search engines. That's the purpose of the site. A league's history is a record of what happened, so results stay with the names they were played under.

Photos. A player can add a photo of themselves, and the platform admin can add or remove one. Like the rest of a player page, it is public. We store a small copy (256 pixels) with everything else the original file carried, such as where and with what it was taken, removed. Removing the photo, or deleting the player, deletes it.

Accounts. If you have an account, we also keep your email address, your password (stored only as a one-way hash; we can't read it), your preferred language, your role (player, club manager and so on), the competitions, players and calendar events you follow, and when you signed up and last changed your password. None of this is shown publicly. Your email is used only for the account itself: sign-in, invitations, password resets and confirmations. We don't send newsletters or marketing.

Two-factor sign-in. If you turn it on, we also keep the key your authenticator app uses (encrypted) and your recovery codes (only as one-way hashes, like your password).

Phone notifications. If you turn them on, we keep, for each device, the address we send its notifications to and the keys that encrypt them, and on your account which kinds of notification you turned off. They are delivered by your browser's own push service (see below), encrypted so that only your device can read them. Turning them off in Settings removes the device; blocking them in your browser removes it the next time we send; deleting your account removes them all.

Invitations. When a club invites you, we keep your email address, who invited you, and any corrections you made to your details when accepting.

Change history. To settle disputes about a result, and to undo mistakes, every change to results, players and competitions is recorded: what changed, when, and which account made it. This history is kept for as long as the records it describes.

Email log. For every email we send we keep the address, the kind of email, and whether it was delivered, but not its contents. It is used to spot delivery problems and to limit how many emails one address can receive, and is deleted after 12 months.

What we don't store: your IP address, browser details, birth date, phone number or location. We don't build profiles of you and we don't sell data.

Cookies and storage in your browser

• Sign-in cookies (authjs.*): keep you signed in, for up to 30 days. Strictly necessary.
• Known-device cookie (cr_device): remembers that you have signed in on this device before, so wrong passwords typed elsewhere cannot block you here. Kept for a year. Strictly necessary.
• Two-factor cookie (cr_2fa): set only if you tick "don't ask again on this device"; remembers for 30 days that this device passed the code. Strictly necessary.
• Language cookie (locale): remembers the language you chose, for one year.
• Preferences in your browser's local storage: theme, colour, how match rows are laid out, which panels you collapsed, and whether you were already offered notifications. They stay on your device and are never sent to us.
• Advertising cookies: set by Google, see below.

Other companies involved

• Hetzner (Germany): the server the site and database run on.
• Cloudflare: delivers the site and protects it from attacks; stores encrypted copies of the database as backups (kept 30 days); stores players' photos; counts visits with Cloudflare Web Analytics, which uses no cookies and doesn't track you across sites.
• Resend (EU region): sends our emails.
• Google, Apple, Mozilla or Microsoft, depending on your browser: deliver phone notifications, if you turn them on. They see that a message went to your device, not what it says.
• Google AdSense: shows ads, see below.

Advertising

CueResults is free and is paid for by ads from Google AdSense. Google and its partners use cookies to show ads, to measure them and, if you agree, to choose ads based on your earlier visits to this and other websites. Visitors in the EU, EEA, UK and Switzerland are asked first and can refuse; ads are then still shown, but not personalised.

You can change how Google personalises ads at adssettings.google.com, and read how Google uses data from sites like this one at policies.google.com/technologies/partner-sites.

Your rights

You can ask us to:

• show you what we hold about you;
• correct it: most of it you can edit yourself on your profile;
• delete your account. We remove your email, password and account; your name stays on results that have been played, since they are part of the league's record. If you don't want your name on them either, tell us and we will anonymise it;
• object to something we do with your data.

Write to [email protected]. We answer within 30 days. If you think we got something wrong, you can also complain to the data protection authority in your country.

Children

Players of any age take part in competitions and appear in results like everyone else. If you are under 16, ask a parent or guardian before creating an account. A parent can ask us about a child's data, or have it corrected or anonymised, at the address above.

Changes

If this policy changes, the new version is published here with a new date. Bigger changes are announced on the site.