Not legal advice, and not yet reviewed by a lawyer. This page describes how the rooms are built and the rules they run by. Once a school district signs a written agreement with us, that agreement governs where the two differ.
privacy policy, sections 1 to 10, for every room
1. Who runs these rooms
When a school uses them, the student records in them belong to the school. We hold them only to run the rooms for that school, as a "school official" under FERPA, and use them for nothing else. A written student data privacy agreement with the district, meeting California Education Code 49073.1, is being prepared and is not yet signed. Until it is, this page is the full statement of how we handle student records; once it is signed, where that agreement and this page differ, the agreement wins.
2. What we promise across every room
- No ads, no selling, no profilingWe never show ads, sell or share student information, or build a long-term profile of a student. The growth record (section 5) is the student's own, counts only, and is deleted after about a year.
- AI never decides about a studentNo room uses AI to grade, place, group, refer or discipline a student. A teacher decides, and anything a room counts is there to help, never to rank or predict behavior.
- No reading of feelingsNo room tries to read a student's emotions or state of mind, or watches how they type, look or move. The one exception is safety: words that sound like a student may be in danger reach an adult, so a person can check on them (section 5).
- No AI trained on student workWe do not use anything a student makes, writes or shows to train or develop an AI system, ours or anyone else's.
- The least we can keepNo room asks for an email address, a phone number or where you are. Screens show a first name, or a first name and last initial, never a full name.
- Your student ID and first name, kept as they areA room you sign in to keeps your student ID and your first name with your work, as plain text, not scrambled or encrypted. That is on purpose. Your school email address is your student ID, and your first name travels in every email you send, unencrypted, so neither is a secret: they are how the school already names you. A room needs them to sign you in, give your own work back to you, and let your teacher find it. What proves it is you is your PIN, and the lock that stops anyone guessing it.
- One sign-inSigning in uses your school student ID and a PIN you set at cromulent.tech/pin. Your PIN is four digits, and it is kept as it is, not scrambled. That is on purpose: scrambling four digits protects nothing, because all 10,000 of them can be tried in a moment. What protects it is the lock: five wrong tries in 15 minutes, or fifteen in a day, locks that student ID at every room until the misses age out or a new PIN is set.
- Deleted on a clockEach room deletes what it keeps on a fixed schedule (below), and sooner when you or your teacher ask.
- Backups age outOff-site backups are encrypted and kept for at most 30 days, so anything deleted is gone from every copy within 30 days, and a restore cannot bring a deleted student back.
3. What each room keeps
A summary. This page is the one privacy policy for every room: glitch, launch, claim and standpoints have their full notices just below the table, and the others link to the page that explains them.
| Room | What it keeps | How long |
|---|---|---|
| glitch | The name you join with, your answers and how long each took, anything you write in a game, and a random tag in your browser so you can rejoin. The voice host may say your first name aloud, in a voice made by ElevenLabs; that recording is deleted within hours. Full notice | Names, answers and writing are deleted at the June 30 cleanup after the game, or sooner. What stays has no names in it. |
| spawn | The games, drawings, sounds and tunes you make, what you ask player two and its answers, and time spent. Your account carries your first name only. A game you share shows its title and your first name. Full notice | An account nobody uses for 180 days is deleted whole, as is one a week after you leave the school's list. A shared game nobody featured is deleted 180 days after it was last shared, and you can take it down at any time. |
| bench | Building needs no account. Signed in: your student ID, first name and class lists, the programs and code you save, what you ask the partner with its answers and which suggested changes you kept, and a program's runs and readings once it is on a device. Full notice | A program's runs and readings are kept 30 days. Saved programs stay until you or your teacher delete them, and everything of yours here is deleted a week after you leave the school's list. A share closes after 7 days. Open item: an erasure request does not yet reach a program shipped to a device on its own. Until it does, ask, and it is deleted directly. |
| launch | Your student ID and your name from your class list, your crew's mission and everything your crew writes, where you are in the game, and when you sign in and out. Full notice | Deleted at the June 30 cleanup after your class's last mission day, or sooner. Your mission record stays while you are on the school's list. A week after you leave the school's list, your place in a crew, what you were writing, the period you chose and your mission record are deleted, and a game you played alone goes with them; a crew's shared mission log stays with the crew, with you taken off it, until the cleanup. |
| train | When you sign in, a session: a record that you are signed in, with when it began and when you last used it, and nothing else. Your examples and models stay on your own device, and no train camera path keeps a frame. See its written retention policy. | The session ends when you sign out, after an hour away, or after twelve hours at most. Your examples and models stay on your device until you delete them. |
| claim | Your first name and class lists from the school's list, the cards and replies you post on a board, your reactions, your answers to the class's questions (where you stand, how a source leaves you feeling), the table your teacher seats you at, and whether you would rather not be called on. Classmates see your name on a card only if you choose to show it, and the room's answers never carry a name; your teacher always sees it. What you ask your partner, and what it answers, is kept for your teacher to read. Your partner is handed your own work here, never your name, so it can meet you where you are: you can read exactly what it is handed, and switch it off. Nothing is used to train an AI. Full notice | Deleted at the June 30 cleanup after the seminar, or sooner when your teacher deletes it. Within minutes of your leaving the school's list, your name and student ID come off every seminar you were in, and what you wrote there, asked your partner or answered in your own words is deleted; an answer you picked stays, with no name, so the room's counts still add up. |
| tag | The pieces you put up on a wall: recordings of your screen walking through your work, with your voice and, if you turn it on, your camera; recordings from your camera or microphone; pictures and writing; the highlights you mark, the tags you add, the place from your teacher's list you pick, where you put a piece on a line between two tags, your reactions and replies, and whom you tag. A recording can show your face and carries your voice: it is kept only as the piece you made. Before it is kept, the server makes a fresh copy and deletes your original, so no location, device or camera time inside the file survives. Your class sees a piece only after your teacher shows it, and sees your name on it only if you choose; your teacher always sees it. You can have your camera drawn as a sketch; that is for comfort, not anonymity, because your voice still identifies you. If you say yes, your piece can be in the wall's reel, one film of its pieces that plays only to your class; taking your yes back removes you from it. No face detection or recognition, no voice recognition, and no AI sees any recording. While you record, your browser keeps the recording on your device until it is up, so a closed tab or a dropped connection loses nothing; it is deleted from the device when it goes up, when you throw it away, after 3 days, or when someone else opens tag's recorder in that browser. What you write on tag is read for words that sound like you may be in danger, as every room does, so an adult can check on you. Once a week tag sends your growth record counts only: pieces you put up, days you put one up, calls you answered, misses where you named a new driver, and walkthroughs you put up on a wall asking you to explain something you built with a helper. Full notice | Deleted at the June 30 cleanup after the wall closes, or sooner by its retention setting, and everything of yours a week after you leave the school's list. You can delete a piece at any time, and save your own pieces first. |
| dive | Reading a dive's question needs no account. Signed in: your student ID and first name (kept as they are, as in every room), and on each dive your guess, what you found, what you did to check it, your claim, and whether your guess held; what you did in the pool to test it, opened from that dive (each view you settled on, never the rows) and each hand-in you made there; and each question you ask the partner, the dive and step you asked it on, and how the round ended. The partner's answer is not kept, only its length and the one idea it named. Your teacher can read your work and your questions, to help you. Once a week data sends your growth record: counts only, including the guesses you judged and the misses where you said what was different. Full notice | Everything of yours here is deleted within minutes of your erasure from the school's list. The dives and their datasets are public and hold nothing about you. |
| standpoints | Your sign-in (made from your student ID by a one-way code, so the ID itself is not kept), your first name and, if your school gives them, your name and email, locked with a key that belongs to you alone; your wonders and observations; your investigations, notes and conversations with your AI partner, encrypted with your key; sensor readings; the area you investigate, never an exact spot; and voice recordings only if you choose to record. Full notice | Raw sensor readings and voice recordings are deleted after 90 days. The rest stays until you ask for it to be deleted; then your key is destroyed and everything locked with it can never be read again. |
The student directory. One list, kept by the academy, holds each student's ID, name, class lists and PIN, so every room signs a student in the same way. Taking a student off it removes them from every room that reads it.
Feedback. The Feedback button on each room sends a report to the person who runs the rooms. It carries your student ID only when you are signed in; otherwise it is anonymous. Use it, or write to us, to report a room that works worse for some students, gets in the way of a student with a disability, or causes harm.
glitch, launch, claim and standpoints in full
Until 2026-11-20 each of these four had its own privacy page, and standpoints its own terms. They are one policy now, and their old addresses land here.
glitch
- What it keeps
- The name you type to join a game, or, if your advisor uses a Lineup, your contestant ID and the name on that Lineup. Your answers, how long each took, and whether you said you were sure. Anything you write in a game: a reason, a question for your advisor, a word for the word cloud. A random tag your browser keeps, so you can get back in if the page closes. glitch does not ask for your email, your phone number or where you are.
- Who sees it
- Your advisor, the person running the game, sees your name and every answer. Other contestants may see names on the projector and the leaderboard; a name you typed shows only after your advisor lets it through.
- The voice host
- The voice host may say your first name out loud in the room. The recording of your name is deleted 24 hours after it is made.
- How long
- Your name, answers and writing are deleted on their own in the June 30 cleanup after the game, or sooner if the school sets a shorter limit or your advisor deletes them. What stays has no names in it, only counts like "12 of 30 got question 4 right". Signed in with your student ID, glitch keeps how you have done across games (no names, no answers) while you are on the school's student list, and that goes when you leave it.
- Deleting it
- Ask your advisor, who can delete a game's names and answers right away, or the person who runs the rooms, who can take you off the student list and everything glitch keeps about you with it.
launch
- What it keeps
- Your student ID and your name from your period's roster, which your advisor loads; on screens you are your first name and last initial. Your crew's mission: every press, every choice, and everything your crew writes, such as goals, reasons and the directives you write for the base's mind. Where you are in the mission, which letters you have read and words you were still typing, so the game is the same on any computer. If your advisor sets your console to its guided cards, that setting and how much help each choice took. When you sign in and out. launch never records your voice.
- Who sees it
- Your crew sees your first name and last initial and your crew's work. Your advisor sees every student's name and work at the advisor desk. The board shown to the room has crews and their progress, never a name.
- Asking H.A.L.
- H.A.L. answers from the script. When the script has no answer and the person who runs launch has switched it on, your question goes to Claude, made by Anthropic, with your crew's game and never your name. Your question and the reply are not kept. What is kept of each question is how you asked it, never its words: whether it asked how to start, said what you were going for, told H.A.L. he got something wrong, or built on his last answer, and how many details it gave. Those counts, and whether you said H.A.L. helped with a run, are part of your weekly record of how you work with AI, which the academy's admin keeps; it has no words and no name in it. While your advisor runs a check, H.A.L. rests and the runs you make are counted as your own. If anything you write in launch, to H.A.L. or anywhere else in the game, sounds like you might be in danger, H.A.L. shows you where to reach a person, and your words go to an adult at the academy with your name.
- Feedback
- The Feedback button sends what you write, any screenshots you add, the page you were on and your browser's name to the person who runs launch, in the rooms' one inbox. Signed in, it also carries your student ID and your crew and period, so they can follow up; signed out, it goes without them. launch keeps no copy once it is sent.
- How long
- Your name, your crew's mission and what your crew wrote are deleted in the June 30 cleanup after your period's last mission day, or sooner by your advisor. Your mission record (what your crew chose in Mission Alpha, crewmates named by student ID, never by name) carries into the next mission while you are on the student list. A week after you leave the list, your place in a crew, what you were writing and the period you chose are deleted, and a game you played alone goes with them; a crew's shared log stays with the crew, with you taken off it, until the cleanup.
- Deleting it
- Ask your advisor, who can delete your period's mission or your mission record right away, or the person who runs the rooms.
claim
- What it keeps
- Your student ID and the name on your teacher's class list, or the name you type if the seminar takes names. Your answers at each step, before and after the talk. Anything you write: a sentence, what in the source shows your answer, a question for the room, a reason, and what moved you. What you ask your partner and what it answers. A random tag your browser keeps, so you can get back in.
- Who sees it
- Your teacher sees your name beside what you answer, write and ask your partner. The room never sees your name beside an answer: the screen shows answers as counts and shapes, and only once five people have answered. A sentence you write may be shown on the screen, without your name. "Your thinking today", your own path through the seminar, opens only on your device.
- Your partner
- Your partner is Claude, made by Anthropic. What you ask it is sent to Anthropic to get an answer, and nowhere else; your name and student ID are never sent. If something you write sounds like you might not be safe, it points you to people who can help, and the person at your school who looks after student safety is told.
- How long
- Deleted on its own in the June 30 cleanup after the seminar, or sooner if the school sets a shorter limit or your teacher deletes it. What stays has no names in it, only counts.
- Deleting it
- Ask your teacher, or the person who runs the rooms. A parent or guardian can ask the same.
standpoints
standpoints, at standpoints.net, is where you investigate a place you know and publish what you find.
- What it keeps
- Your sign-in: your school student ID and PIN, checked by your school's sign-in service; standpoints never stores the PIN, and makes your account from your ID by a one-way code, so it does not keep the ID itself. Advisors sign in with a handle and a password, stored only as a one-way hash. Your first name from your school's sign-in, and your name and email if your school gives them, locked with an encryption key that belongs to you alone. Your wonders and observations, kept as you typed them until you delete one. Your investigations: what you add, your notes and your conversations with your AI partner, saved to a record that cannot be quietly changed and encrypted with your key. Sensor readings from devices in your investigation (raw readings are deleted after 90 days). The area you investigate: a census tract, a zip code, a city, or a shape you draw, never an exact spot. Voice recordings, only if you choose to record; they are deleted 90 days after you make them, and a voice built from them is kept until you delete it or ask us to delete your information.
- Who sees it
- Your advisor sees your name, and only the advisor of your own class; nobody else in standpoints does. Your advisor sees your investigation when you ask them something or hand it in. A class facilitator sees your handle and what you are investigating, never your name, and cannot approve, publish or take down your work. To answer you, your words and the conversation so far are sent to Anthropic, which runs the AI. When a map loads, your browser fetches map images from map providers, which see your device's internet address, as with any website map. The public sees your work only if you publish and your advisor approves: your title, your own conclusions, the evidence you picked, counts, dates and a rounded area, never your name, your other notes, your conversations with your partner or an exact location. Your advisor can take a published record down at any time, and its link then says it was withdrawn.
- Cookies
- No advertising, analytics trackers or tracking cookies. The only cookie keeps you signed in, and it ends after 24 hours without use.
- Deleting it
- You or your family can ask, at the address in section 13, and we answer within 10 days. We destroy your encryption key, so everything locked with it, including your name, email, notes and conversations, can never be read again by anyone, us included. Your wonders, observations and voice recordings are deleted, your account is closed, and a published record says it was withdrawn at your request. The locked records stay in place but unreadable, so the integrity check on everyone else's work still holds. A backup made before your deletion holds your information until it ages out (30 days at most); if one is ever restored, you are deleted again before anything goes back online.
4. train: written retention policy
train teaches a machine to recognize a scene or a thing from a few examples. This is its retention policy, for its examples and its models. It applies on every device train runs on: a browser (webcam), an Adafruit MEMENTO, a HuskyLens 2, a K230, and the classroom box that serves them.
- Signing in
- A student signs in to the train studio with their student ID and PIN, as on every product. Signing in sends the ID and the PIN and nothing else: no example, picture, sound or model. train keeps a session while the student is signed in, and the sign-in is counted in the suite's student directory, as every product's is.
- What an example is
- A picture or a sound a student shows train while teaching it. In a browser, an example is kept as a list of numbers describing the picture plus a small 56-pixel preview, so the student can see what they taught.
- Where examples are kept
- Only on the student's own device: in their browser's storage, or on the camera board they are teaching. We never keep an example. The one time anything leaves the device is a MEMENTO frame checked for faces on the classroom box (below): it is held in memory only, answered pass or fail, and deleted either way.
- How long examples are kept
- Until the student removes them. In a browser, "Clear" deletes the examples of one thing, "Remove" deletes a thing and its examples, and "Forget this device" deletes everything on that device. Clearing the browser's site data does the same. A shared classroom device is wiped before another student uses it (below).
- What a model is
- What train learned: the center and spread of each class, as numbers. A model never contains an example, a picture or a sound.
- Where models are kept, and for how long
- A model is a file the student downloads and keeps, on their device or wherever they choose. It is theirs to keep, share or delete. train holds no model on a server today. If it ever holds one for a student, that copy is held only for that student, read by no one else, deleted when the student or the school asks or when the student leaves the school's list, and never kept longer than the school keeps its own records.
- Faces
- In the train studio in a browser, a student's pictures may include their own face. Those pictures are the
student's. They stay in that browser, are never sent to us or to anyone, and leave the device only in a work
file the student chooses to save. The site is served so that the browser refuses to send anything to any other
address. A model holds an average, as numbers, of each thing it was taught, never a picture, and we never
receive it.
On a shared iPad or Chromebook, Forget this device removes the pictures and models from that browser.
On the classroom cameras, a picture with a face in it is still refused and thrown away before it can become an example. On the K230 the check runs on the camera. For the HuskyLens 2, the classroom software stops the camera from learning while it reports a face. For the MEMENTO, the frame goes to the classroom box, which checks it in memory only, answers pass or fail, and deletes the frame either way; nothing about the face is logged or kept. The face recognition, emotion, gaze and face-direction features of the HuskyLens 2 stay switched off on classroom units.
Where this stands: the classroom camera face checks are being finished and are not yet live on every camera. Until they are, the classroom cameras are for scenes and things only. - Sounds and voices
- In the train studio in a browser, a student can teach sounds with the microphone, and those sounds may include their own voice. The sound itself is never stored: each example keeps only numbers describing one second of it and a small picture of its pitch and loudness. Like pictures, these stay in that browser, are never sent to us or to anyone, and leave the device only in a work file the student chooses to save. The microphone is open only to train's own pages and only while a sound project is on screen.
- A file for the teacher
- A student may choose to save a small file for their teacher from the last step in the studio. It holds the name the student types, the names of the things they taught, how many examples, the model's scores, and what they wrote about where it failed. It holds no picture, no sound and no model. The student sees every line before saving it and hands it over themselves; it never passes through us. The teacher's class view reads these files in the teacher's browser tab and keeps nothing.
- Camera frames on the classroom network
- No train path keeps a camera frame. The MEMENTO face check holds a frame in memory only. Classroom software that relays a HuskyLens 2 to other rooms keeps no frame for train; if any classroom path is ever built to keep frames, this page changes before it goes live.
- Shared classroom devices
- A camera board used by more than one student (a classroom HuskyLens 2, MEMENTO or K230) is wiped of what it was taught before it passes to another student, so one student's examples or classes are never left for the next.
- Sharing and combining models
- We never combine students' examples or models into a model of our own, on any server. A student may choose
to share their own model file with a classmate; that is their choice and can be undone by deleting the file.
Under review: whether, and how, a class may combine the models its students choose to share. Nothing combines models today, and this page will say so before anything does. - Training on student data
- We do not use anything a student shows train to train, develop, tune, test or benchmark any AI system, including train itself. A student's model is built only from that student's own examples, for that student's own project, and is never combined with another student's. Today it is always computed on the student's own device; if a camera ever needs the classroom box to compute it, the same rules hold there. Nothing from a student session (an example, picture, label or log) is used to tune or test train. Pictures a teacher takes in class are treated the same as students' work. Any built-in model we ship for a camera is trained only on public or licensed datasets, synthetic data, or pictures taken outside any school.
- Deleting on request
- Because examples and models stay on the student's device, the student deletes them there, at any time. A teacher can wipe a classroom device on request. If train ever holds anything for a student, a request to the school or to us deletes it, and backups let it go within 30 days.
5. AI helpers
spawn has "player two", bench and data have "the partner", launch has H.A.L., and claim has "your partner": helpers that can answer a student's question with Claude, an AI model made by Anthropic, reached directly through Anthropic's own service, the same way for every room, through an Anthropic account kept for these school rooms. Anthropic does not train its models on what is sent. A helper sends only what it needs to answer (the question and the student's own work), never the student's name or student ID, and the provider uses it only to answer. Anthropic keeps what is sent for a limited time under its own commercial terms; we have not confirmed in writing that it keeps nothing, so this page does not say so. Helpers are optional; every room works without them. A teacher can read the questions their students asked in spawn, bench and data, to help them.
What a helper is, and is not. A helper is there for the task in front of the student. It is not built to be a friend, to keep a student on the screen longer than the work needs, or to draw out anything personal. Its answers can be wrong: it is a helper, not a teacher, and a student should check what it says. That checking is the point of the next part.
In launch, if anything a student writes (a question to H.A.L., a journal line, a reason, a Feedback report) sounds like they might be in danger, H.A.L. shows them where to reach a person, and their words go to an adult at the academy with the student's name, so a person can check on them.
glitch's voice host can say a player's first name aloud. To do that, the first name, and nothing else about the student, is sent to ElevenLabs, which turns it into speech in the host's voice. ElevenLabs is used only to make that line; the recording is deleted within hours.
Growth records: one student across the rooms
spawn, bench, claim, tag and data each send the school's admin one record a week for each student who worked in them: counts only, such as how many things they made, how they worked with a helper, what they did with the helper resting, and in tag, the calls they answered, the misses where they named a new driver, and whether they walked through work they built with a helper. A record has no place for a sentence, so nothing a student wrote, said or recorded is in it, and it carries the student ID, never a name. Never sent: whether a student passed when tagged, would rather not be called on, turned their camera off or chose to hide their name, who tagged whom, the reactions they got, and whether a call was right.
The teacher sees their own students' records, to know where to help. The district sees totals only, with no name or student ID, and nothing for fewer than 5 students. A growth record is never a grade, never a flag, and never changes what a student may do. Records are kept about a school year and its summer (60 weeks), and are deleted when the student is erased from the school's list.
The student's own controls. From their own page in spawn, a student can see which weeks are kept about them and from which rooms, add a short note of their own to one of those weeks (at most 280 characters, which their teacher reads beside that week, and which goes with the week or when the student takes it back), erase everything kept about them in the growth records, their notes and the lab's read of them included, and switch their growth record off, so that no room's week of theirs is kept until they switch it back on. The note is the one place a student's own words sit beside the counts. Erasing asks once more before it goes, and cannot be undone; the work a student made stays in the room they made it in.
The data science lab
The counts follow the four Ds of AI fluency: Delegation (deciding what to do with AI and what to do yourself), Description (communicating clearly with AI), Discernment (evaluating what AI gives you) and Diligence (using AI responsibly and accountably). They come from the AI Fluency Framework, which Anthropic helped write; we use it as published, and neither Anthropic nor its authors review or endorse these rooms.
To find class trends and patterns, and each student's own skill trajectory, the admin and spawn send growth counts to our data science lab, which runs on a separate server of ours. Two kinds of record go there, and neither carries a name, a student ID or anything a student wrote:
- Class totals. A class's counts for a day or a week, sent only when 5 or more students are behind them. The lab keeps these, to compare one week with the next.
- One student's own counts. Sent under a code only our admin can turn back into a student; the lab never holds the key. The lab works out that student's skill trajectory in memory, answers, and keeps nothing.
A skill trajectory belongs to the student. It says where a student's own AI fluency skills look to be heading, drawn only from their own work in these rooms. It is shown to the student first, in plain words, and then to their teacher, to decide together what to try next; while a student's own view is off, their teacher does not see it either. It is never used for a grade, a placement, a group, a referral or discipline, never compares a student with a named classmate, and never guesses at feelings or behavior. No school or district administrator sees one: they see class totals only, never for fewer than 5 students. It is kept in the student's own growth record and deleted with it.
Nothing the lab finds is a grade or a flag, and it never changes what a student may do.
6. Who handles student data
Only these services touch student data, each only to run the rooms. None may use it for anything else, and none trains an AI on it.
| Who | What for | What reaches them |
|---|---|---|
| Hostinger | The servers every room runs on, rented and run by us in Hostinger's United States data centers (Boston and Phoenix), and the mail that sends sign-in and consent messages. | Everything each room keeps, as described above, and the address a message goes to. |
| Our backup server | Encrypted off-site backups, kept at most 30 days. | An encrypted copy of what the rooms keep. It is a machine owned by the person who runs the rooms, not the hosting company's or the school's; the hosting company's backups are not used. |
| Anthropic | Claude, behind the AI helpers. | The question and the student's own work, never a name or student ID. |
| ElevenLabs | glitch's voice host. | A player's first name, to say it aloud; the recording is deleted within hours. |
If we add or change a service on this list, this page changes, and the school is told first.
7. Security, and if something goes wrong
- In transit: every room is served only over HTTPS, and browsers are told never to use a plain connection.
- Backups: encrypted before they leave the server, and aged out within 30 days.
- Who can see records: the person who runs the rooms, and each teacher for their own students. Admin sign-in is by named account, and changes to student records and settings are logged with who made them.
- Signing in: students sign in with their student ID and a PIN; wrong guesses lock the ID at every room (section 2).
- Responsible party: Cromulent, Inc. is responsible for the security and confidentiality of student records, and is the only one with access to the servers.
If student records are exposed. If we learn that student records were seen or taken by someone who should not have them, we:
- stop it, and keep what we need to understand it;
- tell the school district in writing immediately, and no later than 72 hours after confirming it: what happened, when, which records and which students, what we have done, and who to contact;
- work with the district to tell each affected student and their parent or guardian, in plain words, without unreasonable delay, as California law requires (Civil Code 1798.82), or tell them ourselves if the district asks;
- write down what changed so it cannot happen the same way again, and share it with the district.
8. Seeing and deleting your data
- Students: ask your teacher. They can show you what a room keeps and delete it. In train and spawn you can delete your own work yourself.
- Parents and guardians: you may review your child's records, ask for a correction, or ask for them to be deleted. Ask the teacher or the school, or write to sales@cromulent.tech; the school decides, and we carry it out.
- Leaving the school: when a student leaves the school's list, the rooms that read it delete what they keep about that student, each on its own schedule above.
- Under 13: the rooms are built for high school. If a younger student uses them, the school gives consent for classroom use on the family's behalf, as COPPA allows, and a parent may ask at any time to see or delete what is kept.
9. The laws we build to
- FERPA (federal): student records belong to the school; we act only as its school official.
- California's Student Online Personal Information Protection Act (Business and Professions Code 22584), as amended by AB 1159 from 2027-01-01: no ads, profiling or selling, no using student information to train or develop AI, a written retention policy, and deletion when the purpose is done.
- California Education Code 49073.1: the district agreement for storing pupil records.
- COPPA (federal, as amended in 2025): for any user under 13, including its rules on photos and face data.
- California Consumer Privacy Act: we treat face imagery as sensitive information. It is stored only for a student's own creation of it: a recording the student makes in tag, which their teacher, and their class once the teacher shows it, can watch. No room runs face or voice recognition on it, and no AI sees it.
10. The standard we hold ourselves to
The AI Safety and Privacy Standard for Schools (version 1.0, September 2026) is an agreement written by the National Academy for AI Instruction for the AI companies that serve schools. It is not a law and it does not bind us; we are not a party to it, we are not certified under it, and neither the Academy nor any union or AI company has reviewed or endorsed these rooms. We hold ourselves to it anyway, because it asks the right things, and where it is stricter than the law we follow it. Its rule is ours: when in doubt, protect the student.
Where we meet it today:
- No student work used to train any AI, ever, and the AI helpers run through an Anthropic account kept for these school rooms (sections 2 and 5).
- The least we can keep, and no long-term profiles, behavioral tracking, biometrics or reading of feelings (section 2).
- Student records belong to the school and are stored in the United States (sections 1 and 6).
- AI never grades, places or disciplines a student, and a skill trajectory is the student's own (section 5).
- Helpers are not companions, and a student can see their own growth record.
- Notice to the district within 72 hours if student records are exposed (section 7).
Where we do not yet, or only in part:
- A student can see, erase or switch off their own growth record only from their page in spawn so far; the other rooms do not show these controls yet, and a teacher or the school can still have it deleted (section 8).
- There is no single export of a school's records yet. Some rooms have their own downloads (spawn's player two log and glitch's credit roll as CSV, for teachers), and a student can save their own work from spawn, train and tag.
- Not every room yet confirms a deletion in writing.
- Not every room yet shows, on screen, that a helper is AI and that its answers can be wrong.
- A teacher cannot yet choose full, partial or no AI help for each assignment in every room.
- There is no public trust page or product card yet. Section 6 is the list of who handles student data until there is.
- A family guide and FAQ beyond this page are still to come.
- No independent security audit, penetration test, accessibility audit or certification has been done yet.
This list changes as we close each one, and the date at the top changes with it.
11. Terms of use
- Use
- The rooms are for learning. Use them for schoolwork and your own projects, and be kind to the people you share them with. Do not try to get into someone else's account, break a room, or use a camera on people who have not agreed to it.
- In a room
- Answer as yourself and write in your own words. No names of other people in your answers, nothing hurtful, nothing you would not say out loud in class. Keep your PIN to yourself. Your teacher can hold back anything written for the room, and can remove someone from a game, seminar or wall.
- Your partner
- Where a room has an AI partner, it helps you notice, question and put your own thinking into words. Ask it to help you say what you think, not to say it for you. It can be wrong, it is not a teacher or a counselor, and what you claim is yours to stand behind.
- Your work
- What you make is yours. You let us store and show it only as the room needs to (for example, a game you share on Spawn Point), and you can delete it.
- No warranty
- The rooms are provided as they are, without warranty of any kind. A room may be down, change, or lose work; keep a copy of anything that matters to you (train and spawn let you download your work). To the extent the law allows, we are not liable for loss arising from using them.
- Ownership
- The rooms themselves are © Cromulent, Inc. 2026, all rights reserved. The works credited below keep their own licenses.
12. Credits and licenses
train
- Fox by PixelMannen, CC0; rigging and animation by tomkranis, glTF conversion by AsoboStudio and scurest, CC BY 4.0 (Khronos glTF sample).
- Turbine | Turbofan Engine | Jet Engine by blenderbirb, CC BY 4.0.
- Chocolate Berry Cake by Anch0r, CC BY 4.0.
- Toy car by Guido Odendahl and Eric Chadwick, CC0 (Khronos glTF sample).
- Shark by Optic Idealist, CC BY 4.0.
- Victorinox multitool knife by Halil Kantarci, CC BY 4.0; changed: one clip kept, the key ring removed.
- Robin Nest by Unreality3D, CC BY 4.0; changed: simplified.
- Each model is shown scaled, lit and compressed. three.js, MIT License. The Sora typeface, SIL Open Font License 1.1.
bench
- 3D tool models drawn in characters on the front page: "Hammer Game Ready" by re1monsen, "Sledge Hammer" by MaX3Dd, "Adjustable Spanner/Wrench" by CGWorker, "Hex Nut" by SketchyArtz, "Bolt M10x25 Hexagon Head" by Javier.Herrera, "Circular saw blade" by YouniqueIdeaStudio, "Pliers - Tool Assignment" by Joan Tieu, "DAE - Game Asset Tool Assignment" by Martijn Vaes, "Low-Poly Silicone Gun" by TastyTony, "PBR Crowbar Game Ready" by Eric Wallbank, "Tool - Boltcutter" by Nikolas Gaertling, "TOOL | Axe Weapon Model (CS2)" by 6lucius; each CC BY 4.0, with links on the bench front page.
- Blockly, Apache License 2.0.
glitch, spawn and launch
Each credits the works it uses on its own pages, for example launch's credits. Open-source libraries keep their own licenses, shipped beside them.
13. Changes and contact
When this page changes, the date at the top changes with it. A change that keeps more, keeps it longer, or uses it for something new is told to the school before it takes effect.
Questions or requests, including a request to see or delete data: write to sales@cromulent.tech. You can also ask your teacher, or use the Feedback button on any room, which reaches the person who runs them.