Cookies
Kerby is run by Kerby LTD, a company registered in Scotland with company number SC895039. Questions to hello@gokerby.co.uk.
The short version
If you look around this site without signing in, you get no cookies at all. Nothing is stored on your device until you do something that needs it — signing in, or asking for a verification code. There are no analytics cookies, no advertising cookies, and nothing that follows you to another website.
That is also why there is no cookie banner. Everything below is necessary for something you asked Kerby to do, and the law does not require consent for those. A banner would be asking permission for something that is not optional.
What gets set, and when
| Cookie | What it does | How long |
|---|---|---|
sb-…-auth-token | Keeps you signed in as you move between pages. Set when you sign in, cleared when you sign out. It may be split across two cookies because it is too large for one. | Until you sign out |
kerby_pending_email | Remembers which address is waiting for a verification code, so the next screen can check the code against it. It is kept here rather than in the web address because an email address does not belong in browser history or server logs. Your browser cannot read it. | 30 minutes |
hmrc_state | Only if you connect Kerby to HMRC. It ties the request that leaves Kerby to the one that comes back, so somebody else cannot connect their tax account to yours. Deleted as soon as you return. | Minutes, during that connection only |
That is the whole list. There is no fourth cookie, and none of the three records anything about what you looked at.
Other companies
Two other companies are involved in pages you might use, and it is worth being exact about what each one does.
Cloudflare
The sign-up and waiting-list forms run a check from Cloudflare that tells a person apart from a bot. It receives your IP address and some signals about your browser, and it is used for that and nothing else — no advertising, no profile. Cloudflare may set its own cookie on its own domain as part of the check; it cannot set one on Kerby’s.
Stripe
Payments are handled by Stripe, and Kerby loads no Stripe code on this site — when you pay, you leave Kerby and come back afterwards. Any cookie Stripe uses is set on Stripe’s own pages, under their policy, and is there to spot fraudulent payments.
Turning them off
Every browser can block or delete cookies, usually under Settings, Privacy. You are welcome to.
Be aware of what it costs here: blocking cookies for this site means you cannot stay signed in, so the diary, your pupils and the money screens become unreachable. That is not a restriction we have chosen — a signed-in session is a cookie, and there is no other way to hold one. The public pages will carry on working normally.
If this changes
If Kerby ever adds something that is not strictly necessary — analytics being the likely one — then consent becomes required, you will be asked before it loads rather than after, and this page will say so. We are not going to add tracking quietly and describe it here afterwards.
The privacy policy covers everything else Kerby holds and why.