Privacy Policy

Your email address, if you give it

The waitlist form and the "Email me Day 1" form send your email address to beehiiv, the service that runs my email list. Along with it goes which form you used and the chapter you were on, so I can tell what made people sign up.

You get what you asked for, Day 1 or news about my 7-day course, and my newsletter about building apps with AI. Every email has an unsubscribe link.

beehiiv records when you open one of my emails or click a link in it. I use that to see which emails help, and to stop writing to people who never open them.

Legal basis: your consent (GDPR art. 6(1)(a)), which you give by sending the form. Unsubscribing withdraws it.

Your progress and settings

Your browser keeps the tasks you ticked, whether the sound is on and whether you joined the waitlist, in its local storage. Two cookies keep your choices. questbook.view says whether you see a chapter as a map or a list, and questbook.backdrop which backdrop you picked. Both last a year.

The cookies travel to my server with each page request, so the page opens the way you left it. The server reads them and stores nothing. None of this tracks you or goes to anyone else, so it needs no consent. Clearing this site's data in your browser removes all of it, and your progress with it.

How people use the site

PostHog counts the visits to StackQuest and what people do on it: the pages and quests they open, the buttons and links they click with the words on them, the videos they start and watch to the end, the prompts they copy, the tasks they tick and the forms they send. It also measures how fast each page loads and responds for you. With each of these goes the page's address, the site or link campaign that brought you, your browser, system and screen size, and the time. What you type into a field never goes to PostHog, so your email address doesn't either.

PostHog sets no cookie and stores nothing in your browser. To tell visitors apart, its servers turn your IP address and your browser's name into a code with a key that changes every day, then drop the IP address. So I see how many people came on a day and what they did, but not who they are, and the next day you count as someone new. I use it to see which quests help and what makes people join the waitlist.

Legal basis: my legitimate interest in knowing which parts of the site work and which don't (GDPR art. 6(1)(f)).

Server logs and spam protection

StackQuest runs on Vercel. Like any web host, Vercel logs each request with your IP address, the time, the page and your browser's name and version.

I protect the signup forms, so a script can't sign strangers up to my list. When you send a form, Vercel BotID reads a few things about your browser, like its graphics chip and whether automation software controls it. Vercel judges from those and from the request, your IP address included, whether a person sent it, and my server turns away the requests that fail. BotID stores nothing in your browser. Vercel's firewall also turns away more than five signups from one IP address within ten minutes.

Legal basis: my legitimate interest in keeping the site running and the list free of fake signups (GDPR art. 6(1)(f)).

Videos

Mux hosts the videos I record. When a map or a quest shows one of them, your browser loads its still image from Mux. Pressing play, or opening a video from its still on a map or in a list, loads Mux's player, which fetches its code from jsDelivr and Google's Cast software from Google, so both get your IP address too. Mux measures how the video plays, like when it starts and whether it stalls. It works out a rough location from your IP address, shortens the address before it keeps it, and sets no cookie. The player remembers in your browser whether you muted it.

Legal basis: my legitimate interest in showing you the video you asked for (GDPR art. 6(1)(f)).

Fonts

The fonts come from StackQuest's own server. Opening a page sends nothing to Google.