Privacy
Plain-language summary of current practice. Last updated August 30, 2026.
- Students never make accounts. They join with a room code and a first name, and we never ask them for email, phone, or any other contact information.
- Student work (answers, drawings, votes) lives only as long as the activity. It is deleted when the activity ends, with a 6-hour cleanup backstop.
- Student names are never sent to the AI.
- Nothing about students is sold, shared for advertising, or used to train AI models.
How an activity works
A teacher projects a host screen and students join from their own devices with a short room code and a first name (or nickname). Everything students type or draw goes to the game server, appears where the activity needs it (the projector, classmates' screens, the teacher's console), and is discarded when the activity is over. There is nothing to sign up for and nothing to log into.
What we keep, why, and when it is deleted
| What | Why we have it | Where it lives | When it is deleted |
|---|---|---|---|
| Student first names, as typed at join | So the teacher and the class can see who said what during the activity | Server memory, plus a snapshot that lets a game survive a server restart | When the activity ends or the room closes. Any leftover snapshot is swept within 6 hours. |
| Student answers, drawings, votes, and scores | They are the activity | Same as above | Same as above |
| Reconnect tokens | Let a student rejoin after a wifi drop without losing their place | Same as above | Same as above |
| Teacher room PIN | Pairs the teacher's private console with the room | Same as above | Same as above |
| Activity run counts: activity id, player count, start time | Tells us which activities actually get used | Database | Kept as usage statistics. Contains no names and no student work. |
| Teacher-created activities and recipes | Teacher-authored content, so it survives redeploys | Database | Until the teacher or the site owner deletes them. A structural rule keeps student work out of saved activities: nothing students submit is ever folded into a saved object. |
| Site feedback from the feedback widget | Suggestions and bug reports from visitors | Database | Until the site owner deletes it. Anonymous by design: the form has no name or email fields and asks you not to include personal information. |
About the AI
Some activities send the class's collected answers to Claude, an AI service by Anthropic, to do one job: summarize, group, compare, or judge them for the next step of the activity. Student submissions may also be scored by OpenAI's automated moderation service, which does one job: catch harmful or unkind messages before the class sees them. Before anything is sent to either service:
- Student names are replaced with anonymous ids. Real names never appear in any AI request.
- Known contact patterns (email addresses, phone numbers, links) are removed from the text.
- Neither Anthropic nor OpenAI uses this data to train models.
What stays on your device
Favorites, recently used activities, and the list of activities created on a device are stored in that browser's local storage. They never leave the device and we cannot see them.
Classroom safety
- A content filter checks student submissions before they reach anyone. Obvious harmful content is blocked automatically; messages the automatic checks cannot settle are marked for the teacher to review.
- Teachers see a live moderation panel on their private console and can hide any submission or remove any participant.
- Student drawings never reach the projector without the teacher reviewing them first.
- Teacher controls require the room PIN, with a lockout against PIN guessing.
Security
Connections use TLS. Stored data is encrypted at rest by our database provider (Neon). Production logs contain no student names and no student content. Our hosting provider (Render) may keep standard connection logs, which can include IP addresses, for a short period.
Who runs Jamyard
Jamyard is operated by Max Cady. For privacy questions or deletion requests, email mccady at gmail dot com. Formal terms of service and district agreement documents are in progress; this page describes current practice. The project is made with support from assemblycode.org.