Detectors can't tell.
Your keystrokes can.
AI detectors flag real writers constantly — and "check the version history" means asking a teacher to scrub through hours of edits. TypeProof records how you wrote: every insertion, deletion, and pause, replayable in seconds and exportable as verifiable proof.
Runs in your browser. Nothing is uploaded; your draft never leaves this device.
The editor
Type below — recording is already on. Come back later; the draft and its history persist on this device.
Why "process" beats "detection"
Detectors guess
They score style. Real writers — especially non-native speakers and careful drafters — get flagged constantly.
History doesn't
Two thousand small edits over three hours is how humans write. A pasted essay is one event. The difference is visible.
You own the evidence
Proof file is a JSON with the full edit log and a SHA-256 fingerprint. Share it, verify it, keep it.
Honest limits
Couldn't someone fake a history?
Yes — a motivated person could simulate keystrokes. TypeProof raises the cost of faking from zero to "significant effort," and flags pastes. It's evidence for a human reviewer, not an infallible oracle. That's the honest version.
Where does my writing go?
Nowhere. It's stored in this browser's local storage on this device. No account, no server, no upload — which also means clearing browser data deletes it. Export the proof file to keep it.
Does my school/employer have to install anything?
No. You send them the proof file; verification only needs the replay. For classrooms or institutions we can set up a shared verifier — that's what the form below is for.