What a replay can and can't show

Writing Replay records how a text is entered into its editor and lets anyone play that back. It is useful evidence about how something was written. It is not proof of who wrote it, and this page explains why.

What a replay shows

What it can't show

How a replay could be faked

We'd rather you hear it from us:

So treat a replay the way you'd treat a stack of handwritten drafts: strong support for a writer's account, best read together with a conversation about the piece. If a replay is the only thing standing between a student and a penalty, talk to the student.

What the editor records, and what it doesn't

A keylogger records every key, how long it is held and the gaps between, which together can identify a person. The editor records less than that:

Even so, a replay contains the writer's text and the rhythm of their typing. Writers should share it the way they'd share a draft, with the people who asked for it.

Where your writing is stored

Your draft is saved in your own browser's storage on this device, for this site only. It stays there until you start a new piece or clear your browser's data. There is no account and no server copy, so we can't recover a lost draft. Download your replay file when you finish, and keep it like any other document.

Storage belongs to the web address you write at. If this site ever moves to a new address, drafts saved at the old one won't follow, so download your replay before you leave a piece unfinished for long.

Check for yourself that nothing is uploaded

Every page on this site carries a Content Security Policy, an instruction your browser enforces. Ours tells the browser to load scripts only from this site and to refuse every network request the page tries to make. It reads:

default-src 'none'; script-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; connect-src 'none'; form-action 'none'; base-uri 'none'

To see it at work, open your browser's developer tools (F12, or Cmd+Option+I on a Mac), choose the Network tab, and write something in the editor. Nothing is sent. The only requests are the page's own files loading, before you type anything. The source code is public under the MIT license.

No accounts, no cookies, no analytics. Your writing and replays stay in your browser.

Replay links

A replay link carries the whole recording, compressed, after the # in the address. Browsers don't send that part to any server, including ours. Anyone who has the link can watch the replay, so share it like the file itself.

Contact

Found a bug, or a browser where recording goes wrong? Open an issue on GitHub. Please don't paste writing you want kept private into an issue: issues are public.