What we collect and why
Pilot version, last updated 20 November 2026.
This is a pilot. This page describes how the software works today. It is not yet a signed data privacy agreement. Please do not use MS Code Lab with a real class until your school or district has approved it.
About students
| What | Why |
|---|---|
| A display name the student or teacher chooses. We suggest a first name and last initial. | So the teacher and classmates can tell who is who. |
| A username and a passcode. The passcode is stored only in scrambled form. | To sign in. |
| What the student makes: code, pictures and songs, written reflections, and answers to check questions. | So their work is saved and their teacher can review it. |
| Progress: which lessons and steps they have reached, and badges. | For the class map and the teacher's gradebook. |
| Grades and written feedback from the teacher. | To return work to the student. Classmates never see these. |
| Ratings of lessons, "confusing" marks, requests for help, and problem reports. | So the teacher can help, and so lessons can be improved. Ratings and marks reach the teacher as class totals without names. |
We do not ask students for an email address, a birthday, a home address, a phone number or a photo.
About teachers
- Name, email address and a password, stored only in scrambled form, to sign in.
- The classes they create and the feedback they write.
What stays out
- No advertising, and no advertising or analytics trackers.
- No selling or sharing of student information.
- No student work is sent to an AI model.
- Fonts and code libraries are served from this site, so opening a page does not tell another company who visited.
In the browser
- One cookie that keeps you signed in. Scripts on the page cannot read it.
- Display choices such as text size and theme are remembered on the device and are not sent to us.
- The device also remembers whether a student or a teacher last used the app on it, and which class, so the next visit loads faster. No name is kept.
- Read aloud uses the voice built into the browser.
- A few machine learning lessons can use the device's camera. The camera picture is used on the device for that lesson and is not sent to us. In those lessons a student may load a model they trained with Google's Teachable Machine, which is fetched from Google.
In Maker Lab
- Students write their micro:bit code in Microsoft MakeCode, which opens in its own browser tab. We do not send MakeCode anything about the student. A student who chooses to share a project there gets a link from MakeCode, and pastes that link into Maker Lab to turn the project in.
- A teacher may add a video to a lesson. It plays from YouTube's no-cookie player or from Vimeo, which then see the device's internet address. Lessons work without videos.
Who else handles the data
Only the company that hosts our servers and database, in the United States. It will be named here before any class uses the service. Like any web host, it records the internet address of each request in its logs.
Keeping schools apart
Every record belongs to one school, and the database itself refuses to show one school's records to a request from another. Within a school, a teacher can reach only their own classes.
Deleting
- A teacher can remove a student, which deletes that student's work, progress and grades.
- A teacher can delete a class, which deletes every student in it and all their work.
How long copies remain in the host's backups will be stated here before any class uses the service.