Cookies

What we set

• authjs.session-tokenKeeps you signed in. Set only after you sign in, and removed when you sign out.Lasts 8 hours · strictly necessary
• sp-themeRemembers whether you chose light, dark or system appearance. Set only when you choose one.Lasts 1 year · strictly necessary
• sp-cookie-consentRemembers your answer to the cookie question, so you are not asked again — and so the site can honour a "no" before anything third-party loads.Lasts 1 year · strictly necessary

Why you are usually not asked

Every cookie above is strictly necessary — each one is set because of something you did, and the site cannot do what you asked without it. Under the Privacy and Electronic Communications Regulations those do not need consent, and asking anyway would train you to dismiss a box without reading it.

Visitor numbers are measured with Umami, which sets no cookie and stores no identifier for you at all.

When you will be asked

Some parts of the site are provided by other companies and set their own cookies the moment they load. You will be asked before any of them does, refusing will be exactly as easy as accepting, and nothing will be set before you answer. Each has a way to do the same thing without it.

• Cal.com — the booking calendar, on Book a callShows my diary and takes the booking inside the page. Cal.com sets its own cookies when it loads.Without it: the same booking on a separate Cal.com page, linked from the same spot.
• Zoho Assist — the remote-support widget, on Remote desktopWhere you type the session code I give you on a call. Zoho sets its own cookies when it loads.Without it: the same code page on Zoho’s own site, linked from the same spot.
• YouTube and Trustpilot panelsA video panel and a reviews panel that can be switched on later; each sets cookies when it loads.Both are off today. If either is switched on, it waits for your answer like the two above.