Scripting and cookies

Reading needs neither

The pages that show a tournament, its scores, its players and its rankings work with scripting switched off. So do choosing the theme and the language, sorting and filtering lists, and searching. Opening a month of a year, and printing a competition, need it.

Cookies

The site sets a cookie to keep you signed in, and others to remember what you chose: the theme, the language, how you sorted lists, the country, region and sport you filtered by, the view of a competition, which notes and commentaries you have read, and what you have said about notices of what is new. While you sign in with Google it keeps one more, until you are back. They are there so that the site does what you asked, and are not used to follow you. If you never sign in or choose, there is little for them to hold. The privacy page has the whole of what the site keeps.

A browser that refuses cookies can still read a tournament. It will forget your choices, and which notes you have read, at each visit, and it cannot stay signed in.

Registering needs scripting

Registering is the one place scripting is needed. The site asks Google's reCAPTCHA to tell a person from a program, and that runs as a script in your browser. If scripting is off when you open the register page, you are sent to a page that says so, before you have filled anything in. Switch scripting on for this site, then go Back to registering.

Asking for a way back into an account you cannot sign in to does not need scripting.

Next: back to Help for readers.