Cookies

Version 2.0. Published 16 September 2026. Reviewed at least once a year, and whenever what we use changes.

What this page is for

This page is about the small files our websites ask your browser to keep. It says what we use them for, how long each one lasts, and what you can do about any of it.

Everything else about your personal information is on the Privacy Policy. To make a request or a complaint, see Your Privacy Rights.

A cookie is a small piece of text a website asks your browser to keep. Your browser sends it back the next time you visit, which is how a website can tell that you are the same person who signed in a moment ago, or that you had something in a basket.

A cookie set by the website you are looking at is called a first-party cookie. One set by another company whose code the page has loaded is a third-party cookie. We use both, and the tables below say which is which.

We do not track you

We use no analytics cookies and no advertising cookies on our websites. We do not measure how you move around our sites, we do not build a profile of you, and nothing we set follows you onto another website.

We record your IP address and the type of browser you are using, so that we can find the cause when something breaks. We do not use either to identify you or to work out what you are interested in.

We do count visits, and we do record faults. We could not improve the software or fix what breaks without knowing which pages are used and what goes wrong on them. We do both without cookies: nothing is stored on your device, nothing is given a number that follows you between visits, and none of it is shared with an advertising company.

The cookies we set

These are ours. Every one of them is there to make something work that you asked for.

What it does How long it lasts
Keeps you signed in as you move from page to page Until you close your browser
Keeps you signed in between visits, where you have ticked the box asking us to 30 days. It does not extend itself each time you visit
Remembers what you were part-way through, such as a class registration, a basket, or which panels you had open From an hour to 30 days, depending on which
Remembers a setting you chose, such as which events a list shows you 90 days
Protects our forms against a particular kind of attack Until you close your browser

We set each one to the shortest period that still makes the feature work, and we do not keep a cookie alive by renewing it every time you visit.

Cookies set by companies that work for us

Three kinds of outside company set a cookie through our websites. We keep these because the service does not work without them. The period is theirs rather than ours, and we publish what they publish.

Company What it is for How long
Stripe, Square, Helcim and PayPal Taking card payments, and telling a genuine payment from a fraudulent one Up to a year
Google reCAPTCHA and Cloudflare Turnstile Telling a person from an automated program before a form is accepted, so our forms cannot be abused About six months
Tawk.to Our live chat support. It loads only when you click to start a chat, and sets nothing at all if you do not About six months

When your browser fetches code from one of these companies, that company receives your IP address, the address of the page you were on, and what your browser reports about itself. That happens by the fact of the fetch, before any cookie is involved. It is why the list above is short, and why live chat does not load unless you ask for it.

Where each of these companies is, and what it handles for us, is on Service Providers and Subprocessors.

Do we ask your permission?

No, and we do not show you a cookie banner. If we ever add a cookie that needs your permission, we will ask before it is set.

Permission is needed for cookies that are not necessary to provide the service you asked for, such as measuring how a site is used, or advertising. We use none of those. What is left is limited to signing you in, keeping your place, taking a payment and stopping abuse of our forms, and cookies of that kind do not require your permission.

Live chat is the one thing that could have needed it, which is why it loads only when you click to start a chat.

Competition organizers who run their own site on our software

A lot of what we do is running a website for a competition organizer. Those sites are built on our software, but the organizer runs them, and our software lets an organizer add their own code to their own site. Some do, most often to measure their own traffic.

Where that happens, the organizer chose it and we did not. We do not decide what an organizer adds, we do not receive what it collects, and we get no benefit from it. It is their tracking, for their purposes, and their privacy notice, not this page, is the one that should tell you about it.

What this page describes is what we put on a page. So if you are on a competition organizer's site:

The Privacy Policy sets out which of us is responsible for what.

How to block or delete cookies

You do not need our permission and you do not need an account. Every current browser lets you do three things from its own settings, usually under a heading such as Privacy, Cookies or Site data.

Your browser's own help pages say where those settings are on your device. We are not going to print a menu path that may have moved since we wrote it. Some browsers and some browser extensions will also block the code itself, which goes further than blocking cookies.

What stops working if you do

Blocking cookies stops you signing in, and stops a basket or a part-finished registration from surviving. Blocking a payment provider's code will stop a payment going through. If you block code loaded from google.com, reCAPTCHA may not load, and a form that relies on it may then refuse to submit. Blocking Tawk.to stops live chat opening.

Nothing else on our sites depends on a cookie, so blocking the rest costs you nothing.

Changes to this page

We review this page at least once a year, and whenever what we use changes. The date at the top says when it was last checked, so you can tell how current the answer is.

Where a change affects what is set on your device, this page, the list of service providers and the Privacy Policy are updated together, so that no part of them contradicts another.

How to reach us

Contact us if you have a question about anything on this page, or if something on it is wrong. If you have checked one of our websites yourself and found a cookie we have not listed, we want to hear about it.

The address dpo@inchol.com reaches our Privacy Officer.

The telephone number is toll free within Canada and the United States. It may not be reachable from outside North America. If you are in the United Kingdom, the European Economic Area or anywhere else outside North America, please use email or post.

If your complaint is about the Privacy Officer, write to our postal address marked for the attention of the Chief Executive Officer, who then takes the decisions the Privacy Officer would normally take.

Our postal address is on Your Privacy Rights.