Terms and disclaimer
In plain English, because terms nobody reads are not doing their job.
What this site is
Teaching material. Every build here exists to show you how something works so you can go and make your own version. It is written to get you started and to build up your skills, not to be dropped into a live business.
What the builds are not
They are not products. They have not been security tested, they have not been penetration tested, they have not been reviewed by anyone’s legal team, and they carry no support and no guarantee that they work.
Before any of this goes near real employee data, get it checked by whoever owns security and data protection where you work. That usually means IT, your DPO, and someone in Legal. In most organisations that conversation is short. Skipping it is the expensive option.
Code published here is free to use, change and redistribute, including at work and including commercially. You do not need to ask. It is released under the MIT licence unless a repo says otherwise, and that licence carries the line that matters here: the code is provided “as is”, with no warranty of any kind. What you deploy, and what happens after you deploy it, is yours.
This is not advice
Nothing here is legal advice, employment advice, or data protection advice, and nothing here creates a professional relationship of any kind. It is one practitioner writing about the work for other people who do it. Where a situation needs a lawyer, an employment specialist or your data protection officer, take it to them.
What happens to anything you send
Everything comes through the Ask page. There is no email address published on this site, because a published address is a scraped address within days and the inbox stops being usable for the people it was meant for.
Send the problem, not the people. Please do not include company names, employee names, case details or documents. The useful version of a question is the shape of it, and the shape is what turns into something a lot of people can use. A situation described without the people in it also keeps both of us clear of data protection questions that neither of us wants.
What gets built comes from patterns rather than from individual cases. Nothing you send is published, quoted or attributed to you or your employer. Nothing is sold, rented or passed on. Not to vendors, not as a list, not as research a sponsor paid for.
Accounts
The course has a free account. It exists for three things: keeping your place in the lessons, holding your worksheet answers, and issuing your certificate when you pass the exit test. There is no password; signing in is a link we email you.
What we hold if you register: your work email address, the LinkedIn profile URL you gave us, which corner of the People team you told us you work in, the lane you chose in Lesson 0, your lesson progress and worksheet answers, your certificate details once you earn one, and anonymous usage events (which pages and lessons get used, tied to a random id, never to a name until you sign in). That is the whole list. Registration needs a business email address, and the LinkedIn URL is there so certificates go to real practitioners and so your certificate post can name you. Nothing is sold, rented or passed on, and the corner answer changes which examples your emails use, never which course you get.
Where it lives: the account data sits with Supabase, in their London region, and the emails are sent by Resend. Both act as processors for us and nothing else. To delete your account, ask via the Ask page and it goes, certificate records included; self-serve deletion arrives with the platform and this sentence gets replaced when it does.
Sponsorship
Sponsorship never affects a score, a ranking or what gets built. Every benchmark score cites the version of the published rubric it was produced under, so the working can be checked rather than taken on trust.
The newsletter
Joining is optional and it is never a condition of anything else on this site. You are not required to subscribe to ask a question, request a build, download a repo or read anything here. Unsubscribe is one click and it works.
2 September 2026. This page is written in plain language rather than by a solicitor. If you are relying on it for something that matters, tell me and I will point you at the specific thing you need.