What we keep, in plain words
Builder School is run by Samuel Korkoyah. This page says what the site collects, why, where it lives, and how to have it removed. Last updated 15 September 2026.
Without an account
Your checklist ticks are saved in your own browser and nowhere else. Clearing site data removes them.
If you sign in
We store your email address, so we can send you sign-in links, and your ticks, so they follow you between devices. That is the only reason accounts exist. There are no passwords: each sign-in is a one-time link sent by email.
If you ask for emails
If you enter your address to be told when a new tutorial is up, we keep it for that and nothing else. Every email includes a way to stop them, and you can ask us to delete the address at any time.
If you contact us
The contact form stores your name (if given), email, and message so we can reply. We keep messages for as long as the conversation is useful, then delete them.
Where it lives
Data is stored with Supabase and the site is served by Vercel, both of which process it on our behalf under their own security commitments. Hosting logs, which include IP addresses, are kept briefly for reliability and abuse prevention.
What we don’t do
- No advertising, and no advertising trackers.
- We don’t sell or share your data with anyone for their own use.
- We don’t set cookies beyond the one that keeps you signed in.
Your choices
Sign out from your account page. To have your account, ticks, subscription or messages deleted, contact us or email hello@builderschool.io from the address concerned, and it’s done within a few days.
Children
The tutorials are written to be readable by a kid and a parent together. Accounts are meant for adults; a parent can sign in on behalf of a child.
Changes
If this policy changes in a way that matters, we’ll note it here with a new date.