No contact form, on purpose — a plain email thread is easier for both of us when you're describing a bug or a classroom situation. Replies usually come within two or three school days; longer during grading season.
Anything on this list is welcome. Teacher feedback is what most of these games were rebuilt from.
A graph that won't render, a score that looks wrong, a game that stalls on a school Chromebook. Name the game, the browser, and roughly where it happened — that's usually enough to reproduce it.
Several games don't have written plans yet. Ask for one and it moves up the queue — requests set the order. Existing plans are on the resources page.
Using these in your room, on a shared drive, in a PD session, or across a department? Yes, and it's free. Ask if you need that in writing for an administrator.
Found a historical date, an economic definition, or an AP alignment that's off? Send it. Accuracy reports get answered first, ahead of everything else here.
A concept students reliably struggle with, that a simulation would actually help. The most useful messages describe the misconception, not the mechanic.
Reusing screenshots, linking from a course site, writing about Witsooth, or anything outside normal classroom use. Happy to talk.
Witsooth is one person — a social studies teacher with 23+ years in the classroom who built these games for their own students first. No support team, no ticket queue: replies are slower than a company's, but they come from the person who wrote the code.
Witsooth doesn't collect student data, require accounts, or run anything that needs a login. The privacy policy covers data handling in detail; the address above reaches me for anything it doesn't.