See the writing happen.

It records what happened inside the editor: when each character was typed or deleted, when the window lost focus, when a paste was attempted, how fast text arrived. That is a strong record of how the text was produced. It is evidence for a conversation, not a verdict about a student.

It cannot see other screens, other devices, or a person reading from a phone and retyping. A student can type text from another source; the replay will then show a suspiciously steady pace with no revisions, which is worth noticing but is not proof. It also cannot tell you who was at the keyboard.

No. There is no model guessing whether text "sounds like AI". Every number on the report is something that was directly observed in the editor. We think that is the only honest basis for a conversation with a student.

Stored: the name the student types, the text they write, and the timing of each edit — nothing else. No accounts, no email addresses, no IP addresses kept with the work, no third-party scripts, no analytics trackers, no ads, and it is never used to train anything. It is deleted automatically 180 days after the assignment is created. You can also delete it yourself at any time: open your dashboard, scroll to the bottom, and use "Delete this assignment and all student work". That wipes the assignment, every session, the text, and the whole keystroke record immediately, and both links stop working. See the privacy page.

No. They open the link, type a name, and write. If the page reloads or the tablet goes to sleep, the same session continues on that device.

Be careful here: there are no accounts, so nothing can look the link up for you. Right after you create an assignment the dashboard walks you through bookmarking it, copying it, printing a card, and storing your email with it. Do one of those. The browser you created it in also keeps a list at the bottom of the create page.

Keyboard paste, right-click paste, drag-and-drop, and browser "paste" menu items are all blocked and counted. Text can still arrive through browser extensions, accessibility tools, or scripted typing; those show up as large single insertions or machine-speed bursts and are flagged.

Nothing, for one class this school year. There is no card field anywhere in the product and no trial clock. It is cheap to run: a single Cloudflare worker, no servers and no staff. If your department later wants shared dashboards, rosters, and longer retention, that would be a paid thing — leave your email below and we will tell you when it exists and what it costs. Your free class keeps working either way.

Eight write-ups, each about one thing teachers ask for: how to prove a student wrote it (what counts as evidence versus what a detector guesses), running a paste-proof writing assignment (the session end to end, no logins, Chromebooks and phones), the AI-proof in-class essay (the read-at-home, write-in-class split), and keystroke replay for student essays (every field on the report, and what is stored). Then four more: what to do when an AI detector flags an essay, Google Docs version history versus a process replay, in-class writing assignments that can't be pasted, and process-based writing assessment.

One developer, not a company, hosted on Cloudflare. Questions or requests go to a person: lehrerenterprise@gmail.com.