Plain-language summary of current practice. Last updated August 8, 2026.
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 | 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. |
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. Before anything is sent:
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.
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.
Jamyard is operated by [operator name]. For privacy questions or deletion requests, contact [privacy contact email]. Formal terms of service and district agreement documents are in progress; this page describes current practice.