Method v1
What HumanTyped verifies — and what it does not.
HumanTyped records evidence from one controlled editor session. The claim is intentionally narrow: this receipt describes how the text changed here.
The recorded evidence
Every accepted edit becomes an ordered operation: where text was inserted or removed, when the edit occurred, and where the selection ended. Paste and drop events are rejected before they change the editor.
Server reconstruction
On sealing, the server freezes the journal, replays every operation from an empty document, and compares the resulting SHA-256 digest to the browser's final text. A missing or altered operation prevents the receipt from being issued.
The evidence score
The 0–100 score summarizes duration, revisions, cadence variation, journal continuity, and blocked transfer attempts. The private feature vector is never published and is not reused as a biometric signature.
Attached media
Photos, GIFs, and videos are stored separately from the typing journal. The receipt seals each file's SHA-256 hash, type, size, and alternative text so the attachment set cannot be changed silently. This proves which files were attached, not whether a person or an AI created them.
Process evidence or AI detection?
The two methods answer different questions. See the practical comparison of final-text analysis and writing process verification.
Hard limits
HumanTyped cannot prove which person used the keyboard, observe a second device, detect memorized or dictated text, or guarantee that no external AI assistance influenced the author. A receipt is evidence of process, not a certificate of human identity.