What the Lab keeps — the privacy note


In one paragraph

We keep the problem we gave you, the answers you sent, and what our checks said about them. We keep your CAD file so the checker can measure it and so you can ask us why it failed. We do not sell anything, we do not advertise, and we do not train an AI model on your work. The tutor, when it exists, is sent your status codes — never your numbers, and never ours.

En un paragraphe

Nous conservons l'énoncé que nous vous avons donné, les réponses que vous avez envoyées, et ce que nos vérifications en ont dit. Nous conservons votre fichier CAO pour que le vérificateur puisse le mesurer et pour que vous puissiez nous demander pourquoi il a échoué. Nous ne vendons rien, nous ne faisons pas de publicité, et nous n'entraînons aucun modèle d'IA sur votre travail. Le tuteur, lorsqu'il existera, reçoit des codes d'état — jamais vos nombres, ni les nôtres.


What is stored, field by field

From your CAD file we keep measurements, not the file's contents: each geometry check stores the one number it measured and the one it expected — a distance, a diameter, a mass — and a review finding stores the one measure its rule read. No name, author, comment or other metadata from the file is ever read into these rows; the measurement contract refuses any field it does not know.

In plain words:

WhatWhy it existsCould we do without it?
Your email addressto sign you in, to confirm it is yours, and to send a reset link when you ask for one. Nothing else: no newsletter, no marketingNo — it is how you get back in
A hash of your passwordto check the password you type. We never see or store the password itself; a one-way hash cannot be turned back into itNo
Your sessionsfor each device you are signed in on: when it started, its browser name and its internet address, kept by our sign-in provider to spot misuse and to let you sign out everywhereNo
Your student id (user_id links it to your account)to give you the same numbers twice and to find your work. It is a short code made from your account, not your email, and it is the only name your work is filed underNo
What you finished, and when (events)a lesson finished, a practice check passed, a step the checker cleared - each with its day. Your uptime and your inspection marks are counted from these rows every time you look, and never stored beside themNo: they are your progress. Opening a page, a wrong answer or a resent one is never recorded as one
Your working days (shift)the days of the week you work on the Lab, so a day off never breaks your uptimeYes: it starts as Monday to Friday
The name the community sees (display_name)shown beside your questions and answers in the community, so help has a person behind it. You choose it; 2 to 40 characters of a name, never an address or a link, and no two students hold the same one. It is never your email, and your email is never shown to anyoneYes, until you post: it is asked at onboarding, and you can change it any time from Me. Posting needs one
Your questions and answers in the community (threads, posts)what you wrote, where it belongs (a card, the challenge, or general), and when. Filed under your student id; other students see it with your display nameYes: remove any of yours at any time. A removed answer leaves an empty place, without your words or your name
Files you attach to a post (attachments)a PNG, JPEG, WebP or PDF of 2 MB at most, its name, its kind and its size. Images are redrawn on your device before they are sent, which removes their location and camera data. Our checker then reads each file once, on our own worker, before any other student can see it - that it is the kind it says, with nothing hidden after its end and, for a PDF, no scripts or embedded files - and keeps the verdict (checked, check_reason, checked_at). A file that fails is deleted and you are told why. Stored privately; served only to signed-in students, only while its post is shownYes: they are optional. A file on a removed post is shown to no one; it leaves storage when you ask us to delete your data, and with the 24-month reduction at the latest
Reports you make (help_reports)which post you reported, an optional reason and when, so three different students can hide a post that does not belong. The author never sees who reported itYes: reporting is optional
Your three answers (role, goal, start_point)who you are here as, what you want to become able to do, where you start. Chosen from fixed lists, never free text, and all optional. They decide what the home puts first; they are never a gradeYes: skip them, or change them any time from the account menu
Your language, when you accepted the beta terms, your 18+ confirmation and your gallery choiceto show the site in your language, and because the beta is for adults and a gallery needs your yesThe gallery choice, yes: it is optional and starts as no
Your requests to the checker, and the reports it sent back (jobs, pages)so the site can show you your brief and every report againNo — they are what the site displays
Your numbers (params) and the correct answersso that a brief you printed in November still means the same thing in December (Contract 6)No. Re-deriving them instead would silently change your problem the first time we edit the challenge
The values you submitted (student)to tell you what was wrong, and to build the mistake library that makes the teaching betterNo, and this is the one that matters most: see below
What we expected (expected, deviation)so a verdict can be re-read and explained months laterNo. Note that these are never sent to your browser, only stored server-side
Timingsso "why did my report take an hour" has a true answerYes, and we keep them anyway because the answer matters
Your CAD filethe geometry checker measures it; you may ask us why it failedNot while the challenge is open. See retention below

The mistake library, stated plainly, because it is the thing we gain. When your answer is wrong, we record what you answered and which known mistake it matches, and we read those records to write better hints and better challenges. Your work therefore improves the Lab for the students after you. It is stored under your student id, it is not published, and it is not sold. If you would rather it were not kept, say so and we will delete your records — see below.

What is not stored

Who else sees it

WhoWhat they get
Fortune (the operator)everything above. One person, one laptop
Resend, which sends our emailsyour email address and the message: the confirmation, invitation or reset link you asked for. Nothing about your work
Supabase, our database host and sign-in providerstores the data above on our behalf and processes it only to run the database, in Frankfurt, Germany (EU)
Cloudflare, which serves the pagesthe pages themselves only; no student data passes through it
Other students, in the communityyour display name, and the questions, answers and files you post there. Never your email, your student id, your numbers or your reports
The AI tutor, when it shipsstatus codes and hint ids. No numbers at all — not yours, not ours. This is a property of the code, not a policy: the tutor view is built by an allow-list, and our tests fail if a number reaches it
Anyone elsenothing

How long

What your device keeps

No cookies for tracking, no analytics, no advertising. So there is no cookie banner: there is nothing to consent to. What the site does keep on your device, all of it needed for the site to work:

WhatWhereWhyUntil
Your sessionone cookie, __Host-lab_session, that no script on the page can readto keep you signed inyou sign out, or the browser closes (unless you ticked "Keep me signed in": then 2 days without a visit)
Light, dark or autoyour browser's storage (4tun.theme)to show the theme you choseyou change it
Your languageyour browser's storage (lab.lang)to show the site in your languageyou change it
Your draft answers and community posts, a check still running, "brief read"your browser's storage (lab.draft…, lab.pending, lab.seen…)so a reload or a phone that slept loses nothingyou sign out: signing out wipes them

Your choices

Beta, and what that means

The Lab is a beta and is labelled as one. Verdicts are produced by tested code, not by an AI, and no AI can change one. Where a result is a judgement call rather than a measurement — the review panel's cost figures, for instance — it is labelled advisory and dated, so that a number taken to a workshop and found to be 40% out was flagged by us before it was flagged by the machinist.


Anything in this note that the code contradicts is a bug in the code or a lie in the note, and an automated test compares the two every time the code changes, so that neither survives.