Privacy Policy
Last updated 31 October 2026
You can read all of Sulba, and work through every lab, without telling us who you are. Sulba sets no cookies and shows no ads. If you sign in, your account keeps your progress; if you write to us, we use what you send only to answer you.
Who is responsible
Sulba, based in Toronto, Ontario, Canada, decides how the information described here is used and is responsible for it. To reach us, use the contact page.
When you read the site
- Hosting. Sulba runs on Cloudflare's network. Like any web host, Cloudflare receives the details every browser sends with a request, such as your IP address and browser, and uses them to deliver the site and protect it from attacks. If a page fails to load, your browser may report the error to Cloudflare.
- Visit counts. Cloudflare Web Analytics counts visits for us, except visits from the European Union, the UK, Norway, Iceland, Liechtenstein and Switzerland. For the EU, Cloudflare leaves out every visit its data centers there receive. For each page view it counts, it records the page, the page you came from, your country, your browser, your operating system, your type of device, and how quickly the page loaded. It doesn't use cookies or other storage in your browser to track you, it doesn't fingerprint you, and it doesn't record the part of a web address after a question mark. We see only totals.
- Your theme. If you choose Light or Dark, your browser keeps that choice (as
sulba:theme) so the next page opens in it. It stays on your device, and choosing System removes it. - Your editor theme. If you choose an editor theme other than Sulba's, your browser keeps that choice (as
sulba:editor-theme) so the next lab opens in it. It stays on your device, and choosing Sulba's removes it. - Your code in a lab. A lab keeps the code you write for each stage, which stages you've passed, which problems you caught when you finished a review, when you started each interview problem, with your plan and the time you took to solve it, and each design you write in a design round, with your answers, your time and how you marked it against the rubric, in your browser (as
sulba:code:,sulba:passed:,sulba:review:,sulba:problem:andsulba:design:followed by the stage's id), so you can carry on where you left off. Your code runs in your browser, and neither it nor your plans and designs are sent to us. They stay on your device: Reset removes a stage's code, and clearing your browser's data for sulba.dev removes all of it. - A lab that runs on your machine. Some labs run on your own computer instead of in your browser. Their Download makes a zip in your browser, with the lab's tests and the program that runs them, and that program sends nothing about you or your code anywhere: your code stays on your computer. If a lab needs files too large for its zip, such as a dataset, the program downloads them from their publisher, whose address the lab's page gives, before its first run and again if one goes missing or changes; like any website, the publisher receives your IP address with the request. If a lab has models,
uv run sulba.py modeldownloads them, and llama.cpp's server for your computer, from their publishers the same way, into a folder every lab shares, and runs them on your computer. The models answer only programs on your computer, so what your code sends them stays there. If a lab has a database, its tests anduv run sulba.py dbrun Postgres, which comes with the packages the lab installs, on your computer. On Linux, the first run fetches pgvector, the part that searches by vector, from apt.postgresql.org the same way, into that shared folder. The database too answers only programs on your computer, so what you put in it stays there. If a lab has stages in TypeScript, their first run fetches Node.js from nodejs.org, and the packages the lab names from registry.npmjs.org, the same way, into that shared folder. If a lab has stages in Go, their first run fetches Go from dl.google.com the same way, into that shared folder. Go keeps counts of how its commands are used in a folder of its own on your computer, and sends them nowhere unless you turn that on withgo telemetry on. If a lab has stages in Java, their first run fetches a JDK from github.com, and JUnit and Jackson from repo1.maven.org, the same way, into that shared folder. When you pass a stage, it gives you a link to the lab's page. The part of the link after its#holds which stages you passed there, which problems you caught in a review, and each run of the tests since its last link, with how many passed, when, and the time between runs. Browsers don't send that part of a link to a website, and the page takes it out of the address as it opens, then keeps the stages you passed as it keeps a lab's other progress. - Your reviews. The Review page keeps each answer you give a card, which card, how you rated it and when, in your browser (as
sulba:reviews), so it can work out when each card is due again. Clearing your browser's data for sulba.dev removes them. - Fonts. The site's fonts come from sulba.dev itself.
When you sign in
You don't need an account. If you sign in, you do it with your GitHub or Google account, and Supabase runs the account for us.
- Your account. GitHub or Google tells us your email address, your name, your profile picture's address, your account's id there and, for GitHub, your username. Supabase keeps them with your account, along with when you signed in and the IP address and browser of each session.
- Your progress. While you're signed in, each lab sends your account what you do in it: each run of the tests and how many passed, including those a lab that runs on your machine brings back in its link, the hints you open, when you view a solution, when you pass a stage and, in a Catch stage, which problems you caught. Each comes with the time you spent on the stage and the date. Your code, your plans and your designs aren't sent. We use this to keep your progress on every device you sign in on, to show you the days you've studied, and to see how long stages take, so the course's time estimates are right.
- Your reviews. While you're signed in, the Review page sends your account the reviews your browser keeps, including those from before you signed in, and brings back those from your other devices, so each card is due at the same time on every device.
- Your workspaces. In the app, you can create a workspace or join one with an invitation link. Each workspace keeps its name and address, who is in it and each person's role, the invitation links its admins make, the requests its members write for what they want built, the questions asked about each request with the answers given, the specs its members write with their acceptance criteria, each spec's reviewers with their answers and the notes they give with them, the tasks its specs are split into, with who has each, why one is blocked and the address of the pull request that holds its work, each release of a request a member approves, with who approved it, when, the note they left and a copy of the specs, criteria, test counts, tasks and pull requests it was approved on, and a history of every change to these: what changed, when, and whose account made the change. The history notes when a request's, a spec's or a task's text changed without keeping the text. Everyone in a workspace sees the name and email address of each person in it, and its history. An invitation link lets anyone who has it join, until it's revoked or 7 days pass; we keep only a scrambled form of it, from which the link can't be worked out.
- Your workspace's test results. A workspace's admins can add its GitHub repositories. A workflow in one of them can then send the test results of each run on the repository's branch, with a token GitHub makes for the run, which we check and don't keep. For each run we keep the repository, the branch, the commit, the workflow's name and the run's number, and how many tests passed, failed and were skipped. For each test whose name holds a criterion's ID, we keep its name, its file, how it ended, and the first 500 characters of what a failure said. We keep the last 20 runs of each suite of tests. A run on any other branch is answered and not kept. Everyone in the workspace sees them, and removing a repository deletes its runs.
- Your coding agents. You can connect a coding agent, such as Claude Code, to your account. The agent registers itself with Supabase, which keeps the name it gives and the addresses it asks to be sent back to, and you allow or deny it on a page of ours. Once you allow it, Supabase keeps that you did and when, and the agent works in your workspaces as you, within your role: it reads their requests, releases, specs, tasks and test results, asks questions about a request, writes specs, criteria and tasks, and takes tasks and hands them in. The workspace's history names the agent with each change it makes, and each question it asks. What it reads goes to the agent, and from there to the AI model it uses, under your agreement with whoever makes them. Disconnecting it in a workspace's Settings ends its access at once.
- In your browser. Your browser keeps your session, and the one-time code that started each sign-in, under keys that start with
sulba:session. Attempts not yet sent, such as while you're offline, wait assulba:outbox, and the page to return to after signing in waits assulba:nextuntil you close the tab. The app keeps the address of the workspace you opened last assulba:workspace, to open it next time, and if you turn off single-key shortcuts, it keeps that choice assulba:keys. Signing out removes your session and anything waiting to be sent. - Closing your account. We keep your account, progress, reviews and workspaces until you close your account. Closing it, on the Account page, deletes them all at once, with each workspace you're the only member of; you leave the others, whose history keeps what you changed without your name or email address. While you're the only owner of a workspace with other people in it, make one of them an owner first. What your browser keeps on its own, such as your code and reviews, stays until you clear it.
When you write to us
The contact form sends us your name, your email address and your message.
- The bot check. Before your message is sent, Cloudflare Turnstile checks that you're not a bot. It starts when you first use the form and runs in a frame from
challenges.cloudflare.com. It sends Cloudflare your IP address and technical details of your browser and connection, and usually passes without asking you anything. Cloudflare says it uses this only to detect bots and to improve Turnstile, not to identify or profile anyone (Turnstile's privacy terms). When you press Send, our server asks Cloudflare to confirm the check and passes on your IP address. We receive only whether it passed. - Delivery. Resend delivers your message to our mailbox as an email, with your address as the one to reply to. Our mailbox is hosted by Apple (iCloud Mail).
- A record of the request. Cloudflare keeps a record of the request that sends your message, such as when it was made and the address it went to, for 3 days.
We use what you send only to answer you, and keep it as long as we need to.
Who handles it for us
Each provider uses your information only to provide its service to us, under its own privacy terms:
| Provider | What it does | Where |
|---|---|---|
| Supabase, Inc. | Runs accounts and sign-in, signs in the coding agents you connect, and keeps your progress, reviews and workspaces | United States |
| GitHub, Inc. | Confirms who you are when you sign in with GitHub, and signs the token a workflow run sends its test results with | United States |
| Google LLC | Confirms who you are when you sign in with Google | Around the world |
| Cloudflare, Inc. | Hosts the site, counts visits, runs the bot check, and passes your message to Resend | Cloudflare's network, around the world |
| Resend (Plus Five Five, Inc.) | Delivers your message to our mailbox | United States |
| Apple Inc. | Hosts our mailbox (iCloud Mail), where your message is kept | United States |
We don't sell your information or share it for advertising. We'd disclose it only if the law required us to, or to protect the safety of people or of the site.
Our legal basis
- Your account, progress, reviews and workspaces: to provide the account and the workspaces you asked for.
- Answering you: you asked us to, and we have a legitimate interest in answering.
- Visit counts, the bot check and the record of requests: our legitimate interest in running a secure site and knowing how it's used.
In Canada, you consent to what's described here when you sign in or write to us.
Where it's kept
Your account, progress, reviews and workspaces are kept in the United States by Supabase. Your message is processed in the United States by Resend and kept there by Apple, and requests pass through Cloudflare's network. Information kept outside Canada may be accessible to the courts and authorities of the country where it's kept.
Your rights
Depending on where you live, you can ask to see the information we hold about you, to correct it or to delete it, and you can object to how we use it. You can close your account yourself on theAccount page. To ask for anything else, use the contact page. We'll answer within 30 days, and it costs nothing. You can also complain to a privacy authority: in Canada, the Office of the Privacy Commissioner of Canada; in the European Union or the United Kingdom, your local one.
Children
We don't knowingly collect information from children under 13. If a child under 13 has signed in or written to us, tell us through the contact page and we'll delete their account or message.
Changes to this policy
If we change what we collect or how we use it, we'll update this page and its date.