Not legal advice, and not yet reviewed by a lawyer. This page describes how the tools are built and the rules they run by. It is being reviewed by counsel, and it will change if that review asks for changes. Nothing here replaces the written agreement between a school district and us, which governs where the two differ.
1. Who runs these tools
The tools are made and run by William C. Chesher. They are used in class at BusinessTech Academy at Santa Fe High School (Whittier Union High School District) and are free to the school.
When a school uses them, the student records in them belong to the school. We hold them only to run the tools 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, sets this out; where that agreement and this page differ, the agreement wins.
2. What we promise across every tool
- No ads, no sellingWe never show ads, sell student information, or build a profile of a student for anything but their own schoolwork.
- 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 tool 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.
- One sign-inSigning in uses your school student ID and a PIN you set at sfhsbta.com/pin. The PIN is stored only as a scrambled hash.
- Deleted on a clockEach tool 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 tool keeps
A summary. Each tool's own notice has the full detail, and its numbers are the ones the tool actually runs.
| Tool | 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; 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 first name and class lists, the programs and code you save, what you ask player two 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. 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. |
| train | Nothing on our servers. Your examples and models stay on your own device, and no train camera path keeps a frame. See its written retention policy. | On your device, until you delete them. |
The student directory. One list, kept by the academy, holds each student's ID, name, class lists and PIN hash, so every tool signs a student in the same way. Taking a student off it removes them from every tool that reads it.
Feedback. The Feedback button on each tool sends a report to the person who runs the tools. It carries your student ID only when you are signed in; otherwise it is anonymous.
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.
- 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, "remove" deletes one example, "remove class" deletes a class and its examples, and "start over" 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
- train is for scenes and things, never people, and it is never taught to tell people apart. A picture with a
face in it is refused and thrown away before it can become an example. The check runs on the student's
device where it can: in the browser, and on the K230. 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 face check is being finished and is not yet live in every step. Until it is, train is for scenes and things only, and anything shown to it still never leaves the student's device. - 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 tools 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 and bench have "player two", and launch has H.A.L.: helpers that can answer a student's question with Claude, an AI model made by Anthropic, reached through Anthropic or Amazon Web Services. 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. Helpers are optional; every tool works without them. A teacher can read the questions their students asked in spawn and bench, to help them.
In launch, if a question sounds like a student might be in danger, it goes to an adult at the academy with the student's name, so a person can check on them.
6. Seeing and deleting your data
- Students: ask your teacher. They can show you what a tool 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 admin@cromulentech.com; the school decides, and we carry it out.
- Leaving the school: when a student leaves the school's list, the tools that read it delete what they keep about that student, each on its own schedule above.
- Under 13: the tools 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.
7. 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 and keep none.
8. Terms of use
- Use
- The tools 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 tool, or use a camera on people who have not agreed to it.
- Your work
- What you make is yours. You let us store and show it only as the tool needs to (for example, a game you share on Spawn Point), and you can delete it.
- No warranty
- The tools are provided as they are, without warranty of any kind. A tool 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 tools themselves are copyright 2026 William C. Chesher, all rights reserved. The works credited below keep their own licenses.
9. Credits and licenses
train
- Triceratops by DailyArt, CC BY-NC 4.0.
- Turbine | Turbofan Engine | Jet Engine by blenderbirb, CC BY 4.0.
- Chocolate Berry Cake by Anch0r, CC BY 4.0.
- C-17A Globemaster III by VTX, CC BY-NC-SA 4.0; the compressed copy is shared under the same license.
- 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.
10. 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 admin@cromulentech.com. You can also ask your teacher, or use the Feedback button on any tool, which reaches the person who runs them.