01
HASH
Paste or upload your screenplay. Your browser computes the SHA-256 digest of the text. Nothing is uploaded.
Cryptographic Notary
PROOF OF
AUTHORSHIP
Hash your screenplay. Anchor the proof. Defend the date.
Compute the fingerprint of your script in your browser. We sign that fingerprint with a server-side key and return a receipt anyone can verify. We never receive the script itself. Only the 64 characters of the hash.
01Hash
02Sign
03Verify
How it Works
FOUR STEPS, ZERO UPLOAD
The signature proves WHEN we saw the hash, not WHAT was in the file. That is the whole point.
02
SIGN
The 64-character hash is sent to our signing endpoint. We bind it to a server timestamp with an HMAC-SHA256 signature.
03
RECEIPT
You receive a receipt with the hash, the moment we saw it, the signature, and a public receipt id. Download or email it.
04
VERIFY
Anyone holding the receipt can confirm the timestamp via the open verify endpoint. No account, no login, no replay.
Browser-Local Hash
Awaiting Text
Browser-local
0 / 500,000 charsWords 0Min 200 to hash
SHA-256 Digest
Paste at least 200 characters. The hash updates as you type.
Screenplay text never leaves your browser.
Public Verifier
VERIFY A TIMESTAMP
Anyone can check a receipt. No account, no login. Paste a hash or the full tuple below.
Verifies via /api/timestamp/verify. Public endpoint.
Honest Claim
WE DO NOT STORE YOUR SCREENPLAY.
We store the hash. We store the timestamp. We store the HMAC signature. We store the optional title and notes you typed into this form. That is the entire record.
The signature proves when we saw the hash. It does not prove what was in the file. If you change a single character, the hash changes completely, and the receipt no longer corresponds. That is by design.
Phase 2 will add optional anchoring to a public ledger. Until then, the HMAC signature plus our timestamp record is the cryptographic proof.